draft-ietf-netlmm-proxymip6-12.txt   draft-ietf-netlmm-proxymip6-13.txt 
NETLMM WG S. Gundavelli (Editor) NETLMM WG S. Gundavelli (Editor)
Internet-Draft K. Leung Internet-Draft K. Leung
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: October 26, 2008 V. Devarapalli Expires: November 13, 2008 V. Devarapalli
Azaire Networks Wichorus
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
B. Patil B. Patil
Nokia Siemens Networks Nokia Siemens Networks
April 24, 2008 May 12, 2008
Proxy Mobile IPv6 Proxy Mobile IPv6
draft-ietf-netlmm-proxymip6-12.txt draft-ietf-netlmm-proxymip6-13.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 40 skipping to change at page 1, line 40
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 26, 2008. This Internet-Draft will expire on November 13, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
Network-based mobility management enables IP mobility for a host Network-based mobility management enables IP mobility for a host
without requiring its participation in any mobility related without requiring its participation in any mobility related
signaling. The Network is responsible for managing IP mobility on signaling. The Network is responsible for managing IP mobility on
skipping to change at page 2, line 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 4 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 4
2.1. Conventions used in this document . . . . . . . . . . . . 5 2.1. Conventions used in this document . . . . . . . . . . . . 5
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Proxy Mobile IPv6 Protocol Overview . . . . . . . . . . . . . 9 3. Proxy Mobile IPv6 Protocol Overview . . . . . . . . . . . . . 9
4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 15 4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 15
4.1. Peer Authorization Database (PAD) Example Entries . . . . 16 4.1. Peer Authorization Database (PAD) Example Entries . . . . 16
4.2. Security Policy Database (SPD) Example Entries . . . . . . 16 4.2. Security Policy Database (SPD) Example Entries . . . . . . 17
5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 17 5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 17
5.1. Extensions to Binding Cache Entry Data Structure . . . . . 17 5.1. Extensions to Binding Cache Entry Data Structure . . . . . 18
5.2. Supported Home Network Prefix Models . . . . . . . . . . . 19 5.2. Supported Home Network Prefix Models . . . . . . . . . . . 19
5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 19 5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 20
5.3.1. Processing Binding Registrations . . . . . . . . . . . 19 5.3.1. Processing Binding Registrations . . . . . . . . . . . 20
5.3.2. Initial Binding Registration (New Mobility Session) . 22 5.3.2. Initial Binding Registration (New Mobility Session) . 22
5.3.3. Binding Lifetime Extension (No handoff) . . . . . . . 23 5.3.3. Binding Lifetime Extension (No handoff) . . . . . . . 23
5.3.4. Binding Lifetime Extension (After handoff) . . . . . . 23 5.3.4. Binding Lifetime Extension (After handoff) . . . . . . 24
5.3.5. Binding De-Registration . . . . . . . . . . . . . . . 24 5.3.5. Binding De-Registration . . . . . . . . . . . . . . . 24
5.3.6. Constructing the Proxy Binding Acknowledgement 5.3.6. Constructing the Proxy Binding Acknowledgement
Message . . . . . . . . . . . . . . . . . . . . . . . 24 Message . . . . . . . . . . . . . . . . . . . . . . . 25
5.4. Multihoming Support . . . . . . . . . . . . . . . . . . . 27 5.4. Multihoming Support . . . . . . . . . . . . . . . . . . . 27
5.4.1. Binding Cache entry lookup considerations . . . . . . 27 5.4.1. Binding Cache entry lookup considerations . . . . . . 28
5.5. Timestamp Option for Message Ordering . . . . . . . . . . 33 5.5. Timestamp Option for Message Ordering . . . . . . . . . . 33
5.6. Routing Considerations . . . . . . . . . . . . . . . . . . 36 5.6. Routing Considerations . . . . . . . . . . . . . . . . . . 36
5.6.1. Bi-Directional Tunnel Management . . . . . . . . . . . 36 5.6.1. Bi-Directional Tunnel Management . . . . . . . . . . . 36
5.6.2. Forwarding Considerations . . . . . . . . . . . . . . 36 5.6.2. Forwarding Considerations . . . . . . . . . . . . . . 37
5.7. Local Mobility Anchor Address Discovery . . . . . . . . . 37 5.7. Local Mobility Anchor Address Discovery . . . . . . . . . 38
5.8. Mobile Prefix Discovery Considerations . . . . . . . . . . 38 5.8. Mobile Prefix Discovery Considerations . . . . . . . . . . 39
5.9. Route Optimizations Considerations . . . . . . . . . . . . 38 5.9. Route Optimization Considerations . . . . . . . . . . . . 39
6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 38 6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 39
6.1. Extensions to Binding Update List Entry Data Structure . . 39 6.1. Extensions to Binding Update List Entry Data Structure . . 40
6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 40 6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 41
6.3. Supported Access Link Types . . . . . . . . . . . . . . . 41 6.3. Supported Access Link Types . . . . . . . . . . . . . . . 42
6.4. Supported Address Configuration Modes . . . . . . . . . . 41 6.4. Supported Address Configuration Modes . . . . . . . . . . 42
6.5. Access Authentication & Mobile Node Identification . . . . 42 6.5. Access Authentication & Mobile Node Identification . . . . 43
6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 42 6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 43
6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 43 6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 44
6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 43 6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 44
6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 44 6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 45
6.9.1. Binding Registrations . . . . . . . . . . . . . . . . 44 6.9.1. Binding Registrations . . . . . . . . . . . . . . . . 45
6.9.2. Router Solicitation Messages . . . . . . . . . . . . . 52 6.9.2. Router Solicitation Messages . . . . . . . . . . . . . 54
6.9.3. Default-Router . . . . . . . . . . . . . . . . . . . . 53 6.9.3. Default-Router . . . . . . . . . . . . . . . . . . . . 54
6.9.4. Retransmissions and Rate Limiting . . . . . . . . . . 53 6.9.4. Retransmissions and Rate Limiting . . . . . . . . . . 55
6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 54 6.9.5. Path MTU Discovery . . . . . . . . . . . . . . . . . . 56
6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 54 6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 57
6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 55 6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 57
6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . . 56 6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 57
6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . . 56 6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . . 58
6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . . 56 6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . . 59
6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . . 59
6.11. Supporting DHCPv6 based Address Configuration on the 6.11. Supporting DHCPv6 based Address Configuration on the
Access Link . . . . . . . . . . . . . . . . . . . . . . . 58 Access Link . . . . . . . . . . . . . . . . . . . . . . . 61
6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 59 6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 62
6.13. Mobile Node Detachment Detection and Resource Cleanup . . 59 6.13. Mobile Node Detachment Detection and Resource Cleanup . . 62
6.14. Allowing network access to other IPv6 nodes . . . . . . . 60 6.14. Allowing network access to other IPv6 nodes . . . . . . . 63
7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 60 7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 64
7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 61 7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 64
7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 62 7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 65
8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 62 8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 65
8.1. Proxy Binding Update Message . . . . . . . . . . . . . . . 62 8.1. Proxy Binding Update Message . . . . . . . . . . . . . . . 66
8.2. Proxy Binding Acknowledgement Message . . . . . . . . . . 64 8.2. Proxy Binding Acknowledgement Message . . . . . . . . . . 67
8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 65 8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 69
8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . . 66 8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . . 70
8.5. Access Technology Type Option . . . . . . . . . . . . . . 67 8.5. Access Technology Type Option . . . . . . . . . . . . . . 71
8.6. Mobile Node Link-layer Identifier Option . . . . . . . . . 69 8.6. Mobile Node Link-layer Identifier Option . . . . . . . . . 73
8.7. Link-local Address Option . . . . . . . . . . . . . . . . 70 8.7. Link-local Address Option . . . . . . . . . . . . . . . . 74
8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 71 8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 75
8.9. Status Values . . . . . . . . . . . . . . . . . . . . . . 71 8.9. Status Values . . . . . . . . . . . . . . . . . . . . . . 75
9. Protocol Configuration Variables . . . . . . . . . . . . . . . 73 9. Protocol Configuration Variables . . . . . . . . . . . . . . . 77
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74 9.1. Local Mobility Anchor - Configuration Variables . . . . . 77
11. Security Considerations . . . . . . . . . . . . . . . . . . . 75 9.2. Mobile Access Gateway - Configuration Variables . . . . . 78
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 76 9.3. Proxy Mobile IPv6 Domain - Configuration Variables . . . . 79
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 77 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 79
13.1. Normative References . . . . . . . . . . . . . . . . . . . 77 11. Security Considerations . . . . . . . . . . . . . . . . . . . 80
13.2. Informative References . . . . . . . . . . . . . . . . . . 78 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 81
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 81
13.1. Normative References . . . . . . . . . . . . . . . . . . . 81
13.2. Informative References . . . . . . . . . . . . . . . . . . 82
Appendix A. Proxy Mobile IPv6 interactions with AAA Appendix A. Proxy Mobile IPv6 interactions with AAA
Infrastructure . . . . . . . . . . . . . . . . . . . 79 Infrastructure . . . . . . . . . . . . . . . . . . . 83
Appendix B. Routing State . . . . . . . . . . . . . . . . . . . . 79 Appendix B. Routing State . . . . . . . . . . . . . . . . . . . . 84
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 85
Intellectual Property and Copyright Statements . . . . . . . . . . 82 Intellectual Property and Copyright Statements . . . . . . . . . . 87
1. Introduction 1. Introduction
IP mobility for IPv6 hosts is specified in Mobile IPv6 [RFC-3775]. IP mobility for IPv6 hosts is specified in Mobile IPv6 [RFC-3775].
Mobile IPv6 requires client functionality in the IPv6 stack of a Mobile IPv6 requires client functionality in the IPv6 stack of a
mobile node. Exchange of signaling messages between the mobile node mobile node. Exchange of signaling messages between the mobile node
and home agent enables the creation and maintenance of a binding and home agent enables the creation and maintenance of a binding
between the mobile node's home address and its care-of-address. between the mobile node's home address and its care-of-address.
Mobility as specified in [RFC-3775] requires the IP host to send IP Mobility as specified in [RFC-3775] requires the IP host to send IP
mobility management signaling messages to the home agent, which is mobility management signaling messages to the home agent, which is
skipping to change at page 5, line 34 skipping to change at page 5, line 34
Proxy Mobile IPv6 domain refers to the network where the mobility Proxy Mobile IPv6 domain refers to the network where the mobility
management of a mobile node is handled using the Proxy Mobile IPv6 management of a mobile node is handled using the Proxy Mobile IPv6
protocol as defined in this specification. The Proxy Mobile IPv6 protocol as defined in this specification. The Proxy Mobile IPv6
domain includes local mobility anchors and mobile access gateways domain includes local mobility anchors and mobile access gateways
between which security associations can be set up and between which security associations can be set up and
authorization for sending Proxy Binding Updates on behalf of the authorization for sending Proxy Binding Updates on behalf of the
mobile nodes can be ensured. mobile nodes can be ensured.
Local Mobility Anchor (LMA) Local Mobility Anchor (LMA)
Local Mobility Anchor is the home agent for the mobile node in the Local Mobility Anchor is the home agent for the mobile node in a
Proxy Mobile IPv6 domain. It is the topological anchor point for Proxy Mobile IPv6 domain. It is the topological anchor point for
the mobile node's home network prefix and is the entity that the mobile node's home network prefix(es) and is the entity that
manages the mobile node's binding state. The local mobility manages the mobile node's binding state. The local mobility
anchor has the functional capabilities of a home agent as defined anchor has the functional capabilities of a home agent as defined
in Mobile IPv6 base specification [RFC-3775] with the additional in Mobile IPv6 base specification [RFC-3775] with the additional
capabilities required for supporting Proxy Mobile IPv6 protocol as capabilities required for supporting Proxy Mobile IPv6 protocol as
defined in this specification. defined in this specification.
Mobile Access Gateway (MAG) Mobile Access Gateway (MAG)
Mobile Access Gateway is a function that manages the mobility Mobile Access Gateway is a function that manages the mobility
related signaling for a mobile node that is attached to its access related signaling for a mobile node that is attached to its access
skipping to change at page 6, line 41 skipping to change at page 6, line 41
The local mobility anchor views this address as the Care-of The local mobility anchor views this address as the Care-of
Address of the mobile node and registers it in the Binding Cache Address of the mobile node and registers it in the Binding Cache
entry for that mobile node. When the transport network between entry for that mobile node. When the transport network between
the mobile access gateway and the local mobility anchor is an IPv4 the mobile access gateway and the local mobility anchor is an IPv4
network and if the care-of address that is registered at the local network and if the care-of address that is registered at the local
mobility anchor is an IPv4 address, the term, IPv4-Proxy-CoA is mobility anchor is an IPv4 address, the term, IPv4-Proxy-CoA is
used, as specified in [ID-IPV4-PMIP6]. used, as specified in [ID-IPV4-PMIP6].
Mobile Node's Home Network Prefix (MN-HNP) Mobile Node's Home Network Prefix (MN-HNP)
This is the on-link IPv6 prefix that is always present in the This is the prefix that is assigned to a given interface of a
Router Advertisements that the mobile node receives when it is mobile node and is always present in the Router Advertisement
attached to any of the access links in that Proxy Mobile IPv6 messages that the mobile node receives on any of the access links
domain. This home network prefix is topologically anchored at the in that Proxy Mobile IPv6 domain. There can also be multiple home
mobile node's local mobility anchor. The mobile node configures network prefixes assigned to a given interface of a mobile node
its interface with an address from this prefix. If the mobile and in which case all of those assigned prefixes will still be
node connects to the Proxy Mobile IPv6 domain through multiple managed as part of one mobility session. The mobile node
interfaces, simultaneously, each of the connected interfaces will configures its interface with one or more addresses from its home
be assigned a unique home network prefix and under a different network prefix(es). If the mobile node connects to the Proxy
mobility session. Mobile IPv6 domain through multiple interfaces, simultaneously,
each of the attached interfaces will be assigned a unique set of
home network prefixes and all the prefixes assigned to a given
interface of a mobile node will be managed under one mobility
session. Additionally, in some configurations the assigned prefix
can be of 128-bit prefix length. Ex: Home network prefixes P1, P2
assigned to interface I1 will be managed under one mobility
session and prefixes P3, P4, P5 assigned to interface I2 of the
mobile node will be managed under a different mobility session.
Mobile Node's Home Address (MN-HoA) Mobile Node's Home Address (MN-HoA)
MN-HoA is an address from a mobile node's home network prefix MN-HoA is an address from a mobile node's home network prefix.
in a Proxy Mobile IPv6 domain. The mobile node will be able to The mobile node will be able to use this address as long as it is
use this address as long as it is attached to the access attached to the access network that is in the scope of that Proxy
network that is in the scope of that Proxy Mobile IPv6 domain. Mobile IPv6 domain. If the mobile node uses more than one address
Unlike in Mobile IPv6 where the home agent is aware of the home from its home network prefix(es), any one of these addresses is
address of the mobile node, in Proxy Mobile IPv6, the mobility referred to as mobile node's home address. Unlike in Mobile IPv6
entities are only aware of the mobile node's home network where the home agent is aware of the home address of the mobile
prefix and are not always aware of the exact address(es) that node, in Proxy Mobile IPv6, the mobility entities are only aware
the mobile node configured on its interface from that prefix. of the mobile node's home network prefix(es) and are not always
However, in some configurations and based on the enabled aware of the exact address(es) that the mobile node configured on
address configuration modes on the access link, the mobility its interface from its home network prefix(es). However, in some
entities in the network can be certain about the exact address configurations and based on the enabled address configuration
configured by the mobile node. 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 Mobile Node's Home Link
This is the point-to-point link on which the mobile node obtained This is the link on which the mobile node obtained its Layer-3
its Layer-3 address configuration for the attached interface after address configuration for the attached interface after it moved
it moved into that Proxy Mobile IPv6 domain. This is the link into that Proxy Mobile IPv6 domain. This is the link that
that conceptually follows the mobile node. The network will conceptually follows the mobile node. The network will ensure the
ensure the mobile node always sees this link with respect to the mobile node always sees this link with respect to the layer-3
layer-3 network configuration, on any access link that it attaches network configuration, on any access link that it attaches to in
to in that Proxy Mobile IPv6 domain. that Proxy Mobile IPv6 domain.
Multihomed Mobile Node Multihomed Mobile Node
A mobile node that connects to the same Proxy Mobile IPv6 domain A mobile node that connects to the same Proxy Mobile IPv6 domain
through more than one interface and uses these interfaces through more than one interface and uses these interfaces
simultaneously is referred to as a multihomed mobile node. simultaneously is referred to as a multihomed mobile node.
Mobile Node Identifier (MN-Identifier) Mobile Node Identifier (MN-Identifier)
The identity of a mobile node in the Proxy Mobile IPv6 domain. The identity of a mobile node in the Proxy Mobile IPv6 domain.
skipping to change at page 8, line 23 skipping to change at page 8, line 32
node. The mobility entities in the Proxy Mobile IPv6 domain node. The mobility entities in the Proxy Mobile IPv6 domain
require access to these parameters for providing the mobility require access to these parameters for providing the mobility
management to a given mobile node. The specific details on how management to a given mobile node. The specific details on how
the network entities obtain this policy profile is outside the the network entities obtain this policy profile is outside the
scope of this document. scope of this document.
Proxy Binding Update (PBU) Proxy Binding Update (PBU)
A binding registration request message sent by a mobile access A binding registration request message sent by a mobile access
gateway to a mobile node's local mobility anchor for establishing gateway to a mobile node's local mobility anchor for establishing
a binding between the mobile node's MN-HNP and the Proxy-CoA. a binding between the mobile node's home network prefix(es)
assigned to a given interface of a mobile node and its current
care-of address (Proxy-CoA).
Proxy Binding Acknowledgement (PBA) Proxy Binding Acknowledgement (PBA)
A binding registration reply message sent by a local mobility A binding registration reply message sent by a local mobility
anchor in response to a Proxy Binding Update request message that anchor in response to a Proxy Binding Update request message that
it received from a mobile access gateway. it received from a mobile access gateway.
Per-MN-Prefix & Shared-Prefix Models Per-MN-Prefix & Shared-Prefix Models
The term, Per-MN-Prefix model, is used to refer to an addressing The term, Per-MN-Prefix model, is used to refer to an addressing
skipping to change at page 9, line 22 skipping to change at page 9, line 27
mobility management support to a mobile node, without requiring the mobility management support to a mobile node, without requiring the
participation of the mobile node in any IP mobility related participation of the mobile node in any IP mobility related
signaling. The mobility entities in the network will track the signaling. The mobility entities in the network will track the
mobile node's movements and will initiate the mobility signaling and mobile node's movements and will initiate the mobility signaling and
set up the required routing state. set up the required routing state.
The core functional entities in the NETLMM infrastructure are the The core functional entities in the NETLMM infrastructure are the
Local Mobility Anchor (LMA) and the Mobile Access Gateway (MAG). The Local Mobility Anchor (LMA) and the Mobile Access Gateway (MAG). The
local mobility anchor is responsible for maintaining the mobile local mobility anchor is responsible for maintaining the mobile
node's reachability state and is the topological anchor point for the node's reachability state and is the topological anchor point for the
mobile node's home network prefix. The mobile access gateway is the mobile node's home network prefix(es). The mobile access gateway is
entity that performs the mobility management on behalf of a mobile the entity that performs the mobility management on behalf of a
node and it resides on the access link where the mobile node is mobile node and it resides on the access link where the mobile node
anchored. The mobile access gateway is responsible for detecting the is anchored. The mobile access gateway is responsible for detecting
mobile node's movements to and from the access link and for the mobile node's movements to and from the access link and for
initiating binding registrations to the mobile node's local mobility initiating binding registrations to the mobile node's local mobility
anchor. The architecture of a Proxy Mobile IPv6 domain is shown in anchor. The architecture of a Proxy Mobile IPv6 domain is shown in
Figure 1. Figure 1.
+----+ +----+ +----+ +----+
|LMA1| |LMA2| |LMA1| |LMA2|
+----+ +----+ +----+ +----+
LMAA1 -> | | <-- LMAA2 LMAA1 -> | | <-- LMAA2
| | | |
\\ //\\ \\ //\\
skipping to change at page 10, line 25 skipping to change at page 10, line 25
( \\ Network // \\ ) ( \\ Network // \\ )
+------\\--------//------------\\-+ +------\\--------//------------\\-+
\\ // \\ \\ // \\
\\ // \\ \\ // \\
\\ // \\ \\ // \\
Proxy-CoA1--> | | <-- Proxy-CoA2 Proxy-CoA1--> | | <-- Proxy-CoA2
+----+ +----+ +----+ +----+
|MAG1|-----{MN2} |MAG2| |MAG1|-----{MN2} |MAG2|
+----+ | +----+ +----+ | +----+
| | | | | |
MN-HoA1 --> | MN-HoA2 | <-- MN-HoA3 MN-HNP1 --> | MN-HNP2 | <-- MN-HNP3, MN-HNP4
{MN1} {MN3} {MN1} {MN3}
Figure 1: Proxy Mobile IPv6 Domain Figure 1: Proxy Mobile IPv6 Domain
Once a mobile node enters a Proxy Mobile IPv6 domain and attaches to 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 an access link, the mobile access gateway on that access link, after
identifying the mobile node and acquiring its identity, will identifying the mobile node and acquiring its identity, will
determine if the mobile node is authorized for the network-based determine if the mobile node is authorized for the network-based
mobility management service. mobility management service.
If the network determines that the network-based mobility management If the network determines that the network-based mobility management
service needs to be offered to that mobile node, the network will service needs to be offered to that mobile node, the network will
ensure that the mobile node using any of the address configuration ensure that the mobile node using any of the address configuration
mechanisms permitted by the network will be able to obtain the mechanisms permitted by the network will be able to obtain the
address configuration on the connected interface and move anywhere in address configuration on the connected interface and move anywhere in
that Proxy Mobile IPv6 domain. The obtained address configuration that Proxy Mobile IPv6 domain. The obtained address configuration
includes the address(es) from its home network prefix, the default- includes the address(es) from its home network prefix(es), the
router address on the link and other related configuration default-router address on the link and other related configuration
parameters. From the perspective of the mobile node, the entire parameters. From the perspective of the mobile node, the entire
Proxy Mobile IPv6 domain appears as a single link, the network Proxy Mobile IPv6 domain appears as a single link, the network
ensures that the mobile node believes it is always on the same link ensures that the mobile node believes it is always on the same link
where it obtained its initial address configuration, even after where it obtained its initial address configuration, even after
changing its point of attachment in that network. changing its point of attachment in that network.
The mobile node may be an IPv4-only node, IPv6-only node or a dual The mobile node may be an IPv4-only node, IPv6-only node or a dual
IPv4/IPv6 node. Based on what is enabled in the network for that 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, IPv6 or mobile node, the mobile node will be able to obtain an IPv4, IPv6 or
dual IPv4/IPv6 addresses and move anywhere in that Proxy Mobile IPv6 dual IPv4/IPv6 addresses and move anywhere in that Proxy Mobile IPv6
domain. However, the specific details related to the IPv4 addressing domain. However this specification only supports IPv6 address
or IPv4 transport support are specified in the companion document mobility and when the transport network is IPv6 network. The support
[ID-IPV4-PMIP6]. for IPv4 addressing or IPv4 transport network is specified in the
companion document [ID-IPV4-PMIP6].
If the mobile node connects to the Proxy Mobile IPv6 domain through If the mobile node connects to the Proxy Mobile IPv6 domain through
multiple interfaces and over multiple access networks, the network multiple interfaces and over multiple access networks, the network
will allocate a unique home network prefix for each of the connected will allocate a unique set of home network prefixes for each of the
interfaces. The mobile node will be able to configure an address(es) connected interfaces. The mobile node will be able to configure
on those interfaces from the respective home network prefixes. address(es) on those interfaces from the respective home network
However, if the mobile node performs an inter-interface handoff by prefix(es). However, if the mobile node performs an inter-interface
moving its address configuration from one interface to the other and handoff by moving its address configuration from one interface to the
if the local mobility anchor receives a handoff hint from the serving other and if the local mobility anchor receives a handoff hint from
mobile access gateway about the same, the local mobility anchor will the serving mobile access gateway about the same, the local mobility
assign the same home network prefix that it assigned to the anchor will assign the same home network prefix(es) that it
previously attached interface. previously assigned prior to the handoff. The mobile node will also
be able to perform an 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 | | MAG | | LMA |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| | | | | |
MN Attached | | MN Attached | |
| | | | | |
| MN Attached Event from MN/Network | | MN Attached Event from MN/Network |
| (Acquire MN-Id and Profile) | | (Acquire MN-Id and Profile) |
| | | | | |
|--- Rtr Sol --------->| | |--- Rtr Sol --------->| |
| | | | | |
| |--- PBU ------------->| | |--- PBU ------------->|
| | | | | |
| | Accept PBU | | Accept PBU
| | (Allocate MN-HNP, Setup BCE and Tunnel) | | (Allocate MN-HNP(s), Setup BCE and Tunnel)
| | | | | |
| |<------------- PBA ---| | |<------------- PBA ---|
| | | | | |
| Accept PBA | | Accept PBA |
| (Setup Tunnel and Routing) | | (Setup Tunnel and Routing) |
| | | | | |
| |==== Bi-Dir Tunnel ===| | |==== Bi-Dir Tunnel ===|
| | | | | |
|<--------- Rtr Adv ---| | |<--------- Rtr Adv ---| |
| | | | | |
IP Address | | IP Address | |
Configuration | | Configuration | |
| | | | | |
Figure 2: Mobile Node Attachment - Signaling Call Flow Figure 2: Mobile Node Attachment - Signaling Call Flow
Figure 2 shows the signaling call flow when the mobile node enters Figure 2 shows the signaling call flow when the mobile node enters
the Proxy Mobile IPv6 domain. 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 For updating the local mobility anchor about the current location of
the mobile node, the mobile access gateway sends a Proxy Binding the mobile node, the mobile access gateway sends a Proxy Binding
Update message to the mobile node's local mobility anchor. Upon Update message to the mobile node's local mobility anchor. Upon
accepting this Proxy Binding Update message, the local mobility accepting this Proxy Binding Update message, the local mobility
anchor sends a Proxy Binding Acknowledgement message including the anchor sends a Proxy Binding Acknowledgement message including the
mobile node's home network prefix. It also creates the Binding Cache mobile node's home network prefix(es). It also creates the Binding
entry and sets up its endpoint of the bi-directional tunnel to the Cache entry and sets up its endpoint of the bi-directional tunnel to
mobile access gateway. the mobile access gateway.
The mobile access gateway on receiving the Proxy Binding The mobile access gateway on receiving the Proxy Binding
Acknowledgement message sets up its endpoint of the bi-directional Acknowledgement message sets up its endpoint of the bi-directional
tunnel to the local mobility anchor and also sets up the data path tunnel to the local mobility anchor and also sets up the data path
for the mobile node's traffic. At this point the mobile access for the mobile node's traffic. At this point the mobile access
gateway will have all the required information for emulating the gateway will have all the required information for emulating the
mobile node's home link. It sends Router Advertisement messages to mobile node's home link. It sends Router Advertisement messages to
the mobile node on the access link advertising the mobile node's home the mobile node on the access link advertising the mobile node's home
network prefix as the hosted on-link-prefix. network prefix(es) as the hosted on-link-prefix(es).
The mobile node on receiving these Router Advertisement messages on The mobile node on receiving these Router Advertisement messages on
the access link will attempt to configure its interface either using the access link will attempt to configure its interface either using
stateful or stateless address configuration modes, based on the modes stateful or stateless address configuration modes, based on the modes
that are permitted on that access link. At the end of a successful that are permitted on that access link. At the end of a successful
address configuration procedure, the mobile node will end up with an address configuration procedure, the mobile node will end up with one
address from its home network prefix. or more addresses from its home network prefixes(es).
Once the address configuration is complete, the mobile node has a Once the address configuration is complete, the mobile node has one
valid address from its home network prefix at the current point of or more valid addresses from its home network prefix(es) at the
attachment. The serving mobile access gateway and the local mobility current point of attachment. The serving mobile access gateway and
anchor also have proper routing states for handling the traffic sent the local mobility anchor also have proper routing states for
to and from the mobile node using an address from its home network handling the traffic sent to and from the mobile node using any one
prefix. or more of the addresses from its home network prefix(es).
The local mobility anchor, being the topological anchor point for the The local mobility anchor, being the topological anchor point for the
mobile node's home network prefix, receives any packets that are sent mobile node's home network prefix(es), receives any packets that are
to the mobile node by any node in the network. The local mobility sent to the mobile node by any node in the network. The local
anchor forwards these received packets to the mobile access gateway mobility anchor forwards these received packets to the mobile access
through the bi-directional tunnel. The mobile access gateway on gateway through the bi-directional tunnel. The mobile access gateway
other end of the tunnel, after receiving the packet, removes the 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 outer header and forwards the packet on the access link to the mobile
node. However, in some cases the traffic sent from a correspondent node. However, in some cases the traffic sent from a correspondent
node that is locally connected to the mobile access gateway may not 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 be received by the local mobility anchor and may be routed locally by
the mobile access gateway. the mobile access gateway.
The mobile access gateway acts as the default router on the access The mobile access gateway acts as the default router on the access
link. Any packet that the mobile node sends to any correspondent link. Any packet that the mobile node sends to any correspondent
node will be received by the mobile access gateway and will be sent node will be received by the mobile access gateway and will be sent
to its local mobility anchor through the bi-directional tunnel. The to its local mobility anchor through the bi-directional tunnel. The
skipping to change at page 14, line 33 skipping to change at page 14, line 33
| | | (Acquire MN-Id and Profile) | | | (Acquire MN-Id and Profile)
| | | | | | | |
|--- Rtr Sol ------------------------------------->| |--- Rtr Sol ------------------------------------->|
.... ....
Registration steps as in fig 2. Registration steps as in fig 2.
.... ....
| | |==Bi-Dir Tunnel=| | | |==Bi-Dir Tunnel=|
| | | | | | | |
|<------------------------------------ Rtr Adv ----| |<------------------------------------ Rtr Adv ----|
| | | | | | | |
MN retains HoA/HNP MN retains HoA/HNP(s)
| | | | | | | |
Figure 3: Mobile Node Handoff - Signaling Call Flow Figure 3: Mobile Node Handoff - Signaling Call Flow
Figure 3 shows the signaling call flow for the mobile node's handoff Figure 3 shows the signaling call flow for the mobile node's handoff
from previously attached mobile access gateway (p-MAG) to the newly from previously attached mobile access gateway (p-MAG) to the newly
attached mobile access gateway (n-MAG). This call flow reflects only attached mobile access gateway (n-MAG). This call flow reflects only
a specific message ordering, it is possible the registration message a specific message ordering, it is possible the registration message
from the n-MAG may arrive before the de-registration message from the from the n-MAG may arrive before the de-registration message from the
p-MAG arrives. p-MAG arrives.
skipping to change at page 15, line 17 skipping to change at page 15, line 17
update request was received and once it accepts the request will wait update request was received and once it accepts the request will wait
for certain amount of time for allowing the mobile access gateway on for certain amount of time for allowing the mobile access gateway on
the new link to update the binding. However, if it does not receive the new link to update the binding. However, if it does not receive
any binding update request within that given amount of time, it will any binding update request within that given amount of time, it will
delete the binding cache entry. delete the binding cache entry.
The mobile access gateway on the new access link upon detecting the The mobile access gateway on the new access link upon detecting the
mobile node on its access link will signal the local mobility anchor mobile node on its access link will signal the local mobility anchor
for updating the binding state. Once that signaling is complete, the for updating the binding state. Once that signaling is complete, the
mobile node will continue to receive the Router Advertisements mobile node will continue to receive the Router Advertisements
containing its home network prefix, making it believe it is still on containing its home network prefix(es) that were assigned to that
the same link and it will use the same address configuration on the mobility session, making it believe it is still on the same link and
new access link. it will be able to use the same address configuration on the new
access link.
4. Proxy Mobile IPv6 Protocol Security 4. Proxy Mobile IPv6 Protocol Security
The signaling messages, Proxy Binding Update and Proxy Binding The signaling messages, Proxy Binding Update and Proxy Binding
Acknowledgement, exchanged between the mobile access gateway and the Acknowledgement, exchanged between the mobile access gateway and the
local mobility anchor MUST be protected using end-to-end security local mobility anchor MUST be protected using end-to-end security
association(s) offering integrity and data origin authentication. association(s) offering integrity and data origin authentication.
The mobile access gateway and the local mobility anchor MUST The mobile access gateway and the local mobility anchor MUST
implement IPsec for protecting the Proxy Mobile IPv6 signaling implement IPsec for protecting the Proxy Mobile IPv6 signaling
messages [RFC-4301]. That is, IPsec is a mandatory to implement messages [RFC-4301]. That is, IPsec is a mandatory to implement
security mechanism. However, additional documents may specify security mechanism. However, additional documents may specify
alternative mechanisms. As in Mobile IPv6 [RFC-3775], the use of alternative mechanisms and the mobility entities can enable a
IPsec for protecting mobile node's data traffic is optional. specific mechanism for securing Proxy Mobile IPv6 signaling messages,
either based on a static configuration or after a dynamic negotiation
using any standard security negotiation protocols. As in Mobile IPv6
[RFC-3775], the use of IPsec for protecting mobile node's data
traffic is optional.
IPsec ESP [RFC-4303] in transport mode with mandatory integrity IPsec ESP [RFC-4303] in transport mode with mandatory integrity
protection SHOULD be used for protecting the signaling messages. protection SHOULD be used for protecting the signaling messages.
Confidentiality protection of these messages is not required. Confidentiality protection of these messages is not required.
IPsec ESP [RFC-4303] in tunnel mode MAY be used to protect the mobile
node's tunneled data traffic, if protection of data traffic is
required.
IKEv2 [RFC-4306] SHOULD be used to set up security associations IKEv2 [RFC-4306] SHOULD be used to set up security associations
between the mobile access gateway and the local mobility anchor to between the mobile access gateway and the local mobility anchor to
protect the Proxy Binding Update and Proxy Binding Acknowledgement protect the Proxy Binding Update and Proxy Binding Acknowledgement
messages. The mobile access gateway and the local mobility anchor messages. The mobile access gateway and the local mobility anchor
can use any of the authentication mechanisms, as specified in [RFC- can use any of the authentication mechanisms, as specified in [RFC-
4306], for mutual authentication. 4306], for mutual authentication.
The Mobile IPv6 specification [RFC-3775] requires the home agent to The Mobile IPv6 specification [RFC-3775] requires the home agent to
prevent a mobile node from creating security associations or creating prevent a mobile node from creating security associations or creating
binding cache entries for another mobile node's home address. In the binding cache entries for another mobile node's home address. In the
skipping to change at page 16, line 16 skipping to change at page 16, line 25
anchor MUST restrict the creation and manipulation of proxy bindings anchor MUST restrict the creation and manipulation of proxy bindings
to specifically authorized mobile access gateways and prefixes. The to specifically authorized mobile access gateways and prefixes. The
local mobility anchor MUST be locally configurable to authorize such local mobility anchor MUST be locally configurable to authorize such
specific combinations. Additional mechanisms such as a policy store specific combinations. Additional mechanisms such as a policy store
or AAA may be employed, but these are outside the scope of this or AAA may be employed, but these are outside the scope of this
specification. specification.
Unlike in Mobile IPv6 [RFC-3775], these signaling messages do not Unlike in Mobile IPv6 [RFC-3775], these signaling messages do not
carry either the Home Address destination option or the Type 2 carry either the Home Address destination option or the Type 2
Routing header and hence the policy entries and security association Routing header and hence the policy entries and security association
selectors stay the same. selectors stay the same and require no special IPsec related
considerations.
4.1. Peer Authorization Database (PAD) Example Entries 4.1. Peer Authorization Database (PAD) Example Entries
This section describes PAD entries [RFC-4301] on the mobile access This section describes PAD entries [RFC-4301] on the mobile access
gateway and the local mobility anchor. The PAD entries are only gateway and the local mobility anchor. The PAD entries are only
example configurations. Note that the PAD is a logical concept and a example configurations. Note that the PAD is a logical concept and a
particular mobile access gateway or a local mobility anchor particular mobile access gateway or a local mobility anchor
implementation can implement the PAD in any implementation specific implementation can implement the PAD in any implementation specific
manner. The PAD state may also be distributed across various manner. The PAD state may also be distributed across various
databases in a specific implementation. databases in a specific implementation.
skipping to change at page 18, line 20 skipping to change at page 18, line 29
o The identifier of the registered mobile node, MN-Identifier. This o The identifier of the registered mobile node, MN-Identifier. This
identifier is obtained from the Mobile Node Identifier Option identifier is obtained from the Mobile Node Identifier Option
[RFC-4283] present in the received Proxy Binding Update request. [RFC-4283] present in the received Proxy Binding Update request.
o The link-layer identifier of the mobile node's connected interface o The link-layer identifier of the mobile node's connected interface
on the access link. This identifier can be acquired from the on the access link. This identifier can be acquired from the
Mobile Node Link-layer Identifier option, present in the received Mobile Node Link-layer Identifier option, present in the received
Proxy Binding Update request. If the option was not present in Proxy Binding Update request. If the option was not present in
the request, the value MUST be set to ALL_ZERO. the request, the value MUST be set to ALL_ZERO.
o The Link-local address of the mobile access gateway on the point- 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 to-point link shared with the mobile node. This is generated by
the local mobility anchor after accepting the initial Proxy the local mobility anchor after accepting the initial Proxy
Binding Update request. Binding Update request.
o The IPv6 home network prefix that is assigned to the mobile node's o List of IPv6 home network prefixes assigned to the mobile node's
connected interface. The home network prefix of the mobile node connected interface. The home network prefix(es) may have been
may have been statically configured in the mobile node's policy statically configured in the mobile node's policy profile, or,
profile, or, it may have been dynamically allocated by the local they may have been dynamically allocated by the local mobility
mobility anchor. The IPv6 home network prefix also includes the anchor. Each one of these prefix entries will also includes the
corresponding prefix length. corresponding prefix length.
o The tunnel interface identifier (If-Id) of the bi-directional o The tunnel interface identifier (If-Id) of the bi-directional
tunnel between the local mobility anchor and the mobile access tunnel between the local mobility anchor and the mobile access
gateway where the mobile node is currently anchored. This is gateway where the mobile node is currently anchored. This is
internal to the local mobility anchor. The tunnel interface internal to the local mobility anchor. The tunnel interface
identifier is acquired during the tunnel creation. identifier is acquired during the tunnel creation.
o The access technology type, using which the mobile node is o The access technology type, using which the mobile node is
currently attached. This is obtained from the Access Technology currently attached. This is obtained from the Access Technology
Type option, present in the Proxy Binding Update request. Type option, present in the Proxy Binding Update request.
o The 64-bit timestamp value of the most recently accepted Proxy o The 64-bit timestamp value of the most recently accepted Proxy
Binding Update request sent for this mobile node. This is the Binding Update request sent for this mobile node. This is the
time-of-day on the local mobility anchor, when the message was time-of-day on the local mobility anchor, when the message was
received. If the Timestamp option is not present in the Proxy received. If the Timestamp option is not present in the Proxy
Binding Update request (i.e., when the sequence number based Binding Update request (i.e., when the sequence number based
scheme is in use), the value MUST be set to ALL_ZERO. scheme is in use), the value MUST be set to ALL_ZERO.
Typically, the mobile node's home network prefix is the key for Typically, any one of the mobile node's home network prefixes from
locating a Binding Cache entry in all cases except when there has its mobility session is the key for locating a Binding Cache entry in
been an handoff of the mobile node's session to a new mobile access all cases except when there has been an handoff of the mobile node's
gateway and that mobile access gateway is unaware of the home network session to a new mobile access gateway and that mobile access gateway
prefix that was assigned to the handed of session. In such handoff is unaware of the home network prefix(es) assigned to that mobility
cases, the Binding Cache entry can be located under the session. In such handoff cases, the Binding Cache entry can be
considerations specified in Section 5.4.1. located under the considerations specified in Section 5.4.1.
5.2. Supported Home Network Prefix Models 5.2. Supported Home Network Prefix Models
This specification supports the Per-MN-Prefix model and does not This specification supports the Per-MN-Prefix model and does not
support the Shared-Prefix model. As per the Per-MN-Prefix model, support the Shared-Prefix model. As per the Per-MN-Prefix model, a
there will be a unique home network prefix assigned to each mobile prefix assigned to a mobile node is for that mobile node's exclusive
node and no other node shares an address (other than the Subnet- use and no other node shares an address from that prefix (other than
Router anycast address [RFC-4291] which is used by the mobile access the Subnet-Router anycast address [RFC-4291] which is used by the
gateway hosting the prefix on that link). The assigned prefix is mobile access gateway hosting that prefix on that link).
unique to a mobile node and also unique to a given interface of the
mobile node. If the mobile node attaches to the Proxy Mobile IPv6
domain through multiple interfaces and simultaneously, each of those
connected interfaces will be assigned a different prefix.
The mobile node's home network prefix is always hosted on the access There may be more than one prefix assigned to a given interface of
link where the mobile node is anchored. Conceptually, the entire the mobile node and all of those assigned prefixes are unique to that
home network prefix follows the mobile node as it moves within the mobile node and all are part of one mobility session. If the mobile
Proxy Mobile IPv6 domain. The local mobility anchor is not required node attaches to the Proxy Mobile IPv6 domain through multiple
to perform any proxy ND operations [RFC-4861] for defending the interfaces and simultaneously, each of the attached interfaces will
mobile node's home address on the home link. However, from the be assigned one or more unique prefixes and all of the assigned
routing perspective, the home network prefix is topologically prefixes to a given interface will be managed under a different
anchored on the local mobility anchor. 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 proxy ND operations [RFC-4861] 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 5.3. Signaling Considerations
This section provides the rules for processing the signaling This section provides the rules for processing the signaling
messages. The processing rules specified in this section and other messages. The processing rules specified in this section and other
related sections are chained and are in a specific order. When related sections are chained and are in a specific order. When
applying these considerations for processing the signaling messages, applying these considerations for processing the signaling messages,
the specified order MUST be maintained. the specified order MUST be maintained.
5.3.1. Processing Binding Registrations 5.3.1. Processing Binding Registrations
skipping to change at page 21, line 5 skipping to change at page 21, line 26
not authorized for the network-based mobility management not authorized for the network-based mobility management
service, it MUST reject the request and send a Proxy Binding service, it MUST reject the request and send a Proxy Binding
Acknowledgement message with Status field set to Acknowledgement message with Status field set to
PROXY_REG_NOT_ENABLED (Proxy Registration not enabled). PROXY_REG_NOT_ENABLED (Proxy Registration not enabled).
9. The local mobility anchor MUST apply the considerations 9. The local mobility anchor MUST apply the considerations
specified in Section 5.5, for processing the Sequence Number specified in Section 5.5, for processing the Sequence Number
field and the Timestamp option (if present), in the Proxy field and the Timestamp option (if present), in the Proxy
Binding Update request. Binding Update request.
10. If the Home Network Prefix option (containing either ALL_ZERO or 10. If there is no Home Network Prefix option(s) (with any value)
some prefix value) is not present in the Proxy Binding Update present in the Proxy Binding Update request, the local mobility
request, the local mobility anchor MUST reject the request and anchor MUST reject the request and send a Proxy Binding
send a Proxy Binding Acknowledgement message with Status field Acknowledgement message with Status field set to
set to MISSING_HOME_NETWORK_PREFIX_OPTION (Missing home network MISSING_HOME_NETWORK_PREFIX_OPTION (Missing home network prefix
prefix option). option).
11. If the Handoff Indicator option is not present in the Proxy 11. If the Handoff Indicator option is not present in the Proxy
Binding Update request, the local mobility anchor MUST reject Binding Update request, the local mobility anchor MUST reject
the request and send a Proxy Binding Acknowledgement message the request and send a Proxy Binding Acknowledgement message
with Status field set to MISSING_HANDOFF_INDICATOR_OPTION with Status field set to MISSING_HANDOFF_INDICATOR_OPTION
(Missing handoff indicator option). (Missing handoff indicator option).
12. If the Access Technology Type option is not present in the Proxy 12. If the Access Technology Type option is not present in the Proxy
Binding Update request, the local mobility anchor MUST reject Binding Update request, the local mobility anchor MUST reject
the request and send a Proxy Binding Acknowledgement message the request and send a Proxy Binding Acknowledgement message
skipping to change at page 22, line 7 skipping to change at page 22, line 25
* For all other cases, considerations from Section 5.3.4 * For all other cases, considerations from Section 5.3.4
(Binding Lifetime Extension - After handoff) MUST be applied. (Binding Lifetime Extension - After handoff) MUST be applied.
14. When sending the Proxy Binding Acknowledgement message with any 14. When sending the Proxy Binding Acknowledgement message with any
Status field value, the message MUST be constructed as specified Status field value, the message MUST be constructed as specified
in Section 5.3.6. in Section 5.3.6.
5.3.2. Initial Binding Registration (New Mobility Session) 5.3.2. Initial Binding Registration (New Mobility Session)
1. If the Home Network Prefix option present in the Proxy Binding 1. If there is at least one instance of Home Network Prefix option
Update request has the value set to ALL_ZERO, the local mobility present in the Proxy Binding Update request with the prefix value
anchor MUST allocate a prefix and assign it to a new mobility set to ALL_ZERO, the local mobility anchor MUST allocate one or
session created for the mobile node. The local mobility anchor more home network prefix(es) to the mobile node and assign it to
MUST ensure the allocated prefix is not in use by any other node the new mobility session created for the mobile node. The local
or mobility session. 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 attached interface, can be
based on a global policy or a policy specific to that mobile
node. However, when stateful address autoconfiguration using
DHCPv6 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 2. If the local mobility anchor is unable to allocate any home
network prefix for the mobile node, it MUST reject the request network prefix for the mobile node, it MUST reject the request
and send a Proxy Binding Acknowledgement message with Status and send a Proxy Binding Acknowledgement message with Status
field set to 130 (Insufficient resources). field set to 130 (Insufficient resources).
3. If the Home Network Prefix option present in the request has a 3. If there are one or more Home Network Prefix options present in
specific prefix value, the local mobility anchor before accepting the Proxy Binding Update request (with each of the prefixes set
that request, MUST ensure the prefix is owned by the local to a NON_ZERO value), the local mobility anchor before accepting
mobility anchor and further the mobile node is authorized to use that request, MUST ensure each one of those prefixes is owned by
that prefix. If the mobile node is not authorized to use that the local mobility anchor and further the mobile node is
prefix, the local mobility anchor MUST reject the request and authorized to use these prefixes. If the mobile node is not
send a Proxy Binding Acknowledgement message with Status field authorized to use any one or more of those prefixes, the local
set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (Mobile node not mobility anchor MUST reject the request and send a Proxy Binding
authorized to use that prefix). Acknowledgement message with 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 4. Upon accepting the request, the local mobility anchor MUST create
a Binding Cache entry for the mobile node. It must set the a Binding Cache entry for the mobile node. It must set the
fields in the Binding Cache entry to the accepted values for that fields in the Binding Cache entry to the accepted values for that
registration. registration.
5. If there is no existing bi-directional tunnel to the mobile 5. If there is no existing bi-directional tunnel to the mobile
access gateway that sent the request, the local mobility anchor access gateway that sent the request, the local mobility anchor
MUST establish a bi-directional tunnel to that mobile access MUST establish a bi-directional tunnel to that mobile access
gateway. Considerations from Section 5.6.1 MUST be applied for gateway. Considerations from Section 5.6.1 MUST be applied for
managing the dynamically created bi-directional tunnel. managing the dynamically created bi-directional tunnel.
6. The local mobility anchor MUST create a prefix route over the 6. The local mobility anchor MUST create a prefix route(s) over the
tunnel to the mobile access gateway for forwarding any traffic tunnel to the mobile access gateway for forwarding any traffic
received for the mobile node's home network prefix. The created received for the mobile node's home network prefix(es) associated
tunnel and routing state MUST result in the forwarding behavior with this mobility session. The created tunnel and the routing
on the local mobility anchor as specified in Section 5.6.2. 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 7. The local mobility anchor MUST send the Proxy Binding
Acknowledgement message with the Status field set to 0 (Proxy Acknowledgement message with the Status field set to 0 (Proxy
Binding Update Accepted). The message MUST be constructed as Binding Update Accepted). The message MUST be constructed as
specified in Section 5.3.6. specified in Section 5.3.6.
5.3.3. Binding Lifetime Extension (No handoff) 5.3.3. Binding Lifetime Extension (No handoff)
1. Upon accepting the Proxy Binding Update request for extending the 1. Upon accepting the Proxy Binding Update request for extending the
binding lifetime, received from the same mobile access gateway binding lifetime, received from the same mobile access gateway
skipping to change at page 23, line 29 skipping to change at page 24, line 15
5.3.4. Binding Lifetime Extension (After handoff) 5.3.4. Binding Lifetime Extension (After handoff)
1. Upon accepting the Proxy Binding Update request for extending the 1. Upon accepting the Proxy Binding Update request for extending the
binding lifetime, received from a new mobile access gateway (if 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 Binding Cache entry does not match
the Proxy-CoA address in the request) where the mobile node's the Proxy-CoA address in the request) where the mobile node's
session is handed off, the local mobility anchor MUST update the session is handed off, the local mobility anchor MUST update the
Binding Cache entry with the accepted registration values. Binding Cache entry with the accepted registration values.
2. The local mobility anchor MUST remove the previously created 2. The local mobility anchor MUST remove the previously created
route for the mobile node's home network prefix. Additionally, route(s) for the mobile node's home network prefix(es) associated
if there are no other mobile node sessions sharing the with this mobility session. Additionally, if there are no other
dynamically created bi-directional tunnel to the previous mobile mobile node sessions sharing the dynamically created bi-
access gateway, the tunnel MUST be deleted applying directional tunnel to the previous mobile access gateway, the
considerations from section 5.6.1 (if the tunnel is a dynamically tunnel SHOULD be deleted applying considerations from section
created tunnel and not a fixed pre-established tunnel). 5.6.1 (if the tunnel is a dynamically created tunnel and not a
fixed pre-established tunnel).
3. If there is no existing bi-directional tunnel to the mobile 3. If there is no existing bi-directional tunnel to the mobile
access gateway that sent the request, the local mobility anchor access gateway that sent the request, the local mobility anchor
MUST establish a bi-directional tunnel to that mobile access MUST establish a bi-directional tunnel to that mobile access
gateway. Considerations from Section 5.6.1 MUST be applied for gateway. Considerations from Section 5.6.1 MUST be applied for
managing the dynamically created bi-directional tunnel. managing the dynamically created bi-directional tunnel.
4. The local mobility anchor MUST create a prefix route over the 4. The local mobility anchor MUST create prefix route(s) over the
tunnel to the mobile access gateway for forwarding any traffic tunnel to the mobile access gateway for forwarding any traffic
received for the mobile node's home network prefix. The created received for the mobile node's home network prefix(es) associated
tunnel and routing state MUST result in the forwarding behavior with that mobility session. The created tunnel and routing state
on the local mobility anchor as specified in Section 5.6.2. 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 5. The local mobility anchor MUST send the Proxy Binding
Acknowledgement message with the Status field set to 0 (Proxy Acknowledgement message with the Status field set to 0 (Proxy
Binding Update Accepted). The message MUST be constructed as Binding Update Accepted). The message MUST be constructed as
specified in Section 5.3.6. specified in Section 5.3.6.
5.3.5. Binding De-Registration 5.3.5. Binding De-Registration
1. If the received Proxy Binding Update request with the lifetime 1. If the received Proxy Binding Update request with the lifetime
value of zero, has a Source Address in the IPv6 header (or the value of zero, has a Source Address in the IPv6 header (or the
skipping to change at page 25, line 10 skipping to change at page 25, line 38
o The local mobility anchor when sending the Proxy Binding o The local mobility anchor when sending the Proxy Binding
Acknowledgement message to the mobile access gateway MUST Acknowledgement message to the mobile access gateway MUST
construct the message as specified below. construct the message as specified below.
IPv6 header (src=LMAA, dst=Proxy-CoA) IPv6 header (src=LMAA, dst=Proxy-CoA)
Mobility header Mobility header
- BA /* P flag must be set to value of 1 */ - BA /* P flag must be set to value of 1 */
Mobility Options Mobility Options
- Mobile Node Identifier Option (mandatory) - Mobile Node Identifier Option (mandatory)
- Home Network Prefix option (mandatory) - Home Network Prefix option(s) (mandatory)
- Handoff Indicator option (mandatory) - Handoff Indicator option (mandatory)
- Access Technology Type option (mandatory) - Access Technology Type option (mandatory)
- Timestamp Option (optional) - Timestamp Option (optional)
- Mobile Node Link-layer Identifier option (optional) - Mobile Node Link-layer Identifier option (optional)
- Link-local Address option (optional) - Link-local Address option (optional)
Figure 6: Proxy Binding Acknowledgement message format Figure 6: Proxy Binding Acknowledgement message format
o The Source Address field in the IPv6 header of the message MUST be o The Source Address field in the IPv6 header of the message MUST be
set to the destination address of the received Proxy Binding set to the destination address of the received Proxy Binding
Update request. Update request.
o The Destination Address field in the IPv6 header of the 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 MUST be set to the source address of the received Proxy Binding
Update request. When there is no Alternate Care-of Address option Update request. When there is no Alternate Care-of Address option
present in the request, the destination address is the same as the present in the request, the destination address is the same as the
Proxy-CoA address, otherwise, the address may not be the same as Proxy-CoA address, otherwise, the address may not be the same as
the Proxy-CoA. the Proxy-CoA.
skipping to change at page 25, line 36 skipping to change at page 26, line 21
present in the request, the destination address is the same as the present in the request, the destination address is the same as the
Proxy-CoA address, otherwise, the address may not be the same as Proxy-CoA address, otherwise, the address may not be the same as
the Proxy-CoA. the Proxy-CoA.
o The Mobile Node Identifier option [RFC-4283] MUST be present. The o The Mobile Node Identifier option [RFC-4283] MUST be present. The
identifier field in the option MUST be copied from the Mobile Node identifier field in the option MUST be copied from the Mobile Node
Identifier option in the received Proxy Binding Update request. Identifier option in the received Proxy Binding Update request.
If the option was not present in the request, the identifier in If the option was not present in the request, the identifier in
the option MUST be set to a zero length identifier. the option MUST be set to a zero length identifier.
o The Home Network Prefix option MUST be present. 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 * If the Status field is set to a value greater than or equal to
128, i.e., if the binding request is rejected, then the prefix 128, i.e., if the binding request is rejected, all the Home
value in the Home Network Prefix option MUST be set to the Network Prefix options that were present in the request (along
prefix value in the Home Network Prefix option of the received with their prefix values) MUST be present in the reply. But,
Proxy Binding Update request. But, if the option was not if there was no Home Network Prefix option present in the
present in the request, the value in the option MUST be set to request, then there MUST be only one Home Network Prefix option
ALL_ZERO. and with the value in the option set to ALL_ZERO.
* For all other cases, the prefix value in the option MUST be set * For all other cases, there MUST be a Home Network Prefix option
to the allocated prefix value for that mobility session. for each of the assigned home network prefixes (for that
mobility 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 o The Handoff Indicator option MUST be present. The handoff
indicator field in the option MUST be copied from the Handoff indicator field in the option MUST be copied from the Handoff
Indicator option in the received Proxy Binding Update request. If Indicator option in the received Proxy Binding Update request. If
the option was not present in the request, the value in the option the option was not present in the request, the value in the option
MUST be set to zero. MUST be set to zero.
o The Access Technology Type option MUST be present. The access 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 field in the option MUST be copied from the Access
Technology Type option in the received Proxy Binding Update Technology Type option in the received Proxy Binding Update
request. If the option was not present in the request, the value request. If the option was not present in the request, the value
in the option MUST be set to zero. in the option MUST be set to zero.
o The Timestamp option MUST be present, if the same option was o The Timestamp option MUST be present only if the same option was
present in the received Proxy Binding Update request. present in the received Proxy Binding Update request and MUST NOT
Considerations from Section 5.5 must be applied for constructing be present otherwise. Considerations from Section 5.5 must be
the Timestamp option. applied for constructing the Timestamp option.
o The Mobile Node Link-layer Identifier option MUST be present, if o The Mobile Node Link-layer Identifier option MUST be present only
the same option was present in the received Proxy Binding Update if the same option was present in the received Proxy Binding
request. The link-layer identifier value MUST be copied from the Update request and MUST NOT be present otherwise. The link-layer
Mobile Node Link-layer Identifier option present in the received identifier value MUST be copied from the Mobile Node Link-layer
Proxy Binding Update request. Identifier option present in the received Proxy Binding Update
request.
o The Link-local Address option MUST be present, if the same option o The Link-local Address option MUST be present only if the same
was present in the received Proxy Binding Update request. option was present in the received Proxy Binding Update request
and MUST NOT be present otherwise.
* If the received Proxy Binding Update request has the Link-local * If the received Proxy Binding Update request has the Link-local
Address option with any value other than ALL_ZERO, the same Address option with any value other than ALL_ZERO, the same
value MUST be copied to the Link-local Address field of the value MUST be copied to the Link-local Address field of the
Binding Cache entry and it must also be copied to the Link- Binding Cache entry and it must also be copied to the Link-
local Address option in the reply. local Address option in the reply.
* If there is no existing Binding Cache entry (i.e., if this is a * If there is no existing Binding Cache entry (i.e., if this is a
request for a new mobility session), then the local mobility request for a new mobility session), then the local mobility
anchor MUST generate the link-local address that the mobile anchor MUST generate the link-local address that the mobile
skipping to change at page 27, line 13 skipping to change at page 27, line 49
NOT be present in the IPv6 header of the packet. NOT be present in the IPv6 header of the packet.
5.4. Multihoming Support 5.4. Multihoming Support
This specification allows mobile nodes to connect to a Proxy Mobile This specification allows mobile nodes to connect to a Proxy Mobile
IPv6 domain through multiple interfaces for simultaneous access. IPv6 domain through multiple interfaces for simultaneous access.
Following are the key aspects of this multihoming support. Following are the key aspects of this multihoming support.
o When a mobile node connects to a Proxy Mobile IPv6 domain through o When a mobile node connects to a Proxy Mobile IPv6 domain through
multiple interfaces for simultaneous access, the local mobility multiple interfaces for simultaneous access, the local mobility
anchor MUST allocate a unique home network prefix for each of the anchor MUST allocate a mobility session for each of the attached
connected interfaces. interfaces. Each of the mobility session should be managed under
a separate Binding Cache entry and with its own lifetime.
o The local mobility anchor MUST manage each of the allocated home o The local mobility anchor MAY allocate more than one home network
network prefixes as part of a separate mobility session, each prefix for a given interface of the mobile node. However, all the
under a separate Binding Cache entry and with its own lifetime. 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 for an handoff between two o The local mobility anchor MUST allow for an handoff between two
different interfaces of the mobile node. In such a scenario, the different interfaces of a mobile node. In such a scenario, all
home network prefix that is associated with a specific link-layer the home network prefix(es) associated with one interface (part of
identifier of the mobile node will be updated with the new link- one mobility session) will be associated with a different
layer identifier. The decision on when to create a new mobility interface of the mobile node). The decision on when to create a
session and when to update an existing mobility session MUST be new mobility session and when to update an existing mobility
based on the Handover hint present in the Proxy Binding Update session MUST be based on the Handover hint present in the Proxy
message and under the considerations specified in this section. Binding Update message and under the considerations specified in
this section.
5.4.1. Binding Cache entry lookup considerations 5.4.1. Binding Cache entry lookup considerations
There can be multiple Binding Cache entries for a given mobile node. 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 When doing a lookup for a mobile node's Binding Cache entry for
processing a received Proxy Binding Update request message, the local processing a received Proxy Binding Update request message, the local
mobility anchor MUST apply the following multihoming considerations mobility anchor MUST apply the following multihoming considerations
(in the below specified order). These rules are chained with the (in the below specified order, starting with Section 5.4.1.1). These
processing rules specified in Section 5.3. rules are chained with the processing rules specified in Section 5.3.
5.4.1.1. Home Network Prefix Option (NON_ZERO Value) present in the
request
+=====================================================================+
| Registration/De-Registration Message |
+=====================================================================+
| HNP (NON_ZERO Value) |
+=====================================================================+
| ATT |
+=====================================================================+
| MN-LL-Identifier Opt Present | MN-LL-Identifier Opt Not Present |
+=====================================================================+
| HI |
+==================================+==================================+
| BCE Lookup Key: (Home Network Prefix) |
+=====================================================================+
Figure 7: BCE lookup using home network prefix
1. The local mobility anchor MUST verify if there is an existing
Binding Cache entry with the home network prefix value matching
the prefix value in the Home Network Prefix option of the
received Proxy Binding Update request. [BCE(HNP) equals
PBU(HNP)]
2. If there does not exist a Binding Cache entry (matching the MN-
HNP), the request MUST be considered as a request for creating a
new mobility session.
3. If there exists a Binding Cache entry (matching MN-HNP), and 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 request, 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 the requesting home network prefix). [BCE(MN-
Identifier) not equals PBU(MN-Identifier)]
4. If there exists a Binding Cache entry (matching MN-Identifier and
MN-HNP) 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. [BCE(MN-Identifier) equals PBU(MN-
Identifier)]
* If there is a Mobile Node Link-layer Identifier option present
in the request, and if the link-layer identifier value in that
option matches the link-layer identifier value in the Binding
Cache entry and 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. [BCE(ATT,
MN-LL-Identifier) equals PBU(ATT, MN-LL-Identifier)]
* 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). [PBU(HI) equals
2]
* 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
Cache entry 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.
[BCE(Proxy-CoA, ATT) equals PBU(Proxy-CoA, ATT)].
5. For all other cases, the message MUST be considered as a request
for creating a new mobility session.
5.4.1.2. Mobile Node Link-layer Identifier Option present in the 5.4.1.1. Mobile Node Link-layer Identifier Option present in the
request request
+=====================================================================+ +=====================================================================+
| Registration/De-Registration Message | | Registration/De-Registration Message |
+=====================================================================+ +=====================================================================+
| HNP (ALL_ZERO Value) | | HNP Option(s) |
+=====================================================================+ +=====================================================================+
| ATT | | ATT |
+=====================================================================+ +=====================================================================+
| MN-LL-Identifier Option Present (NON_ZERO Value) | | MN-LL-Identifier Option Present (NON_ZERO Value) |
+=====================================================================+ +=====================================================================+
| HI | | HI |
+==================================+==================================+ +==================================+==================================+
| BCE Lookup Keys: (MN-Identifier + ATT + MN-LL-Identifier) | | BCE Lookup Keys: (MN-Identifier + ATT + MN-LL-Identifier) |
+=====================================================================+ +=====================================================================+
Figure 8: BCE Lookup using Link-layer Identifier Figure 7: BCE Lookup using Link-layer Identifier
1. The local mobility anchor MUST verify if there is an existing 1. The local mobility anchor MUST verify if there is an existing
Binding Cache entry, with the mobile node identifier matching the Binding Cache entry, with the mobile node identifier matching the
identifier in the received Mobile Node Identifier option, access identifier in the received Mobile Node Identifier option, access
technology type matching the value in the received Access technology type matching the value in the received Access
Technology Type option and the link-layer identifier value Technology Type option and the link-layer identifier value
matching the identifier in the received Mobile Node Link-layer matching the identifier in the received Mobile Node Link-layer
Identifier option. [BCE(MN-Identifier, ATT, MN-LL-Identifier) Identifier option. [BCE(MN-Identifier, ATT, MN-LL-Identifier)
equals PBU(MN-Identifier, ATT, MN-LL-Identifier)] equals PBU(MN-Identifier, ATT, MN-LL-Identifier)]
2. If there exists a Binding Cache entry (matching MN-Identifier, 2. If there exists a Binding Cache entry (matching MN-Identifier,
ATT and MN-LL-Identifier), the request MUST be considered as a ATT and MN-LL-Identifier), the request MUST be considered as a
request for updating that Binding Cache entry. request for updating that Binding Cache entry (mobility session).
3. If there does not exist a Binding Cache entry (matching MN- 3. If there does not exist a Binding Cache entry (matching MN-
Identifier, ATT and MN-LL-Identifier) and the Handoff Indicator Identifier, ATT and MN-LL-Identifier) and the Handoff Indicator
field in the Handoff Indicator option present in the request is field in the Handoff Indicator option present in the request is
set to a value of 2 (Handoff between two different interfaces of set to a value of 2 (Handoff between two different interfaces of
the mobile node). The local mobility anchor MUST apply the the mobile node). The local mobility anchor MUST apply the
following additional considerations. [PBU(HI) equals 2] following additional considerations. [PBU(HI) equals 2]
* The local mobility anchor MUST verify if there exists one and * The local mobility anchor MUST verify if there exists one and
only one Binding Cache entry with the mobile node identifier only one Binding Cache entry with the mobile node identifier
skipping to change at page 32, line 5 skipping to change at page 30, line 13
the local mobility anchor upon accepting the request MUST the local mobility anchor upon accepting the request MUST
consider the request as a request for creating a new mobility consider the request as a request for creating a new mobility
session. The local mobility anchor MAY also choose to create session. The local mobility anchor MAY also choose to create
a new mobility session and without waiting for a de- a new mobility session and without waiting for a de-
registration message and this should be configurable on the registration message and this should be configurable on the
local mobility anchor. local mobility anchor.
5. For all other cases, the message MUST be considered as a request 5. For all other cases, the message MUST be considered as a request
for creating a new mobility session. for creating a new mobility session.
5.4.1.2. Home Network Prefix Option (NON_ZERO Value) present in the
request
+=====================================================================+
| Registration/De-Registration Message |
+=====================================================================+
| At least one HNP Option with NON_ZERO Value |
+=====================================================================+
| ATT |
+=====================================================================+
| MN-LL-Identifier Opt Not Present |
+=====================================================================+
| HI |
+==================================+==================================+
| BCE Lookup Key: Any of the Home Network Prefixes from the request |
+=====================================================================+
Figure 8: BCE lookup using home network prefix
If there is at least one Home Network Prefix option present in the
request with NON_ZERO prefix value, the following considerations MUST
be applied. If there are more than instances 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 request. [BCE(HNP)
equals PBU(HNP)]
2. If there does not exist a Binding Cache entry (with one 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 request), the request MUST be considered as
a request for creating a new mobility session. [BCE(HNP) not
equals PBU(HNP)]
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 the Home Network Prefix options of the received
Proxy Binding Update request) 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 request, 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). [BCE(MN-Identifier) not equals PBU(MN-Identifier)]
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 the Home Network Prefix options
of the received Proxy Binding Update request), 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 NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (mobile
node is not authorized for the requesting home network prefix).
[BCE(HNP1, HNP2, .. HNPn) not equals PBU(HNP1, HNP2, ..HNPn)] OR
[BCE(Count(HNP))] not equals PBU(Count(HNP))]
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 request) 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. [BCE(MN-Identifier) equals
PBU(MN-Identifier)] AND [BCE(HNP1, HNP2, .. HNPn) equals
PBU(HNP1, HNP2, ..HNPn)]
* 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). [PBU(HI) equals
2]
* 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 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.
[BCE(Proxy-CoA, ATT) equals PBU(Proxy-CoA, ATT)].
6. For all other cases, the message MUST be considered as a request
for creating a new mobility session.
5.4.1.3. Mobile Node Link-layer Identifier Option not present in the 5.4.1.3. Mobile Node Link-layer Identifier Option not present in the
request request
+=====================================================================+ +=====================================================================+
| Registration/De-Registration Message | | Registration/De-Registration Message |
+=====================================================================+ +=====================================================================+
| HNP (ALL_ZERO Value) | | HNP option with ALL_ZERO Value |
+=====================================================================+ +=====================================================================+
| ATT | | ATT |
+=====================================================================+ +=====================================================================+
| MN-LL-Identifier Option Not Present | | MN-LL-Identifier Option Not Present |
+=====================================================================+ +=====================================================================+
| HI | | HI |
+==================================+==================================+ +==================================+==================================+
| BCE Lookup Key: (MN-Identifier) | | BCE Lookup Key: (MN-Identifier) |
+=====================================================================+ +=====================================================================+
Figure 9: BCE Lookup using Mobile Node Identifier Figure 9: BCE Lookup using Mobile Node Identifier
1. The local mobility anchor MUST verify if there exists one and 1. The local mobility anchor MUST verify if there exists one and
only one Binding Cache entry with the mobile node identifier only one Binding Cache entry with the mobile node identifier
matching the identifier in the Mobile Node Identifier option matching the identifier in the Mobile Node Identifier option
present in the request. present in the request.
2. If there exists only one such entry (matching the MN-Identifier) 2. If there exists only one such entry (matching the MN-Identifier)
and the Handoff Indicator field in the Handoff Indicator option and the Handoff Indicator field in the Handoff Indicator option
present in the request is set to a value of 2 (Handoff between present in the request is set to a value of 2 (Handoff between
two different interfaces of the mobile node), the request MUST be two different interfaces of the mobile node) or set to a value of
considered as a request for updating that Binding Cache entry. 3 (Handoff between mobile access gateways for the same
[PBU(HI) equals 2] interface), then the request MUST be considered as a request for
updating that Binding Cache entry. [PBU(HI) equals 2] or
[PBU(HI) equals 3]
3. If there exists only one such entry (matching the MN-Identifier) 3. If there exists only one such entry (matching the MN-Identifier)
and the Handoff Indicator field in the Handoff Indicator option and the Handoff Indicator field in the Handoff Indicator option
present in the request is set to a value of 4 (Handoff state present in the request is set to a value of 4 (Handoff state
unknown), the local mobility anchor SHOULD wait till the existing unknown), the local mobility anchor SHOULD wait till the existing
Binding Cache entry is de-registered by the previously serving Binding Cache entry is de-registered by the previously serving
mobile access gateway, before the request can be considered as a mobile access gateway, before the request can be considered as a
request for updating that Binding Cache entry. However, if there request for updating that Binding Cache entry. However, if there
is no de-registration message that is received within is no de-registration message that is received within
MaxDelayBeforeNewBCEAssign amount of time, the local mobility MaxDelayBeforeNewBCEAssign amount of time, the local mobility
anchor upon accepting the request MUST consider the request as a anchor upon accepting the request MUST consider the request as a
skipping to change at page 33, line 26 skipping to change at page 33, line 39
the mobile node moves from one mobile access gateway to another and the mobile node moves from one mobile access gateway to another and
in the absence of mechanisms such as context transfer between the in the absence of mechanisms such as context transfer between the
mobile access gateways, the serving mobile access gateway will be mobile access gateways, the serving mobile access gateway will be
unable to determine the sequence number that it needs to use in the unable to determine the sequence number that it needs to use in the
signaling messages. Hence, the sequence number scheme, as specified signaling messages. Hence, the sequence number scheme, as specified
in [RFC-3775], will be insufficient for Proxy Mobile IPv6. in [RFC-3775], will be insufficient for Proxy Mobile IPv6.
If the local mobility anchor cannot determine the sending order of If the local mobility anchor cannot determine the sending order of
the received binding registration messages, it may potentially the received binding registration messages, it may potentially
process an older message sent by a mobile access gateway where the process an older message sent by a mobile access gateway where the
mobile node was previously anchored, resulting in an incorrect mobile node was previously anchored, but delivered out of order,
Binding Cache entry. 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 previously serving gateway.
For solving this problem, this specification adopts two alternative For solving this problem, this specification adopts two alternative
solutions. One is based on timestamps and the other based on solutions. One is based on timestamps and the other based on
sequence numbers, as defined in [RFC-3775]. sequence numbers, as defined in [RFC-3775].
The basic principle behind the use of timestamps in binding The basic principle behind the use of timestamps in binding
registration messages is that the node generating the message inserts registration messages is that the node generating the message inserts
the current time-of-day, and the node receiving the message checks the current time-of-day, and the node receiving the message checks
that this timestamp is greater than all previously accepted that this timestamp is greater than all previously accepted
timestamps. The timestamp based solution may be used when the timestamps. The timestamp based solution may be used when the
serving mobile access gateways in a Proxy Mobile IPv6 domain do not 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 have the ability to obtain the last sequence number that was sent in
a binding registration message for updating a given mobile node's a binding registration message for updating a given mobile node's
binding. binding.
If the mechanism used for clock synchronization in the Proxy Mobile
IPv6 domain cannot assure a clock drift between the two mobile access
gateways (between which the mobile node did a handoff), which is not
less than half the total time it took for the mobile node to roam
between the two mobile access gateways and the time it took for the
serving mobile access gateway to detect the node on its access link
and construct the Proxy Binding Update message, then this solution
will not predictably work in all cases and hence SHOULD NOT be used.
As an alternative to the Timestamp based approach, the specification As an alternative to the Timestamp based approach, the specification
also allows the use of Sequence Number based scheme, as specified in also allows the use of Sequence Number based scheme, as specified in
[RFC-3775]. However, for this scheme to work, the serving mobile [RFC-3775]. However, for this scheme to work, the serving mobile
access gateways in a Proxy Mobile IPv6 domain MUST have the ability access gateway in a Proxy Mobile IPv6 domain MUST have the ability to
to obtain the last sequence number that was sent in a binding obtain the last sequence number that was sent in a binding
registration message for updating a given mobile node's binding. The registration message. The sequence number MUST be maintained on a
sequence number MUST be maintained on a per mobile node basis and per mobile node basis and MUST be available to the serving mobile
MUST be synchronized between the serving mobile access gateways. access gateway. This may be achieved by using context transfer
schemes or by maintaining the sequence number in a policy store.
This may be achieved by using context transfer schemes or by However, the specific details on how the mobile node's sequence
maintaining the sequence number in a policy store. However, the number is made available to the serving mobile access gateway prior
specific details on how the mobile node's sequence number is to sending the binding registration messages is outside the scope of
synchronized between different mobile access gateways is outside the this document."
scope of this document.
Using the Timestamps based approach: Using the Timestamps based approach:
1. A local mobility anchor implementation MUST support the Timestamp 1. A local mobility anchor implementation MUST support the Timestamp
option. If the Timestamp option is present in the received Proxy option. If the Timestamp option is present in the received Proxy
Binding Update request message, then the local mobility anchor Binding Update request message, then the local mobility anchor
MUST include a valid Timestamp option in the Proxy Binding MUST include a valid Timestamp option in the Proxy Binding
Acknowledgement message that it sends to the mobile access Acknowledgement message that it sends to the mobile access
gateway. gateway.
skipping to change at page 35, line 13 skipping to change at page 35, line 38
the Proxy Binding Acknowledgement message. the Proxy Binding Acknowledgement message.
6. Upon receipt of a Proxy Binding Update message with the Timestamp 6. Upon receipt of a Proxy Binding Update message with the Timestamp
option, the local mobility anchor MUST check the timestamp field option, the local mobility anchor MUST check the timestamp field
for validity. In order for it to be considered valid, the for validity. In order for it to be considered valid, the
timestamp value contained in the Timestamp option MUST be close timestamp value contained in the Timestamp option MUST be close
enough (within TimestampValidityWindow amount of time difference) enough (within TimestampValidityWindow amount of time difference)
to the local mobility anchor's time-of-day clock and the to the local mobility anchor's time-of-day clock and the
timestamp MUST be greater than all previously accepted timestamps timestamp MUST be greater than all previously accepted timestamps
in the Proxy Binding Update messages sent for that mobile node. in the Proxy Binding Update messages sent for that mobile node.
However, if the flag MobileNodeGeneratedTimestampInUse is set to
value of 1, this check MUST NOT be performed.
7. If the timestamp value in the received Proxy Binding Update is 7. If the timestamp value in the received Proxy Binding Update is
valid (validity as specified in the above considerations), the valid (validity as specified in the above considerations) or if
local mobility anchor MUST return the same timestamp value in the the flag MobileNodeGeneratedTimestampInUse is set to value of 1,
Timestamp option included in the Proxy Binding Acknowledgement the local mobility anchor MUST return the same timestamp value in
message that it sends to the mobile access gateway. 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 8. If the timestamp value in the received Proxy Binding Update is
lower than the previously accepted timestamp in the Proxy Binding lower than the previously accepted timestamp in the Proxy Binding
Update messages sent for that mobility binding, the local Update messages sent for that mobility binding, the local
mobility anchor MUST reject the Proxy Binding Update request and mobility anchor MUST reject the Proxy Binding Update request and
send a Proxy Binding Acknowledgement message with Status field send a Proxy Binding Acknowledgement message with Status field
set to TIMESTAMP_LOWER_THAN_PREV_ACCEPTED (Timestamp lower than set to TIMESTAMP_LOWER_THAN_PREV_ACCEPTED (Timestamp lower than
previously accepted timestamp). The message MUST also include previously accepted timestamp). The message MUST also include
the Timestamp option with the value set to the current time-of- the Timestamp option with the value set to the current time-of-
day on the local mobility anchor. day on the local mobility anchor.
skipping to change at page 36, line 18 skipping to change at page 36, line 44
obtain the last sequence number that was sent in a binding obtain the last sequence number that was sent in a binding
registration message for updating a given mobile node's binding. registration message for updating a given mobile node's binding.
5.6. Routing Considerations 5.6. Routing Considerations
5.6.1. Bi-Directional Tunnel Management 5.6.1. Bi-Directional Tunnel Management
The bi-directional tunnel MUST be used for routing the mobile node's The bi-directional tunnel MUST be used for routing the mobile node's
data traffic between the mobile access gateway and the local mobility data traffic between the mobile access gateway and the local mobility
anchor. A tunnel hides the topology and enables a mobile node to use anchor. A tunnel hides the topology and enables a mobile node to use
an address from its home network prefix from any access link in that address(es) from its home network prefix(es) from any access link in
Proxy Mobile IPv6 domain. A tunnel may be created dynamically when that Proxy Mobile IPv6 domain. A tunnel may be created dynamically
needed and removed when not needed. However, implementations MAY when needed and removed when not needed. However, implementations
choose to use static pre-established tunnels instead of dynamically MAY choose to use static pre-established tunnels instead of
creating and tearing them down on a need basis. The following dynamically creating and tearing them down on a need basis. The
considerations MUST be applied when using dynamic tunnels. following considerations MUST be applied when using dynamic tunnels.
o A bi-directional tunnel MUST be established between the local o A bi-directional tunnel MUST be established between the local
mobility anchor and the mobile access gateway with IP-in-IP mobility anchor and the mobile access gateway with IPv6-in-IPv6
encapsulation, as described in [RFC-2473]. The tunnel end points encapsulation, as described in [RFC-2473]. The tunnel end points
are the Proxy-CoA and LMAA. When using IPv4 transport, the end are the Proxy-CoA and LMAA. When using IPv4 transport, the end
points of the tunnel are the IPv4-LMAA and IPv4-Proxy-CoA, as points of the tunnel are the IPv4-LMAA and IPv4-Proxy-CoA, as
specified in [ID-IPV4-PMIP6]. specified in [ID-IPV4-PMIP6].
o Implementations can use a software timer for managing the tunnel o Implementations MAY use a software timer for managing the tunnel
lifetime and a counter for keeping a count of all the mobile nodes 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 that are sharing the tunnel. The timer value can be set to the
accepted binding lifetime and can be updated after each periodic accepted binding lifetime and can be updated after each periodic
re-registration for extending the lifetime. If the tunnel is re-registration for extending the lifetime. If the tunnel is
shared for multiple mobile nodes, the tunnel lifetime must be set shared for multiple mobile nodes, the tunnel lifetime must be set
to the highest binding lifetime that is granted to any one of to the highest binding lifetime that is granted to any one of
those mobile nodes sharing that tunnel. those mobile nodes sharing that tunnel.
o The tunnel MUST be deleted when either the tunnel lifetime expires o The tunnel SHOULD be deleted when either the tunnel lifetime
or when there are no mobile nodes sharing the tunnel. expires or when there are no mobile nodes sharing the tunnel.
5.6.2. Forwarding Considerations 5.6.2. Forwarding Considerations
Intercepting Packets Sent to the Mobile Node's Home Network: Intercepting Packets Sent to the Mobile Node's Home Network:
o When the local mobility anchor is serving a mobile node, it MUST 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 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 network. In order for it to receive those packets, it MUST
advertise a connected route in to the Routing Infrastructure for advertise a connected route in to the Routing Infrastructure for
the mobile node's home network prefix or for an aggregated prefix the mobile node's home network prefix(es) or for an aggregated
with a larger scope. This essentially enables IPv6 routers in prefix with a larger scope. This essentially enables IPv6 routers
that network to detect the local mobility anchor as the last-hop in that network to detect the local mobility anchor as the last-
router for that prefix. hop router for the mobile node's home network prefix(es).
Forwarding Packets to the Mobile Node: Forwarding Packets to the Mobile Node:
o On receiving a packet from a correspondent node with the o On receiving a packet from a correspondent node with the
destination address matching a mobile node's home network prefix, destination address matching a mobile node's home network
the local mobility anchor MUST forward the packet through the bi- prefix(es), the local mobility anchor MUST forward the packet
directional tunnel set up for that mobile node. The format of the through the bi-directional tunnel set up for that mobile node.
tunneled packet is shown below. Considerations from [RFC-2473]
MUST be applied for IPv6 encapsulation. However, when using IPv4 o The format of the tunneled packet is shown below. Considerations
transport, the format of the packet is as described in [ID-IPV4- from [RFC-2473] MUST be applied for IPv6 encapsulation. However,
PMIP6]. when using IPv4 transport, the format of the packet is as
described in [ID-IPV4-PMIP6].
IPv6 header (src= LMAA, dst= Proxy-CoA /* Tunnel Header */ IPv6 header (src= LMAA, dst= Proxy-CoA /* Tunnel Header */
IPv6 header (src= CN, dst= MN-HOA ) /* Packet Header */ IPv6 header (src= CN, dst= MN-HOA ) /* Packet Header */
Upper layer protocols /* Packet Content*/ Upper layer protocols /* Packet Content*/
Figure 10: Tunneled Packets from LMA to MAG 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].
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: Forwarding Packets Sent by the Mobile Node:
o All the reverse tunneled packets that the local mobility anchor o All the reverse tunneled packets that the local mobility anchor
received from the mobile access gateway, after removing the tunnel received from the mobile access gateway, after removing the tunnel
header MUST be routed to the destination specified in the inner header MUST be routed to the destination specified in the inner
packet header. These routed packets will have the source address packet header. These routed packets will have the source address
field set to the mobile node's home address. Considerations from field set to the mobile node's home address. Considerations from
[RFC-2473] MUST be applied for IPv6 decapsulation. [RFC-2473] MUST be applied for IPv6 decapsulation.
skipping to change at page 38, line 5 skipping to change at page 38, line 45
10.5 of [RFC-3775], allows a mobile node to discover all the home 10.5 of [RFC-3775], allows a mobile node to discover all the home
agents on its home link by sending an ICMP Home Agent Address agents on its home link by sending an ICMP Home Agent Address
Discovery Request message to the Mobile IPv6 Home-Agents anycast Discovery Request message to the Mobile IPv6 Home-Agents anycast
address, derived from its home network prefix. address, derived from its home network prefix.
The DHAAD message in the current form cannot be used in Proxy Mobile 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 IPv6 for discovering the address of the mobile node's local mobility
anchor. In Proxy Mobile IPv6, the local mobility anchor will not be anchor. In Proxy Mobile IPv6, the local mobility anchor will not be
able to receive any messages sent to the Mobile IPv6 Home-Agents able to receive any messages sent to the Mobile IPv6 Home-Agents
anycast address corresponding to the mobile node's home network anycast address corresponding to the mobile node's home network
prefix, as the prefix is not hosted on any of its interfaces. 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 Further, the mobile access gateway will not predictably be able to
locate the serving local mobility anchor that has the mobile node's locate the serving local mobility anchor that has the mobile node's
binding cache entry. Hence, this specification does not support binding cache entry. Hence, this specification does not support
Dynamic Home Agent Address Discovery protocol. Dynamic Home Agent Address Discovery protocol.
In Proxy Mobile IPv6, the address of the local mobility anchor In Proxy Mobile IPv6, the address of the local mobility anchor
configured to serve a mobile node can be discovered by the mobility 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 entities in other ways. This may be a configured entry in the mobile
node's policy profile, or it may be obtained through mechanisms node's policy profile, or it may be obtained through mechanisms
outside the scope of this document. outside the scope of this document.
5.8. Mobile Prefix Discovery Considerations 5.8. Mobile Prefix Discovery Considerations
This specification does not support mobile prefix discovery. The This specification does not support mobile prefix discovery. The
mobile prefix discovery mechanism as specified in [RFC-3775] is not mobile prefix discovery mechanism as specified in [RFC-3775] is not
applicable to Proxy Mobile IPv6. applicable to Proxy Mobile IPv6.
5.9. Route Optimizations Considerations 5.9. Route Optimization Considerations
The Route Optimization in Mobile IPv6, as defined in [RFC-3775], The Route Optimization in Mobile IPv6, as defined in [RFC-3775],
enables a mobile node to communicate with a correspondent node enables a mobile node to communicate with a correspondent node
directly using its care-of address and further the Return Routability directly using its care-of address and further the Return Routability
procedure enables the correspondent node to have reasonable trust procedure enables the correspondent node to have reasonable trust
that the mobile node is reachable at both its home address and that the mobile node is reachable at both its home address and
care-of address. care-of address.
In Proxy Mobile IPv6, the mobile node is not involved in any IP In Proxy Mobile IPv6, the mobile node is not involved in any IP
mobility related signaling. The mobile node uses only its home mobility related signaling. The mobile node uses address(es) from
address for all its communication and the Care-of address (Proxy-CoA) its home network prefix(es) for all its communication and the Care-of
is not visible to the mobile node. Hence, the Return Routability address (Proxy-CoA) is not visible to the mobile node. Hence, the
procedure as defined in Mobile IPv6 [RFC-3775] cannot be used in Return Routability procedure as defined in Mobile IPv6 [RFC-3775]
Proxy Mobile IPv6. cannot be used in Proxy Mobile IPv6.
6. Mobile Access Gateway Operation 6. Mobile Access Gateway Operation
The Proxy Mobile IPv6 protocol described in this document introduces The Proxy Mobile IPv6 protocol described in this document introduces
a new functional entity, the Mobile Access Gateway (MAG). The mobile a new functional entity, the Mobile Access Gateway (MAG). The mobile
access gateway is the entity that is responsible for detecting the access gateway is the entity that is responsible for detecting the
mobile node's movements to and from the access link and sending the mobile node's movements to and from the access link and sending the
binding registration requests to the local mobility anchor. In binding registration requests to the local mobility anchor. In
essence, the mobile access gateway performs mobility management on essence, the mobile access gateway performs mobility management on
behalf of a mobile node. behalf of a mobile node.
skipping to change at page 39, line 15 skipping to change at page 40, line 12
that is achieved or the signaling interactions between those that is achieved or the signaling interactions between those
functional entities are beyond the scope of this document. functional entities are beyond the scope of this document.
The mobile access gateway has the following key functional roles: The mobile access gateway has the following key functional roles:
o It is responsible for detecting the mobile node's movements on the o It is responsible for detecting the mobile node's movements on the
access link and for initiating the mobility signaling with the access link and for initiating the mobility signaling with the
mobile node's local mobility anchor. mobile node's local mobility anchor.
o Emulation of the mobile node's home link on the access link by o Emulation of the mobile node's home link on the access link by
sending Router Advertisements with the mobile node's home network sending Router Advertisement messages containing the mobile node's
prefix information. home network prefix(es), each prefix carried using the Prefix
Information option [RFC-4861].
o Responsible for setting up the data path for enabling the mobile o Responsible for setting up the data path for enabling the mobile
node to configure an address from its home network prefix and use node to configure one or more addresses from its home network
it from its access link. prefix(es) and use it from the attached access link.
6.1. Extensions to Binding Update List Entry Data Structure 6.1. Extensions to Binding Update List Entry Data Structure
Every mobile access gateway MUST maintain a Binding Update List. Every mobile access gateway MUST maintain a Binding Update List.
Each entry in the Binding Update List represents a mobile node's Each entry in the Binding Update List represents a mobile node's
mobility binding with its local mobility anchor. The Binding Update mobility binding with its local mobility anchor. The Binding Update
List is a conceptual data structure, described in Section 11.1 of List is a conceptual data structure, described in Section 11.1 of
[RFC-3775]. [RFC-3775].
For supporting this specification, the conceptual Binding Update List For supporting this specification, the conceptual Binding Update List
skipping to change at page 39, line 42 skipping to change at page 40, line 40
fields. fields.
o The Identifier of the attached mobile node, MN-Identifier. This o The Identifier of the attached mobile node, MN-Identifier. This
identifier is acquired during the mobile node's attachment to the identifier is acquired during the mobile node's attachment to the
access link through mechanisms outside the scope of this document. access link through mechanisms outside the scope of this document.
o The link-layer identifier of the mobile node's connected o The link-layer identifier of the mobile node's connected
interface. This can be acquired from the received Router interface. This can be acquired from the received Router
Solicitation messages from the mobile node or during the mobile Solicitation messages from the mobile node or during the mobile
node's attachment to the access network. This is typically a node's attachment to the access network. This is typically a
Link-layer identifier conveyed by the mobile node; however, the link-layer identifier conveyed by the mobile node; however, the
specific details on how that is conveyed is out of scope for this specific details on how that is conveyed is out of scope for this
specification. If this identifier is not available, the value specification. If this identifier is not available, this variable
MUST be set to ALL_ZERO. length field MUST be set to some default size and MUST be
initialized to a value of ALL_ZERO.
o The IPv6 home network prefix of the attached mobile node. The o List of IPv6 home network prefixes assigned to the mobile node's
home network prefix of the mobile node is acquired from the mobile connected interface. The home network prefix(es) may have been
node's local mobility anchor through the received Proxy Binding statically configured in the mobile node's policy profile, or, may
Acknowledgement messages. The IPv6 home network prefix also have been dynamically allocated by the local mobility anchor.
includes the corresponding prefix length. Each of these prefix entries will also includes the corresponding
prefix length.
o The Link-local address of the mobile node on the interface o The Link-local address of the mobile access gateway on the access
attached to the access link. link shared with the mobile node.
o The IPv6 address of the local mobility anchor serving the attached o The IPv6 address of the local mobility anchor serving the attached
mobile node. This address is acquired from the mobile node's mobile node. This address is acquired from the mobile node's
policy profile or from other means. policy profile or from other means.
o The interface identifier (If-Id) of the point-to-point link o The interface identifier (If-Id) of the point-to-point link
between the mobile node and the mobile access gateway. This is between the mobile node and the mobile access gateway. This is
internal to the mobile access gateway and is used to associate the internal to the mobile access gateway and is used to associate the
Proxy Mobile IPv6 tunnel to the access link where the mobile node Proxy Mobile IPv6 tunnel to the access link where the mobile node
is attached. is attached.
skipping to change at page 40, line 48 skipping to change at page 41, line 47
node MUST have access to its policy profile. node MUST have access to its policy profile.
The following are the mandatory fields of the policy profile: The following are the mandatory fields of the policy profile:
o The mobile node's identifier (MN-Identifier) o The mobile node's identifier (MN-Identifier)
o The IPv6 address of the local mobility anchor (LMAA) o The IPv6 address of the local mobility anchor (LMAA)
The following are the optional fields of the policy profile: The following are the optional fields of the policy profile:
o The mobile node's IPv6 home network prefix (MN-HNP) o The mobile node's IPv6 home network prefix(es) assigned to the
o The mobile node's IPv6 home network Prefix lifetime mobile node's connected interface
o The mobile node's IPv6 home network Prefix lifetime. This
lifetime will be same for all the hosted prefixes on the link, as
they all are part of one mobility session.
o Supported address configuration procedures (Stateful, Stateless or o Supported address configuration procedures (Stateful, Stateless or
both) for the mobile node in the Proxy Mobile IPv6 domain both) for the mobile node in the Proxy Mobile IPv6 domain
6.3. Supported Access Link Types 6.3. Supported Access Link Types
This specification supports only point-to-point access link types and This specification supports only point-to-point access link types and
thus it assumes that the mobile node and the mobile access gateway thus it assumes that the mobile node and the mobile access gateway
are the only two nodes on the access link. The link is assumed to are the only two nodes on the access link. The link is assumed to
have multicast capability. This protocol may also be used on other have multicast capability. This protocol may also be used on other
link types, as long as the link is configured in such a way that it link types, as long as the link is configured in such a way that it
guarantees a point-to-point delivery between the mobile node and the emulates point-to-point delivery between the mobile node and the
mobile access gateway for all the protocol traffic. mobile access gateway for all the protocol traffic.
6.4. Supported Address Configuration Modes 6.4. Supported Address Configuration Modes
A mobile node in the Proxy Mobile IPv6 domain can configure one or A mobile node in the Proxy Mobile IPv6 domain can configure one or
more global IPv6 addresses on its interface using Stateless, Stateful more global IPv6 addresses on its interface (using Stateless,
or manual address autoconfiguration procedures. The Router Stateful or manual address autoconfiguration procedures) from the
Advertisement messages sent on the access link specify the address hosted prefix(es) on that link. The Router Advertisement messages
configuration methods permitted on that access link for that mobile sent on the access link specify the address configuration methods
node. However, the advertised flags with respect to the address permitted on that access link for that mobile node. However, the
configuration will be consistent for a mobile node, on any of the advertised flags with respect to the address configuration will be
access links in that Proxy Mobile IPv6 domain. Typically, these consistent for a mobile node, on any of the access links in that
configuration settings will be based on the domain wide policy or Proxy Mobile IPv6 domain. Typically, these configuration settings
based on a policy specific to each mobile node. will be based on the domain wide policy or based on a policy specific
to each mobile node.
When stateless address autoconfiguration is supported on the access When stateless address autoconfiguration is supported on the access
link, the mobile node can generate one or more IPv6 addresses by link, the mobile node can generate one or more IPv6 addresses from
standard IPv6 mechanisms such as Stateless Autoconfiguration [RFC- the hosted prefix(es) by standard IPv6 mechanisms such as Stateless
4862] or Privacy extensions [RFC-4941]. Autoconfiguration [RFC-4862] or Privacy extensions [RFC-4941].
When stateful address autoconfiguration is supported on the link, the When stateful address autoconfiguration is supported on the link, the
mobile node can obtain the address configuration from the DHCPv6 mobile node can obtain the address configuration from the DHCPv6
server located in the Proxy Mobile IPv6 domain, by standard DHCPv6 server located in the Proxy Mobile IPv6 domain, by standard DHCPv6
mechanisms, as specified in [RFC-3315]. The obtained address will be mechanisms, as specified in [RFC-3315]. The obtained address(es)
from its respective home network prefix. Section 6.11 specifies the will be from its home network prefix(es). Section 6.11 specifies the
details on how this configuration can be achieved. details on how this configuration can be achieved.
Additionally, other address configuration mechanisms specific to the Additionally, other address configuration mechanisms specific to the
access link between the mobile node and the mobile access gateway may access link between the mobile node and the mobile access gateway may
also be used for pushing the address configuration to the mobile also be used for delivering the address configuration to the mobile
node. This specification does not change the behavior of address node. This specification does not modify the behavior of any of the
configuration mechanisms in any way. standard IPv6 address configuration mechanisms.
6.5. Access Authentication & Mobile Node Identification 6.5. Access Authentication & Mobile Node Identification
When a mobile node attaches to an access link connected to the mobile When a mobile node attaches to an access link connected to the mobile
access gateway, the deployed access security protocols on that link access gateway, the deployed access security protocols on that link
SHOULD ensure that the network-based mobility management service is SHOULD ensure that the network-based mobility management service is
offered only after authenticating and authorizing the mobile node for offered only after authenticating and authorizing the mobile node for
that service. The exact specifics on how this is achieved or the that service. The exact specifics on how this is achieved or the
interactions between the mobile access gateway and the access interactions between the mobile access gateway and the access
security service is outside the scope of this document. This security service is outside the scope of this document. This
skipping to change at page 43, line 18 skipping to change at page 44, line 18
6.7. Home Network Emulation 6.7. Home Network Emulation
One of the key functions of a mobile access gateway is to emulate the One of the key functions of a mobile access gateway is to emulate the
mobile node's home network on the access link. It must ensure, the mobile node's home network on the access link. It must ensure, the
mobile node believes it is still connected to its home link or on the mobile node believes it is still connected to its home link or on the
link where it obtained its initial address configuration after it link where it obtained its initial address configuration after it
moved into that Proxy Mobile IPv6 domain. moved into that Proxy Mobile IPv6 domain.
For emulating the mobile node's home link on the access link, the For emulating the mobile node's home link on the access link, the
mobile access gateway must be able to send Router Advertisements mobile access gateway must be able to send Router Advertisement
advertising the mobile node's home network prefix and other address messages advertising the mobile node's home network prefix(es)
configuration parameters consistent with its home link properties. carried using the Prefix Information option(s) [RFC-4861] and with
Typically, these configuration settings will be based on the domain other address configuration parameters consistent with its home link
wide policy or based on a policy specific to each mobile node. properties. Typically, these configuration settings will be based on
the domain wide policy or based on a policy specific to each mobile
node.
Typically, the mobile access gateway learns the mobile node's home Typically, the mobile access gateway learns the mobile node's home
network prefix information from the received Proxy Binding network prefix(es) details from the received Proxy Binding
Acknowledgement message or it may be obtained from the mobile node's Acknowledgement message or it may obtain them from the mobile node's
policy profile. However, the mobile access gateway SHOULD send the policy profile. However, the mobile access gateway SHOULD send the
Router Advertisements advertising the mobile node's home network Router Advertisements advertising the mobile node's home network
prefix only after successfully completing the binding registration prefix(es) only after successfully completing the binding
with the mobile node's local mobility anchor. registration with the mobile node's local mobility anchor.
When advertising the home network prefix in the Router Advertisement When advertising the home network prefix(es) in the Router
messages, the mobile access gateway MAY set the prefix lifetime value Advertisement messages, the mobile access gateway MAY set the prefix
for the advertised prefix to any chosen value at its own discretion. lifetime value for the advertised prefix(es) to any chosen value at
An implementation MAY choose to tie the prefix lifetime to the mobile its own discretion. An implementation MAY choose to tie the prefix
node's binding lifetime. The prefix lifetime can also be an optional lifetime to the mobile node's binding lifetime. The prefix lifetime
configuration parameter in the mobile node's policy profile. can also be an optional configuration parameter in the mobile node's
policy profile.
6.8. Link-Local and Global Address Uniqueness 6.8. Link-Local and Global Address Uniqueness
A mobile node in the Proxy Mobile IPv6 domain, as it moves from one A mobile node in the Proxy Mobile IPv6 domain, as it moves from one
mobile access gateway to the other, will continue to detect its home mobile access gateway to the other, will continue to detect its home
network and thus believe it is still on the same link. Every time network and thus believe it is still on the same link. Every time
the mobile node attaches to a new link, the event related to the the mobile node attaches to a new link, the event related to the
interface state change will trigger the mobile node to perform DAD interface state change will trigger the mobile node to perform DAD
operation on the link-local and global addresses. However, if the operation on the link-local and global address(es). However, if the
mobile node is DNAv6 enabled, as specified in [ID-DNAV6], it may not mobile node is DNAv6 enabled, as specified in [ID-DNAV6], it may not
detect the link change due to DNAv6 optimizations and may not trigger detect the link change due to DNAv6 optimizations and may not trigger
the duplicate address detection (DAD) procedure for its existing the duplicate address detection (DAD) procedure for its existing
addresses, which may potentially lead to address collisions after the addresses, which may potentially lead to address collisions after the
mobile node's handoff to a new link. mobile node's handoff to a new link.
The issue of address collision is not relevant to the mobile node's The issue of address collision is not relevant to the mobile node's
global address(es). Since there is a unique home network prefix global address(es). Since the assigned home network prefix(es) are
assigned for each mobile node, no other node shares an address (other for the mobile node's exclusive usage, no other node shares an
than Subnet-Router anycast address which is configured by the mobile address (other than Subnet-Router anycast address which is configured
access gateway) from that prefix and so the uniqueness for the mobile by the mobile access gateway) from the prefix(es) and so the
node's global address is assured on the access link. uniqueness for the mobile node's global address is assured on the
access link.
The issue of address collision is however relevant to the mobile The issue of address collision is however relevant to the mobile
node's link-local addresses since the mobile access gateway and the node's link-local addresses since the mobile access gateway and the
mobile node will have link-local addresses configured from the same mobile node will have link-local addresses configured from the same
link-local prefix (FE80::/64). This leaves a room for link-local link-local prefix (FE80::/64). This leaves a room for link-local
address collision between the two neighbors (i.e., the mobile node address collision between the two neighbors (i.e., the mobile node
and the mobile access gateway) on that access link. For solving this and the mobile access gateway) on that access link. For solving this
problem, this specification requires that the link-local address that problem, this specification requires that the link-local address that
the mobile access gateway configures on the point-to-point link the mobile access gateway configures on the point-to-point link
shared with a given mobile node be generated by the local mobility shared with a given mobile node be generated by the local mobility
anchor and be stored in the mobile node's Binding Cache entry. This anchor and be stored in the mobile node's Binding Cache entry. This
address will not change for the duration of that mobile node's address will not change for the duration of that mobile node's
session and can be provided to the serving mobile access gateway at session and can be provided to the serving mobile access gateway at
every mobile node's handoff, as part of the Proxy Mobile IPv6 every mobile node's handoff, as part of the Proxy Mobile IPv6
signaling messages. The specific method by which the local mobility signaling messages. The specific method by which the local mobility
anchor generates the link-local addresses is out of scope for this anchor generates the link-local address is out of scope for this
specification. specification.
Optionally, implementations MAY choose to configure a fixed link- Optionally, implementations MAY choose to configure a fixed link-
local address across all the access links in a Proxy Mobile IPv6 local address across all the access links in a Proxy Mobile IPv6
domain and without a need for carrying this address from the local domain and without a need for carrying this address from the local
mobility anchor to the mobile access gateway in the Proxy Mobile IPv6 mobility anchor to the mobile access gateway in the Proxy Mobile IPv6
signaling messages. signaling messages.
6.9. Signaling Considerations 6.9. Signaling Considerations
skipping to change at page 45, line 5 skipping to change at page 46, line 9
access gateway MUST identify the mobile node and acquire its MN- access gateway MUST identify the mobile node and acquire its MN-
Identifier. If it determines that the network-based mobility Identifier. If it determines that the network-based mobility
management service needs to be offered to the mobile node, it management service needs to be offered to the mobile node, it
MUST send a Proxy Binding Update message to the local mobility MUST send a Proxy Binding Update message to the local mobility
anchor. anchor.
2. The Proxy Binding Update message MUST include the Mobile Node 2. The Proxy Binding Update message MUST include the Mobile Node
Identifier option [RFC-4283], carrying the MN-Identifier for Identifier option [RFC-4283], carrying the MN-Identifier for
identifying the mobile node. identifying the mobile node.
3. The Home Network Prefix option MUST be present in the Proxy 3. The Home Network Prefix option(s) MUST be present in the Proxy
Binding Update message. If the mobile access gateway learns the Binding Update message. If the mobile access gateway learns the
mobile node's home network prefix either from its policy store mobile node's home network prefix(es) either from its policy
or from other means, the mobile access gateway MAY choose to store or from other means, the mobile access gateway MAY choose
specify the same in the Home Network Prefix option for to request the local mobility anchor to allocate the requested
requesting the local mobility anchor to allocate that prefix, prefix(es) by including a Home Network Prefix option for each of
otherwise it MUST specify a value of ALL_ZERO. If the specified those requested prefixes. The mobile access gateway MAY also
value is ALL_ZERO, then the local mobility anchor will do the choose to include just one Home Network Prefix option with the
prefix assignment. prefix value of ALL_ZERO, for requesting the local mobility
anchor to do the prefix assignment. However, when including a
Home Network Prefix option with the prefix value of ALL_ZERO,
then there MUST be only one instance of the Home Network prefix
option in the request.
4. The Handoff Indicator option MUST be present in the Proxy 4. The Handoff Indicator option MUST be present in the Proxy
Binding Update message. The Handoff Indicator field in the Binding Update message. The Handoff Indicator field in the
Handoff Indicator option MUST be set to a value indicating the Handoff Indicator option MUST be set to a value indicating the
handoff hint. handoff hint.
* The Handoff Indicator field MUST be set to value 1 * The Handoff Indicator field MUST be set to value 1
(Attachment over a new interface), if the mobile access (Attachment over a new interface), if the mobile access
gateway determines (under the Handoff Indicator gateway determines (under the Handoff Indicator
considerations specified in this section) that the mobile considerations specified in this section) that the mobile
skipping to change at page 49, line 34 skipping to change at page 50, line 40
Status field value set to TIMESTAMP_MISMATCH (Invalid timestamp Status field value set to TIMESTAMP_MISMATCH (Invalid timestamp
value), the mobile access gateway SHOULD try to register again value), the mobile access gateway SHOULD try to register again
only after it has synchronized its clock to a common time source only after it has synchronized its clock to a common time source
that is used by all the mobility entities in that domain for that is used by all the mobility entities in that domain for
their clock synchronization. The mobile access gateway SHOULD their clock synchronization. The mobile access gateway SHOULD
NOT synchronize its clock to the local mobility anchor's system NOT synchronize its clock to the local mobility anchor's system
clock, based on the timestamp present in the received message. clock, based on the timestamp present in the received message.
10. If the received Proxy Binding Acknowledgement message has the 10. If the received Proxy Binding Acknowledgement message has the
Status field value set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX Status field value set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX
(mobile node is not authorized for the requesting home network (The mobile node is not authorized for one or more of the
prefix), the mobile access gateway SHOULD NOT request for the requesting home network prefix(es)), the mobile access gateway
same prefix again, but can request the local mobility anchor to SHOULD NOT request for the same prefix(es) again, but can only
dynamically assign a prefix, by specifying a ALL_ZERO value in request the local mobility anchor to do the assignment of
the Home Network Prefix option carried in the subsequent Proxy prefix(es) by including only one Home Network Prefix option with
Binding Update message. the prefix value set to ALL_ZERO.
11. If the received Proxy Binding Acknowledgement message has the 11. If the received Proxy Binding Acknowledgement message has the
Status field value set to any value greater than or equal to 128 Status field value set to any value greater than or equal to 128
(i.e., if the binding is rejected), the mobile access gateway (i.e., if the binding is rejected), the mobile access gateway
MUST NOT advertise the mobile node's home network prefix in the MUST NOT advertise the mobile node's home network prefix(es) in
Router Advertisements sent on that access link and MUST deny the the Router Advertisement messages sent on that access link and
mobility service to the mobile node by not forwarding any MUST deny the mobility service to the mobile node by not
packets using the source address from that home network prefix forwarding any packets received from the mobile node using an
and originating from that point-to-point link. address from the home network prefix(es). It MAY also tear down
the point-to-point link shared with the mobile node.
12. If the received Proxy Binding Acknowledgement message has the 12. If the received Proxy Binding Acknowledgement message has the
Status field value set to 0 (Proxy Binding Update accepted), the Status field value set to 0 (Proxy Binding Update accepted), the
mobile access gateway MUST update the routing state, as mobile access gateway MUST setup the routing state, as explained
explained in section 6.10, and MUST also update the Binding in section 6.10, and MUST also update the Binding Update List
Update List entry for reflecting the accepted binding entry for reflecting the accepted binding registration status.
registration status. It MUST also advertise the mobile node's home network prefix(es)
as the hosted on-link prefixes, by including them in the Router
Advertisement messages that it sends on that access link.
13. If the received Proxy Binding Acknowledgement message has the 13. If the received Proxy Binding Acknowledgement message has the
address in the Link-local Address option set to a NON_ZERO address in the Link-local Address option set to a NON_ZERO
value, the mobile access gateway MUST configure that link-local value, the mobile access gateway MUST configure that link-local
address on that point-to-point link and MUST NOT configure any address on that point-to-point link and MUST NOT configure any
other link-local address on that point-to-point link. This will other link-local address on that point-to-point link. This will
avoid any link-local address collisions on that access link. avoid any link-local address collisions with the mobile node on
that access link.
6.9.1.3. Extending Binding Lifetime 6.9.1.3. Extending Binding Lifetime
1. For extending the lifetime of a currently registered mobile node 1. For extending the lifetime of a currently registered mobile node
(i.e., after a successful initial binding registration from the (i.e., after a successful initial binding registration from the
same mobile access gateway), the mobile access gateway can send a same mobile access gateway), the mobile access gateway can send a
Proxy Binding Update message to the local mobility anchor with a Proxy Binding Update message to the local mobility anchor with a
new lifetime value. This re-registration message MUST be new lifetime value. This re-registration message MUST be
constructed with the same set of options as the initial binding constructed with the same set of options as the initial binding
registration message, under the considerations specified in registration message, under the considerations specified in
Section 6.9.1.1. However the following exceptions apply. Section 6.9.1.1. However the following exceptions apply.
2. The prefix value in the Home Network Prefix option MUST be set to 2. There MUST be a Home Network Prefix option for each of the
the currently assigned home network prefix. assigned home network prefixes assigned for that mobility session
and with the prefix value in the option set to that respective
prefix value.
3. The Handoff Indicator field in the Handoff Indicator option MUST 3. The Handoff Indicator field in the Handoff Indicator option MUST
be set to a value of 5 (Handoff state not changed - Re- be set to a value of 5 (Handoff state not changed - Re-
Registration). Registration).
6.9.1.4. Mobile Node Detachment and Binding De-Registration 6.9.1.4. Mobile Node Detachment and Binding De-Registration
1. If at any point the mobile access gateway detects that the mobile 1. If at any point the mobile access gateway detects that the mobile
node has moved away from its access link, or if it decides to node has moved away from its access link, or if it decides to
terminate the mobile node's mobility session, it SHOULD send a terminate the mobile node's mobility session, it SHOULD send a
Proxy Binding Update message to the local mobility anchor with Proxy Binding Update message to the local mobility anchor with
the lifetime value set to zero. This de-registration message the lifetime value set to zero. This de-registration message
MUST be constructed with the same set of options as the initial MUST be constructed with the same set of options as the initial
binding registration message, under the considerations specified binding registration message, under the considerations specified
in Section 6.9.1.1. However, the following exceptions apply. in Section 6.9.1.1. However, the following exceptions apply.
2. The prefix value in the Home Network Prefix option MUST be set to 2. There MUST be a Home Network Prefix option for each of the
the currently assigned home network prefix. assigned home network prefix(es) assigned for that mobility
session and with the prefix value in the option set to the
respective prefix value.
3. The Handoff Indicator field in the Handoff Indicator option MUST 3. The Handoff Indicator field in the Handoff Indicator option MUST
be set to a value of 4 (Handoff state unknown). be set to a value of 4 (Handoff state unknown).
Either upon receipt of a Proxy Binding Acknowledgement message from Either upon receipt of a Proxy Binding Acknowledgement message from
the local mobility anchor or after INITIAL_BINDACK_TIMEOUT [RFC-3775] the local mobility anchor or after INITIAL_BINDACK_TIMEOUT [RFC-3775]
timeout waiting for the reply, the mobile access gateway MUST do the timeout waiting for the reply, the mobile access gateway MUST do the
following: following:
1. It MUST remove the Binding Update List entry for the mobile node 1. It MUST remove the Binding Update List entry for the mobile node
skipping to change at page 51, line 36 skipping to change at page 53, line 10
o The mobile access gateway when sending the Proxy Binding Update o The mobile access gateway when sending the Proxy Binding Update
request to the local mobility anchor MUST construct the message as request to the local mobility anchor MUST construct the message as
specified below. specified below.
IPv6 header (src=Proxy-CoA, dst=LMAA) IPv6 header (src=Proxy-CoA, dst=LMAA)
Mobility header Mobility header
- BU /* P & A flags MUST be set to value 1 */ - BU /* P & A flags MUST be set to value 1 */
Mobility Options Mobility Options
- Mobile Node Identifier option (mandatory) - Mobile Node Identifier option (mandatory)
- Home Network Prefix option (mandatory) - Home Network Prefix option(s) (mandatory)
- Handoff Indicator option (mandatory) - Handoff Indicator option (mandatory)
- Access Technology Type option (mandatory) - Access Technology Type option (mandatory)
- Timestamp option (optional) - Timestamp option (optional)
- Mobile Node Link-layer Identifier option (optional) - Mobile Node Link-layer Identifier option (optional)
- Link-local Address option (optional) - Link-local Address option (optional)
Figure 11: Proxy Binding Update message format Figure 12: Proxy Binding Update message format
o The Source Address field in the IPv6 header of the message MUST be o The Source Address field in the IPv6 header of the message MUST be
set to the global address configured on the egress interface of set to the global address configured on the egress interface of
the mobile access gateway. When there is no Alternate Care-of the mobile access gateway. When there is no Alternate Care-of
Address option present in the request, this address will be Address option present in the request, this address will be
considered as the Proxy-CoA address for this binding registration considered as the Proxy-CoA address for this binding registration
request. However, when there is Alternate Care-of Address option request. However, when there is Alternate Care-of Address option
present in the request, this address will be not be considered as present in the request, this address will be not be considered as
the Proxy-CoA address, but the address in the alternate Care-of the Proxy-CoA address, but the address in the alternate Care-of
Address option will be considered as the Proxy-CoA address. Address option will be considered as the Proxy-CoA address.
o The Destination Address field in the IPv6 header of the message o The Destination Address field in the IPv6 header of the message
MUST be set to the local mobility anchor address. MUST be set to the local mobility anchor address.
o The Mobile Node Identifier option [RFC-4283] MUST be present. o The Mobile Node Identifier option [RFC-4283] MUST be present.
o The Home Network Prefix option MUST be present. o At least one Home Network Prefix option MUST be present.
o The Handoff Indicator option MUST be present. o The Handoff Indicator option MUST be present.
o The Access Technology Type option MUST be present. o The Access Technology Type option MUST be present.
o The Timestamp option MAY be present. o The Timestamp option MAY be present.
o The Mobile Node Link-layer Identifier option MAY be present. o The Mobile Node Link-layer Identifier option MAY be present.
o The Link-local Address option MAY be present. o The Link-local Address option MAY be present.
skipping to change at page 52, line 44 skipping to change at page 54, line 16
6.9.2. Router Solicitation Messages 6.9.2. Router Solicitation Messages
A mobile node may send a Router Solicitation message on the access A mobile node may send a Router Solicitation message on the access
link shared with the mobile access gateway. The Router Solicitation link shared with the mobile access gateway. The Router Solicitation
message that the mobile node sends is as specified in [RFC-4861]. message that the mobile node sends is as specified in [RFC-4861].
The mobile access gateway on receiving the Router Solicitation The mobile access gateway on receiving the Router Solicitation
message or before sending a Router Advertisement message MUST apply message or before sending a Router Advertisement message MUST apply
the following considerations. the following considerations.
1. The mobile access gateway on receiving the Router Solicitation 1. The mobile access gateway on receiving the Router Solicitation
message SHOULD send a Router Advertisement containing the mobile message SHOULD send a Router Advertisement message containing the
node's home network prefix as the on-link prefix. However, mobile node's home network prefix(es) as the on-link prefix(es).
before sending the Router Advertisement message containing the However, before sending the Router Advertisement message
mobile node's home network prefix, it SHOULD complete the binding containing the mobile node's home network prefix(es), it SHOULD
registration process with the mobile node's local mobility complete the binding registration process with the mobile node's
anchor. local mobility anchor.
2. If the local mobility anchor rejects the binding registration 2. If the local mobility anchor rejects the binding registration
request, or, if the mobile access gateway failed to complete the request, or, if the mobile access gateway failed to complete the
binding registration process for whatever reason, the mobile binding registration process for whatever reason, the mobile
access gateway MUST NOT advertise the mobile node's home network access gateway MUST NOT advertise the mobile node's home network
prefix in the Router Advertisement messages that it sends on the prefix(es) in the Router Advertisement messages that it sends on
access link. However, it MAY choose to advertise a local visited the access link. However, it MAY choose to advertise a local
network prefix to enable the mobile node for regular IPv6 access. visited network prefix(es) to enable the mobile node for regular
IPv6 access.
3. The mobile access gateway SHOULD add the MTU option, as specified 3. The mobile access gateway SHOULD add the MTU option, as specified
in [RFC-4861], to the Router Advertisement messages that it sends in [RFC-4861], to the Router Advertisement messages that it sends
on the access link. This will ensure the mobile node on the link on the access link. This will ensure the mobile node on the link
uses the advertised MTU value. The MTU value MUST reflect the uses the advertised MTU value. The MTU value MUST reflect the
tunnel MTU for the bi-directional tunnel between the mobile tunnel MTU for the bi-directional tunnel between the mobile
access gateway and the local mobility anchor. access gateway and the local mobility anchor. Considerations
from Section 6.9.5 SHOULD be applied for determining the tunnel
MTU value.
6.9.3. Default-Router 6.9.3. Default-Router
In Proxy Mobile IPv6, the mobile access gateway is the IPv6 default- In Proxy Mobile IPv6, the mobile access gateway is the IPv6 default-
router for the mobile node on the access link, as it is the entity router for the mobile node on the access link, as it is the entity
that sends the Router Advertisements on the access link. However, as that sends the Router Advertisements on the access link. However, as
the mobile node moves from one access link to another, the serving the mobile node moves from one access link to another, the serving
mobile access gateway on those respective links will send the Router mobile access gateway on those respective links will send the Router
Advertisements. If these Router Advertisements are sent using a Advertisement messages. If these Router Advertisements are sent
different link-local address or a different link-layer address, the using a different link-local address or a different link-layer
mobile node will always detect a new default-router after every address, the mobile node will always detect a new default-router
handoff. For solving this problem, this specification requires all after every handoff. For solving this problem, this specification
the mobile access gateways in the Proxy Mobile IPv6 domain to use the requires all the mobile access gateways in the Proxy Mobile IPv6
same link-local and link-layer address on any of the access links domain to use the same link-local and link-layer address on any of
where ever the mobile node attaches. The link-layer address can be a the access links where ever the mobile node attaches. These
fixed address across that all the mobile access gateways can use on addresses can be fixed addresses across the entire Proxy Mobile IPv6
any of the point-to-point links. However, the link-local address can domain and all the mobile access gateways can use these globally
be an address provided by the local mobility anchor, or a fixed fixed address on any of the point-to-point links. Additionally, this
address. specification allows the local mobility anchor to generate the link-
local address and provide it to the mobile access gateway as part of
the signaling messages.
However, both of these approaches (a link-local address generated by
the local mobility anchor or when using a globally fixed link-local
address) have implications on the deployment of SEcure Neighbor
Discovery (SEND) [RFC-3971]. In SEND, routers have certificates and
public key pairs, and their Router Advertisements are signed with the
private keys of these key pairs. When a number of different routers
use the same addresses, the routers either all have to be able to
construct these signatures for the same key pair, or the used key
pair and the router's cryptographic identity must change after a
movement. Both approaches are problematic. Sharing of private key
information across a number of nodes would be inappropriate. And
changing even the cryptographic identity of the router goes against
the general idea of the Proxy Mobile IPv6 being as invisible to the
hosts as possible.
There is, however, ongoing work at the IETF to revise the SEND
specifications. It is suggested that these revisions also address
the above problem. Other revisions are needed to deal with other
problematic cases (such as Neighbor Discovery proxies) before wide-
spread deployment of SEND.
6.9.4. Retransmissions and Rate Limiting 6.9.4. Retransmissions and Rate Limiting
The mobile access gateway is responsible for retransmissions and rate The mobile access gateway is responsible for retransmissions and rate
limiting the binding registration requests that it sends to the local limiting the binding registration requests that it sends to the local
mobility anchor. The Retransmission and the Rate Limiting rules are mobility anchor. The Retransmission and the Rate Limiting rules are
as specified in [RFC-3775]. However, the following considerations as specified in [RFC-3775]. However, the following considerations
MUST be applied. MUST be applied.
1. When the mobile access gateway sends a Proxy Binding Update 1. When the mobile access gateway sends a Proxy Binding Update
skipping to change at page 54, line 29 skipping to change at page 56, line 27
MAY continue to send these messages at this slower rate MAY continue to send these messages at this slower rate
indefinitely. indefinitely.
4. If the Timestamp based scheme is in use, the retransmitted Proxy 4. If the Timestamp based scheme is in use, the retransmitted Proxy
Binding Update messages MUST use the latest timestamp. If the Binding Update messages MUST use the latest timestamp. If the
Sequence number scheme is in use, the retransmitted Proxy Binding Sequence number scheme is in use, the retransmitted Proxy Binding
Update messages MUST use a Sequence Number value greater than Update messages MUST use a Sequence Number value greater than
that used for the previous transmission of this Proxy Binding that used for the previous transmission of this Proxy Binding
Update message, just as specified in [RFC-3775]. Update message, just as specified in [RFC-3775].
6.9.5. Path MTU Discovery
For getting optimal throughput, it is required that the routed
packets between the local mobility anchor and the mobile access
gateway are sent in the largest size and without fragmentation. If
the mobility entities are aware of the Path MTU (PMTU) between
themselves, it can be used for determining the Tunnel Path MTU and
also for advertising this value as the link MTU on the access link
shared with the mobile node. The following are some of the
considerations related to Path MTU discovery.
o The local mobility anchor and mobile access gateway MAY use the
Path MTU Discovery mechanisms as specified in [RFC-1981] and [RFC-
4821]. for determining the Path MTU (PMTU) for the path between
themselves.
o The local mobility anchor and the mobile access gateway MAY use
any standard application probes for determining the PMTU. The
specifics details related to the type of traffic that can be used
for the PMTU discovery is outside the scope of this document.
o If there is an administratively configured PMTU value for the path
between the local mobility anchor and the mobile access gateway,
the dynamic discovery of PMTU is not required.
o The IPv6 tunnel MTU for the established tunnel between the local
mobility anchor and the mobile access gateway can be computed
based on this Path MTU value, as specified in Section 6.7 of [RFC-
2473].
o The mobile access gateway MAY use this determined tunnel Path MTU
value (for the tunnel established with the mobile node's local
mobility anchor) as the MTU value in the MTU option that it sends
in the Router Advertisements on the access link shared with the
mobile node.
6.10. Routing Considerations 6.10. Routing Considerations
This section describes how the mobile access gateway handles the This section describes how the mobile access gateway handles the
traffic to/from the mobile node that is attached to one of its access traffic to/from the mobile node that is attached to one of its access
interfaces. interfaces.
Proxy-CoA LMAA Proxy-CoA LMAA
| | | |
+--+ +---+ +---+ +--+ +--+ +---+ +---+ +--+
|MN|----------|MAG|======================|LMA|----------|CN| |MN|----------|MAG|======================|LMA|----------|CN|
+--+ +---+ +---+ +--+ +--+ +---+ +---+ +--+
IPv6 Tunnel IPv6 Tunnel
Figure 12: Proxy Mobile IPv6 Tunnel Figure 13: Proxy Mobile IPv6 Tunnel
6.10.1. Transport Network 6.10.1. Transport Network
As per this specification, the transport network between the local As per this specification, the transport network between the local
mobility anchor and the mobile access gateway is an IPv6 network. mobility anchor and the mobile access gateway is an IPv6 network.
The companion document [ID-IPV4-PMIP6] specifies the required The companion document [ID-IPV4-PMIP6] specifies the required
extensions for negotiating IPv4 transport and the corresponding extensions for negotiating IPv4 transport and the corresponding
encapsulation mode. encapsulation mode.
6.10.2. Tunneling & Encapsulation Modes 6.10.2. Tunneling & Encapsulation Modes
Each IPv6 address that a mobile node uses from its home network An IPv6 address that a mobile node uses from its home network
prefix is topologically anchored at the local mobility anchor. For a prefix(es) is topologically anchored at the local mobility anchor.
mobile node to use this address from an access network attached to a For a mobile node to use this address from an access network attached
mobile access gateway, proper tunneling techniques have to be in to a mobile access gateway, proper tunneling techniques have to be in
place. Tunneling hides the network topology and allows the mobile place. Tunneling hides the network topology and allows the mobile
node's IPv6 datagram to be encapsulated as a payload of another IPv6 node's IPv6 datagram to be encapsulated as a payload of another IPv6
packet and to be routed between the local mobility anchor and the packet and to be routed between the local mobility anchor and the
mobile access gateway. The Mobile IPv6 base specification [RFC-3775] mobile access gateway. The Mobile IPv6 base specification [RFC-3775]
defines the use of IPv6-over-IPv6 tunneling, between the home agent defines the use of IPv6-over-IPv6 tunneling [RFC-2473], between the
and the mobile node and this specification extends the use of the home agent and the mobile node and this specification extends the use
same tunneling mechanism between the local mobility anchor and the of the same tunneling mechanism for use between the local mobility
mobile access gateway. anchor and the mobile access gateway.
On most operating systems, a tunnel is implemented as a virtual On most operating systems, a tunnel is implemented as a virtual
point-to-point interface. The source and the destination address of point-to-point interface. The source and the destination address of
the two end points of this virtual interface along with the the two end points of this virtual interface along with the
encapsulation mode are specified for this virtual interface. Any encapsulation mode are specified for this virtual interface. Any
packet that is routed over this interface gets encapsulated with the packet that is routed over this interface gets encapsulated with the
outer header and the addresses as specified for that point to point outer header as specified for that point to point tunnel interface.
tunnel interface. For creating a point to point tunnel to any local
mobility anchor, the mobile access gateway may implement a tunnel For creating a point to point tunnel to any local mobility anchor,
interface with the source address field set to its Proxy-CoA address the mobile access gateway may implement a tunnel interface with the
and the destination address field set to the LMA address. source address field set to a global address on its egress interface
(Proxy-CoA) and the destination address field set to the global
address of the local mobility anchor (LMAA).
The following is the supported packet encapsulation mode that can be The following is the supported packet encapsulation mode that can be
used by the mobile access gateway and the local mobility anchor for used by the mobile access gateway and the local mobility anchor for
routing mobile node's IPv6 datagrams. routing mobile node's IPv6 datagrams.
o IPv6-In-IPv6 - IPv6 datagram encapsulated in an IPv6 packet [RFC- o IPv6-In-IPv6 - IPv6 datagram encapsulated in an IPv6 packet [RFC-
2473]. 2473].
The companion document [ID-IPV4-PMIP6] specifies other encapsulation The companion document [ID-IPV4-PMIP6] specifies other encapsulation
modes for supporting IPv4 transport. modes for supporting IPv4 transport.
skipping to change at page 56, line 12 skipping to change at page 58, line 48
packet with a TLV header. This mode is specified in [ID-IPV4- packet with a TLV header. This mode is specified in [ID-IPV4-
PMIP6]. PMIP6].
6.10.3. Local Routing 6.10.3. Local Routing
If there is data traffic between a visiting mobile node and a If there is data traffic between a visiting mobile node and a
correspondent node that is locally attached to an access link correspondent node that is locally attached to an access link
connected to the mobile access gateway, the mobile access gateway MAY connected to the mobile access gateway, the mobile access gateway MAY
optimize on the delivery efforts by locally routing the packets and optimize on the delivery efforts by locally routing the packets and
by not reverse tunneling them to the mobile node's local mobility by not reverse tunneling them to the mobile node's local mobility
anchor. The configuration variable, EnableMAGLocalRouting MAY be anchor. The flag EnableMAGLocalRouting MAY be used for controlling
used for controlling this aspect. However, in some systems, this may this behavior. However, in some systems, this may have an
have an implication on the mobile node's accounting and policy implication on the mobile node's accounting and policy enforcement as
enforcement as the local mobility anchor is not in the path for that the local mobility anchor is not in the path for that traffic and it
traffic and it will not be able to apply any traffic policies or do will not be able to apply any traffic policies or do any accounting
any accounting for those flows. for those flows.
This decision of path optimization SHOULD be based on the policy This decision of path optimization SHOULD be based on the policy
configured on the mobile access gateway, but enforced by the mobile configured on the mobile access gateway, but enforced by the mobile
node's local mobility anchor. The specific details on how this is node's local mobility anchor. The specific details on how this is
achieved are beyond of the scope of this document. achieved are beyond of the scope of this document.
6.10.4. Tunnel Management 6.10.4. Tunnel Management
All the considerations mentioned in Section 5.6.1 for the tunnel All the considerations mentioned in Section 5.6.1 for the tunnel
management on the local mobility anchor apply for the mobile access management on the local mobility anchor apply for the mobile access
skipping to change at page 56, line 44 skipping to change at page 59, line 32
o On receiving a packet from the bi-directional tunnel established o On receiving a packet from the bi-directional tunnel established
with the mobile node's local mobility anchor, the mobile access with the mobile node's local mobility anchor, the mobile access
gateway MUST use the destination address of the inner packet for gateway MUST use the destination address of the inner packet for
forwarding it on the interface where the destination network forwarding it on the interface where the destination network
prefix is hosted. The mobile access gateway MUST remove the outer prefix is hosted. The mobile access gateway MUST remove the outer
header before forwarding the packet. Considerations from [RFC- header before forwarding the packet. Considerations from [RFC-
2473] MUST be applied for IPv6 decapsulation. If the mobile 2473] MUST be applied for IPv6 decapsulation. If the mobile
access gateway cannot find the connected interface for that access gateway cannot find the connected interface for that
destination address, it MUST silently drop the packet. For destination address, it MUST silently drop the packet. For
reporting an error in such a scenario, in the form of ICMP control reporting an error in such a scenario, in the form of ICMP control
message, the considerations from [RFC-2473] must be applied. message, the considerations from [RFC-2473] MUST be applied.
o On receiving a packet from a correspondent node that is locally o On receiving a packet from a correspondent node that is locally
connected and which is destined to a mobile node that is on connected and which is destined to a mobile node that is on
another locally connected access link, the mobile access gateway another locally connected access link, the mobile access gateway
MUST check the configuration variable, EnableMAGLocalRouting, to MUST check the flag EnableMAGLocalRouting, to ensure the mobile
ensure the mobile access gateway is allowed to route the packet access gateway is allowed to route the packet directly to the
directly to the mobile node. If the mobile access gateway is not mobile node. If the mobile access gateway is not allowed to route
allowed to route the packet directly, it MUST route the packet the packet directly, it MUST route the packet through the bi-
through the bi-directional tunnel established between itself and directional tunnel established between itself and the mobile
the mobile node's local mobility anchor. Otherwise, it can route node's local mobility anchor. Otherwise, it can route the packet
the packet directly to the mobile node. directly to the mobile node.
Forwarding Packets Sent by the Mobile Node: Forwarding Packets Sent by the Mobile Node:
o On receiving a packet from a mobile node connected to its access o On receiving a packet from a mobile node connected to its access
link, the mobile access gateway MUST ensure that there is an link, the mobile access gateway MUST ensure that there is an
established binding for that mobile node with its local mobility established binding for that mobile node with its local mobility
anchor before forwarding the packet directly to the destination or anchor before forwarding the packet directly to the destination or
before tunneling the packet to the mobile node's local mobility before tunneling the packet to the mobile node's local mobility
anchor. anchor.
o On receiving a packet from a mobile node connected to its access o On receiving a packet from a mobile node connected to its access
link to a destination that is locally connected, the mobile access link for a destination that is locally connected, the mobile
gateway MUST check the configuration variable, access gateway MUST check the flag EnableMAGLocalRouting, to
EnableMAGLocalRouting, to ensure the mobile access gateway is ensure the mobile access gateway is allowed to route the packet
allowed to route the packet directly to the destination. If the directly to the destination. If the mobile access gateway is not
mobile access gateway is not allowed to route the packet directly, allowed to route the packet directly, it MUST route the packet
it MUST route the packet through the bi-directional tunnel through the bi-directional tunnel established between itself and
established between itself and the mobile node's local mobility the mobile node's local mobility anchor. Otherwise, it MUST route
anchor. Otherwise, it can route the packet directly to the the packet directly to the destination.
destination.
o On receiving a packet from the mobile node connected to its access o On receiving a packet from a mobile node connected to its access
link, to a destination that is not directly connected, the packet link, to a destination that is not directly connected, the packet
MUST be forwarded to the local mobility anchor through the bi- MUST be forwarded to the local mobility anchor through the bi-
directional tunnel established between itself and the mobile directional tunnel established between itself and the mobile
node's local mobility anchor. However, the packets that are sent node's local mobility anchor. However, the packets that are sent
with the link-local source address MUST NOT be forwarded. with the link-local source address MUST NOT be forwarded.
o The format of the tunneled packet is shown below. Considerations o The format of the tunneled packet is shown below. Considerations
from [RFC-2473] MUST be applied for IPv6 encapsulation. from [RFC-2473] MUST be applied for IPv6 encapsulation. However,
Additionally, when using IPv4 transport, the format of the when using IPv4 transport, the format of the tunneled packet is as
tunneled packet is as described in [ID-IPV4-PMIP6]. described in [ID-IPV4-PMIP6].
IPv6 header (src= Proxy-CoA, dst= LMAA /* Tunnel Header */ IPv6 header (src= Proxy-CoA, dst= LMAA /* Tunnel Header */
IPv6 header (src= MN-HoA, dst= CN ) /* Packet Header */ IPv6 header (src= MN-HoA, dst= CN ) /* Packet Header */
Upper layer protocols /* Packet Content*/ Upper layer protocols /* Packet Content*/
Figure 13: Tunneled Packets from MAG to LMA Figure 14: Tunneled Packet from MAG to LMA
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].
IPv6 header (src= Proxy-CoA, dst= LMAA /* Tunnel Header */
ESP Header in tunnel mode /* ESP Header */
IPv6 header (src= MN-HoA, dst= CN ) /* Packet Header */
Upper layer protocols /* Packet Content*/
Figure 15: Tunneled Packet from MAG to LMA with Payload Protection
6.11. Supporting DHCPv6 based Address Configuration on the Access Link 6.11. Supporting DHCPv6 based Address Configuration on the Access Link
This section explains how Stateful Address Configuration using DHCPv6 This section explains how Stateful Address Configuration using DHCPv6
can be enabled on the point-to-point link between the mobile node and can be enabled on the point-to-point link between the mobile node and
the mobile access gateway and how a mobile node attached to that link the mobile access gateway and how a mobile node attached to that link
can obtain an address from its home network prefix and using DHCPv6. can obtain an address from its home network prefix and using DHCPv6.
o For supporting Stateful Address Configuration using DHCPv6, the o For supporting Stateful Address Configuration using DHCPv6, the
DHCPv6 relay agent [RFC-3315] service MUST be configured on each DHCPv6 relay agent [RFC-3315] service MUST be configured on each
of the mobile access gateways in the Proxy Mobile IPv6 domain. of the mobile access gateways in the Proxy Mobile IPv6 domain.
Further, as specified in Section 20 of [RFC-3315], the DHCPv6 Further, as specified in Section 20 of [RFC-3315], the DHCPv6
relay agent should be configured to use a list of destination relay agent should be configured to use a list of destination
addresses, which MAY include unicast addresses, the addresses, which MAY include unicast addresses, the
All_DHCP_Servers multicast address, or other addresses selected by All_DHCP_Servers multicast address, or other addresses selected by
the network administrator. the network administrator.
o A DHCPv6 server in the Proxy Mobile IPv6 domain can be configured o The DHCPv6 server in the Proxy Mobile IPv6 domain MUST be
with a set of prefixes (P1, P2, ..., Pn). Each one of these configured with prefix groups, One Prefix Group: ([P1], [P2], .. ,
prefixes in this prefix list is a home network prefix that the [Pn]), Two Prefix Group: ([P5,P6], [P7,P8] .. [Pm-1, Pm]. Each
local mobility anchor(s) can assign to any mobile node. However, of the entries represent a link on which the prefix(es) are
the DHCPv6 server will not know the relation between a given hosted. The local mobility anchor(s) will assign all the
prefix and a mobile node to which the corresponding prefix is prefix(es) under a given entry to a mobile node's interface. The
allocated. It just views these prefixes as hosted prefixes on prefixes under a given entry always go as a group and cannot be
different links in that domain and assigns individual addresses mixed in any order and can only be assigned to only one mobile
from the respective prefixes based on the prefix value present in node's interface. If the Proxy Mobile IPv6 domain support only
the link-address option of the received DHCPv6 request. single prefix for a given mobile node's interface, then the DHCPv6
server need to maintain just one group of single prefixes.
o The DHCPv6 server will not know the relation between the
prefix(es) listed under an entry and a mobile node to which the
corresponding prefixes are allocated. It just views these
prefixes as hosted prefixes on a given link in that domain. Based
on the prefix value present in the link-address option of the
received DHCPv6 request, the DHCPv6 server assigns addresses from
all of the prefixes associated with that link,
o When a mobile node sends a DHCPv6 request message, the DHCPv6 o When a mobile node sends a DHCPv6 request message, the DHCPv6
relay agent function on the mobile access gateway will set the relay agent function on the mobile access gateway will set the
link-address field in the DHCPv6 message to an address in the link-address field in the DHCPv6 message to an address in the
mobile node's home network prefix. The address is generated as mobile node's home network prefix (any one of the mobile node's
per [RFC-4862] by combining the mobile node's home network prefix home network prefix assigned to that mobile node's attached
(assigned by the local mobility anchor for this mobility session) interface). The address is generated as per [RFC-4862] by
and its own interface identifier on the access link shared with combining that mobile node's home network prefix and its own
the mobile node, so as to provide a prefix hint to the DHCPv6 interface identifier on the access link shared with the mobile
Server for the prefix selection. The DHCPv6 server on receiving node, so as to provide a hint to the DHCPv6 Server for the link
the request from the mobile node, will allocate an address from identification. The DHCPv6 server on receiving the request from
the prefix pointed to by the link-address field of the request. the mobile node, will allocate address(es) from the prefixes
associated with that link (identified using the link-address field
of the request).
o Once the mobile node obtains an address and moves to a different o Once the mobile node obtains address(es) and moves to a different
link and sends a DHCPv6 request (at any time) for extending the link and sends a DHCPv6 request (at any time) for extending the
DHCP lease, the DHCPv6 relay agent on the new link will set the DHCP lease, the DHCPv6 relay agent on the new link will set the
prefix hint in the DHCPv6 message to the mobile node's home prefix hint in the DHCPv6 message to one of the mobile node's home
network prefix (assigned by the local mobility anchor for this network prefix (assigned by the local mobility anchor for this
mobility session). The DHCPv6 server will identify the client mobility session). The DHCPv6 server will identify the client
from the Client-DUID option present in the request and will from the Client-DUID option present in the request and will
allocate the same address as before. allocate the same address(es) as before.
o The DHCPv6 based address configuration is not recommended for o The DHCPv6 based address configuration is not recommended for
deployments where the local mobility anchor and the mobile access deployments where the local mobility anchor and the mobile access
gateways are located in different administrative domains. For gateways are located in different administrative domains. For
this configuration to work, all the mobile access gateways in the this configuration to work, all the mobile access gateways in the
Proxy Mobile IPv6 domain should be able to ensure that the DHCPv6 Proxy Mobile IPv6 domain should be able to ensure that the DHCPv6
request messages from a given mobile node anchored on any of the request messages from a given mobile node anchored on any of the
access links in that domain, will always be handled by the same access links in that domain, will always be handled by the same
DHCPv6 server or by a server from the same group of coordinated DHCPv6 server or by a server from the same group of coordinated
DHCPv6 servers serving that domain. DHCPv6 servers serving that domain.
o The DHCPv6 server should be configured to offer low address lease o The DHCPv6 server should be configured to offer low address lease
times. A lease time that is too large prevents the DHCPv6 server times. A lease time that is too large prevents the DHCPv6 server
from reclaiming the address even after the local mobility anchor from reclaiming the address even after the local mobility anchor
deletes the mobile node's binding cache entry. It is recommended deletes the mobile node's binding cache entry. It is recommended
that the configured lease time be lower than the accepted binding that the configured lease time be lower than the accepted binding
lifetime for any mobility binding. lifetime for any mobility binding.
6.12. Home Network Prefix Renumbering 6.12. Home Network Prefix Renumbering
If the mobile node's home network prefix gets renumbered or becomes If the mobile node's home network prefix(es) gets renumbered or
invalid during the middle of a mobility session, the mobile access becomes invalid during the middle of a mobility session, the mobile
gateway MUST withdraw the prefix by sending a Router Advertisement on access gateway MUST withdraw the prefix(es) by sending a Router
the access link with zero prefix lifetime for the mobile node's home Advertisement message on the access link with zero prefix lifetime
network prefix. Also, the local mobility anchor and the mobile for the prefix(es) that is being renumbered. Also, the local
access gateway MUST delete the routing state for that prefix. mobility anchor and the mobile access gateway MUST delete the created
However, the specific details on how the local mobility anchor routing state for the renumbered prefix(es). However, the specific
notifies the mobile access gateway about the mobile node's home details on how the local mobility anchor notifies the mobile access
network prefix renumbering are outside the scope of this document. gateway about the mobile node's home network prefix(es) renumbering
are outside the scope of this document.
6.13. Mobile Node Detachment Detection and Resource Cleanup 6.13. Mobile Node Detachment Detection and Resource Cleanup
Before sending a Proxy Binding Update message to the local mobility Before sending a Proxy Binding Update message to the local mobility
anchor for extending the lifetime of a currently existing binding of anchor for extending the lifetime of a currently existing binding of
a mobile node, the mobile access gateway MUST make sure the mobile a mobile node, the mobile access gateway MUST make sure the mobile
node is still attached to the connected link by using some reliable node is still attached to the connected link by using some reliable
method. If the mobile access gateway cannot predictably detect the method. If the mobile access gateway cannot predictably detect the
presence of the mobile node on the connected link, it MUST NOT presence of the mobile node on the connected link, it MUST NOT
attempt to extend the registration lifetime of the mobile node. attempt to extend the registration lifetime of the mobile node.
skipping to change at page 60, line 41 skipping to change at page 64, line 5
node. If the mobile node is entitled for network-based mobility node. If the mobile node is entitled for network-based mobility
management service, then the mobile access gateway must ensure the management service, then the mobile access gateway must ensure the
mobile node believes it is on its home link, as explained in various mobile node believes it is on its home link, as explained in various
sections of this specification. sections of this specification.
If the mobile node is not entitled for the network-based mobility If the mobile node is not entitled for the network-based mobility
management service, as determined from the policy considerations, the management service, as determined from the policy considerations, the
mobile access gateway MAY choose to offer regular IPv6 access to the mobile access gateway MAY choose to offer regular IPv6 access to the
mobile node and in such a scenario the normal IPv6 considerations mobile node and in such a scenario the normal IPv6 considerations
apply. If IPv6 access is enabled, the mobile node SHOULD be able to apply. If IPv6 access is enabled, the mobile node SHOULD be able to
obtain an IPv6 address using normal IPv6 address configuration obtain IPv6 address(es) using the normal IPv6 address configuration
procedures. The obtained address must be from a local visitor procedures. The obtained address(es) must be from a local visitor
network prefix. This essentially ensures that the mobile access network prefix(es). This essentially ensures that the mobile access
gateway functions as a normal access router to a mobile node attached gateway functions as a normal access router to a mobile node attached
to its access link and without impacting its host-based mobility to its access link and without impacting its host-based mobility
protocol operation. protocol operation.
7. Mobile Node Operation 7. Mobile Node Operation
This non-normative section explains the mobile node's operation in a This non-normative section explains the mobile node's operation in a
Proxy Mobile IPv6 domain. Proxy Mobile IPv6 domain.
7.1. Moving into a Proxy Mobile IPv6 Domain 7.1. Moving into a Proxy Mobile IPv6 Domain
skipping to change at page 61, line 19 skipping to change at page 64, line 30
an access network, the mobile access gateway on the access link an access network, the mobile access gateway on the access link
detects the attachment of the mobile node and completes the binding detects the attachment of the mobile node and completes the binding
registration with the mobile node's local mobility anchor. If the registration with the mobile node's local mobility anchor. If the
binding update operation is successfully performed, the mobile access binding update operation is successfully performed, the mobile access
gateway will create the required state and set up the data path for gateway will create the required state and set up the data path for
the mobile node's data traffic. the mobile node's data traffic.
If the mobile node is IPv6 enabled, on attaching to the access link, If the mobile node is IPv6 enabled, on attaching to the access link,
it will typically send a Router Solicitation message [RFC-4861]. The it will typically send a Router Solicitation message [RFC-4861]. The
mobile access gateway on the access link will respond to the Router mobile access gateway on the access link will respond to the Router
Solicitation message with a Router Advertisement. The Router Solicitation message with a Router Advertisement message. The Router
Advertisement will have the mobile node's home network prefix, Advertisement message will carry the mobile node's home network
default-router address and other address configuration parameters. prefix(es), default-router address and other address configuration
Parameters.
If the mobile access gateway on the access link receives a Router If the mobile access gateway on the access link receives a Router
Solicitation message from the mobile node, before it completes the Solicitation message from the mobile node, before it completes the
signaling with the mobile node's local mobility anchor, the mobile signaling with the mobile node's local mobility anchor, the mobile
access gateway may not know the mobile node's home network prefix and access gateway may not know the mobile node's home network prefix(es)
may not be able to emulate the mobile node's home link on the access and may not be able to emulate the mobile node's home link on the
link. In such a scenario, the mobile node may notice a slight delay access link. In such a scenario, the mobile node may notice a slight
before it receives a Router Advertisement message. delay before it receives a Router Advertisement message.
If the received Router Advertisement has the Managed Address If the received Router Advertisement message has the Managed Address
Configuration flag set, the mobile node, as it would normally do, Configuration flag set, the mobile node, as it would normally do,
will send a DHCPv6 Request [RFC-3315]. The DHCP relay service will send a DHCPv6 Request [RFC-3315]. The DHCP relay service
enabled on that access link will ensure the mobile node will obtain enabled on that access link will ensure the mobile node can obtain
its IPv6 address as a lease from its home network prefix. one or more addresses and from its home network prefix(es).
If the received Router Advertisement does not have the Managed If the received Router Advertisement message does not have the
Address Configuration flag set and if the mobile node is allowed to Managed Address Configuration flag set and if the mobile node is
use an autoconfigured address, the mobile node will be able to obtain allowed to use autoconfigured address(es), the mobile node will be
an IPv6 address using any of the standard IPv6 address configuration able to obtain IPv6 address(es) and from each of its home network
prefixes using any of the standard IPv6 address configuration
mechanisms permitted for that mode. mechanisms permitted for that mode.
If the mobile node is IPv4 enabled and if the network permits, it If the mobile node is IPv4 enabled and if the network permits, it
will be able to obtain the IPv4 address configuration as specified in will be able to obtain the IPv4 address configuration as specified in
the companion document [ID-IPV4-PMIP6]. the companion document [ID-IPV4-PMIP6].
Once the address configuration is complete, the mobile node can Once the address configuration is complete, the mobile node can
continue to use this address configuration as long as it is attached continue to use this address configuration as long as it is attached
to the network that is in the scope of that Proxy Mobile IPv6 domain. to the network that is in the scope of that Proxy Mobile IPv6 domain.
7.2. Roaming in the Proxy Mobile IPv6 Domain 7.2. Roaming in the Proxy Mobile IPv6 Domain
After obtaining the address configuration in the Proxy Mobile IPv6 After obtaining the address configuration in the Proxy Mobile IPv6
domain, as the mobile node moves and changes its point of attachment domain, as the mobile node moves and changes its point of attachment
from one mobile access gateway to the other, it can still continue to from one mobile access gateway to the other, it can still continue to
use the same address configuration. As long as the attached access use the same address configuration. As long as the attached access
link is in the scope of that Proxy Mobile IPv6 domain, the mobile link is in the scope of that Proxy Mobile IPv6 domain, the mobile
node will always detect the same default-router advertising the node will always detect the same default-router advertising the
mobile node's home network prefix on each connected link. If the mobile node's home network prefix(es) on each connected link. If the
mobile node performs DHCP operation, it will always obtain the same mobile node has address configuration that it obtained using DHCPv6,
address as before. it will be able to retain the address configuration and extend the
lease lifetime.
8. Message Formats 8. Message Formats
This section defines extensions to the Mobile IPv6 [RFC-3775] This section defines extensions to the Mobile IPv6 [RFC-3775]
protocol messages. protocol messages.
8.1. Proxy Binding Update Message 8.1. Proxy Binding Update Message
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 63, line 23 skipping to change at page 67, line 6
Mobility Options Mobility Options
Variable-length field of such length that the complete Mobility Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. This field Header is an integer multiple of 8 octets long. This field
contains zero or more TLV-encoded mobility options. The encoding contains zero or more TLV-encoded mobility options. The encoding
and format of defined options are described in Section 6.2 of and format of defined options are described in Section 6.2 of
[RFC-3775]. The local mobility anchor MUST ignore and skip any [RFC-3775]. The local mobility anchor MUST ignore and skip any
options which it does not understand. options which it does not understand.
As per this specification, the following mobility options are As per this specification, the following mobility options are
valid in a Proxy Binding Update message. There can be only one valid in a Proxy Binding Update message. These options can be
instance of each of these options present in the message and in present in the message in any order. There can be one or more
any order. instances of the Home Network Prefix options present in the
message. However, there cannot be more than one instance of any
of the other options.
Mobile Node Identifier option Mobile Node Identifier option
Home Network Prefix option Home Network Prefix option
Handoff Indicator option Handoff Indicator option
Access Technology Type option Access Technology Type option
Timestamp option Timestamp option
Mobile Node Link-layer Identifier option Mobile Node Link-layer Identifier option
Link-local Address option Link-local Address option
Additionally, there can one or more instances of the Vendor-
Specific Mobility option [RFC-5094].
For descriptions of other fields present in this message, refer to For descriptions of other fields present in this message, refer to
section 6.1.7 of [RFC-3775]. section 6.1.7 of [RFC-3775].
8.2. Proxy Binding Acknowledgement Message 8.2. Proxy Binding Acknowledgement Message
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |K|R|P|Reserved | | Status |K|R|P|Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 65, line 6 skipping to change at page 68, line 30
Mobility Options Mobility Options
Variable-length field of such length that the complete Mobility Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. This field Header is an integer multiple of 8 octets long. This field
contains zero or more TLV-encoded mobility options. The encoding contains zero or more TLV-encoded mobility options. The encoding
and format of defined options are described in Section 6.2 of and format of defined options are described in Section 6.2 of
[RFC-3775]. The mobile access gateway MUST ignore and skip any [RFC-3775]. The mobile access gateway MUST ignore and skip any
options which it does not understand. options which it does not understand.
As per this specification, the following mobility options are As per this specification, the following mobility options are
valid in a Proxy Binding Acknowledgement message. There can be valid in a Proxy Binding Acknowledgement message. These options
only one instance of each of these options present in the message can be present in the message in any order. There can be one or
and in any order. more instances of the Home Network Prefix options present in the
message. However, there cannot be more than one instance of any
of the other options.
Mobile Node Identifier option Mobile Node Identifier option
Home Network Prefix option Home Network Prefix option
Handoff Indicator option Handoff Indicator option
Access Technology Type option Access Technology Type option
Timestamp option Timestamp option
Mobile Node Link-layer Identifier option Mobile Node Link-layer Identifier option
Link-local Address option Link-local Address option
Additionally, there can one or more instances of the Vendor-
Specific Mobility option [RFC-5094].
Status Status
8-bit unsigned integer indicating the disposition of the Proxy 8-bit unsigned integer indicating the disposition of the Proxy
Binding Update. Values of the Status field less than 128 indicate Binding Update. Values of the Status field less than 128 indicate
that the Proxy Binding Update was accepted by the local mobility that the Proxy Binding Update was accepted by the local mobility
anchor. Values greater than or equal to 128 indicate that the anchor. Values greater than or equal to 128 indicate that the
binding registration was rejected by the local mobility anchor. binding registration was rejected by the local mobility anchor.
Section 8.9 defines the Status values that can used in Proxy Section 8.9 defines the Status values that can used in Proxy
Binding Acknowledgement message. Binding Acknowledgement message.
For descriptions of other fields present in this message, refer to For descriptions of other fields present in this message, refer to
the section 6.1.8 of [RFC-3775]. the section 6.1.8 of [RFC-3775].
8.3. Home Network Prefix Option 8.3. Home Network Prefix Option
A new option, Home Network Prefix Option is defined for using it in A new option, Home Network Prefix Option is defined for using it in
the Proxy Binding Update and Proxy Binding Acknowledgement messages the Proxy Binding Update and Proxy Binding Acknowledgement messages
exchanged between a local mobility anchor and a mobile access exchanged between a local mobility anchor and a mobile access
gateway. This option is used for exchanging the mobile node's home gateway. This option is used for exchanging the mobile node's home
network prefix information. network prefix information. There can be multiple Home Network
Prefix options present in the message.
The Home Network Prefix Option has an alignment requirement of 8n+4. The Home Network Prefix Option has an alignment requirement of 8n+4.
Its format is as follows: Its format is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix Length | | Type | Length | Reserved | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 68, line 40 skipping to change at page 72, line 40
Access Technology Type (ATT) Access Technology Type (ATT)
A 8-bit field that specifies the access technology through A 8-bit field that specifies the access technology through
which the mobile node is connected to the access link on the which the mobile node is connected to the access link on the
mobile access gateway. mobile access gateway.
The values (0 - 255) will be allocated and managed by IANA. The The values (0 - 255) will be allocated and managed by IANA. The
following values are currently reserved for the below specified following values are currently reserved for the below specified
access technology types. access technology types.
0: Reserved 0: Reserved ("Reserved")
1: Virtual 1: Virtual ("Logical Network Interface")
2: PPP 2: PPP ("Point-to-Point Protocol")
3: 802.3 (Ethernet) 3: IEEE 802.3 ("Ethernet")
4: 802.11a/b/g 4: IEEE 802.11a/b/g ("Wireless LAN")
5: 802.16e 5: IEEE 802.16e ("WIMAX")
8.6. Mobile Node Link-layer Identifier Option 8.6. Mobile Node Link-layer Identifier Option
A new option, Mobile Node Link-layer Identifier Option is defined for A new option, Mobile Node Link-layer Identifier Option is defined for
using it in the Proxy Binding Update and Proxy Binding using it in the Proxy Binding Update and Proxy Binding
Acknowledgement messages exchanged between a local mobility anchor Acknowledgement messages exchanged between a local mobility anchor
and a mobile access gateway. This option is used for exchanging the and a mobile access gateway. This option is used for exchanging the
mobile node's link-layer identifier. mobile node's link-layer identifier.
The format of the Link-layer Identifier option is shown below. Based The format of the Link-layer Identifier option is shown below. Based
skipping to change at page 72, line 23 skipping to change at page 76, line 23
Not local mobility anchor for this mobile node Not local mobility anchor for this mobile node
MAG_NOT_AUTHORIZED_FOR_PROXY_REG: IANA MAG_NOT_AUTHORIZED_FOR_PROXY_REG: IANA
The mobile access gateway is not authorized to send proxy binding The mobile access gateway is not authorized to send proxy binding
registrations registrations
NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX: IANA NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX: IANA
The mobile node is not authorized for the requesting home network The mobile node is not authorized for one or more of the
prefix requesting home network prefixes.
TIMESTAMP_MISMATCH: IANA TIMESTAMP_MISMATCH: IANA
Invalid timestamp value (the clocks are out of sync) Invalid timestamp value (the clocks are out of sync)
TIMESTAMP_LOWER_THAN_PREV_ACCEPTED: IANA TIMESTAMP_LOWER_THAN_PREV_ACCEPTED: IANA
The timestamp value is lower than the previously accepted value The timestamp value is lower than the previously accepted value
MISSING_HOME_NETWORK_PREFIX_OPTION: IANA MISSING_HOME_NETWORK_PREFIX_OPTION: IANA
skipping to change at page 73, line 23 skipping to change at page 77, line 23
0 Proxy Binding Update accepted 0 Proxy Binding Update accepted
128 Reason unspecified 128 Reason unspecified
129 Administratively prohibited 129 Administratively prohibited
130 Insufficient resources 130 Insufficient resources
9. Protocol Configuration Variables 9. Protocol Configuration Variables
9.1. Local Mobility Anchor - Configuration Variables
The local mobility anchor MUST allow the following variables to be The local mobility anchor MUST allow the following variables to be
configured by the system management. The configured values for these configured by the system management. The configured values for these
protocol variables MUST survive server reboots and service restarts. protocol variables MUST survive server reboots and service restarts.
MinDelayBeforeBCEDelete MinDelayBeforeBCEDelete
This variable specifies the amount of time in milliseconds the This variable specifies the amount of time in milliseconds the
local mobility anchor MUST wait before it deletes a Binding Cache local mobility anchor MUST wait before it deletes a Binding Cache
entry of a mobile node, upon receiving a Proxy Binding Update entry of a mobile node, upon receiving a Proxy Binding Update
message from a mobile access gateway with a lifetime value of 0. message from a mobile access gateway with a lifetime value of 0.
skipping to change at page 74, line 22 skipping to change at page 78, line 27
This variable specifies the maximum amount of time difference in This variable specifies the maximum amount of time difference in
milliseconds between the timestamp in the received Proxy Binding milliseconds between the timestamp in the received Proxy Binding
Update message and the current time-of-day on the local mobility Update message and the current time-of-day on the local mobility
anchor, that is allowed by the local mobility anchor for the anchor, that is allowed by the local mobility anchor for the
received message to be considered valid. received message to be considered valid.
The default value for this variable is 300 milliseconds. This The default value for this variable is 300 milliseconds. This
variable must be adjusted to suit the deployments. variable must be adjusted to suit the deployments.
9.2. Mobile Access Gateway - Configuration Variables
The mobile access gateway MUST allow the following variables to be The mobile access gateway MUST allow the following variables to be
configured by the system management. The configured values for these configured by the system management. The configured values for these
protocol variables MUST survive server reboots and service restarts. protocol variables MUST survive server reboots and service restarts.
EnableMAGLocalRouting EnableMAGLocalRouting
This flag indicates whether or not the mobile access gateway is This flag indicates whether or not the mobile access gateway is
allowed to enable local routing of the traffic exchanged between a allowed to enable local routing of the traffic exchanged between a
visiting mobile node and a correspondent node that is locally visiting mobile node and a correspondent node that is locally
connected to one of the interfaces of the mobile access gateway. connected to one of the interfaces of the mobile access gateway.
skipping to change at page 74, line 45 skipping to change at page 79, line 8
The default value for this flag is set to value of 0, indicating The default value for this flag is set to value of 0, indicating
that the mobile access gateway MUST reverse tunnel all the traffic that the mobile access gateway MUST reverse tunnel all the traffic
to the mobile node's local mobility anchor. to the mobile node's local mobility anchor.
When the value of this flag is set to value of 1, the mobile When the value of this flag is set to value of 1, the mobile
access gateway MUST route the traffic locally. access gateway MUST route the traffic locally.
This aspect of local routing MAY be defined as policy on a per This aspect of local routing MAY be defined as policy on a per
mobile basis and when present will take precedence over this flag. mobile basis and when present will take precedence over this flag.
9.3. Proxy Mobile IPv6 Domain - Configuration Variables
All the mobile entities (local mobility anchors and mobile access
gateways in a Proxy Mobile IPv6 domain MUST allow the following
variables to be configured by the system management. The configured
values for these protocol variables MUST survive server reboots and
service restarts. These variables MUST be globally fixed for a given
Proxy Mobile IPv6 domain resulting in the same values being enforced
on all the mobility entities in that domain.
MobileNodeGeneratedTimestampInUse
This flag indicates whether or not the mobile node generated
timestamp mechanism is in use in that Proxy Mobile IPv6 domain.
When the value for this flag is set to 1, the local mobility
anchors and mobile access gateways in that Proxy Mobile IPv6
domain MUST apply the mobile node generated timestamp
considerations.
The default value for this flag is set to value of 0, indicating
that the mobile node generated timestamp mechanism is not in use
in that Proxy Mobile IPv6 domain.
10. IANA Considerations 10. IANA Considerations
This document defines six new Mobility Header options, the Home This document defines six new Mobility Header options, the Home
Network Prefix option, Handoff Indicator option, Access Technology Network Prefix option, Handoff Indicator option, Access Technology
Type option, Mobile Node Link-layer Identifier option, Link-local Type option, Mobile Node Link-layer Identifier option, Link-local
Address option and Timestamp option. These options are described in Address option and Timestamp option. These options are described in
Section 8. The Type value for these options needs to be assigned Section 8. The Type value for these options needs to be assigned
from the same numbering space as allocated for the other mobility from the same numbering space as allocated for the other mobility
options, as defined in [RFC-3775]. options, as defined in [RFC-3775].
skipping to change at page 76, line 28 skipping to change at page 81, line 14
message for a given mobile node, may ensure that the mobile node is message for a given mobile node, may ensure that the mobile node is
definitively attached to the mobile access gateway that sent the definitively attached to the mobile access gateway that sent the
proxy binding registration request. This may be accomplished by proxy binding registration request. This may be accomplished by
contacting a trusted entity which is able to track the mobile node's contacting a trusted entity which is able to track the mobile node's
current point of attachment. However, the specific details of the current point of attachment. However, the specific details of the
actual mechanisms for achieving this is outside the scope of this actual mechanisms for achieving this is outside the scope of this
document. document.
12. Acknowledgements 12. Acknowledgements
The authors would like to specially thank Julien Laganier, Christian The authors would like to specially thank Jari Arkko, Julien
Vogt, Dave Thaler, Pete McCann, Brian Haley, Ahmad Muhanna, JinHyeock Laganier, Christian Vogt, Dave Thaler, Pasi Eronen, Pete McCann,
Choi, Jari Arkko and Elwyn Davies for their thorough review of this Brian Haley, Ahmad Muhanna, JinHyeock Choi and Elwyn Davies for their
document. thorough review of this document.
The authors would also like to thank Alex Petrescu, Alice Qinxia, The authors would also like to thank Alex Petrescu, Alice Qinxia,
Alper Yegin, Ashutosh Dutta, Behcet Sarikaya, Fred Templin, Genadi Alper Yegin, Ashutosh Dutta, Behcet Sarikaya, Fred Templin, Genadi
Velev, George Tsirtsis, Gerardo Giaretta, Henrik Levkowetz, Hesham Velev, George Tsirtsis, Gerardo Giaretta, Henrik Levkowetz, Hesham
Soliman, James Kempf, Jean-Michel Combes, Jun Awano, John Zhao, Jong- Soliman, James Kempf, Jean-Michel Combes, Jun Awano, John Zhao, Jong-
Hyouk Lee, Jonne Soininen, Jouni Korhonen, Kalin Getov, Kilian Hyouk Lee, Jonne Soininen, Jouni Korhonen, Kalin Getov, Kilian
Weniger, Marco Liebsch, Mohamed Khalil, Nishida Katsutoshi, Phil Weniger, Lars Eggert, Magnus Westerlund, Marco Liebsch, Mohamed
Roberts, Ryuji Wakikawa, Sangjin Jeong, Suresh Krishnan, Uri Khalil, Nishida Katsutoshi, Phil Roberts, Ryuji Wakikawa, Sangjin
Blumenthal, Ved Kafle, Vidya Narayanan, Youn-Hee Han and many others Jeong, Suresh Krishnan, Uri Blumenthal, Ved Kafle, Vidya Narayanan,
for their passionate discussions in the working group mailing list on Youn-Hee Han and many others for their passionate discussions in the
the topic of localized mobility management solutions. These working group mailing list on the topic of localized mobility
discussions stimulated much of the thinking and shaped the draft to management solutions. These discussions stimulated much of the
the current form and we acknowledge that ! thinking and shaped the draft to the current form and we acknowledge
that !
The authors would also like to thank Ole Troan, Akiko Hattori, Parviz The authors would also like to thank Ole Troan, Akiko Hattori, Parviz
Yegani, Mark Grayson, Michael Hammer, Vojislav Vucetic, Jay Iyer and Yegani, Mark Grayson, Michael Hammer, Vojislav Vucetic, Jay Iyer and
Tim Stammers for their input on this document. Tim Stammers for their input on this document.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 78, line 10 skipping to change at page 82, line 41
[RFC-4861] Narten, T., Nordmark, E. and W. Simpson, Soliman, H., [RFC-4861] Narten, T., Nordmark, E. and W. Simpson, Soliman, H.,
"Neighbor Discovery for IP Version 6 (IPv6)", RFC 4861, September "Neighbor Discovery for IP Version 6 (IPv6)", RFC 4861, September
2007. 2007.
13.2. Informative References 13.2. Informative References
[RFC-1661] Simpson, W., Ed., "The Point-To-Point Protocol (PPP)", STD [RFC-1661] Simpson, W., Ed., "The Point-To-Point Protocol (PPP)", STD
51, RFC 1661, July 1994. 51, RFC 1661, July 1994.
[RFC-1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery
for IP version 6", RFC 1981, August 1996.
[RFC-2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC-2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June
2000. 2000.
[RFC-3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC-3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC-3971] Arkko, J., Ed., Kempf, J., Sommerfeld, B., Zill, B., and [RFC-3971] Arkko, J., Ed., Kempf, J., Sommerfeld, B., Zill, B., and
P. Nikander, "SEcure Neighbor Discovery (SEND)", RFC 3971, March P. Nikander, "SEcure Neighbor Discovery (SEND)", RFC 3971, March
2005. 2005.
[RFC-4306] Kaufman, C, et al, "Internet Key Exchange (IKEv2) [RFC-4306] Kaufman, C, et al, "Internet Key Exchange (IKEv2)
Protocol", RFC 4306, December 2005. Protocol", RFC 4306, December 2005.
[RFC-4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4 [RFC-4330] Mills, D., "Simple Network Time Protocol (SNTP) Version 4
for IPv4, IPv6 and OSI", RFC 4330, October 1996. for IPv4, IPv6 and OSI", RFC 4330, October 1996.
[RFC-4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, [RFC-4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney,
"Chargeable User Identity", RFC 4372, January 2006. "Chargeable User Identity", RFC 4372, January 2006.
[RFC-4821] Mathis, M. and Heffner, J., "Packetization Layer Path MTU
Discovery", RFC 4821, March 2007.
[RFC-4830] Kempf, J., Leung, K., Roberts, P., Nishida, K., Giaretta, [RFC-4830] Kempf, J., Leung, K., Roberts, P., Nishida, K., Giaretta,
G., Liebsch, M., "Problem Statement for Network-based Localized G., Liebsch, M., "Problem Statement for Network-based Localized
Mobility Management", September 2006. Mobility Management", September 2006.
[RFC-4831] Kempf, J., Leung, K., Roberts, P., Nishida, K., Giaretta, [RFC-4831] Kempf, J., Leung, K., Roberts, P., Nishida, K., Giaretta,
G., Liebsch, M., "Goals for Network-based Localized Mobility G., Liebsch, M., "Goals for Network-based Localized Mobility
Management", October 2006. Management", October 2006.
[RFC-4832] Vogt, C., Kempf, J., "Security Threats to Network-Based [RFC-4832] Vogt, C., Kempf, J., "Security Threats to Network-Based
Localized Mobility Management", September 2006. Localized Mobility Management", September 2006.
[RFC-4862] Thompson, S., Narten, T., Jinmei, T., "IPv6 Stateless [RFC-4862] Thompson, S., Narten, T., Jinmei, T., "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[RFC-4941] Narten, T., Draves, R., Krishnan, S., "Privacy Extensions [RFC-4941] Narten, T., Draves, R., Krishnan, S., "Privacy Extensions
for Stateless Address Autoconfiguration in IPv6", RFC 4941, September for Stateless Address Autoconfiguration in IPv6", RFC 4941, September
2007. 2007.
[RFC-5094] Devarapalli, V., Leung, K. and Patel, A., "Mobile IPv6
Vendor Specific Option", RFC 5094, December 2007.
[ID-IPV4-PMIP6] Wakikawa, R. and Gundavelli, S., "IPv4 Support for [ID-IPV4-PMIP6] Wakikawa, R. and Gundavelli, S., "IPv4 Support for
Proxy Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-02.txt, Proxy Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-02.txt,
November 2007. November 2007.
[ID-DNAV6] Narayanan, S., et al "Detecting Network Attachment in IPv6 [ID-DNAV6] Narayanan, S., et al "Detecting Network Attachment in IPv6
Networks (DNAv6)", draft-ietf-dna-protocol-07.txt, February 2008. Networks (DNAv6)", draft-ietf-dna-protocol-07.txt, February 2008.
Appendix A. Proxy Mobile IPv6 interactions with AAA Infrastructure Appendix A. Proxy Mobile IPv6 interactions with AAA Infrastructure
Every mobile node that roams in a proxy Mobile IPv6 domain, would Every mobile node that roams in a proxy Mobile IPv6 domain, would
typically be identified by an identifier, MN-Identifier, and that typically be identified by an identifier, MN-Identifier, and that
identifier will have an associated policy profile that identifies the identifier will have an associated policy profile that identifies the
mobile node's home network prefix, permitted address configuration mobile node's home network prefix(es) on a per-interface basis,
modes, roaming policy and other parameters that are essential for permitted address configuration modes, roaming policy and other
providing network-based mobility service. This information is parameters that are essential for providing network-based mobility
typically configured in AAA. It is possible the home network prefix management service. This information is typically configured in AAA.
is dynamically allocated for the mobile node when it boots up for the In some cases, the home network prefix(es) may be dynamically
first time in the network, or it could be a statically configured assigned to the mobile node's interface, after its initial attachment
value on per mobile node basis. However, for all practical purposes, to the Proxy Mobile IPv6 domain over that interface and may not be
the network entities in the proxy Mobile IPv6 domain, while serving a configured in the mobile node's policy profile.
mobile node will have access to this profile and these entities can
query this information using RADIUS [RFC-2865] or DIAMETER [RFC-3588] The network entities in the proxy Mobile IPv6 domain, while serving a
protocols. mobile node will have access to the mobile node's policy profile and
these entities can query this information using RADIUS [RFC-2865] or
DIAMETER [RFC-3588] protocols.
Appendix B. Routing State Appendix B. Routing State
The following section explains the routing state for a mobile node on The following section explains the routing state created for a mobile
the mobile access gateway. This routing state reflects only one node on the mobile access gateway. This routing state reflects only
specific way of implementation and one MAY choose to implement it in one specific way of implementation and one MAY choose to implement it
other ways. The policy based route defined below acts as a traffic in other ways. The policy based route defined below acts as a
selection rule for routing a mobile node's traffic through a specific traffic selection rule for routing a mobile node's traffic through a
tunnel created between the mobile access gateway and that mobile specific tunnel created between the mobile access gateway and that
node's local mobility anchor and with the specific encapsulation mobile node's local mobility anchor and with the specific
mode, as negotiated. encapsulation mode, as negotiated.
The below example identifies the routing state for two visiting The below example identifies the routing state for two visiting
mobile nodes, MN1 and MN2 with their respective local mobility mobile nodes, MN1 and MN2 with their respective local mobility
anchors LMA1 and LMA2. anchors LMA1 and LMA2.
For all traffic from the mobile node, identified by the mobile node's For all traffic from the mobile node, identified by the mobile node's
MAC address, ingress interface or source prefix (MN-HNP) to MAC address, ingress interface or source prefix (MN-HNP) to
_ANY_DESTINATION_ route via interface tunnel0, next-hop LMAA. _ANY_DESTINATION_ route via interface tunnel0, next-hop LMAA.
+==================================================================+ +==================================================================+
| Packet Source | Destination Address | Destination Interface | | Packet Source | Destination Address | Destination Interface |
+==================================================================+ +==================================================================+
| MAC_Address_MN1, | _ANY_DESTINATION_ | Tunnel0 | | MAC_Address_MN1, | _ANY_DESTINATION_ | Tunnel0 |
| (IPv6 Prefix or |----------------------------------------------| | (IPv6 Prefix or |----------------------------------------------|
| Input Interface) | Locally Connected | Tunnel0 | | Input Interface) | Locally Connected | Tunnel0 |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
| MAC_Address_MN2, | _ANY_DESTINATION_ | Tunnel1 | | MAC_Address_MN2, | _ANY_DESTINATION_ | Tunnel1 |
+ (IPv6 Prefix or -----------------------------------------------| + (IPv6 Prefix or -----------------------------------------------|
| Input Interface | Locally Connected | direct | | Input Interface | Locally Connected | direct |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 24: Example - Policy based Route Table
Figure 22: Example - Policy based Route Table
+==================================================================+ +==================================================================+
| Interface | Source Address | Destination Address | Encapsulation | | Interface | Source Address | Destination Address | Encapsulation |
+==================================================================+ +==================================================================+
| Tunnel0 | Proxy-CoA | LMAA1 | IPv6-in-IPv6 | | Tunnel0 | Proxy-CoA | LMAA1 | IPv6-in-IPv6 |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
| Tunnel1 | Proxy-CoA | LMAA2 | IPv6-in-IPv6 | | Tunnel1 | Proxy-CoA | LMAA2 | IPv6-in-IPv6 |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 23: Example - Tunnel Interface Table Figure 25: Example - Tunnel Interface Table
Authors' Addresses Authors' Addresses
Sri Gundavelli Sri Gundavelli
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: sgundave@cisco.com Email: sgundave@cisco.com
skipping to change at page 81, line 4 skipping to change at page 85, line 33
Email: sgundave@cisco.com Email: sgundave@cisco.com
Kent Leung Kent Leung
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: kleung@cisco.com Email: kleung@cisco.com
Vijay Devarapalli Vijay Devarapalli
Azaire Networks Wichorus
4800 Great America Pkwy 3590 North First Street
Santa Clara, CA 95054 San Jose, CA 95134
USA USA
Email: vijay.devarapalli@azairenet.com Email: vijay@wichorus.com
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
30 International Place 30 International Place
Tewksbury, MA Tewksbury, MA
Email: kchowdhury@starentnetworks.com Email: kchowdhury@starentnetworks.com
Basavaraj Patil Basavaraj Patil
Nokia Siemens Networks Nokia Siemens Networks
6000 Connection Drive 6000 Connection Drive
 End of changes. 164 change blocks. 
630 lines changed or deleted 895 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/