rfc-5871

IANA Allocation Guidelines for the IPv6 Routing Header

J. Arkko, S. Bradner

date2010-05 streamIETF areaint wg6man statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc5871 doi10.17487/RFC5871

This document specifies the IANA guidelines for allocating new values for the Routing Type field in the IPv6 Routing Header. [STANDARDS TRACK]

updates

rfc-2460 — Internet Protocol, Version 6 (IPv6) Specification

Extracted elements (5)

design-rationale §1

Prior to this document, no IANA guidance existed for allocating Routing Type values in the IPv6 Routing Header, creating a gap that this document fills by establishing IETF Review or IESG Approval as the required allocation policy.

ip, registry

interoperability-note §2

Two experimental Routing Type values, 253 and 254, are already available for use per RFC 4727 and are not subject to the new allocation process.

ip, registry

normative-requirement §2 REQUIRED

New Routing Type values in the IPv6 Routing Header MUST be allocated through IETF Review or IESG Approval as defined in RFC 5226.

registry, ip

registry §2

The IPv6 Routing Header Routing Type registry is governed by this document. New Routing Type values are allocated through IETF Review or IESG Approval per RFC 5226.

registry, ip

security-consideration §3

This specification does not change the security properties of the Routing Header. However, past experience (notably RFC 5095 deprecating Type 0 Routing Headers) shows that it is easy to design routing headers with significant security problems.

security, ip