| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 21:19:36 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=FWh0cHzo_tOUleZtpA24GAA6utrsAQsEXTI4cqpoSTY-1760131176-1.0.1.1-4zwYPayLxi8ukHeA0InXL5yH5GuIRzXs_b_v1hmHYiultPpxuVpl5fJxwfwmeeyJsCYiyuwz9OKKqi8L159da_CP9eoYxw4s3DODuUGc9Lw; path=/; expires=Fri, 10-Oct-25 21:49:36 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c928248a10c177-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6410 » RFC Editor
Search RFCs
- File formats:
- Status:
- BEST CURRENT PRACTICE
- Updates:
- RFC 2026
- Authors:
- R. Housley
D. Crocker
E. Burger - Stream:
- IETF
- Source:
- NON WORKING GROUP
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6410
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6410
Abstract
This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an Internet Best Current Practice.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us