NETLMM WGNetwork Working Group S.Gundavelli (Editor) Internet-DraftGundavelli, Ed. Request for Comments: 5213 K. LeungIntended status:Category: Standards Track CiscoExpires: December 1, 2008V. Devarapalli Wichorus K. Chowdhury Starent Networks B. Patil Nokia Siemens NetworksMay 30,June 2008 Proxy Mobile IPv6draft-ietf-netlmm-proxymip6-18.txtStatus ofthisThis MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents ofThis document specifies an Internet standards track protocol for the InternetEngineering Task Force (IETF), its areas,community, andits working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents validrequests discussion and suggestions fora maximumimprovements. Please refer to the current edition ofsix monthsthe "Internet Official Protocol Standards" (STD 1) for the standardization state andmay 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." The liststatus ofcurrent Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The listthis protocol. Distribution ofInternet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on December 1, 2008. Copyright Notice Copyright (C) The IETF Trust (2008).this memo is unlimited. Abstract Network-based mobility management enables IP mobility for a host without requiring its participation in anymobility relatedmobility-related signaling. TheNetworknetwork is responsible for managing IP mobility on behalf of the host. The mobility entities in the network are responsible for tracking the movements of the host and initiating the required mobility signaling on its behalf. This specification describes a network-based mobility management protocol and is referred to as Proxy Mobile IPv6. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions&and Terminology . . . . . . . . . . . . . . . . .. 45 2.1. ConventionsusedUsed inthis documentThis Document . . . . . . . . . . . . 5 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 3. Proxy Mobile IPv6 Protocol Overview . . . . . . . . . . . . . 9 4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 15 4.1. Peer Authorization Database (PAD) Example Entries . . . . 16 4.2. Security Policy Database (SPD) Example Entries . . . . . . 17 5. Local Mobility Anchor Operation . . . . . . . . . . . . . . .1817 5.1. Extensions to Binding Cache Entry Data Structure . . . . . 18 5.2. Supported Home Network Prefix Models . . . . . . . . . . . 19 5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 20 5.3.1. Processing Proxy Binding Updates . . . . . . . . . . . 20 5.3.2. Initial Binding Registration (New Mobility Session) . 22 5.3.3. Binding Lifetime Extension (Nohandoff)Handoff) . . . . . . . 23 5.3.4. Binding Lifetime Extension (Afterhandoff)Handoff) . . . . . .2423 5.3.5. Binding De-Registration . . . . . . . . . . . . . . .2524 5.3.6. Constructing the Proxy Binding Acknowledgement Message . . . . . . . . . . . . . . . . . . . . . . . 25 5.4. Multihoming Support . . . . . . . . . . . . . . . . . . .2827 5.4.1. Binding Cacheentry lookup considerationsEntry Lookup Considerations . . . . . . 28 5.5. Timestamp Option for Message Ordering . . . . . . . . . .3433 5.6. Routing Considerations . . . . . . . . . . . . . . . . . .3736 5.6.1. Bi-Directional Tunnel Management . . . . . . . . . . .3736 5.6.2. Forwarding Considerations . . . . . . . . . . . . . .3837 5.6.3.ECNExplicit Congestion Notification (ECN) Considerations for Proxy Mobile IPv6 Tunnels . . .39. . 38 5.7. Local Mobility Anchor Address Discovery . . . . . . . . .4039 5.8. Mobile Prefix Discovery Considerations . . . . . . . . . .4039 5.9. Route Optimization Considerations . . . . . . . . . . . .4139 6. Mobile Access Gateway Operation . . . . . . . . . . . . . . .4140 6.1. Extensions to Binding Update List Entry Data Structure . .4240 6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . .4341 6.3. Supported Access Link Types . . . . . . . . . . . . . . .4442 6.4. Supported Address Configuration Modes . . . . . . . . . .4443 6.5. Access Authentication&and Mobile Node Identification . . .. 4543 6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . .4544 6.7. Home Network Emulation . . . . . . . . . . . . . . . . . .4644 6.8. Link-Local and Global Address Uniqueness . . . . . . . . .4645 6.9. Signaling Considerations . . . . . . . . . . . . . . . . .4846 6.9.1. Binding Registrations . . . . . . . . . . . . . . . .4846 6.9.2. Router Solicitation Messages . . . . . . . . . . . . .5655 6.9.3. Default-Router . . . . . . . . . . . . . . . . . . . .5756 6.9.4. Retransmissions and Rate Limiting . . . . . . . . . .5856 6.9.5. Path MTU Discovery . . . . . . . . . . . . . . . . . .5957 6.10. Routing Considerations . . . . . . . . . . . . . . . . . .6059 6.10.1. Transport Network . . . . . . . . . . . . . . . . . .6059 6.10.2. Tunneling&and Encapsulation Modes . . . . . . . . . .. 6059 6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . .6160 6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . .6260 6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . .6261 6.11. SupportingDHCP basedDHCP-Based Address Configuration on the Access Link . . . . . . . . . . . . . . . . . . . . . . .6462 6.12. Home Network Prefix Renumbering . . . . . . . . . . . . .6664 6.13. Mobile Node Detachment Detection and Resource Cleanup . .6665 6.14. Allowingnetwork accessNetwork Access tootherOther IPv6nodesNodes . . . . . . .6765 7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . .6766 7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . .6766 7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . .6867 8. Message Formats . . . . . . . . . . . . . . . . . . . . . . .6968 8.1. Proxy Binding Update Message . . . . . . . . . . . . . . .6968 8.2. Proxy Binding Acknowledgement Message . . . . . . . . . .7169 8.3. Home Network Prefix Option . . . . . . . . . . . . . . . .7271 8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . .7372 8.5. Access Technology Type Option . . . . . . . . . . . . . .7473 8.6. Mobile Node Link-layer Identifier Option . . . . . . . . .7675 8.7.Link-localLink-Local Address Option . . . . . . . . . . . . . . . .7776 8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . .7876 8.9. Status Values . . . . . . . . . . . . . . . . . . . . . .7877 9. Protocol Configuration Variables . . . . . . . . . . . . . . .8079 9.1. Local Mobility Anchor - Configuration Variables . . . . .8079 9.2. Mobile Access Gateway - Configuration Variables . . . . .8180 9.3. Proxy Mobile IPv6 Domain - Configuration Variables . . . .8281 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .8381 11. Security Considerations . . . . . . . . . . . . . . . . . . .8482 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .8483 13. References . . . . . . . . . . . . . . . . . . . . . . . . . .8584 13.1. Normative References . . . . . . . . . . . . . . . . . . .8584 13.2. Informative References . . . . . . . . . . . . . . . . . .8685 Appendix A. Proxy Mobile IPv6interactionsInteractions with AAA Infrastructure . . . . . . . . . . . . . . . . . . . 87 Appendix B. Routing State . . . . . . . . . . . . . . . . . . . .88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 89 Intellectual Property and Copyright Statements . . . . . . . . . . 9187 1. Introduction IP mobility for IPv6 hosts is specified in Mobile IPv6 [RFC3775]. Mobile IPv6 requires client functionality in the IPv6 stack of a mobile node. Exchange of signaling messages between the mobile node and home agent enables the creation and maintenance of a binding between the mobile node's home address and itscare-of-address.Care-of Address. Mobility as specified in [RFC3775] requires the IP host to send IP mobility management signaling messages to the home agent, which is located in the network. Network-based mobility is another approach to solving the IP mobility challenge. It is possible to support mobility for IPv6 nodes without host involvement by extending Mobile IPv6 [RFC3775] signaling messages between a network node and a home agent. This approach to supporting mobility does not require the mobile node to be involved in the exchange of signaling messages between itself and the home agent. A proxy mobility agent in the network performs the signaling with the home agent and does the mobility management on behalf of the mobile node attached to the network. Because of the use and extension of Mobile IPv6 signaling and home agent functionality, this protocol is referred to as Proxy Mobile IPv6 (PMIPv6). Network deploymentswhichthat are designed to support mobility would be agnostic to the capability in the IPv6 stack of the nodeswhichthat it serves. IP mobility for nodeswhichthat have mobile IP client functionality in the IPv6 stack as well as those nodeswhichthat do not, would be supported by enabling Proxy Mobile IPv6 protocol functionality in the network. The advantages of developing anetwork basednetwork-based mobility protocol based on Mobile IPv6 are: o Reuse of home agent functionality and the messages/format used in mobility signaling. Mobile IPv6 is a mature protocol with several implementations that have undergone interoperability testing. o A common home agent would serve as the mobility agent for all types of IPv6 nodes. The problem statement and the need for anetwork basednetwork-based mobility protocol solution has been documented in [RFC4830]. Proxy Mobile IPv6 is a solution that addresses these issues and requirements. 2. Conventions&and Terminology 2.1. ConventionsusedUsed inthis documentThis Document 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 generalmobility relatedmobility-related terms used in this document are to be interpreted as defined in the Mobile IPv6 base specification[RFC 3775].[RFC3775]. This document adopts the terms, Local Mobility Anchor (LMA) and Mobile Access Gateway (MAG) from the NETLMM Goals document[RFC 4831].[RFC4831]. This document also provides the followingcontext specificcontext-specific explanation to the following terms used in this document. Proxy Mobile IPv6 Domain (PMIPv6-Domain) Proxy Mobile IPv6 domain refers to the network where the mobility management of a mobile node is handled using the Proxy Mobile IPv6 protocol as defined in this specification. The Proxy Mobile IPv6 domain includes local mobility anchors and mobile access gateways between which security associations can be set up and authorization for sending Proxy Binding Updates on behalf of the mobile nodes can be ensured. Local Mobility Anchor (LMA) Local Mobility Anchor is the home agent for the mobile node in a Proxy Mobile IPv6 domain. It is the topological anchor point for the mobile node's home network prefix(es) and is the entity that manages the mobile node's binding state. The local mobility anchor has the functional capabilities of a home agent as defined in Mobile IPv6 base specification [RFC3775] with the additional capabilities required for supporting Proxy Mobile IPv6 protocol as defined in this specification. Mobile Access Gateway (MAG) Mobile Access Gateway is a function on an access router that manages themobility relatedmobility-related signaling for a mobile node that is attached to its access link. It is responsible for tracking the mobile node's movements to and from the access link and for signaling the mobile node's local mobility anchor. Mobile Node (MN) Throughout this document, the term mobile node is used to refer to an IP host or router whose mobility is managed by the network. The mobile node may be an IPv4-only node, IPv6-onlynodenode, or a dual-stack node and is not required to participate in any IP mobility related signaling for achieving mobility for an IP address that is obtained in that Proxy Mobile IPv6 domain. LMA Address (LMAA) The global address that is configured on the interface of the local mobility anchor and is the transport endpoint of the bi- directional tunnel established between the local mobility anchor and the mobile access gateway. This is the address towherewhich the mobile access gateway sends the Proxy Binding Update messages. When supporting IPv4 traversal, i.e., when the network between the local mobility anchor and the mobile access gateway is an IPv4 network, this address will be an IPv4 address and will be referred to as IPv4-LMAA, as specified in[ID-IPV4-PMIP6].[IPV4-PMIP6]. Proxy Care-of Address (Proxy-CoA) Proxy-CoA is the global address configured on the egress interface of the mobile access gateway and is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. The local mobility anchor views this address as the Care-of Address of the mobile node and registers it in the Binding Cache entry for that mobile node. When the transport network between the mobile access gateway and the local mobility anchor is an IPv4 network and if thecare-of addressCare-of Address that is registered at the local mobility anchor is an IPv4 address, the term, IPv4- Proxy-CoA is used, as specified in[ID-IPV4-PMIP6].[IPV4-PMIP6]. Mobile Node's Home Network Prefix (MN-HNP) The MN-HNP is a prefix assigned to the link between the mobile node and the mobile access gateway. More than one prefix can be assigned to the link between the mobile node and the mobile access gateway, in which case, all of the assigned prefixes are managed as a set associated with a mobility session. The mobile node configures its interface with one or more addresses from its home network prefix(es). If the mobile node connects to the Proxy Mobile IPv6 domain through multiple interfaces, simultaneously, each of the attached interfaces will be assigned a unique set of home networkprefixesprefixes, and all the prefixes assigned to a given interface of a mobile node will be managed under one mobility session.Ex: HomeFor example, home network prefixesP1,P1 and P2 assigned to interface I1 will be managed under one mobility session and prefixes P3, P4, and P5 assigned to interface I2 of the mobile node will be managed under a different mobility session. Additionally, in some configurations the assigned prefix can be of 128-bit prefix length. Mobile Node's Home Address (MN-HoA) MN-HoA is an address from a mobile node's home network prefix. The mobile node will be able to use this address as long as it is attached to the access network that is in the scope of that Proxy Mobile IPv6 domain. If the mobile node uses more than one address from its home network prefix(es), any one of these addresses is referred to as mobile node's home address. Unlike in Mobile IPv6 where the home agent is aware of the home address of the mobile node, in Proxy Mobile IPv6, the mobility entities are only aware of the mobile node's home network prefix(es) and are not always aware of the exact address(es) that the mobile node configured on its interface from its home network prefix(es). However, in some configurations and based on the enabled address configuration modes on the access link, the mobility entities in the network can be certain about the exact address(es) configured by the mobile node. Mobile Node's Home Link This is the link on which the mobile node obtained itsLayer-3layer-3 address configuration for the attached interface after it moved into that Proxy Mobile IPv6 domain. This is the link that conceptually follows the mobile node. The network will ensure the mobile node always sees this link with respect to the layer-3 network configuration, on any access link that it attaches to in that Proxy Mobile IPv6 domain. Multihomed Mobile Node A mobile node that connects to the same Proxy Mobile IPv6 domain through more than one interface and uses these interfaces simultaneously is referred to as a multihomed mobile node. Mobile Node Identifier (MN-Identifier) The identity of a mobile node in the Proxy Mobile IPv6 domain. This is the stable identifier of a mobile node that the mobility entities in a Proxy Mobile IPv6 domain can always acquire and useitfor predictably identifying a mobile node. This is typically an identifier such as a Network Access Identifier (NAI) [RFC4282] or other identifier such as a Media Access Control (MAC) address. Mobile Node Link-layer Identifier (MN-LL-Identifier) An identifier that identifies the attached interface of a mobile node. For those interfaces that have a link-layer identifier, this identifier can be based on that. The link-layeridentifieridentifier, in somecasescases, is generated by the mobile node and conveyed to the mobile access gateway. This identifier of the attached interface must bestablestable, as seen by any of the mobile access gateways in a given Proxy Mobile IPv6 domain. In some other cases, there might not be any link-layer identifier associated with the mobile node's interface. An identifier value of ALL_ZERO is not considered a valid identifier and cannot be used as an interface identifier. Policy Profile Policy Profile is an abstract term for referring to a set of configuration parameters that are configured for a given mobile node. The mobility entities in the Proxy Mobile IPv6 domain require access to these parameters for providing the mobility management to a given mobile node. The specific details on how the network entities obtain this policy profile is outside the scope of this document. Proxy Binding Update (PBU) A request message sent by a mobile access gateway to a mobile node's local mobility anchor for establishing a binding between the mobile node's home network prefix(es) assigned to a given interface of a mobile node and its currentcare-of addressCare-of Address (Proxy- CoA). Proxy Binding Acknowledgement (PBA) A reply message sent by a local mobility anchor in response to a Proxy Binding Update message that it received from a mobile access gateway. Per-MN-Prefix&and Shared-Prefix Models Theterm,term Per-MN-Prefixmodel,model is used to refer to an addressing model where there is a unique network prefix or prefixes assigned for each node. Theterm,term Shared-Prefixmodel,model is used to refer to an addressing model where the prefix(es) are shared by more than one node. This specification supports the Per-MN-Prefix model and does not support the Shared-Prefix model. Mobility Session In the context of Proxy Mobile IPv6 specification, the term mobility session refers to the creation or existence of state associated with the mobile node's mobility binding on the local mobility anchor and on the serving mobile access gateway. DHCP Throughout this document, the acronym DHCP refers to DHCP for IPv6, as defined in [RFC3315]. ALL_ZERO&and NON_ZERO Protocol message fields initialized with value 0 in each byte of the field.Ex: AnFor example, an 8-byte link-layer identifier field with the value set to 0 in each of the 8 bytes, or an IPv6 address with the value 0 in all of the 16 bytes. Conversely, the term NON_ZERO is used to refer to any value other than an ALL_ZERO value. 3. Proxy Mobile IPv6 Protocol Overview This specification describes a network-based mobility management protocol. It is called Proxy Mobile IPv6 and is based on Mobile IPv6 [RFC3775]. Proxy Mobile IPv6 protocol is intended for providing network-based IP mobility management support to a mobile node, without requiring the participation of the mobile node in any IP mobility related signaling. The mobility entities in the network will track the mobile node's movements and will initiate the mobility signaling and set up the required routing state. The core functional entities in the NETLMM infrastructure are the Local Mobility Anchor (LMA) and the Mobile Access Gateway (MAG). The local mobility anchor is responsible for maintaining the mobile node's reachability state and is the topological anchor point for the mobile node's home network prefix(es). The mobile access gateway is the entity that performs the mobility management on behalf of a mobilenodenode, and it resides on the access link where the mobile node is anchored. The mobile access gateway is responsible for detecting the mobile node's movements to and from the access link and for initiating binding registrations to the mobile node's local mobility anchor. There can be multiple local mobility anchors in a Proxy Mobile IPv6 domain each serving a different group of mobile nodes. The architecture of a Proxy Mobile IPv6 domain is shown in Figure 1. +----+ +----+ |LMA1| |LMA2| +----+ +----+ LMAA1 -> | | <-- LMAA2 | | \\ //\\ \\ // \\ \\ // \\ +---\\------------- //------\\----+ ( \\ IPv4/IPv6 // \\ ) ( \\ Network // \\ ) +------\\--------//------------\\-+ \\ // \\ \\ // \\ \\ // \\ Proxy-CoA1--> | | <-- Proxy-CoA2 +----+ +----+ |MAG1|-----{MN2} |MAG2| +----+ | +----+ | | | MN-HNP1 --> | MN-HNP2 | <-- MN-HNP3, MN-HNP4 {MN1} {MN3} Figure 1: Proxy Mobile IPv6 Domain Once a mobile node enters a Proxy Mobile IPv6 domain and attaches to an access link, the mobile access gateway on that access link, after identifying the mobile node and acquiring its identity, will determine if the mobile node is authorized for the network-based mobility management service. If the network determines that the network-based mobility management service needs to be offered to that mobile node, the network will ensure that the mobile node using any of the address configuration mechanisms permitted by the network will be able to obtain the address configuration on the connected interface and move anywhere in that Proxy Mobile IPv6 domain. The obtained address configuration includes the address(es) from its home network prefix(es), the default-router address on thelinklink, and other related configuration parameters. From the perspective of each mobile node, the entire Proxy Mobile IPv6 domain appears as a single link, the network ensures that the mobile node does not detect any change with respect to its layer-3 attachment even after changing its point of attachment in the network. The mobile node may be an IPv4-only node, IPv6-onlynodenode, or a dual IPv4/IPv6 node. Based on what is enabled in the network for that mobile node, the mobile node will be able to obtain an IPv4,IPv6IPv6, or dual IPv4/IPv6addressesaddress and move anywhere in that Proxy Mobile IPv6 domain.HoweverHowever, this specification only supports IPv6 address mobility and when the transport network is an IPv6 network. The support for IPv4 addressing or an IPv4 transport network is specified in the companion document[ID-IPV4-PMIP6].[IPV4-PMIP6]. If the mobile node connects to the Proxy Mobile IPv6 domain through multiple interfaces and over multiple access networks, the network will allocate a unique set of home network prefixes for each of the connected interfaces. The mobile node will be able to configure address(es) on those interfaces from the respective home network prefix(es). However, if the mobile node performsana handoff by moving its address configuration from one interface to theotherother, and if the local mobility anchor receives a handoff hint from the serving mobile access gateway about the same, the local mobility anchor will assign the same home network prefix(es) that it previously assigned prior to the handoff. The mobile node will also be able to performana handoff by changing its point of attachment from one mobile access gateway to a different mobile access gateway using the same interface and will be able to retain the address configuration on the attached interface. +-----+ +-----+ +-----+ | MN | | MAG | | LMA | +-----+ +-----+ +-----+ | | | MN Attached | | | | | | MN Attached Event from MN/Network | | (Acquire MN-Id and Profile) | | | | |--- Rtr Sol --------->| | | | | | |--- PBU ------------->| | | | | | Accept PBU | | (Allocate MN-HNP(s), Setup BCE and Tunnel) | | | | |<------------- PBA ---| | | | | Accept PBA | | (Setup Tunnel and Routing) | | | | | |==== Bi-Dir Tunnel ===| | | | |<--------- Rtr Adv ---| | | | | IP Address | | Configuration | | | | | Figure 2: Mobile Node Attachment - Signaling Call Flow Figure 2 shows the signaling call flow when the mobile node enters the Proxy Mobile IPv6 domain. The Router Solicitation message from the mobile node may arrive at any time after the mobile node's attachment and has no strict ordering relation with the other messages in the call flow. For updating the local mobility anchor about the current location of the mobile node, the mobile access gateway sends a Proxy Binding Update message to the mobile node's local mobility anchor. Upon accepting this Proxy Binding Update message, the local mobility anchor sends a Proxy Binding Acknowledgement message including the mobile node's home network prefix(es). It also creates the Binding Cache entry and sets up its endpoint of the bi-directional tunnel to the mobile access gateway. The mobile access gateway on receiving the Proxy Binding Acknowledgement message sets up its endpoint of the bi-directional tunnel to the local mobility anchor and also sets up the forwarding for the mobile node's traffic. At thispointpoint, the mobile access gateway will have all the required information for emulating the mobile node's home link. It sends Router Advertisement messages to the mobile node on the access link advertising the mobile node's home network prefix(es) as the hostedon-link-prefix(es).on-link prefix(es). The mobilenodenode, on receiving these Router Advertisement messages on the accesslinklink, will attempt to configure its interfaceeitherusing either stateful or stateless address configuration modes, based on the modes that are permitted on that access link as indicated in Router Advertisement messages. At the end of a successful address configuration procedure, the mobile node will end up with one or more addresses from its home network prefix(es). Once the address configuration is complete, the mobile node has one or more valid addresses from its home network prefix(es) at the current point of attachment. The serving mobile access gateway and the local mobility anchor also have proper routing states for handling the traffic sent to and from the mobile node using any one or more of the addresses from its home network prefix(es). The local mobility anchor, being the topological anchor point for the mobile node's home network prefix(es), receives any packets that are sent to the mobile node by any node in or outside the Proxy Mobile IPv6 domain. The local mobility anchor forwards these received packets to the mobile access gateway through the bi-directional tunnel. The mobile access gateway on other end of the tunnel, after receiving the packet, removes the outer header and forwards the packet on the access link to the mobile node. However, in somecasescases, the traffic sent from a correspondent node that is locally connected to the mobile access gateway may not be received by the local mobility anchor and may be routed locally by the mobile access gateway(Refer(refer to Section 6.10.3). The mobile access gateway acts as the default router on the point-to- point link shared with the mobile node. Any packet that the mobile node sends to any correspondent node will be received by the mobile access gateway and will be sent to its local mobility anchor through the bi-directional tunnel. The local mobility anchor on the other end of the tunnel, after receiving the packet, removes the outer header and routes the packet to the destination.HoweverHowever, in somecasescases, the traffic sent to a correspondent node that is locally connected to the mobile access gateway may be locally routed by the mobile access gateway(Refer(refer to Section 6.10.3). +-----+ +-----+ +-----+ +-----+ | MN | |p-MAG| | LMA | |n-MAG| +-----+ +-----+ +-----+ +-----+ | | | | | |==Bi-Dir Tunnel=| | MN Detached | | | | MN Detached Event | | | | | | | |-- DeReg PBU -->| | | | | | | | Accept PBU | | | (Start MinDelayBeforeBCEDelete Timer) | | | | | |<-------- PBA --| | | | | | MN Attached | | | | | | MN Attached event received | | | from MN or from network | | | (Acquire MN-Id and Profile) | | | | |--- Rtr Sol ------------------------------------->| .... Registration steps as infigFig. 2. .... | | |==Bi-Dir Tunnel=| | | | | |<------------------------------------ Rtr Adv ----| | | | | MN retains HoA/HNP(s) | | | | Figure 3: Mobile Node Handoff - Signaling Call Flow Figure 3 shows the signaling call flow for the mobile node's handoff from the previously attached mobile access gateway (p-MAG) to the newly attached mobile access gateway (n-MAG). This call flowreflectsonly reflects a specific message ordering, it is possible the registration message from the n-MAG may arrive before the de-registration message from the p-MAG arrives. After obtaining the initial address configuration in the Proxy Mobile IPv6 domain, if the mobile node changes its point of attachment, the mobile access gateway on the previous link will detect the mobile node's detachment from thelink andlink. It will signal the local mobility anchor and will remove the binding and routing state for that mobile node. The local mobilityanchoranchor, upon receiving thisrequestrequest, will identify the corresponding mobility session for which the request wasreceivedreceived, and once it accepts therequestrequest, will wait for a certain amount of timefor allowingto allow the mobile access gateway on the new link to update the binding. However, if it does not receive any Proxy Binding Update message withinthatthe given amount of time, it will delete the binding cache entry. The mobile access gateway on the new accesslinklink, upon detecting the mobile node on its accesslinklink, will signal the local mobility anchorfor updatingto update the binding state. Once that signaling is complete, the serving mobile access gateway will send the Router Advertisements containing the mobile node's home networkprefix(es)prefix(es), and this will ensure the mobile node will not detect any change with respect toitsthe layer-3 attachment of its interface. 4. Proxy Mobile IPv6 Protocol Security The signaling messages, Proxy BindingUpdateUpdate, and Proxy Binding Acknowledgement, exchanged between the mobile access gateway and the local mobilityanchoranchor, MUST be protected using end-to-end security association(s) offering integrity and data origin authentication. The mobile access gateway and the local mobility anchor MUST implement IPsec for protecting the Proxy Mobile IPv6 signaling messages [RFC4301]. That is, IPsec is amandatory to implementmandatory-to-implement security mechanism. However, additional documents may specify alternative mechanisms and the mobility entities can enable a specific mechanism for securing Proxy Mobile IPv6 signaling messages,eitherbased on either a static configuration or after a dynamic negotiation using any standard security negotiation protocols. As in Mobile IPv6 [RFC3775], the use of IPsec for protecting a mobile node's data traffic is optional. IPsecESPEncapsulating Security Payload (ESP) [RFC4303] in transport mode with mandatory integrity protection SHOULD be used for protecting the signaling messages. Confidentiality protection of these messages is not required. IPsec ESP [RFC4303] in tunnel mode MAY be used to protect the mobile node's tunneled data traffic, if protection of data traffic is required.IKEv2Internet Key Exchange Protocol version 2 (IKEv2) [RFC4306] SHOULD be used to set up security associations between the mobile access gateway and the local mobility anchor to protect the Proxy Binding Update and Proxy Binding Acknowledgement messages. The mobile access gateway and the local mobility anchor can use any of the authentication mechanisms, as specified in[RFC 4306],[RFC4306], for mutual authentication. The Mobile IPv6 specification [RFC3775] requires the home agent to prevent a mobile node from creating security associations or creating binding cache entries for another mobile node's home address. In the protocol described in this document, the mobile node is not involved in creating security associations for protecting the signaling messages or sending binding updates. Therefore, the local mobility anchor MUST restrict the creation and manipulation of proxy bindings to specifically authorized mobile access gateways and prefixes. The local mobility anchor MUST be locally configurable to authorize such specific combinations. Additionalmechanismsmechanisms, such as a policy store orAAAAuthentication, Authorization, and Accounting (AAA) may be employed, but these are outside the scope of this specification. Unlike in Mobile IPv6 [RFC3775], these signaling messages do not carry either the Home Address destination option or the Type 2 Routingheaderheader, and hence the policy entries and security association selectors stay the same and require no special IPsec related considerations. 4.1. Peer Authorization Database (PAD) Example Entries This section describes PAD entries [RFC4301] on the mobile access gateway and the local mobility anchor. The PAD entries are only example configurations. Note that the PAD is a logical concept and a particular mobile access gateway or a local mobility anchor implementation can implement the PAD in anyimplementation specificimplementation-specific manner. The PAD state may also be distributed across various databases in a specific implementation. In the example shown below, the identity of the local mobility anchor is assumed to be lma_identity_1 and the identity of the mobile access gateway is assumed to be mag_identity_1. mobile access gateway PAD: - IF remote_identity = lma_identity_1 Then authenticate (shared secret/certificate/EAP) and authorize CHILD_SAs for remote address lma_address_1 local mobility anchor PAD: - IF remote_identity = mag_identity_1 Then authenticate (shared secret/certificate/EAP) and authorize CHILD_SAs for remote address mag_address_1 Figure 4: PAD Entries The list of authentication mechanisms in the above examples is not exhaustive. There could be other credentials used for authentication stored in the PAD. 4.2. Security Policy Database (SPD) Example Entries This section describes the security policy entries [RFC4301] on the mobile access gateway and the local mobility anchor required to protect the Proxy Mobile IPv6 signaling messages. The SPD entries are only example configurations. A particular mobile access gateway or a local mobility anchor implementation could configure different SPD entries as long as they provide the required security. In the example shown below, the identity of the mobile access gateway is assumed to be mag_identity_1, the address of the mobile access gateway is assumed to be mag_address_1, and the address of the local mobility anchor is assumed to be lma_address_1. The acronym MH represents the protocol number for the Mobility Header[RFC3775];[RFC3775], while the terms local_mh_type and remote_mh_type stand for local mobility header type and remote mobility headertypetype, respectively. mobile access gateway SPD-S: - IF local_address = mag_address_1 & remote_address = lma_address_1 & proto = MH & (local_mh_type = BU | remote_mh_type = BA) Then use SA ESP transport mode Initiate using IDi = mag_identity_1 to address lma_address_1 local mobility anchor SPD-S: - IF local_address = lma_address_1 & remote_address = mag_address_1 & proto = MH & (local_mh_type = BA | remote_mh_type = BU) Then use SA ESP transport mode Figure 5: SPD Entries 5. Local Mobility Anchor Operation The local mobility anchor MUST support the home agent function as defined in [RFC3775] andadditionallythe extensions defined in this specification. A home agent with these modifications and enhanced capabilities for supporting the Proxy Mobile IPv6 protocol is referred to as a local mobility anchor. This section describes the operational details of the local mobility anchor. 5.1. Extensions to Binding Cache Entry Data Structure Every local mobility anchor MUST maintain a Binding Cache entry for each currently registered mobile node. A Binding Cache entry is a conceptual data structure, described in Section 9.1 of [RFC3775]. For supporting this specification, the Binding Cache Entry data structure needs to be extended with the following additional fields. o A flag indicating whether or not this Binding Cache entry is created due to a proxy registration. This flag is set to value 1 for Binding Cache entries that are proxy registrations and is set to value 0 for all other entries. o The identifier of the registered mobile node, MN-Identifier. This identifier is obtained from the Mobile Node Identifier Option [RFC4283] present in the received Proxy Binding Update message. o The link-layer identifier of the mobile node's connected interface on the access link. This identifier can be acquired from the Mobile Node Link-layer Identifier option, present in the received Proxy Binding Update message. If the option was not present in the request, this variable length field MUST be set to two (octets) and MUST be initialized to a value of ALL_ZERO. o The link-local address of the mobile access gateway on the point- to-point link shared with the mobile node. This is generated by the local mobility anchor after accepting the initial Proxy Binding Update message. oListA list of IPv6 home network prefixes assigned to the mobile node's connected interface. The home network prefix(es) may have been statically configured in the mobile node's policy profile, or, they may have been dynamically allocated by the local mobility anchor. Each one of these prefix entries will alsoincludesinclude the corresponding prefix length. o The tunnel interface identifier (tunnel-if-id) of the bi- directional tunnel between the local mobility anchor and the mobile access gateway where the mobile node is currently anchored. This is internal to the local mobility anchor. The tunnel interface identifier is acquired during the tunnel creation. o The access technology type, by which the mobile node is currently attached. This is obtained from the Access Technology Type option, present in the Proxy Binding Update message. o The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is thetime-of-daytime of day on the local mobility anchor, when the message was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when thesequence number basedsequence-number-based scheme is in use), the value MUST be set to ALL_ZERO. Typically, any one of the mobile node's home network prefixes from its mobility session may be used as a key for locating its Binding Cache entry in all cases except when there has beenana handoff of the mobile node's session to a new mobile accessgatewaygateway, and that mobile access gateway is unaware of the home network prefix(es) assigned to that mobility session. In such handoff cases, the Binding Cache entry can be located under the considerations specified in Section 5.4.1. 5.2. Supported Home Network Prefix Models This specification supports the Per-MN-Prefix model and does not support the Shared-Prefix model. According to the Per-MN-Prefix model, home network prefix(es) assigned to a mobile node are for that mobile node's exclusive use and no other node shares an address from that prefix (other than the Subnet-Router anycast address [RFC4291]whichthat is used by the mobile access gateway hosting that prefix on that link). There may be more than one prefix assigned to a given interface of the mobile node; all of those assigned prefixes MUST be unique to that mobilenodenode, and all are part of exactly one mobility session. If the mobile node simultaneously attaches to the Proxy Mobile IPv6 domain through multiple interfaces, each of the attached interfaces MUST be assigned one or more unique prefixes. Prefixes that are not assigned to the same interface MUST NOT be managed under the same mobility session. The mobile node's home network prefix(es) assigned to a given interface of a mobile node (part of a mobility session) will be hosted on the access link where the mobile node is attached (using that interface). The local mobility anchor is not required to perform any proxyNDNeighbor Discovery (ND) operations [RFC4861] for defending the mobile node's home address(es), as the prefixes are not locally hosted on the local mobility anchor. However, from the routing perspective, the home network prefix(es) is topologically anchored on the local mobility anchor. 5.3. Signaling Considerations This section provides the rules for processing the signaling messages. The processing rules specified in this section and other related sections are chained and are in a specific order. When applying these considerations for processing the signaling messages, the specified order MUST be maintained. 5.3.1. Processing Proxy Binding Updates 1. The received Proxy Binding Update message (a Binding Update message with the 'P' flag set to value of 1, format specified in Section 8.1) MUST be authenticated as described in Section 4. When IPsec is used for message authentication, theSPISecurity Parameter Index (SPI) in the IPsec header [RFC4306] of the received packet is needed for locating the security association, for authenticating the Proxy Binding Update message. 2. The local mobility anchor MUST observe the rules described in Section 9.2 of [RFC3775] when processing the Mobility Header in the received Proxy Binding Update message. 3. The local mobility anchor MUST ignore the check, specified in Section 10.3.1 of [RFC3775], related to the presence of the Home Address destination option in the Proxy Binding Update message. 4. The local mobility anchor MUST identify the mobile node from the identifier present in the Mobile Node Identifier option[RFC 4283][RFC4283] of the Proxy Binding Update message. If the Mobile Node Identifier option is not present in the Proxy Binding Update message, the local mobility anchor MUST reject the request and send a Proxy Binding Acknowledgement message with Status field set to MISSING_MN_IDENTIFIER_OPTION (Missingmobile node identifierMobile Node Identifier option) and the identifier in the Mobile Node IdentifierOptionoption carried in the message MUST be set to a zero length identifier. 5. The local mobility anchor MUST apply the required policy checks, as explained in Section 4, to verify that the sender is a trusted mobile accessgateway,gateway authorized to send Proxy Binding Update messages on behalf of this mobile node. 6. If the local mobility anchor determines that the requesting node is not authorized to send Proxy Binding Update messages for the identified mobile node, it MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to MAG_NOT_AUTHORIZED_FOR_PROXY_REG (not authorized to send proxy binding updates). 7. If the local mobility anchor cannot identify the mobile node based on the identifier present in the Mobile Node Identifier option [RFC4283] of the Proxy Binding Update message, it MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to NOT_LMA_FOR_THIS_MOBILE_NODE (Not a local mobility anchor for this mobile node). 8. If the local mobility anchor determines that the mobile node is not authorized for the network-based mobility management service, it MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to PROXY_REG_NOT_ENABLED (Proxy Registration not enabled). 9. The local mobility anchor MUST apply the considerations specified in Section5.5,5.5 for processing the Sequence Number field and the Timestamp option (ifpresent),present) in the Proxy Binding Update message. 10. If there is no Home Network Prefix option(s) (with any value) present in the Proxy Binding Update message, the local mobility anchor MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to MISSING_HOME_NETWORK_PREFIX_OPTION (Missinghome network prefixHome Network Prefix option). 11. If the Handoff Indicator option is not present in the Proxy Binding Update message, the local mobility anchor MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to MISSING_HANDOFF_INDICATOR_OPTION (Missinghandoff indicatorHandoff Indicator option). 12. If the Access Technology Type option is not present in the Proxy Binding Update message, the local mobility anchor MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to MISSING_ACCESS_TECH_TYPE_OPTION (Missingaccess technology typeAccess Technology Type option). 13. Considerations specified in Section 5.4.1 MUST be applied for performing the Binding Cache entry existence test. If those checks specified in Section5.4.1,5.4.1 result in associating the received Proxy Binding Update message to a new mobility session creation request, considerations from Section 5.3.2 (Initial Binding Registration - New Mobility Session), MUST be applied. If those checks result in associating the request to an existing mobility session, the following checks determine the next set of processing rules thatneedsneed to be applied. * If the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 5 (Handoff state not changed), considerations from Section 5.3.3 (Binding LifetimeExtension-Extension - No handoff) MUST be applied. * If the received Proxy Binding Update message has the lifetime value of zero, considerations from Section 5.3.5 (Binding De- Registration) MUST be applied. * For all other cases, considerations from Section 5.3.4 (Binding Lifetime Extension - After handoff) MUST be applied. 14. When sending the Proxy Binding Acknowledgement message with any Status field value, the message MUST be constructed as specified in Section 5.3.6. 5.3.2. Initial Binding Registration (New Mobility Session) 1. If there is at least one instance of the Home Network Prefix option present in the Proxy Binding Update message with the prefix value set to ALL_ZERO, the local mobility anchor MUST allocate one or more home networkprefix(es)prefixes to the mobile node and assign it to the new mobility session created for the mobile node. The local mobility anchor MUST ensure the allocated prefix(es) is not in use by any other node or mobility session. The decision on how many prefixes to be allocated for the attachedinterface,interface can be based on a global policy or a policy specific to that mobile node. However, when stateful address autoconfiguration using DHCP is supported on the link, considerations from Section 6.11 MUST be applied for the prefix assignment. 2. If the local mobility anchor is unable to allocate any home network prefix for the mobile node, it MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to 130 (Insufficient resources). 3. If there are one or more Home Network Prefix options present in the Proxy Binding Update message (with each of the prefixes set to a NON_ZERO value), the local mobilityanchoranchor, before accepting that request, MUST ensure each one of those prefixes is owned by the local mobilityanchoranchor, and further that the mobile node is authorized to use these prefixes. If the mobile node is not authorized to use any one or more of those prefixes, the local mobility anchor MUST reject the request and send a Proxy Binding Acknowledgement message with the Status field set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (mobile node not authorized for one or more of the requesting home network prefixes). 4. Upon accepting the request, the local mobility anchor MUST create a Binding Cache entry for the mobile node. It must set the fields in the Binding Cache entry to the accepted values for that registration. 5. If there is no existing bi-directional tunnel to the mobile access gateway that sent the request, the local mobility anchor MUST establish a bi-directional tunnel to that mobile access gateway. Considerations from Section 5.6.1 MUST be applied for managing the dynamically created bi-directional tunnel. 6. The local mobility anchor MUST create a prefix route(s) over the tunnel to the mobile access gateway for forwarding any traffic received for the mobile node's home network prefix(es) associated with this mobility session. The created tunnel and the routing state MUST result in the forwarding behavior on the local mobility anchor as specified in Section 5.6.2. 7. The local mobility anchor MUST send the Proxy Binding Acknowledgement message with the Status field set to 0 (Proxy Binding Update Accepted). The message MUST be constructed as specified in Section 5.3.6. 5.3.3. Binding Lifetime Extension (Nohandoff)Handoff) 1. Upon accepting the Proxy Binding Update message for extending the binding lifetime, received from the same mobile access gateway (if the Proxy-CoA address in the Binding Cache entry is the same as the Proxy-CoA address in the request) that last updated the binding, the local mobility anchor MUST update the Binding Cache entry with the accepted registration values. 2. The local mobility anchor MUST send the Proxy Binding Acknowledgement message with the Status field set to 0 (Proxy Binding Update Accepted). The message MUST be constructed as specified in Section 5.3.6. 5.3.4. Binding Lifetime Extension (Afterhandoff)Handoff) 1. Upon accepting the Proxy Binding Update message for extending the binding lifetime, received from a new mobile access gateway (if the Proxy-CoA address in the Binding Cache entry does not match the Proxy-CoA address in the request) where the mobile node's mobility session is handed off, the local mobility anchor MUST update the Binding Cache entry with the accepted registration values. 2. The local mobility anchor MUST remove the previously created route(s) for the mobile node's home network prefix(es) associated with this mobility session. Additionally, if there are no other mobilenodenodes sharing the dynamically created bi-directional tunnel to the previous mobile access gateway, the tunnel SHOULD bedeleteddeleted, applying considerations from section 5.6.1 (if the tunnel is a dynamically created tunnel and not a fixedpre-establishedpre- established tunnel). 3. If there is no existing bi-directional tunnel to the mobile access gateway that sent the request, the local mobility anchor MUST establish a bi-directional tunnel to that mobile access gateway. Considerations from Section 5.6.1 MUST be applied for managing the dynamically created bi-directional tunnel. 4. The local mobility anchor MUST create prefix route(s) over the tunnel to the mobile access gateway for forwarding any traffic received for the mobile node's home network prefix(es) associated with that mobility session. The created tunnel and routing state MUST result in the forwarding behavior on the local mobility anchor as specified in Section 5.6.2. 5. The local mobility anchor MUST send the Proxy Binding Acknowledgement message with the Status field set to 0 (Proxy Binding Update Accepted). The message MUST be constructed as specified in Section 5.3.6. 5.3.5. Binding De-Registration 1. If the received Proxy Binding Update message with the lifetime value of zero, has a Source Address in the IPv6 header (or the address in the Alternate Care-of Address option, if the option is present) different from what is present in the Proxy-CoA address field in the Binding Cache entry, the local mobility anchor MUST ignore the request. 2. Upon accepting the Proxy Binding Updatemessagemessage, with the lifetime value of zero, the local mobility anchor MUST wait for MinDelayBeforeBCEDelete amount of time, before it deletes the Binding Cache entry. However, it MUST send the Proxy Binding Acknowledgement message with the Status field set to 0 (Proxy Binding Update Accepted). The message MUST be constructed as specified in Section 5.3.6. * During this wait period, the local mobility anchor SHOULD drop the mobile node's data traffic. * During this wait period, if the local mobility anchor receives a valid Proxy Binding Update message for the same mobility session with the lifetime value of greater than zero, and if that request is accepted, then the Binding Cache entry MUST NOT be deleted, but must be updated with the newly accepted registrationvaluesvalues, andadditionallythe wait period should be ended. * By the end of this wait period, if the local mobility anchor did not receive any valid Proxy Binding Updatemessagemessages for this mobility session, then it MUST delete the Binding Cache entry and remove the routing state created for that mobility session. The local mobility anchor can potentially reassign the prefix(es) associated with this mobility session to other mobile nodes. 5.3.6. Constructing the Proxy Binding Acknowledgement Message o The local mobilityanchoranchor, when sending the Proxy Binding Acknowledgement message to the mobile accessgatewaygateway, MUST construct the message as specified below. IPv6 header (src=LMAA, dst=Proxy-CoA) Mobility header - BA /* P flag must be set to value of 1 */ Mobility Options - Mobile Node IdentifierOptionoption (mandatory) - Home Network Prefix option(s) (mandatory) - Handoff Indicator option (mandatory) - Access Technology Type option (mandatory) - TimestampOptionoption (optional) - Mobile Node Link-layer Identifier option (optional) - Link-local Address option (optional) Figure 6: Proxy Binding Acknowledgementmessage formatMessage Format o The Source Address field in the IPv6 header of the message MUST be set to the destination address of the received Proxy Binding Update message. o The Destination Address field in the IPv6 header of the message MUST be set to the source address of the received Proxy Binding Update message. When there is no Alternate Care-of Address option present in the request, the destination address is the same as the Proxy-CoA address, otherwise, the address may not be the same as the Proxy-CoA. o The Mobile Node Identifier option [RFC4283] MUST be present. The identifier field in the option MUST be copied from the Mobile Node Identifier option in the received Proxy Binding Update message. If the option was not present in the request, the identifier in the option MUST be set to a zero length identifier. o At least one Home Network Prefix option MUST be present. * If the Status field is set to a value greater than or equal to 128, i.e., if the Proxy Binding Update is rejected, all the Home Network Prefix options that were present in the request (along with their prefix values) MUST be present in the reply. But, if there was no Home Network Prefix option present in the request, then there MUST be only one Home Network Prefix optionandwith the value in the option set to ALL_ZERO. * For all other cases, there MUST be a Home Network Prefix option for each of the assigned home network prefixes (for that mobilitysession)session), and with the prefix value in the option set to the allocated prefix value. o The Handoff Indicator option MUST be present. The handoff indicator field in the option MUST be copied from the Handoff Indicator option in the received Proxy Binding Update message. If the option was not present in the request, the value in the option MUST be set to zero. o The Access Technology Type option MUST be present. The access technology type field in the option MUST be copied from the Access Technology Type option in the received Proxy Binding Update message. If the option was not present in the request, the value in the option MUST be set to zero. o The Timestamp option MUST be present only if the same option was present in the received Proxy Binding Update message and MUST NOT be present otherwise. Considerations from Section 5.5 must be applied for constructing the Timestamp option. o The Mobile Node Link-layer Identifier option MUST be present only if the same option was present in the received Proxy Binding Update message and MUST NOT be present otherwise. The link-layer identifier value MUST be copied from the Mobile Node Link-layer Identifier option present in the received Proxy Binding Update message. o The Link-local Address option MUST be present only if the same option was present in the received Proxy Binding Update message and MUST NOT be present otherwise. If the Status field in the reply is set to a value greater than or equal to 128, i.e., if the Proxy Binding Update is rejected, then the link-local address from the request MUST be copied to the Link-local Address option in the reply, otherwise the following considerations apply. * If the received Proxy Binding Update message has the Link-local Address option with ALL_ZERO value and if there is an existing Binding Cache entry associated with this request, then the link-local address from the Binding Cache entry MUST be copied to the Link-local Address option in the reply. * If the received Proxy Binding Update message has the Link-local Address option with ALL_ZERO value and if there is no existing Binding Cache entry associated with this request, then the local mobility anchor MUST generate the link-local address that the mobile access gateway can use on the point-to-point link shared with the mobile node. This generated address MUST be copied to the Link-local Address option in the reply. The same address MUST also be copied to the link-local address field of Binding Cache entry created for this mobility session. * If the received Proxy Binding Update message has the Link-local Address option with NON_ZERO value, then the link-local address from the request MUST be copied to the Link-local Address option in the reply. The same address MUST also be copied to the link-local address field of the Binding Cache entry associated with this request (after creating the Binding Cache entry, ifthereone does notexist one).exist). o If IPsec is used for protecting the signaling messages, the message MUST beprotected,protected using the security association existing between the local mobility anchor and the mobile access gateway. o Unlike in Mobile IPv6 [RFC3775], the Type 2 Routing header MUST NOT be present in the IPv6 header of the packet. 5.4. Multihoming Support This specification allows mobile nodes to connect to a Proxy Mobile IPv6 domain through multiple interfaces for simultaneous access.FollowingThe following are the key aspects of this multihoming support. o When a mobile node connects to a Proxy Mobile IPv6 domain through multiple interfaces for simultaneous access, the local mobility anchor MUST allocate a mobility session for each of the attached interfaces. Each mobility session should be managed under a separate Binding Cache entry and with its own lifetime. o The local mobility anchor MAY allocate more than one home network prefix for a given interface of the mobile node. However, all the prefixes associated with a given interface MUST be managed as part of one mobility session, associated with that interface. o The local mobility anchor MUST allow forana handoff between two different interfaces of a mobile node. In such a scenario, all the home networkprefix(es)prefixes associated with one interface (part of one mobility session) will be associated with a different interface of the mobilenode).node. The decision on when to create a new mobility session and when to update an existing mobility session MUST be based on the Handover hint present in the Proxy Binding Update message and under the considerations specified in thissection 5.4.section. 5.4.1. Binding Cacheentry lookup considerationsEntry Lookup Considerations There can be multiple Binding Cache entries for a given mobile node. When doing a lookup for a mobile node's Binding Cache entry for processing a received Proxy Binding Update message, the local mobility anchor MUST apply the following multihoming considerations (in the below specified order, starting with Section 5.4.1.1). These rules are chained with the processing rules specified in Section 5.3. 5.4.1.1. Home Network Prefix Option (NON_ZERO Value)presentPresent in therequestRequest +=====================================================================+ | Registration/De-Registration Message | +=====================================================================+ | At least one HNP Option with NON_ZERO Value | +=====================================================================+ | ATT | +=====================================================================+ | MN-LL-Identifier Opt Present | MN-LL-Identifier Opt Not Present | +=====================================================================+ | HI | +==================================+==================================+ | BCE Lookup Key: Any of the Home Network Prefixes from the request | +=====================================================================+ Figure 7:BCE lookup using home network prefixBinding Cache Entry (BCE) Lookup Using Home Network Prefix If there is at least one Home Network Prefix option present in the request with a NON_ZERO prefix value and irrespective of the presence of the Mobile Node Link-layer Identifier option in the request, the following considerations MUST be applied. If thereareis more than oneinstancesinstance of the Home Network Prefix option, any one of the Home Network Prefix options present in the request (with NON_ZERO prefix value) can be used for locating the Binding Cache entry. 1. The local mobility anchor MUST verify if there is an existing Binding Cache entry with one of its home network prefixes matching the prefix value in one of the Home Network Prefix options of the received Proxy Binding Update message. 2. Ifthere does not exista Binding Cache entry does not exist (with one of its home network prefixes in the Binding Cache entry matching the prefix value in one of the Home Network Prefix options of the received Proxy Binding Update message), the request MUST be considered as a request for creating a new mobility session. 3. If there exists a Binding Cache entry (with one of its home network prefixes in the Binding Cache entry matching the prefix value in one of the Home Network Prefix options of the received Proxy Binding Updatemessage)message), but if the mobile node identifier in the entry does not match the mobile node identifier in the Mobile Node Identifier option of the received Proxy Binding Update message, the local mobility anchor MUST reject the request with the Status field value set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (mobile node is not authorized for one or more of the requesting home network prefixes). 4. If there exists a Binding Cache entry (matching MN-Identifier and one of its home network prefixes in the Binding Cache entry matching the prefix value in one of the Home Network Prefix options of the received Proxy Binding Update message), but if all the prefixes in the request do not match all the prefixes in the Binding Cache entry, or if they do not match in count, then the local mobility anchor MUST reject the request with the Status field value set to BCE_PBU_PREFIX_SET_DO_NOT_MATCH (all the home network prefixes listed in the BCE do not match all the prefixes in the received PBU). 5. If there exists a Binding Cache entry (matching MN-Identifier and all the home network prefixes in the Binding Cache entry matching all the home network prefixes in the received Proxy Binding Update message) and if any one or more of these below stated conditions match, the request MUST be considered as a request for updating that Binding Cache entry. * If the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 2 (Handoff between two different interfaces of the mobile node). * If there is no Mobile Node Link-layer Identifier option present in the request, the link-layer identifier value in the Binding Cache entry is set to ALL_ZERO, the access technology type field in the Access Technology Type option present in the request matches the access technology type in the Binding Cacheentryentry, and if the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 3 (Handoff between mobile access gateways for the same interface). * If the Proxy-CoA address in the Binding Cache entry matches the source address of the request (or the address in the alternate Care-of Address option, if the option is present) and if the access technology type field in the Access Technology Type option present in the request matches the access technology type in the Binding Cache entry. 6. For all other cases, the message MUST be considered as a request for creating a new mobility session. However, if the received Proxy Binding Update message has the lifetime value of zero and if the request cannot be associated with any existing mobility session, the message MUST be silently ignored. 5.4.1.2. Mobile NodeLink-layerLink-Layer Identifier OptionpresentPresent in therequestRequest +=====================================================================+ | Registration/De-Registration Message | +=====================================================================+ | No HNP option with a NON_ZERO Value | +=====================================================================+ | ATT | +=====================================================================+ | MN-LL-Identifier Option Present (NON_ZERO Value) | +=====================================================================+ | HI | +==================================+==================================+ | BCE Lookup Keys: (MN-Identifier + ATT + MN-LL-Identifier) | +=====================================================================+ Figure 8: BCE Lookupusing Link-layerUsing Link-Layer Identifier If there is no Home Network Prefix option present in the request with a NON_ZERO prefix value, but if there is a Mobile Node Link-layer Identifier option present in therequestrequest, then the following considerations MUST be applied for locating the Binding Cache entry. 1. The local mobility anchor MUST verify if there is an existing Binding Cache entry, with the mobile node identifier matching the identifier in the received Mobile Node Identifier option, access technology type matching the value in the received Access Technology Typeoptionoption, and the link-layer identifier value matching the identifier in the received Mobile Node Link-layer Identifier option. 2. If there exists a Binding Cache entry (matching MN-Identifier,ATTAccess Technology Type (ATT), and MN-LL-Identifier), the request MUST be considered as a request for updating that Binding Cache entry. 3. If there does not exist a Binding Cache entry (matching MN- Identifier,ATTATT, and MN-LL-Identifier) and the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 2 (Handoff between two different interfaces of the mobile node). The local mobility anchor MUST apply the following additional considerations. * The local mobility anchor MUST verify if there exists one and only one Binding Cache entry with the mobile node identifier matching the identifier in the Mobile Node Identifier option present in the request and for any link-layer identifier value. If there exists only one such entry (matching the MN- Identifier), the request MUST be considered as a request for updating that Binding Cache entry. 4. If there does not exist a Binding Cache entry (matching MN- Identifier,ATTATT, and MN-LL-Identifier) and if the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 4 (Handoff state unknown), the local mobility anchor MUST apply the following additional considerations. * The local mobility anchor MUST verify if there exists one and only one Binding Cache entry with the mobile node identifier matching the identifier in the Mobile Node Identifier option present in the request and for any link-layer identifier value. If there exists only one such entry (matching the MN- Identifier), the local mobility anchor SHOULD waittilluntil the existing Binding Cache entry is de-registered by the previously serving mobile access gateway, before the request can be considered as a request for updating that Binding Cache entry. However, if there is no de-registration message that is received within MaxDelayBeforeNewBCEAssign amount of time, the local mobilityanchoranchor, upon accepting therequestrequest, MUST consider the request as a request for creating a new mobility session. The local mobility anchor MAY also choose to create a new mobility session without waiting for a de-registrationmessagemessage, and this should be configurable on the local mobility anchor. 5. For all other cases, the message MUST be considered as a request for creating a new mobility session. However, if the received Proxy Binding Update message has the lifetime value of zero and if the request cannot be associated with any existing mobility session, the message MUST be silently ignored. 5.4.1.3. Mobile NodeLink-layerLink-Layer Identifier Optionnot present in the request +=====================================================================+ | Registration/De-Registration Message | +=====================================================================+ | No HNP option with a NON_ZERO Value | +=====================================================================+ | ATT | +=====================================================================+ | MN-LL-Identifier OptionNot Present| +=====================================================================+ | HI | +==================================+==================================+ | BCE Lookup Key: (MN-Identifier) | +=====================================================================+in the Request Figure 9: BCE LookupusingUsing Mobile Node Identifier If there is no Home Network Prefix option present in the request with a NON_ZERO prefix value and if there is also no Mobile Node Link- layer Identifier option present in therequestrequest, then the following considerations MUST be applied for locating the Binding Cache entry. 1. The local mobility anchor MUST verify if there exists one and only one Binding Cache entry with the mobile node identifier matching the identifier in the Mobile Node Identifier option present in the request. 2. If there exists only one such entry (matching the MN-Identifier) and the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 2 (Handoff between two different interfaces of the mobile node) or set to a value of 3 (Handoff between mobile access gateways for the same interface), then the request MUST be considered as a request for updating that Binding Cache entry. 3. If there exists only one such entry (matching the MN-Identifier) and the Handoff Indicator field in the Handoff Indicator option present in the request is set to a value of 4 (Handoff state unknown), the local mobility anchor SHOULD waittilluntil the existing Binding Cache entry is de-registered by the previously serving mobile accessgateway,gateway before the request can be considered as a request for updating that Binding Cache entry. However, if there is no de-registration message that is received within MaxDelayBeforeNewBCEAssign amount of time, the local mobilityanchoranchor, upon accepting therequestrequest, MUST consider the request as a request for creating a new mobility session. The local mobility anchor MAY also choose to create a new mobility sessionandwithout waiting for a de-registrationmessagemessage, and this should be configurable on the local mobility anchor. 4. For all other cases, the message MUST be considered as a request for creating a new mobility session. However, if the received Proxy Binding Update message has the lifetime value of zero and if the request cannot be associated with any existing mobility session, the message MUST be silently ignored. 5.5. Timestamp Option for Message Ordering Mobile IPv6 [RFC3775] uses the Sequence Number field in binding registration messages as a way for the home agent to process the binding updates in the order they were sent by a mobile node. The home agent and the mobile node are required to manage this counter over the lifetime of a binding. However, in Proxy Mobile IPv6, as the mobile node moves from one mobile access gateway to another and in the absence of mechanisms such as context transfer between the mobile access gateways, the serving mobile access gateway will be unable to determine the sequence number that it needs to use in the signaling messages. Hence, the sequence number scheme, as specified in [RFC3775], will be insufficient for Proxy Mobile IPv6. If the local mobility anchor cannot determine the sending order of the received Proxy Binding Update messages, it may potentially process an older message sent by a mobile access gateway where the mobile node was previously anchored, but delivered out of order, resulting in incorrectly updating the mobile node's Binding Cache entry and creating a routing state for tunneling the mobile node's traffic to the previous mobile access gateway. For solving this problem, this specification adopts two alternative solutions. One is based on timestamps and the other based on sequence numbers, as defined in [RFC3775]. The basic principle behind the use of timestamps in binding registration messages is that the node generating the message inserts the currenttime-of-day,time of day, and the node receiving the message checks that this timestamp is greater than all previously accepted timestamps. Thetimestamp basedtimestamp-based solution may be used when the serving mobile access gateways in a Proxy Mobile IPv6 domain do not have the ability to obtain the last sequence number that was sent in a Proxy Binding Update message for updating a given mobile node's binding. Clock drift reduces the effectiveness of the timestamp mechanism. The time required for reconnection is the total of the time required for the mobile node to roam between two mobile access gateways and the time required for the serving mobile access gateway to detect the mobile node on its access link and construct the Proxy Binding Update message. If the clock skew on any one of these two neighboring mobile access gateways (relative to the common time source used for clock synchronization) is more than half this reconnection time, the timestamp solution will not predictably work in all cases and hence SHOULD NOT be used. As an alternative to theTimestamp basedTimestamp-based approach, the specification also allows the use ofSequence Number basedSequence-Number-based scheme, as specified in [RFC3775]. However, for this scheme to work, the serving mobile access gateway in a Proxy Mobile IPv6 domain MUST have the ability to obtain the last sequence number that was sent in a binding registration message. The sequence number MUST be maintained on a per mobile node basis and MUST be available to the serving mobile access gateway. This may be achieved by using context transfer schemes or by maintaining the sequence number in a policy store. However, the specific details on how the mobile node's sequence number is made available to the serving mobile access gateway prior to sending the Proxy Binding Update message is outside the scope of thisdocument."document. Using theTimestamps based approach:Timestamp-Based Approach: 1. A local mobility anchor implementation MUST support the Timestamp option. If the Timestamp option is present in the received Proxy Binding Update message, then the local mobility anchor MUST include a valid Timestamp option in the Proxy Binding Acknowledgement message that it sends to the mobile access gateway. 2. All the mobility entities in a Proxy Mobile IPv6 domain that are exchanging binding registration messages using the Timestamp option MUST have adequately synchronized time-of-day clocks. This is the essential requirement for this solution to work. If this requirement is not met, the solution will not predictably work in all cases. 3. The mobility entities in a Proxy Mobile IPv6 domain SHOULD synchronize their clocks to a common time source. For synchronizing the clocks, the nodes MAY use the Network Time Protocol [RFC4330]. Deployments MAY also adopt other approaches suitable for that specific deployment. Alternatively, if there is a mobile node generated timestamp that is increasing at every attachment to the access link and if that timestamp is available to the mobile access gateway(Ex:(e.g., thetimestampTimestamp option in the SEND [RFC3971] messages that the mobile node sends), the mobile access gateway can use this timestamp or sequence number in the Proxy Binding Update messages and does not have to depend on any external clock source. However, the specific details on how this is achieved are outside the scope of this document. 4. When generating the timestamp value for building the Timestamp option, the mobility entities MUST ensure that the generated timestamp is the elapsed time past the same reference epoch, as specified in the format for the Timestamp option (Section 8.8). 5. If the Timestamp option is present in the received Proxy Binding Update message, the local mobility anchor MUST ignore the sequence number field in the message. However, it MUST copy the sequence number from the received Proxy Binding Update message to the Proxy Binding Acknowledgement message. 6. Upon receipt of a Proxy Binding Update message with the Timestamp option, the local mobility anchor MUST check the timestamp field for validity. In order for it to be considered valid, the following MUST be true. * The timestamp value contained in the Timestamp option MUST be close enough (within TimestampValidityWindow amount of time difference) to the local mobility anchor's time-of-day clock. However, if the flag MobileNodeGeneratedTimestampInUse is set to a value of 1, the local mobility anchor MUST ignore this check and perform only the following check. * The timestamp MUST be greater than all previously accepted timestamps in the Proxy Binding Update messages sent for that mobile node. 7. If the timestamp value in the received Proxy Binding Update is valid (validity as specified in the above considerations) or if the flag MobileNodeGeneratedTimestampInUse is set to value of 1, the local mobility anchor MUST return the same timestamp value in the Timestamp option included in the Proxy Binding Acknowledgement message that it sends to the mobile access gateway. 8. If the timestamp value in the received Proxy Binding Update is lower than the previously accepted timestamp in the Proxy Binding Update messages sent for that mobility binding, the local mobility anchor MUST reject the Proxy Binding Update message and send a Proxy Binding Acknowledgement message with the Status field set to TIMESTAMP_LOWER_THAN_PREV_ACCEPTED (Timestamp lower than previously accepted timestamp). The message MUST also include the Timestamp option with the value set to the currenttime-of-time of day on the local mobility anchor. 9. If the timestamp value in the received Proxy Binding Update is not valid (validity as specified in the above considerations), the local mobility anchor MUST reject the Proxy Binding Update and send a Proxy Binding Acknowledgement message with the Status field set to TIMESTAMP_MISMATCH (Timestamp mismatch). The message MUST also include the Timestamp option with the value set to the currenttime-of-daytime of day on the local mobility anchor. Using theSequence Number based approach:Sequence-Number-Based Approach: 1. If the Timestamp option is not present in the received Proxy Binding Update message, the local mobility anchor MUST fall back to theSequence Number basedSequence-Number-based scheme. It MUST process the sequence number field as specified in [RFC3775]. Also, it MUST NOT include the Timestamp option in the Proxy Binding Acknowledgement messages that it sends to the mobile access gateway. 2. An implementation MUST support theSequence Number basedSequence-Number-based scheme, as specified in [RFC3775]. 3. TheSequence Number basedSequence-Number-based approach can be used only when there is some mechanism (such as context transfer procedure between mobile access gateways) that allows the serving mobile access gateway to obtain the last sequence number that was sent in a Proxy Binding Update message for updating a given mobile node's binding. 5.6. Routing Considerations 5.6.1. Bi-Directional Tunnel Management The bi-directional tunnel MUST be used for routing the mobile node's data traffic between the mobile access gateway and the local mobility anchor. A tunnel hides the topology and enables a mobile node to use address(es) from its home network prefix(es) from any access link in that Proxy Mobile IPv6 domain. A tunnel may be created dynamically when needed and removed when not needed. However, implementations MAY choose to use static pre-established tunnels instead of dynamically creating and tearing them down on a need basis. The following considerations MUST be applied when using dynamic tunnels. o A bi-directional tunnel MUST be established between the local mobility anchor and the mobile access gateway with IPv6-in-IPv6 encapsulation, as described in [RFC2473]. The tunnelend pointsendpoints are the Proxy-CoA and LMAA. However, when using IPv4 transport, theend pointsendpoints of the tunnel are IPv4-LMAA and IPv4-Proxy-CoA with the encapsulation mode as specified in[ID-IPV4-PMIP6].[IPV4-PMIP6]. o Implementations MAY use a software timer for managing the tunnel lifetime and a counter for keeping a count of all the mobile nodes that are sharing the tunnel. The timer value can be set to the accepted binding lifetime and can be updated after each periodic re-registration for extending the lifetime. If the tunnel is shared for multiple mobile nodes, the tunnel lifetime must be set to the highest binding lifetime that is granted to any one of those mobile nodes sharing that tunnel. o The tunnel SHOULD be deleted when either the tunnel lifetime expires or when there are no mobile nodes sharing the tunnel. 5.6.2. Forwarding Considerations Intercepting Packets Sent to the Mobile Node's Home Network: o When the local mobility anchor is serving a mobile node, it MUST be able to receive packets that are sent to the mobile node's home network. In order for it to receive those packets, it MUST advertise a connected route in to the Routing Infrastructure for the mobile node's home network prefix(es) or for an aggregated prefix with a larger scope. This essentially enables IPv6 routers in that network to detect the local mobility anchor as the last- hop router for the mobile node's home network prefix(es). Forwarding Packets to the Mobile Node: o On receiving a packet from a correspondent node with the destination address matching a mobile node's home network prefix(es), the local mobility anchor MUST forward the packet through the bi-directional tunnel set up for that mobile node. o The format of the tunneled packet is shown below. Considerations from [RFC2473] MUST be applied for IPv6 encapsulation. However, when using IPv4 transport, the format of the packet is as described in[ID-IPV4-PMIP6].[IPV4-PMIP6]. IPv6 header (src= LMAA, dst= Proxy-CoA /* Tunnel Header */ IPv6 header (src= CN, dst= MN-HOA ) /* Packet Header */ Upper layer protocols /* Packet Content*/ Figure 10: Tunneled Packet from LMA to MAG o The format of the tunneled packet is shown below, when payload protection using IPsec is enabled for the mobile node's data traffic. However, when using IPv4 transport, the format of the packet is as described in[ID-IPV4-PMIP6].[IPV4-PMIP6]. IPv6 header (src= LMAA, dst= Proxy-CoA /* Tunnel Header */ ESP Header in tunnel mode /* ESP Header */ IPv6 header (src= CN, dst= MN-HoA ) /* Packet Header */ Upper layer protocols /* Packet Content*/ Figure 11: Tunneled Packet from LMA to MAG with Payload Protection Forwarding Packets Sent by the Mobile Node: o All the reverse tunneled packets that the local mobility anchor received from the mobile access gateway, after removing the tunnel header MUST be routed to the destination specified in the inner packet header. These routed packets will have thesource addressSource Address field set to the mobile node's home address. Considerations from [RFC2473] MUST be applied for IPv6 decapsulation. 5.6.3.ECNExplicit Congestion Notification (ECN) Considerations for Proxy Mobile IPv6 Tunnels This section describes how the ECN information needs to be handled by the mobility agents at the tunnel entry and exit points. The ECN considerations for IP tunnels are specified in[RFC3168][RFC3168], and the same considerations apply to Proxy Mobile IPv6 tunnels (using IPv6- in-IPv6 encapsulation mode).SpecificallySpecifically, the full-functionality option MUST be supported. The relevant ECN considerations from[RFC 3168][RFC3168] are summarized here for convenience. Encapsulation Considerations: o If the Explicit Congestion Notification (ECN) field in the inner header is set to ECT(0) or ECT(1), where ECT stands for ECN- Capable Transport (ECT), the ECN field from the inner header MUST be copied to the outer header. Additionally, when payload protection using IPsec is enabled for the mobile node's data traffic, the ECN considerations from [RFC4301] MUST be applied. Decapsulation Considerations: o If the Explicit Congestion Notification (ECN) field in the inner header is set to ECT(0) or ECT(1), and if the ECN field in the outer header is set to Congestion Experienced (CE), then the ECN field in the inner header MUST be set to CE. Otherwise, the ECN field in the inner header MUST NOT be modified. Additionally, when payload protection using IPsec is enabled for the mobile node's data traffic, the ECN considerations from [RFC4301] MUST be applied. 5.7. Local Mobility Anchor Address Discovery Dynamic Home Agent Address Discovery (DHAAD), as explained in Section 10.5 of [RFC3775], allows a mobile node to discover all the home agents on its home link by sending an ICMP Home Agent Address Discovery Request message to the Mobile IPv6Home-AgentsHome-Agent's anycast address, derived from its home network prefix. The DHAAD message in the current form cannot be used in Proxy Mobile IPv6 for discovering the address of the mobile node's local mobility anchor. In Proxy Mobile IPv6, the local mobility anchor will not be able to receive any messages sent to the Mobile IPv6Home-AgentsHome-Agent's anycast address corresponding to the mobile node's home network prefix(es), as the prefix(es) is not hosted on any of its interfaces. Further, the mobile access gateway will not predictably be able to locate the serving local mobility anchor that has the mobile node's binding cache entry. Hence, this specification does not support Dynamic Home Agent Address Discovery protocol. In Proxy Mobile IPv6, the address of the local mobility anchor configured to serve a mobile node can be discovered by the mobility entities in other ways. This may be a configured entry in the mobile node's policy profile, or it may be obtained through mechanisms outside the scope of this document. 5.8. Mobile Prefix Discovery Considerations This specification does not support mobile prefix discovery. The mobile prefix discovery mechanism as specified in [RFC3775] is not applicable to Proxy Mobile IPv6. 5.9. Route Optimization Considerations The Route Optimization in Mobile IPv6, as defined in [RFC3775], enables a mobile node to communicate with a correspondent node directly using itscare-of addressCare-of Address and further the Return Routability procedure enables the correspondent node to have reasonable trust that the mobile node is reachable at both its home address andcare-of address.Care-of Address. This specification does not support the Route Optimizationasspecified in Mobile IPv6 [RFC3775]. However, this specification does support some other form of routeoptimizationoptimization, as specified in Section 6.10.3. 6. Mobile Access Gateway Operation The Proxy Mobile IPv6 protocol described in this document introduces a new functional entity, theMobile Access Gatewaymobile access gateway (MAG). The mobile access gateway is the entity that is responsible for detecting the mobile node's movements to and from the access link and sending the Proxy Binding Update messages to the local mobility anchor. In essence, the mobile access gateway performs mobility management on behalf of a mobile node. The mobile access gateway is a function that typically runs on an access router. However, implementations MAY choose to split this function and run it across multiple systems. The specifics on how that is achieved or the signaling interactions between those functional entities are beyond the scope of this document. The mobile access gateway has the following key functional roles: o It is responsible for detecting the mobile node's movements on the access link and for initiating the mobility signaling with the mobile node's local mobility anchor. o Emulation of the mobile node's home link on the access link by sending Router Advertisement messages containing the mobile node's home network prefix(es), each prefix carried using the Prefix Information option [RFC4861]. o Responsible for setting up the forwarding for enabling the mobile node to configure one or more addresses from its home network prefix(es) and use it from the attached access link. 6.1. Extensions to Binding Update List Entry Data Structure Every mobile access gateway MUST maintain a Binding Update List. Each entry in the Binding Update List represents a mobile node's mobility binding with its local mobility anchor. The Binding Update List is a conceptual data structure, described in Section 11.1 of [RFC3775]. For supporting this specification, the conceptual Binding Update List entry data structure needs be extended with the following additional fields. o TheIdentifieridentifier of the attached mobile node, MN-Identifier. This identifier is acquired during the mobile node's attachment to the access link through mechanisms outside the scope of this document. o The link-layer identifier of the mobile node's connected interface. This can be acquired from the received Router Solicitation messages from the mobile node or during the mobile node's attachment to the access network. This is typically a link-layer identifier conveyed by the mobile node; however, the specific details on how t