Reserved IPv6 Interface Identifier for Proxy Mobile IPv6
updates
- rfc-5213 — Proxy Mobile IPv6
Extracted elements (8)
The base PMIPv6 specification (RFC 5213) required use of fixed link-local and link-layer addresses but did not reserve specific values, creating operational challenges in multi-vendor deployments requiring manual coordination. This specification addresses that by making explicit reservations to simplify deployment.
Considerations from RFC 5342 (IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters) apply with respect to the use of Ethernet parameters in IETF protocols when using the reserved link-layer address.
All mobile access gateways in a Proxy Mobile IPv6 domain SHOULD use the reserved IPv6 interface identifier 0200:5EFF:FE00:5213 on all access links shared with mobile nodes. The protocol configuration variable FixedMAGLinkLocalAddressOnAllAccessLinks SHOULD be set to the link-local address generated using this reserved interface identifier.
The reserved Ethernet unicast address for Proxy Mobile IPv6 is 00-00-5E-00-52-13, allocated from the IANA Ethernet Address Block - Unicast Use registry. It is used as a fixed link-layer address on MAG access links.
The reserved IPv6 interface identifier for Proxy Mobile IPv6 is 0200:5EFF:FE00:5213. It is a modified EUI-64 interface identifier generated from the allocated Ethernet unicast address 00-00-5E-00-52-13 per the procedure in RFC 4291 Appendix A.
This specification reserves Ethernet unicast address 00-00-5E-00-52-13 for Proxy Mobile IPv6 in the IANA registry 'IANA Ethernet Address Block - Unicast Use'.
This specification reserves IPv6 interface identifier 0200:5EFF:FE00:5213 for Proxy Mobile IPv6 in the IANA registry 'Reserved IPv6 Interface Identifiers' (RFC 5453).
The security considerations from RFC 5213 and RFC 5844 continue to apply. The reservations made here extend the use of the same fixed link-local and link-layer addresses beyond a single PMIPv6 domain, expanding the scope of the existing problem of asserting ownership of configured addresses from a single domain to a multi-domain environment. Future work may be needed to address these issues.