V6OPS WG S. Gundavelli Internet-Draft Cisco Updates: 5213 (if approved) December 11, 2011 Intended status: Standards Track Expires: June 13, 2012 Reserved IPv6 Interface Identifier for Proxy Mobile IPv6 draft-gundavelli-v6ops-pmipv6-address-reservations-04.txt Abstract Proxy Mobile IPv6 [RFC5213] requires all the mobile access gateways to use a fixed link-local and link-layer addresses on any of its access links that it shares with the mobile nodes. This was intended to ensure a mobile node does not detect any change with respect to its layer-3 attachment even after it roams from one mobile access gateway to another. In the absence of any reserved addresses for this use, it requires coordination across vendors and the manual configuration of these addresses on all the mobility elements in a Proxy Mobile IPv6 domain. This document attempts to simplify this operational requirement by making reservation for special addresses that can be used for this purpose and it also updates RFC 5213. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on June 13, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents Gundavelli Expires June 13, 2012 [Page 1] Internet-Draft Reserved IPv6 IID for PMIPv6 December 2011 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . . 4 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Normative References . . . . . . . . . . . . . . . . . . . 5 6.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Gundavelli Expires June 13, 2012 [Page 2] Internet-Draft Reserved IPv6 IID for PMIPv6 December 2011 1. Introduction Proxy Mobile IPv6 [RFC5213] is a network-based mobility management protocol that enables IP mobility support for a mobile node without requiring its participation in any mobility-related signaling. The mobility elements in the network ensure that the mobile node does not detect any change with respect to its layer-3 attachment even after it roams from one mobile access gateway to another and changes its point of attachment in the network. All the mobile access gateways in a Proxy Mobile IPv6 use a fixed link-local address and a fixed link-layer address on any of its access links that they share with the mobile nodes. This essentially ensures a mobile node after performing an handoff does not detect any change with respect to the IP network configuration. Although the base Proxy Mobile IPv6 specification [RFC5213] requires the use of a fixed link-local and a fixed link-layer address, it did not reserve any specific addresses for this purpose and this is proving to be a operational challenge in deployments involving multi- vendor equipment. To address this problem, this specification makes the following two reservations. 1. This specification reserves one single Ethernet unicast address, IANA-TBD1, for the use of Proxy Mobile IPv6. This reserved link- layer address can by used by the mobile access gateway in a Proxy Mobile IPv6 domain, on all of the access links that it shares with the mobile nodes. This address will be used in all packet communication with the mobile node on the access links. Considerations from [RFC5342] apply with respect to the use of Ethernet parameters in IETF protocols. This address is allocated from the registry, "IANA Ethernet Address block - Unicast Use". 2. This specification reserves an IPv6 interface identifier, IANA- TBD2. This identifier is an EUI-64 based interface identifier generated based on the hardware address, IANA-TBD1, reserved by this specification. This EUI-64 based interface identifier is generated as per the rules specified in [RFC4291]. The reserved IPv6 interface identifier SHOULD be used by all the mobile access gateways in a Proxy Mobile IPv6 domain on all of the access links that it shares with the mobile nodes. Specifically, the mobile access gateway can use this reserved IPv6 interface identifier for generating the link-local address that it uses in the Neighbor Discovery [RFC4861] related communication with the mobile node. Gundavelli Expires June 13, 2012 [Page 3] Internet-Draft Reserved IPv6 IID for PMIPv6 December 2011 2. Conventions & Terminology 2.1. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2.2. Terminology All the mobility related terms used in this document are to be interpreted as defined in the base Proxy Mobile IPv6 specifications [RFC5213], [RFC5844]. All the IPv6 addressing related terminology is to be interpreted as specified in [RFC4291]. 3. IANA Considerations This document requires the following two IANA actions. o Action-1: This specification reserves a IANA Ethernet unicast address (IANA-TBD1) for Proxy Mobile IPv6. This address needs to be reserved from the block. "IANA Ethernet Address block - Unicast Use". o Action-2: This specification reserves an IPv6 interface identifier (IANA-TBD2) for Proxy Mobile IPv6 [RFC5213]. This fixed interface identifier is an EUI-64 based interface identifier generated based on the Ethernet unicast address, IANA-TBD1, reserved by this specification. 4. Security Considerations All the security considerations specified in [RFC5213], and [RFC5844] continue to apply to the mobility elements in a Proxy Mobile IPv6 domain, when enabled to conform to this specification. Specifically, the issues related to the use of fixed link-local and link-layer address documented in section 6.9.3 of the base Proxy Mobile IPv6 specification are equally relevant here. In some sense, the reservations made in this specification results in the use of the same set of link-local and link-layer address values beyond a single Proxy Mobile IPv6 domain, thereby expanding the scope of the existing problem related to asserting ownership on the configured addresses from a single domain to multi-domain. Future work may be needed to address these issues. Gundavelli Expires June 13, 2012 [Page 4] Internet-Draft Reserved IPv6 IID for PMIPv6 December 2011 5. Acknowledgements The author would like to thank Jari Arkko and Dave Thaler for all the discussions around the use of fixed link-local and link-layer address, during the standardization of Proxy Mobile IPv6 [RFC5213]. The authors would also like to thank Tero Kivinen, Donald Eastlake 3rd, Stephen Farrell, Suresh Krishnan, Margaret Wasserman, Thomas Narten and Eric Voit for their reviews and participations in the discussions related to this document. 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. 6.2. Informative References [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, September 2007. [RFC5342] Eastlake, D., "IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters", BCP 141, RFC 5342, September 2008. [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy Mobile IPv6", RFC 5844, May 2010. Author's Address Sri Gundavelli Cisco 170 West Tasman Drive San Jose, CA 95134 USA Email: sgundave@cisco.com Gundavelli Expires June 13, 2012 [Page 5]