CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 09:56:16 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=3YXAlp1r.cFRiyGhsuR.zELTzqQFqTe4P7PHbh37md0-1760176576-1.0.1.1-PjUUy1eq73utvqyASYtvN3l7q_c8clAoOtNvu0en_J4J65K4T3Xmd92H.tFW10yDzl8tPzRCBHDeFvxPPfEXU3.rTv1DkHuQxro5nnh35Tc; path=/; expires=Sat, 11-Oct-25 10:26:16 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd7c8b3e62af3d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5871 » RFC Editor
Search RFCs
RFC 5871
IANA Allocation Guidelines for the IPv6 Routing Header, May 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 2460
- Authors:
- J. Arkko
S. Bradner - Stream:
- IETF
- Source:
- 6man (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5871
Discuss this RFC: Send questions or comments to the mailing list ipv6@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5871
Abstract
This document specifies the IANA guidelines for allocating new values for the Routing Type field in the IPv6 Routing Header. [STANDARDS TRACK]
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