draft-ietf-netlmm-proxymip6-11.txt   draft-ietf-netlmm-proxymip6-12.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: August 28, 2008 V. Devarapalli Expires: October 26, 2008 V. Devarapalli
Azaire Networks Azaire Networks
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
B. Patil B. Patil
Nokia Siemens Networks Nokia Siemens Networks
February 25, 2008 April 24, 2008
Proxy Mobile IPv6 Proxy Mobile IPv6
draft-ietf-netlmm-proxymip6-11.txt draft-ietf-netlmm-proxymip6-12.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 August 28, 2008. This Internet-Draft will expire on October 26, 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 17 skipping to change at page 2, line 17
required mobility signaling on its behalf. This specification required mobility signaling on its behalf. This specification
describes a network-based mobility management protocol and is describes a network-based mobility management protocol and is
referred to as Proxy Mobile IPv6. referred to as Proxy Mobile IPv6.
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 . . . . . . . . . . . . . 8 3. Proxy Mobile IPv6 Protocol Overview . . . . . . . . . . . . . 9
4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 14 4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 15
4.1. Peer Authorization Database (PAD) Entries . . . . . . . . 15 4.1. Peer Authorization Database (PAD) Example Entries . . . . 16
4.2. Security Policy Database (SPD) Entries . . . . . . . . . . 15 4.2. Security Policy Database (SPD) Example Entries . . . . . . 16
5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 16 5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 17
5.1. Extensions to Binding Cache Entry Data Structure . . . . . 16 5.1. Extensions to Binding Cache Entry Data Structure . . . . . 17
5.2. Supported Home Network Prefix Models . . . . . . . . . . . 18 5.2. Supported Home Network Prefix Models . . . . . . . . . . . 19
5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 18 5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 19
5.3.1. Processing Binding Registrations . . . . . . . . . . . 18 5.3.1. Processing Binding Registrations . . . . . . . . . . . 19
5.3.2. Initial Binding Registration (New Mobility Session) . 20 5.3.2. Initial Binding Registration (New Mobility Session) . 22
5.3.3. Binding Lifetime Extension (No handoff) . . . . . . . 21 5.3.3. Binding Lifetime Extension (No handoff) . . . . . . . 23
5.3.4. Binding Lifetime Extension (After handoff) . . . . . . 22 5.3.4. Binding Lifetime Extension (After handoff) . . . . . . 23
5.3.5. Binding De-Registration . . . . . . . . . . . . . . . 22 5.3.5. Binding De-Registration . . . . . . . . . . . . . . . 24
5.3.6. Constructing the Proxy Binding Acknowledgement 5.3.6. Constructing the Proxy Binding Acknowledgement
Message . . . . . . . . . . . . . . . . . . . . . . . 23 Message . . . . . . . . . . . . . . . . . . . . . . . 24
5.4. Multihoming Support . . . . . . . . . . . . . . . . . . . 25 5.4. Multihoming Support . . . . . . . . . . . . . . . . . . . 27
5.4.1. Binding Cache entry lookup considerations . . . . . . 26 5.4.1. Binding Cache entry lookup considerations . . . . . . 27
5.5. Timestamp Option for Message Ordering . . . . . . . . . . 31 5.5. Timestamp Option for Message Ordering . . . . . . . . . . 33
5.6. Routing Considerations . . . . . . . . . . . . . . . . . . 34 5.6. Routing Considerations . . . . . . . . . . . . . . . . . . 36
5.6.1. Bi-Directional Tunnel Management . . . . . . . . . . . 34 5.6.1. Bi-Directional Tunnel Management . . . . . . . . . . . 36
5.6.2. Forwarding Considerations . . . . . . . . . . . . . . 34 5.6.2. Forwarding Considerations . . . . . . . . . . . . . . 36
5.7. Local Mobility Anchor Address Discovery . . . . . . . . . 35 5.7. Local Mobility Anchor Address Discovery . . . . . . . . . 37
5.8. Mobile Prefix Discovery Considerations . . . . . . . . . . 36 5.8. Mobile Prefix Discovery Considerations . . . . . . . . . . 38
5.9. Route Optimizations Considerations . . . . . . . . . . . . 36 5.9. Route Optimizations Considerations . . . . . . . . . . . . 38
6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 36 6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 38
6.1. Extensions to Binding Update List Entry Data Structure . . 37 6.1. Extensions to Binding Update List Entry Data Structure . . 39
6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 38 6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 40
6.3. Supported Access Link Types . . . . . . . . . . . . . . . 38 6.3. Supported Access Link Types . . . . . . . . . . . . . . . 41
6.4. Supported Address Configuration Modes . . . . . . . . . . 39 6.4. Supported Address Configuration Modes . . . . . . . . . . 41
6.5. Access Authentication & Mobile Node Identification . . . . 39 6.5. Access Authentication & Mobile Node Identification . . . . 42
6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 40 6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 42
6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 40 6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 43
6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 41 6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 43
6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 42 6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 44
6.9.1. Binding Registrations . . . . . . . . . . . . . . . . 42 6.9.1. Binding Registrations . . . . . . . . . . . . . . . . 44
6.9.2. Router Solicitation Messages . . . . . . . . . . . . . 50 6.9.2. Router Solicitation Messages . . . . . . . . . . . . . 52
6.9.3. Default-Router Lifetime . . . . . . . . . . . . . . . 51 6.9.3. Default-Router . . . . . . . . . . . . . . . . . . . . 53
6.9.4. Retransmissions and Rate Limiting . . . . . . . . . . 51 6.9.4. Retransmissions and Rate Limiting . . . . . . . . . . 53
6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 52 6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 54
6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 53 6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 54
6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 53 6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 55
6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . . 54 6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . . 56
6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . . 54 6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . . 56
6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . . 54 6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . . 56
6.11. Supporting DHCPv6 based Address Configuration on the 6.11. Supporting DHCPv6 based Address Configuration on the
Access Link . . . . . . . . . . . . . . . . . . . . . . . 56 Access Link . . . . . . . . . . . . . . . . . . . . . . . 58
6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 57 6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 59
6.13. Mobile Node Detachment Detection and Resource Cleanup . . 57 6.13. Mobile Node Detachment Detection and Resource Cleanup . . 59
6.14. Allowing network access to other IPv6 nodes . . . . . . . 58 6.14. Allowing network access to other IPv6 nodes . . . . . . . 60
7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 58 7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 60
7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 58 7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 61
7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 59 7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 62
8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 60 8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 62
8.1. Proxy Binding Update Message . . . . . . . . . . . . . . . 60 8.1. Proxy Binding Update Message . . . . . . . . . . . . . . . 62
8.2. Proxy Binding Acknowledgement Message . . . . . . . . . . 62 8.2. Proxy Binding Acknowledgement Message . . . . . . . . . . 64
8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 63 8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 65
8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . . 64 8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . . 66
8.5. Access Technology Type Option . . . . . . . . . . . . . . 65 8.5. Access Technology Type Option . . . . . . . . . . . . . . 67
8.6. Mobile Node Interface Identifier Option . . . . . . . . . 67 8.6. Mobile Node Link-layer Identifier Option . . . . . . . . . 69
8.7. Link-local Address Option . . . . . . . . . . . . . . . . 68 8.7. Link-local Address Option . . . . . . . . . . . . . . . . 70
8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 68 8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 71
8.9. Status Values . . . . . . . . . . . . . . . . . . . . . . 69 8.9. Status Values . . . . . . . . . . . . . . . . . . . . . . 71
9. Protocol Configuration Variables . . . . . . . . . . . . . . . 71 9. Protocol Configuration Variables . . . . . . . . . . . . . . . 73
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 72 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74
11. Security Considerations . . . . . . . . . . . . . . . . . . . 73 11. Security Considerations . . . . . . . . . . . . . . . . . . . 75
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 74 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 76
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 74 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 77
13.1. Normative References . . . . . . . . . . . . . . . . . . . 74 13.1. Normative References . . . . . . . . . . . . . . . . . . . 77
13.2. Informative References . . . . . . . . . . . . . . . . . . 75 13.2. Informative References . . . . . . . . . . . . . . . . . . 78
Appendix A. Proxy Mobile IPv6 interactions with AAA Appendix A. Proxy Mobile IPv6 interactions with AAA
Infrastructure . . . . . . . . . . . . . . . . . . . 76 Infrastructure . . . . . . . . . . . . . . . . . . . 79
Appendix B. Supporting Shared-Prefix Model using DHCPv6 . . . . . 77 Appendix B. Routing State . . . . . . . . . . . . . . . . . . . . 79
Appendix C. Routing State . . . . . . . . . . . . . . . . . . . . 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 80
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 78 Intellectual Property and Copyright Statements . . . . . . . . . . 82
Intellectual Property and Copyright Statements . . . . . . . . . . 80
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 28 skipping to change at page 5, line 28
Mobile Access Gateway (MAG) from the NETLMM Goals document [RFC- Mobile Access Gateway (MAG) from the NETLMM Goals document [RFC-
4831]. This document also provides the following context specific 4831]. This document also provides the following context specific
explanation to the following terms used in this document. explanation to the following terms used in this document.
Proxy Mobile IPv6 Domain (PMIPv6-Domain) Proxy Mobile IPv6 Domain (PMIPv6-Domain)
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 setup and authorization between which security associations can be set up and
for sending Proxy Binding Updates on behalf of the mobile nodes authorization for sending Proxy Binding Updates on behalf of the
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 the
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 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
skipping to change at page 6, line 9 skipping to change at page 6, line 9
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
link. It is responsible for tracking the mobile node's movements link. It is responsible for tracking the mobile node's movements
to and from the access link and for signaling the mobile node's to and from the access link and for signaling the mobile node's
local mobility anchor. local mobility anchor.
Mobile Node (MN) Mobile Node (MN)
Throughout this document, the term mobile node is used to refer to Throughout this document, the term mobile node is used to refer to
an IP host or router whose mobility is managed by the network. an IP host or router whose mobility is managed by the network.
The mobile node may be operating in IPv6 mode, IPv4 mode or in The mobile node may be an IPv4-only node, IPv6-only node or a
IPv4/IPv6 dual mode. The mobile node is not required to dual-stack node and is not required to participate in any IP
participate in any IP mobility related signaling for achieving mobility related signaling for achieving mobility for an IP
mobility for an IP address that is obtained in that Proxy Mobile address that is obtained in that Proxy Mobile IPv6 domain.
IPv6 domain.
LMA Address (LMAA) LMA Address (LMAA)
The address that is configured on the interface of the local The global address that is configured on the interface of the
mobility anchor and is the transport endpoint of the bi- local mobility anchor and is the transport endpoint of the bi-
directional tunnel established between the local mobility anchor directional tunnel established between the local mobility anchor
and the mobile access gateway. This is the address to where the and the mobile access gateway. This is the address to where the
mobile access gateway sends the Proxy Binding Update messages. mobile access gateway sends the Proxy Binding Update messages.
When supporting IPv4 traversal, i.e., when the network between the When supporting IPv4 traversal, i.e., when the network between the
local mobility anchor and the mobile access gateway is an IPv4 local mobility anchor and the mobile access gateway is an IPv4
network, this address will be an IPv4 address and will be referred network, this address will be an IPv4 address and will be referred
to as IPv4-LMAA, as specified in [ID-IPV4-PMIP6]. to as IPv4-LMAA, as specified in [ID-IPV4-PMIP6].
Proxy Care-of Address (Proxy-CoA) Proxy Care-of Address (Proxy-CoA)
Proxy-CoA is the address configured on the interface of the mobile Proxy-CoA is the global address configured on the interface of the
access gateway and is the transport endpoint of the tunnel between mobile access gateway and is the transport endpoint of the tunnel
the local mobility anchor and the mobile access gateway. The between the local mobility anchor and the mobile access gateway.
local mobility anchor views this address as the Care-of Address of The local mobility anchor views this address as the Care-of
the mobile node and registers it in the Binding Cache entry for Address of the mobile node and registers it in the Binding Cache
that mobile node. When the transport network between the mobile entry for that mobile node. When the transport network between
access gateway and the local mobility anchor is an IPv4 network the mobile access gateway and the local mobility anchor is an IPv4
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 Address (MN-HoA)
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 use
this address as long as it is attached to the access network that
is in the scope of that Proxy Mobile IPv6 domain. Unlike in
Mobile IPv6 where the home agent is aware of the home address of
the mobile node, in Proxy Mobile IPv6, the mobility entities are
only aware of the mobile node's home network prefix and are not
always aware of the exact address(es) that the mobile node
configured on its interface from that prefix. However, in some
configurations and based on the enabled address configuration
modes on the access link, the mobility entities in the network can
be certain about the exact address configured by the mobile node.
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 on-link IPv6 prefix that is always present in the
Router Advertisements that the mobile node receives when it is Router Advertisements that the mobile node receives when it is
attached to any of the access links in that Proxy Mobile IPv6 attached to any of the access links in that Proxy Mobile IPv6
domain. This home network prefix is topologically anchored at the domain. This home network prefix is topologically anchored at the
mobile node's local mobility anchor. The mobile node configures mobile node's local mobility anchor. The mobile node configures
its interface with an address from this prefix. If the mobile its interface with an address from this prefix. If the mobile
node connects to the Proxy Mobile IPv6 domain through multiple node connects to the Proxy Mobile IPv6 domain through multiple
interfaces, simultaneously, each of the connected interface will interfaces, simultaneously, each of the connected interfaces will
be assigned a unique home network prefix and under a different be assigned a unique home network prefix and under a different
mobility session. mobility session.
Mobile Node's Home Address (MN-HoA)
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
use this address as long as it is attached to the access
network that is in the scope of that Proxy Mobile IPv6 domain.
Unlike in Mobile IPv6 where the home agent is aware of the home
address of the mobile node, in Proxy Mobile IPv6, the mobility
entities are only aware of the mobile node's home network
prefix and are not always aware of the exact address(es) that
the mobile node configured on its interface from that prefix.
However, in some configurations and based on the enabled
address configuration modes on the access link, the mobility
entities in the network can be certain about the exact address
configured by the mobile node.
Mobile Node's Home Link Mobile Node's Home Link
This is the link on which the mobile node obtained its Layer-3 This is the point-to-point link on which the mobile node obtained
address configuration for the attached interface after it moved its Layer-3 address configuration for the attached interface after
into that Proxy Mobile IPv6 domain. This is the link that it moved into that Proxy Mobile IPv6 domain. This is the link
conceptually follows the mobile node. The network will ensure the that conceptually follows the mobile node. The network will
mobile node always sees this link with respect to the layer-3 ensure the mobile node always sees this link with respect to the
network configuration, on any access link that it attaches to in layer-3 network configuration, on any access link that it attaches
that Proxy Mobile IPv6 domain. to in that Proxy Mobile IPv6 domain.
Multihomed Mobile Node Multihomed Mobile Node
A mobile node that connects to the 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.
This is the stable identifier of a mobile node that the mobility This is the stable identifier of a mobile node that the mobility
entities in a Proxy Mobile IPv6 domain can always acquire and use entities in a Proxy Mobile IPv6 domain can always acquire and use
it for predictably identifying a mobile node. This is typically it for predictably identifying a mobile node. This is typically
an identifier such as Network Access Identifier (NAI) or other an identifier such as Network Access Identifier (NAI) [RFC-4282]
identifier such as a Media Access Control (MAC) address. or other identifier such as a Media Access Control (MAC) address.
Mobile Node Interface Identifier (MN-Interface-Identifier) Mobile Node Link-layer Identifier (MN-LL-Identifier)
The interface identifier that identifies a given interface of a An identifier that identifies the attached interface of a mobile
mobile node. For those interfaces that have a layer-2 identifier, node. For those interfaces that have a link-layer identifier,
the interface identifier can be based on that layer-2 identifier. this identifier can be based on that. The link-layer identifier
The interface identifier in some cases is generated by the mobile in some cases is generated by the mobile node and conveyed to the
node and conveyed to the access router or the mobile access mobile access gateway. This identifier of the attached interface
gateway. In some cases, there might not be any interface must be stable as seen by any of the mobile access gateways in a
identifier associated with the mobile node's interface. given Proxy Mobile IPv6 domain. In some other cases, there might
not be any link-layer identifier associated with the mobile node's
interface.
Policy Profile Policy Profile
Policy Profile is an abstract term for referring to a set of Policy Profile is an abstract term for referring to a set of
configuration parameters that are configured for a given mobile configuration parameters that are configured for a given mobile
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.
skipping to change at page 8, line 34 skipping to change at page 8, line 37
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
model where there is an unique network prefix assigned for each model where there is an unique network prefix assigned for each
node. The term, Shared-Prefix model, is used to refer to an node. The term, Shared-Prefix model, is used to refer to an
addressing model where the prefix is shared by more than one node. addressing model where the prefix is shared by more than one node.
This specification supports the Per-MN-Prefix model and does not
support the Shared-Prefix model.
ALL_ZERO & NON_ZERO ALL_ZERO & NON_ZERO
Protocol message fields initialized with value 0 in each byte of Protocol message fields initialized with value 0 in each byte of
the field. Ex: An 8-byte interface identifier field with the the field. Ex: An 8-byte link-layer identifier field with the
value set to 0 in each of the 8 bytes, or an IPv6 address with the value set to 0 in each of the 8 bytes, or an IPv6 address with the
value 0 in all of the 16 bytes. Conversely, the term NON_ZERO is value 0 in all of the 16 bytes. Conversely, the term NON_ZERO is
used to refer to any value other than an ALL_ZERO value. used to refer to any value other than an ALL_ZERO value.
3. Proxy Mobile IPv6 Protocol Overview 3. Proxy Mobile IPv6 Protocol Overview
This specification describes a network-based mobility management This specification describes a network-based mobility management
protocol. It is called Proxy Mobile IPv6 and is based on Mobile IPv6 protocol. It is called Proxy Mobile IPv6 and is based on Mobile IPv6
[RFC-3775]. [RFC-3775].
skipping to change at page 10, line 24 skipping to change at page 11, line 6
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, the default-
router address on the link and other related configuration 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 operating in an IPv4-only mode, IPv6-only mode The mobile node may be an IPv4-only node, IPv6-only node or a dual
or in dual IPv4/IPv6 mode. Based on what is enabled in the network IPv4/IPv6 node. Based on what is enabled in the network for that
for that mobile node, the mobile node will be able to obtain an IPv4, mobile node, the mobile node will be able to obtain an IPv4, IPv6 or
IPv6 or dual IPv4/IPv6 addresses and move anywhere in that Proxy dual IPv4/IPv6 addresses and move anywhere in that Proxy Mobile IPv6
Mobile IPv6 domain. However, the specific details related to the domain. However, the specific details related to the IPv4 addressing
IPv4 addressing or IPv4 transport support are specified in the or IPv4 transport support are specified in the companion document
companion document [ID-IPV4-PMIP6]. [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 home network prefix for each of the connected
interfaces and the mobile node will be able to configure an interfaces. The mobile node will be able to configure an address(es)
address(es) on those interfaces from the respective home network on those interfaces from the respective home network prefixes.
prefixes. However, if the mobile node performs an handoff from one However, if the mobile node performs an inter-interface handoff by
interface to another and if the local mobility anchor receives an moving its address configuration from one interface to the other and
handoff hint from the serving mobile access gateway about the same, if the local mobility anchor receives a handoff hint from the serving
the local mobility anchor will assign the same prefix to the new mobile access gateway about the same, the local mobility anchor will
interface. assign the same home network prefix that it assigned to the
previously attached interface.
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| MN | | MAG | | LMA | | MN | | MAG | | LMA |
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| | | | | |
MN Attached | | MN Attached | |
| | | | | |
| MN Attached Event | | MN Attached Event from MN/Network |
| (Acquire MN-Id and Profile) | | (Acquire MN-Id and Profile) |
| | | | | |
| |----- PBU ----------->| |--- Rtr Sol --------->| |
| | |
| |--- PBU ------------->|
| | | | | |
| | Accept PBU | | Accept PBU
| | (Allocate MN-HNP, Setup BCE and Tunnel) | | (Allocate MN-HNP, 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 Sol --------->| | |<--------- 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.
skipping to change at page 12, line 35 skipping to change at page 13, line 33
to and from the mobile node using an address from its home network to and from the mobile node using an address from its home network
prefix. prefix.
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, receives any packets that are sent
to the mobile node by any node in the network. The local mobility to the mobile node by any node in the network. The local mobility
anchor forwards these received packets to the mobile access gateway anchor forwards these received packets to the mobile access gateway
through the bi-directional tunnel. The mobile access gateway on through the bi-directional tunnel. The mobile access gateway on
other end of the tunnel, after receiving the packet, removes the 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. node. However, in some cases the traffic sent from a correspondent
node that is locally connected to the mobile access gateway may not
be received by the local mobility anchor and may be routed locally by
the mobile access gateway.
The mobile access gateway typically acts as a default router on the The mobile access gateway acts as the default router on the access
access link. Any packet that the mobile node sends to any link. Any packet that the mobile node sends to any correspondent
correspondent node will be received by the mobile access gateway and node will be received by the mobile access gateway and will be sent
will be sent to its local mobility anchor through the bi-directional to its local mobility anchor through the bi-directional tunnel. The
tunnel. The local mobility anchor on the other end of the tunnel, local mobility anchor on the other end of the tunnel, after receiving
after receiving the packet, removes the outer header and routes the the packet, removes the outer header and routes the packet to the
packet to the destination. destination. However in some cases the traffic sent to a
correspondent node that is locally connected to the mobile access
gateway may be locally routed by the mobile access gateway.
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| MN | |p-MAG| | LMA | |n-MAG| | MN | |p-MAG| | LMA | |n-MAG|
+-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+ +-----+
| | | | | | | |
| |==Bi-Dir Tunnel=| | | |==Bi-Dir Tunnel=| |
MN Detached | | | MN Detached | | |
| MN Detached Event | | | MN Detached Event | |
| | | | | | | |
| |-- DeReg PBU -->| | | |-- DeReg PBU -->| |
| | | | | | | |
| | Accept PBU | | | Accept PBU |
| | (Start MinDelayBeforeBCEDelete Timer) | | (Start MinDelayBeforeBCEDelete Timer)
| | | | | | | |
| |<-------- PBA --| | | |<-------- PBA --| |
| | | | | | | |
MN Attached | | | MN Attached | | |
| | | MN Attached Event | | | MN Attached event received
| | | from MN or from network
| | | (Acquire MN-Id and Profile) | | | (Acquire MN-Id and Profile)
| | | |
|--- Rtr Sol ------------------------------------->|
.... ....
Registration steps as in fig 2. Registration steps as in fig 2.
.... ....
| | |==Bi-Dir Tunnel=| | | |==Bi-Dir Tunnel=|
|--- Rtr Sol ------------------------------------->|
| | | | | | | |
|<------------------------------------ Rtr Adv ----| |<------------------------------------ Rtr Adv ----|
| | | | | | | |
MN retains HoA/HNP MN retains HoA/HNP
| | | | | | | |
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
skipping to change at page 14, line 28 skipping to change at page 15, line 30
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 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. alternative mechanisms. 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.
IKEv2 [RFC-4306] SHOULD be used to setup security associations IKEv2 [RFC-4306] SHOULD be used to setup 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 IKEv2, can use any of the authentication mechanisms, as specified in [RFC-
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
protocol described in this document, the mobile node is not involved protocol described in this document, the mobile node is not involved
in creating security associations for protecting the signaling in creating security associations for protecting the signaling
messages or sending binding updates. Therefore, the local mobility messages or sending binding updates. Therefore, the local mobility
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.
4.1. Peer Authorization Database (PAD) Entries Unlike in Mobile IPv6 [RFC-3775], these signaling messages do not
carry either the Home Address destination option or the Type 2
Routing header and hence the policy entries and security association
selectors stay the same.
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.
mobile access gateway PAD: mobile access gateway PAD:
- IF remote_identity = lma_identity_1 - IF remote_identity = lma_identity_1
Then authenticate (shared secret/certificate/EAP) Then authenticate (shared secret/certificate/EAP)
and authorize CHILD_SA for remote address lma_addres_1 and authorize CHILD_SA for remote address lma_address_1
local mobility anchor PAD: local mobility anchor PAD:
- IF remote_identity = mag_identity_1 - IF remote_identity = mag_identity_1
Then authenticate (shared secret/certificate/EAP) Then authenticate (shared secret/certificate/EAP)
and authorize CHILD_SAs for remote address mag_address_1 and authorize CHILD_SAs for remote address mag_address_1
Figure 4: PAD Entries Figure 4: PAD Entries
The list of authentication mechanisms in the above examples is not The list of authentication mechanisms in the above examples is not
exhaustive. There could be other credentials used for authentication exhaustive. There could be other credentials used for authentication
stored in the PAD. stored in the PAD.
4.2. Security Policy Database (SPD) Entries 4.2. Security Policy Database (SPD) Example Entries
This section describes the security policy entries [RFC-4301] on the This section describes the security policy entries [RFC-4301] on the
mobile access gateway and the local mobility anchor required to mobile access gateway and the local mobility anchor required to
protect the Proxy Mobile IPv6 signaling messages. The SPD entries protect the Proxy Mobile IPv6 signaling messages. The SPD entries
are only example configurations. A particular mobile access gateway are only example configurations. A particular mobile access gateway
or a local mobility anchor implementation could configure different or a local mobility anchor implementation could configure different
SPD entries as long as they provide the required security. SPD entries as long as they provide the required security.
In the examples shown below, the identity of the mobile access In the examples shown below, the identity of the mobile access
gateway is assumed to be mag_1, the address of the mobile access gateway is assumed to be mag_1, the address of the mobile access
skipping to change at page 16, line 25 skipping to change at page 17, line 32
proto = MH & local_mh_type = BA & remote_mh_type = BU proto = MH & local_mh_type = BA & remote_mh_type = BU
Then use SA ESP transport mode Then use SA ESP transport mode
Figure 5: SPD Entries Figure 5: SPD Entries
5. Local Mobility Anchor Operation 5. Local Mobility Anchor Operation
The local mobility anchor MUST support the home agent function as The local mobility anchor MUST support the home agent function as
defined in [RFC-3775] and additionally the extensions defined in this defined in [RFC-3775] and additionally the extensions defined in this
specification. A home agent with these modifications and enhanced specification. A home agent with these modifications and enhanced
capabilities for supporting Proxy Mobile IPv6 protocol is referred to capabilities for supporting the Proxy Mobile IPv6 protocol is
as the local mobility anchor. referred to as a local mobility anchor.
This section describes the operational details of the local mobility This section describes the operational details of the local mobility
anchor. anchor.
5.1. Extensions to Binding Cache Entry Data Structure 5.1. Extensions to Binding Cache Entry Data Structure
Every local mobility anchor MUST maintain a Binding Cache entry for Every local mobility anchor MUST maintain a Binding Cache entry for
each currently registered mobile node. Binding Cache entry is a each currently registered mobile node. Binding Cache entry is a
conceptual data structure, described in Section 9.1 [RFC-3775]. conceptual data structure, described in Section 9.1 of [RFC-3775].
For supporting this specification, the Binding Cache Entry data For supporting this specification, the Binding Cache Entry data
structure needs to be extended with the following additional fields. structure needs to be extended with the following additional fields.
o A flag indicating whether or not this Binding Cache entry is o A flag indicating whether or not this Binding Cache entry is
created due to a proxy registration. This flag is set to value 1 created due to a proxy registration. This flag is set to value 1
for Binding Cache entries that are proxy registrations and is set for Binding Cache entries that are proxy registrations and is set
to value 0 for all other entries. to value 0 for all other entries.
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 interface 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 Interface 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 node on the interface o The Link-local address of the mobile access gateway on the point-
attached to the access link. This is obtained from the Link-local to-point link shared with the mobile node. This is generated by
Address option, present in the Proxy Binding Update request. If the local mobility anchor after accepting the initial Proxy
the option was not present in the request, the value MUST be set Binding Update request.
to ALL_ZERO.
o The IPv6 home network prefix that is assigned to the mobile node's o The IPv6 home network prefix that is assigned to the mobile node's
connected interface. The home network prefix of the mobile node connected interface. The home network prefix of the mobile node
may have been statically configured in the mobile node's policy may have been statically configured in the mobile node's policy
profile, or, it may have been dynamically allocated by the local profile, or, it may have been dynamically allocated by the local
mobility anchor. The IPv6 home network prefix also includes the mobility anchor. The IPv6 home network prefix also includes the
corresponding prefix length. corresponding prefix length.
o The interface identifier (If-Id) of the bi-directional tunnel o The tunnel interface identifier (If-Id) of the bi-directional
between the local mobility anchor and the mobile access gateway tunnel between the local mobility anchor and the mobile access
where the mobile node is currently anchored. This is internal to gateway where the mobile node is currently anchored. This is
the local mobility anchor. The tunnel interface identifier is internal to the local mobility anchor. The tunnel interface
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 sequence number based scheme is Binding Update request (i.e., when the sequence number based
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, the mobile node's home network prefix is the key for
locating a Binding Cache entry in all cases except when there has locating a Binding Cache entry in all cases except when there has
been an handoff of the mobile node's session to a new mobile access been an handoff of the mobile node's session to a new mobile access
gateway and that mobile access gateway is unaware of the home network gateway and that mobile access gateway is unaware of the home network
prefix that was assigned to the handed of session. In such handoff prefix that was assigned to the handed of session. In such handoff
cases, the Binding Cache entry can be located under the cases, the Binding Cache entry can be located under the
considerations specified in Section 5.4.1. considerations specified in Section 5.4.1.
5.2. Supported Home Network Prefix Models 5.2. Supported Home Network Prefix Models
This specification supports Per-MN-Prefix model and does not support This specification supports the Per-MN-Prefix model and does not
Shared-Prefix model. As per the Per-MN-Prefix model, there will be a support the Shared-Prefix model. As per the Per-MN-Prefix model,
unique home network prefix assigned to each mobile node and no other there will be a unique home network prefix assigned to each mobile
node shares an address from that prefix. The assigned prefix is node and no other node shares an address (other than the Subnet-
Router anycast address [RFC-4291] which is used by the mobile access
gateway hosting the prefix on that link). The assigned prefix is
unique to a mobile node and also unique to a given interface of the 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 mobile node. If the mobile node attaches to the Proxy Mobile IPv6
domain through multiple interfaces and simultaneously, each of those domain through multiple interfaces and simultaneously, each of those
connected interfaces will be assigned a different prefix. connected interfaces will be assigned a different prefix.
The mobile node's home network prefix is always hosted on the access The mobile node's home network prefix is always hosted on the access
link where the mobile node is anchored. Conceptually, the entire link where the mobile node is anchored. Conceptually, the entire
home network prefix follows the mobile node as it moves within the home network prefix follows the mobile node as it moves within the
Proxy Mobile IPv6 domain. The local mobility anchor is not required Proxy Mobile IPv6 domain. The local mobility anchor is not required
to perform any proxy ND operations [RFC-4861] for defending the to perform any proxy ND operations [RFC-4861] for defending the
skipping to change at page 18, line 44 skipping to change at page 20, line 6
1. The received Proxy Binding Update message (a Binding Update 1. The received Proxy Binding Update message (a Binding Update
message with the 'P' flag set to value of 1, format specified in message with the 'P' flag set to value of 1, format specified in
Section 8.1) MUST be authenticated as described in Section 4. Section 8.1) MUST be authenticated as described in Section 4.
When IPsec is used for message authentication, the SPI in the When IPsec is used for message authentication, the SPI in the
IPsec header [RFC-4306] of the received packet is needed for IPsec header [RFC-4306] of the received packet is needed for
locating the security association, for authenticating the Proxy locating the security association, for authenticating the Proxy
Binding Update message. Binding Update message.
2. The local mobility anchor MUST observe the rules described in 2. The local mobility anchor MUST observe the rules described in
Section 9.2 [RFC-3775] when processing Mobility Header in the Section 9.2 of [RFC-3775] when processing Mobility Header in the
received Proxy Binding Update request. received Proxy Binding Update request.
3. The local mobility anchor MUST ignore the check, specified in 3. The local mobility anchor MUST ignore the check, specified in
Section 10.3.1 [RFC-3775], related to the presence of Home Section 10.3.1 of [RFC-3775], related to the presence of Home
Address destination option in the Proxy Binding Update request. Address destination option in the Proxy Binding Update request.
4. The local mobility anchor MUST identify the mobile node from the 4. The local mobility anchor MUST identify the mobile node from the
identifier present in the Mobile Node Identifier option [RFC- identifier present in the Mobile Node Identifier option [RFC-
4283] of the Proxy Binding Update request. If the Mobile Node 4283] of the Proxy Binding Update request. If the Mobile Node
Identifier option is not present in the Proxy Binding Update Identifier option is not present in the Proxy Binding Update
request, the local mobility anchor MUST reject the request and request, the local mobility anchor MUST reject the request and
send a Proxy Binding Acknowledgement message with Status field send a Proxy Binding Acknowledgement message with Status field
set to MISSING_MN_IDENTIFIER_OPTION (Missing mobile node set to MISSING_MN_IDENTIFIER_OPTION (Missing mobile node
identifier option) and the identifier in the Mobile Node identifier option) and the identifier in the Mobile Node
skipping to change at page 21, line 11 skipping to change at page 22, line 20
session created for the mobile node. The local mobility anchor session created for the mobile node. The local mobility anchor
MUST ensure the allocated prefix is not in use by any other node MUST ensure the allocated prefix is not in use by any other node
or mobility session. or mobility session.
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 the Home Network Prefix option present in the request has a
specific prefix hint, the local mobility anchor before accepting specific prefix value, the local mobility anchor before accepting
that request, MUST ensure the prefix is owned by the local that request, MUST ensure the prefix is owned by the local
mobility anchor and further the mobile node is authorized to use mobility anchor and further the mobile node is authorized to use
that prefix. If the mobile node is not authorized to use that that prefix. If the mobile node is not authorized to use that
prefix, the local mobility anchor MUST reject the request and prefix, the local mobility anchor MUST reject the request and
send a Proxy Binding Acknowledgement message with Status field send a Proxy Binding Acknowledgement message with Status field
set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (Mobile node not set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (Mobile node not
authorized to use that prefix). authorized to use that prefix).
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. The local mobility anchor MUST establish a bi-directional tunnel 5. If there is no existing bi-directional tunnel to the mobile
to the mobile access gateway (if there does not exist one) that access gateway that sent the request, the local mobility anchor
sent the request and setup the routing state. Considerations MUST establish a bi-directional tunnel to that mobile access
from Section 5.6 MUST be applied for creating the routing state. gateway. Considerations from Section 5.6.1 MUST be applied for
managing the dynamically created bi-directional tunnel.
6. The local mobility anchor MUST send the Proxy Binding 6. The local mobility anchor MUST create a prefix route over the
tunnel to the mobile access gateway for forwarding any traffic
received for the mobile node's home network prefix. The created
tunnel and routing state MUST result in the forwarding behavior
on the local mobility anchor as specified in Section 5.6.2.
7. The local mobility anchor MUST send the Proxy Binding
Acknowledgement message with the Status field set to 0 (Proxy 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
that last updated the binding (i.e., when there is no handoff), (if the Proxy-CoA address in the Binding Cache entry is the same
the local mobility anchor MUST update the Binding Cache entry as the Proxy-CoA address in the request) that last updated the
with the accepted registration values. However, if the link- binding, the local mobility anchor MUST update the Binding Cache
local address value in the Link-local address option is ALL_ZERO entry with the accepted registration values.
value, the link-local address field in the Binding Cache entry
MUST NOT be updated.
2. The local mobility anchor MUST send the Proxy Binding 2. 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.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 where binding lifetime, received from a new mobile access gateway (if
the mobile node's session is handed off, the local mobility the Proxy-CoA address in the Binding Cache entry does not match
anchor MUST update the Binding Cache entry with the accepted the Proxy-CoA address in the request) where the mobile node's
registration values. However, if the link-local address value in session is handed off, the local mobility anchor MUST update the
the Link-local address option is ALL_ZERO value, the link-local Binding Cache entry with the accepted registration values.
address field in the Binding Cache entry MUST NOT be updated.
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 for the mobile node's home network prefix. Additionally,
if there are no other mobile node's sessions sharing the tunnel if there are no other mobile node sessions sharing the
to the previous mobile access gateway, the tunnel MUST also be dynamically created bi-directional tunnel to the previous mobile
deleted applying considerations from section 5.6.1 (if the tunnel access gateway, the tunnel MUST be deleted applying
is a dynamically created tunnel and not a fixed pre-established considerations from section 5.6.1 (if the tunnel is a dynamically
tunnel). created tunnel and not a fixed pre-established tunnel).
3. The local mobility anchor MUST establish a bi-directional tunnel 3. If there is no existing bi-directional tunnel to the mobile
to the mobile access gateway that sent the request. access gateway that sent the request, the local mobility anchor
Considerations from Section 5.6 MUST be applied for creating the MUST establish a bi-directional tunnel to that mobile access
routing state. gateway. Considerations from Section 5.6.1 MUST be applied for
managing the dynamically created bi-directional tunnel.
4. The local mobility anchor MUST send the Proxy Binding 4. The local mobility anchor MUST create a prefix route over the
tunnel to the mobile access gateway for forwarding any traffic
received for the mobile node's home network prefix. The created
tunnel and routing state MUST result in the forwarding behavior
on the local mobility anchor as specified in Section 5.6.2.
5. The local mobility anchor MUST send the Proxy Binding
Acknowledgement message with the Status field set to 0 (Proxy 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
address in the Alternate Care-of Address option, if the option is address in the Alternate Care-of Address option, if the option is
present) different from what is present in the Proxy-CoA address present) different from what is present in the Proxy-CoA address
skipping to change at page 23, line 34 skipping to change at page 25, line 14
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 (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 Interface 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
skipping to change at page 24, line 41 skipping to change at page 26, line 18
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, if the same option was
present in the received Proxy Binding Update request. present in the received Proxy Binding Update request.
Considerations from Section 5.5 must be applied for constructing Considerations from Section 5.5 must be applied for constructing
the Timestamp option. the Timestamp option.
o The Mobile Node Interface Identifier option MUST be present, if o The Mobile Node Link-layer Identifier option MUST be present, if
the same option was present in the received Proxy Binding Update the same option was present in the received Proxy Binding Update
request. The interface identifier value MUST be copied from the request. The link-layer identifier value MUST be copied from the
Mobile Node Interface Indicator option present in the received Mobile Node Link-layer Identifier option present in the received
Proxy Binding Update request. 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, if the same option
was present in the received Proxy Binding Update request. was present in the received Proxy Binding Update request.
* 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 option in the value MUST be copied to the Link-local Address field of the
reply. Binding Cache entry and it must also be copied to the Link-
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), or if there is an existing request for a new mobility session), then the local mobility
Binding Cache entry with the link-local address value set to anchor MUST generate the link-local address that the mobile
ALL_ZERO, then the link-local address in the option MUST be access gateway can use on the point-to-point link shared with
copied from the Link-local Address option present in the the mobile node and the same must be copied to the Link-local
received Proxy Binding Update request. Address field of the Binding Cache entry and it must also be
copied to the Link-local Address option in the reply.
* For all other cases, the link-local address in the option MUST * For all other cases, the link-local address in the option MUST
be copied from the Link-local Address field of the Binding be copied from the Link-local Address field of the Binding
Cache entry. Cache entry.
o If IPsec is used for protecting the signaling messages, the o If IPsec is used for protecting the signaling messages, the
message MUST be protected, using the security association existing message MUST be protected, using the security association existing
between the local mobility anchor and the mobile access gateway. between the local mobility anchor and the mobile access gateway.
o Unlike in Mobile IPv6 [RFC-3775], the Type 2 Routing header MUST o Unlike in Mobile IPv6 [RFC-3775], the Type 2 Routing header MUST
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 and 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 and for simultaneous access, the local multiple interfaces for simultaneous access, the local mobility
mobility anchor MUST allocate a unique home network prefix for anchor MUST allocate a unique home network prefix for each of the
each of the connected interfaces. connected interfaces.
o The local mobility anchor MUST manage each of the allocated home o The local mobility anchor MUST manage each of the allocated home
network prefixes as part of a separate mobility session, each network prefixes as part of a separate mobility session, each
under a separate Binding Cache entry and with its own lifetime. under a separate Binding Cache entry and with its own lifetime.
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 case, the home different interfaces of the mobile node. In such a scenario, the
network prefix that is associated with a specific interface home network prefix that is associated with a specific link-layer
identifier of a mobile node will be updated with the new interface identifier of the mobile node will be updated with the new link-
identifier. The decision on when to create a new mobility session layer identifier. The decision on when to create a new mobility
and when to update an existing mobility session MUST be based on session and when to update an existing mobility session MUST be
the Handover hint present in the Proxy Binding Update message and based on the Handover hint present in the Proxy Binding Update
under the considerations specified in this section. 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). These rules are chained with the
processing rules specified in Section 5.3. processing rules specified in Section 5.3.
5.4.1.1. Home Network Prefix Option (NON_ZERO Value) present in the 5.4.1.1. Home Network Prefix Option (NON_ZERO Value) present in the
request request
+=====================================================================+ +=====================================================================+
| Registration/De-Registration Message | | Registration/De-Registration Message |
+=====================================================================+ +=====================================================================+
| HNP (NON_ZERO Value) | | HNP (NON_ZERO Value) |
+=====================================================================+ +=====================================================================+
| ATT | | ATT |
+=====================================================================+ +=====================================================================+
| IID Option Present | IID Option Not present | | MN-LL-Identifier Opt Present | MN-LL-Identifier Opt Not Present |
+=====================================================================+ +=====================================================================+
| HI | | HI |
+==================================+==================================+ +==================================+==================================+
| BCE Lookup Key: (Home Network Prefix) | | BCE Lookup Key: (Home Network Prefix) |
+=====================================================================+ +=====================================================================+
Figure 7: BCE lookup using home network prefix Figure 7: BCE lookup using home network prefix
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 home network prefix value matching Binding Cache entry with the home network prefix value matching
skipping to change at page 27, line 11 skipping to change at page 29, line 4
MUST reject the request with the Status field value set to MUST reject the request with the Status field value set to
NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (mobile node is not NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX (mobile node is not
authorized for the requesting home network prefix). [BCE(MN- authorized for the requesting home network prefix). [BCE(MN-
Identifier) not equals PBU(MN-Identifier)] Identifier) not equals PBU(MN-Identifier)]
4. If there exists a Binding Cache entry (matching MN-Identifier and 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 MN-HNP) and if any one or more of these below stated conditions
match, the request MUST be considered as a request for updating match, the request MUST be considered as a request for updating
that Binding Cache entry. [BCE(MN-Identifier) equals PBU(MN- that Binding Cache entry. [BCE(MN-Identifier) equals PBU(MN-
Identifier)] Identifier)]
* If there is a Mobile Node Link-layer Identifier option present
* If there is a Mobile Node Interface Identifier option present in the request, and if the link-layer identifier value in that
in the request, and if the interface identifier value in that option matches the link-layer identifier value in the Binding
option matches the interface identifier value in the Binding
Cache entry and the access technology type field in the Access Cache entry and the access technology type field in the Access
Technology Type option present in the request matches the Technology Type option present in the request matches the
access technology type in the Binding Cache entry . [BCE(ATT, access technology type in the Binding Cache entry . [BCE(ATT,
MN-Interface-Identifier) equals PBU(ATT, MN-Interface- MN-LL-Identifier) equals PBU(ATT, MN-LL-Identifier)]
Identifier)]
* If the Handoff Indicator field in the Handoff Indicator option * If 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). [PBU(HI) equals two different interfaces of the mobile node). [PBU(HI) equals
2] 2]
* If there is no Mobile Node Interface Identifier option present * If there is no Mobile Node Link-layer Identifier option
in the request, the interface identifier value in the Binding present in the request, the link-layer identifier value in the
Cache entry is set to ALL_ZERO, the access technology type Binding Cache entry is set to ALL_ZERO, the access technology
field in the Access Technology Type option present in the type field in the Access Technology Type option present in the
request matches the access technology type in the Binding request matches the access technology type in the Binding
Cache entry and if the Handoff Indicator field in the Handoff Cache entry and if the Handoff Indicator field in the Handoff
Indicator option present in the request is set to a value of 3 Indicator option present in the request is set to a value of 3
(Handoff between mobile access gateways for the same (Handoff between mobile access gateways for the same
interface). interface).
* If the Proxy-CoA address in the Binding Cache entry matches * If the Proxy-CoA address in the Binding Cache entry matches
the source address of the request (or the address in the the source address of the request (or the address in the
alternate Care-of Address option, if the option is present) alternate Care-of Address option, if the option is present)
and if the access technology type field in the Access and if the access technology type field in the Access
Technology Type option present in the request matches the Technology Type option present in the request matches the
access technology type in the Binding Cache entry. access technology type in the Binding Cache entry.
[BCE(Proxy-CoA, ATT) equals PBU(Proxy-CoA, ATT)]. [BCE(Proxy-CoA, ATT) equals PBU(Proxy-CoA, ATT)].
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. Mobile Node Interface Identifier Option present in the request 5.4.1.2. Mobile Node Link-layer Identifier Option present in the
request
+=====================================================================+ +=====================================================================+
| Registration/De-Registration Message | | Registration/De-Registration Message |
+=====================================================================+ +=====================================================================+
| HNP (ALL_ZERO Value) | | HNP (ALL_ZERO Value) |
+=====================================================================+ +=====================================================================+
| ATT | | ATT |
+=====================================================================+ +=====================================================================+
| IID Option Present (NON_ZERO Value) | | MN-LL-Identifier Option Present (NON_ZERO Value) |
+=====================================================================+ +=====================================================================+
| HI | | HI |
+==================================+==================================+ +==================================+==================================+
| BCE Lookup Keys: (MN-Identifier + Access Technology Type + | | BCE Lookup Keys: (MN-Identifier + ATT + MN-LL-Identifier) |
| MN-Interface-Identifier) |
+=====================================================================+ +=====================================================================+
Figure 8: BCE Lookup using Interface Identifier Figure 8: 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 interface identifier value Technology Type option and the link-layer identifier value
matching the identifier in the received Mobile Node Interface matching the identifier in the received Mobile Node Link-layer
Identifier option. [BCE(MN-Identifier, ATT, MN-Interface- Identifier option. [BCE(MN-Identifier, ATT, MN-LL-Identifier)
Identifier) equals PBU(MN-Identifier, ATT, MN-Interface- equals PBU(MN-Identifier, ATT, MN-LL-Identifier)]
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-Interface-Identifier), the request MUST be considered ATT and MN-LL-Identifier), the request MUST be considered as a
as a request for updating that Binding Cache entry. request for updating that Binding Cache entry.
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-Interface-Identifier) and the Handoff Identifier, ATT and MN-LL-Identifier) and the Handoff Indicator
Indicator field in the Handoff Indicator option present in the field in the Handoff Indicator option present in the request is
request is set to a value of 2 (Handoff between two different set to a value of 2 (Handoff between two different interfaces of
interfaces of the mobile node). The local mobility anchor MUST the mobile node). The local mobility anchor MUST apply the
apply the following additional considerations. [PBU(HI) equals following additional considerations. [PBU(HI) equals 2]
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
matching the identifier in the Mobile Node Identifier option matching the identifier in the Mobile Node Identifier option
present in the request and for any interface identifier value. present in the request and for any link-layer identifier
If there exists only one such entry (matching the MN- value. If there exists only one such entry (matching the MN-
Identifier), the request MUST be considered as a request for Identifier), the request MUST be considered as a request for
updating that Binding Cache entry. [BCE(MN-Identifier) equals updating that Binding Cache entry. [BCE(MN-Identifier) equals
PBU(MN-Identifier)] PBU(MN-Identifier)]
4. If there does not exist a Binding Cache entry (matching MN- 4. If there does not exist a Binding Cache entry (matching MN-
Identifier, ATT and MN-Interface-Identifier) and if the Handoff Identifier, ATT and MN-LL-Identifier) and if the Handoff
Indicator field in the Handoff Indicator option present in the Indicator field in the Handoff Indicator option present in the
request is set to a value of 4 (Handoff state unknown), the local request is set to a value of 4 (Handoff state unknown), the local
mobility anchor MUST apply the following additional mobility anchor MUST apply the following additional
considerations. considerations.
* 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
matching the identifier in the Mobile Node Identifier option matching the identifier in the Mobile Node Identifier option
present in the request and for any interface identifier value. present in the request and for any link-layer identifier
If there exists only one such entry (matching the MN- value. If there exists only one such entry (matching the MN-
Identifier), the local mobility anchor SHOULD wait till the Identifier), the local mobility anchor SHOULD wait till the
existing Binding Cache entry is de-registered by the existing Binding Cache entry is de-registered by the
previously serving mobile access gateway, before the request previously serving mobile access gateway, before the request
can be considered as a request for updating that Binding Cache can be considered as a request for updating that Binding Cache
entry. However, if there is no de-registration message that entry. However, if there is no de-registration message that
is received within MaxDelayBeforeNewBCEAssign amount of time, is received within MaxDelayBeforeNewBCEAssign amount of time,
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.3. Mobile Node Interface 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 (ALL_ZERO Value) |
+=====================================================================+ +=====================================================================+
| ATT | | ATT |
+=====================================================================+ +=====================================================================+
| IID 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
skipping to change at page 31, line 37 skipping to change at page 33, line 37
Binding Cache entry. Binding Cache entry.
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.
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 per [RFC- also allows the use of Sequence Number based scheme, as specified in
3775]. However, for this scheme to work, the serving mobile access [RFC-3775]. However, for this scheme to work, the serving mobile
gateways in a Proxy Mobile IPv6 domain MUST have the ability to access gateways in a Proxy Mobile IPv6 domain MUST have the ability
obtain the last sequence number that was sent in a binding to obtain the last sequence number that was sent in a binding
registration message for updating a given mobile node's binding. The registration message for updating a given mobile node's binding. The
sequence number MUST be maintained on a per mobile node basis and sequence number MUST be maintained on a per mobile node basis and
MUST be synchronized between the serving mobile access gateways. MUST be synchronized between the serving mobile access gateways.
This may be achieved by using context transfer schemes or by This may be achieved by using context transfer schemes or by
maintaining the sequence number in a policy store. However, the maintaining the sequence number in a policy store. However, the
specific details on how the mobile node's sequence number is specific details on how the mobile node's sequence number is
synchronized between different mobile access gateways is outside the synchronized between different mobile access gateways is outside the
scope of this document. scope of this document.
Using Timestamps based approach: Using the Timestamps based approach:
1. A local mobility anchor implementation MUST support 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.
2. All the mobility entities in a Proxy Mobile IPv6 domain that are 2. All the mobility entities in a Proxy Mobile IPv6 domain that are
exchanging binding registration messages using the Timestamp exchanging binding registration messages using the Timestamp
option must have adequately synchronized time-of-day clocks. option MUST have adequately synchronized time-of-day clocks.
This is the essential requirement for this solution to work. If This is the essential requirement for this solution to work. If
this requirement is not met, the solution will not predictably this requirement is not met, the solution will not predictably
work in all cases. work in all cases.
3. The mobility entities in a Proxy Mobile IPv6 domain SHOULD 3. The mobility entities in a Proxy Mobile IPv6 domain SHOULD
synchronize their clocks to a common time source. For synchronize their clocks to a common time source. For
synchronizing the clocks, the nodes may use Network Time Protocol synchronizing the clocks, the nodes MAY use the Network Time
[RFC-4330]. Deployments may also adopt other approaches suitable Protocol [RFC-4330]. Deployments MAY also adopt other approaches
for that specific deployment. Alternatively, if there is mobile suitable for that specific deployment. Alternatively, if there
node generated timestamp that is increasing at every attachment is mobile node generated timestamp that is increasing at every
to the access link and if that timestamp is available to the attachment to the access link and if that timestamp is available
mobile access gateway (Ex: The timestamp option in the SEND to the mobile access gateway (Ex: The timestamp option in the
messages that the mobile node sends), the mobile access gateway SEND messages that the mobile node sends), the mobile access
can use this timestamp or sequence number in the Proxy Binding gateway can use this timestamp or sequence number in the Proxy
Update messages and does not have to depend on any external clock Binding Update messages and does not have to depend on any
source. However, the specific details on how this is achieved is external clock source. However, the specific details on how this
outside the scope of this document. is achieved is outside the scope of this document.
4. When generating the timestamp value for building the Timestamp 4. When generating the timestamp value for building the Timestamp
option, the mobility entities MUST ensure that the generated option, the mobility entities MUST ensure that the generated
timestamp is the elapsed time past the same reference epoch, as timestamp is the elapsed time past the same reference epoch, as
specified in the format for the Timestamp option [Section 8.8]. specified in the format for the Timestamp option (Section 8.8).
5. If the Timestamp option is present in the received Proxy Binding 5. If the Timestamp option is present in the received Proxy Binding
Update message, the local mobility anchor MUST ignore the Update message, the local mobility anchor MUST ignore the
sequence number field in the message. However, it MUST copy the sequence number field in the message. However, it MUST copy the
sequence number from the received Proxy Binding Update message to sequence number from the received Proxy Binding Update message to
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
skipping to change at page 33, line 38 skipping to change at page 35, line 38
day on the local mobility anchor. day on the local mobility anchor.
9. If the timestamp value in the received Proxy Binding Update is 9. If the timestamp value in the received Proxy Binding Update is
not valid (validity as specified in the above considerations), not valid (validity as specified in the above considerations),
the local mobility anchor MUST reject the Proxy Binding Update the local mobility anchor MUST reject the Proxy Binding Update
and send a Proxy Binding Acknowledgement message with Status and send a Proxy Binding Acknowledgement message with Status
field set to TIMESTAMP_MISMATCH (Timestamp mismatch). The field set to TIMESTAMP_MISMATCH (Timestamp mismatch). The
message MUST also include the Timestamp option with the value set message MUST also include the Timestamp option with the value set
to the current time-of-day on the local mobility anchor. to the current time-of-day on the local mobility anchor.
Using Sequence Number based approach: Using the Sequence Number based approach:
1. If the Timestamp option is not present in the received Proxy 1. If the Timestamp option is not present in the received Proxy
Binding Update request, the local mobility anchor MUST fallback Binding Update request, the local mobility anchor MUST fallback
to the Sequence Number based scheme. It MUST process the to the Sequence Number based scheme. It MUST process the
sequence number field as specified in [RFC-3775]. Also, it MUST sequence number field as specified in [RFC-3775]. Also, it MUST
NOT include the Timestamp option in the Proxy Binding NOT include the Timestamp option in the Proxy Binding
Acknowledgement messages that it sends to the mobile access Acknowledgement messages that it sends to the mobile access
gateway. gateway.
2. An implementation MUST support Sequence Number based scheme, as 2. An implementation MUST support the Sequence Number based scheme,
per [RFC-3775]. as specified in [RFC-3775].
3. The Sequence Number based approach can be used only when there is
some mechanism (such as context transfer procedure between mobile
access gateways) that allows the serving mobile access gateway to
obtain the last sequence number that was sent in a 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
data traffic between the mobile access gateway and the local mobility
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
Proxy Mobile IPv6 domain. A tunnel may be created dynamically when
needed and removed when not needed. However, implementations MAY
choose to use static pre-established tunnels instead of dynamically
creating and tearing them down on a need basis. The following
considerations MUST be applied when using dynamic tunnels.
o A bi-directional tunnel MUST be established between the local 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 IP-in-IP
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 with a are the Proxy-CoA and LMAA. When using IPv4 transport, the end
specific encapsulation mode, the end points of the tunnel are the points of the tunnel are the IPv4-LMAA and IPv4-Proxy-CoA, as
IPv4-LMAA and IPv4-Proxy-CoA, as specified in [ID-IPV4-PMIP6]. specified in [ID-IPV4-PMIP6].
o The bi-directional tunnel MUST be used for routing the mobile
node's data traffic between the mobile access gateway and the
local mobility anchor. The tunnel hides the topology and enables
a mobile node to use an address from its home network prefix from
any access link attached to the mobile access gateway.
o The bi-directional tunnel is established after accepting the Proxy
Binding Update request message. The created tunnel may be shared
with other mobile nodes attached to the same mobile access gateway
and with the local mobility anchor having a Binding Cache entry
for those mobile nodes. Implementations MAY choose to use static
tunnels instead of dynamically creating and tearing them down on a
need basis.
o Implementations MAY use a software timer for managing the tunnel o Implementations can 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 MUST be set to the that are sharing the tunnel. The timer value can be set to the
accepted binding lifetime and will 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
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 or for an aggregated prefix
with a larger scope. This essentially enables IPv6 routers in with a larger scope. This essentially enables IPv6 routers in
that network to detect the local mobility anchor as the last-hop that network to detect the local mobility anchor as the last-hop
router for that prefix. router for that prefix.
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 prefix,
the local mobility anchor MUST forward the packet through the bi- the local mobility anchor MUST forward the packet through the bi-
directional tunnel setup for that mobile node. The format of the directional tunnel setup for that mobile node. The format of the
tunneled packet is shown below. However, when using IPv4 tunneled packet is shown below. Considerations from [RFC-2473]
MUST be applied for IPv6 encapsulation. However, when using IPv4
transport, the format of the packet is as described in [ID-IPV4- transport, the format of the packet is as described in [ID-IPV4-
PMIP6]. 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 Packets from LMA to MAG
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
receives 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. field set to the mobile node's home address. Considerations from
[RFC-2473] MUST be applied for IPv6 decapsulation.
5.7. Local Mobility Anchor Address Discovery 5.7. Local Mobility Anchor Address Discovery
Dynamic Home Agent Address Discovery, as explained in Section 10.5 Dynamic Home Agent Address Discovery (DHAAD), as explained in Section
[RFC-3775], allows a mobile node to discover all the home agents on 10.5 of [RFC-3775], allows a mobile node to discover all the home
its home link by sending an ICMP Home Agent Address Discovery Request agents on its home link by sending an ICMP Home Agent Address
message to the Mobile IPv6 Home-Agents anycast address, derived from Discovery Request message to the Mobile IPv6 Home-Agents anycast
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, as the prefix 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
skipping to change at page 37, line 19 skipping to change at page 39, line 27
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 an address from its home network prefix and use
it from its access link. it from its 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 [RFC- List is a conceptual data structure, described in Section 11.1 of
3775]. [RFC-3775].
For supporting this specification, the conceptual Binding Update List For supporting this specification, the conceptual Binding Update List
entry data structure needs be extended with the following additional entry data structure needs be extended with the following additional
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 interface identifier of the mobile node's connected interface. o The link-layer identifier of the mobile node's connected
This address can be acquired from the received Router Solicitation interface. This can be acquired from the received Router
messages from the mobile node or during the mobile node's Solicitation messages from the mobile node or during the mobile
attachment to the access network. This is typically a Layer-2 node's attachment to the access network. This is typically a
identifier conveyed by the mobile node; however, the specific Link-layer identifier conveyed by the mobile node; however, the
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, the value
MUST be set to ALL_ZERO. MUST be set to ALL_ZERO.
o The IPv6 home network prefix of the attached mobile node. The o The IPv6 home network prefix of the attached mobile node. The
home network prefix of the mobile node is acquired from the mobile home network prefix of the mobile node is acquired from the mobile
node's local mobility anchor through the received Proxy Binding node's local mobility anchor through the received Proxy Binding
Acknowledgement messages. The IPv6 home network prefix also Acknowledgement messages. The IPv6 home network prefix also
includes the corresponding prefix length. 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 node on the interface
attached to the access link. attached to the access link.
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 access link where the o The interface identifier (If-Id) of the point-to-point link
mobile node is currently attached. This is internal to the mobile between the mobile node and the mobile access gateway. This is
access gateway and is used to associate the Proxy Mobile IPv6 internal to the mobile access gateway and is used to associate the
tunnel to the access link where the mobile node is attached. Proxy Mobile IPv6 tunnel to the access link where the mobile node
is attached.
o The interface identifier (If-Id) of the bi-directional tunnel o The tunnel interface identifier (If-Id) of the bi-directional
between the mobile node's local mobility anchor and the mobile tunnel between the mobile node's local mobility anchor and the
access gateway. This is internal to the mobile access gateway. mobile access gateway. This is internal to the mobile access
The tunnel interface identifier is acquired during the tunnel gateway. The tunnel interface identifier is acquired during the
creation. tunnel creation.
6.2. Mobile Node's Policy Profile 6.2. Mobile Node's Policy Profile
A mobile node's policy profile contains the essential operational A mobile node's policy profile contains the essential operational
parameters that are required by the network entities for managing the parameters that are required by the network entities for managing the
mobile node's mobility service. These policy profiles are stored in mobile node's mobility service. These policy profiles are stored in
a local or a remote policy store. The mobile access gateway and the a local or a remote policy store. The mobile access gateway and the
local mobility anchor MUST be able to obtain a mobile node's policy local mobility anchor MUST be able to obtain a mobile node's policy
profile. The policy profile MAY also be handed over to a serving profile. The policy profile MAY also be handed over to a serving
mobile access gateway as part of a context transfer procedure during mobile access gateway as part of a context transfer procedure during
skipping to change at page 39, line 12 skipping to change at page 41, line 22
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 guarantees a 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 IPv6 addresses on its interface using Stateless or Stateful more global IPv6 addresses on its interface using Stateless, Stateful
address autoconfiguration procedures. The Router Advertisement or manual address autoconfiguration procedures. The Router
messages sent on the access link specify the address configuration Advertisement messages sent on the access link specify the address
methods permitted on that access link for that mobile node. However, configuration methods permitted on that access link for that mobile
the advertised flags with respect to the address configuration will node. However, the advertised flags with respect to the address
be consistent for a mobile node, on any of the access links in that configuration will be consistent for a mobile node, on any of the
Proxy Mobile IPv6 domain. Typically, these configuration settings access links in that Proxy Mobile IPv6 domain. Typically, these
will be based on the domain wide policy or based on a policy specific configuration settings will be based on the domain wide policy or
to each mobile node. 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 by
standard IPv6 mechanisms such as Stateless Autoconfiguration standard IPv6 mechanisms such as Stateless Autoconfiguration [RFC-
specification [RFC-4862] or Privacy extension specification [RFC- 4862] or Privacy extensions [RFC-4941].
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 DHCPv6 specification [RFC-3315]. The mechanisms, as specified in [RFC-3315]. The obtained address will be
obtained address will be from its respective home network prefix. from its respective home network prefix. Section 6.11 specifies the
Section 6.11 specifies the details on how this configuration can be details on how this configuration can be achieved.
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 pushing the address configuration to the mobile
node. This specification does not change the behavior of address node. This specification does not change the behavior of address
configuration mechanisms in any way. configuration mechanisms in any way.
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
skipping to change at page 40, line 11 skipping to change at page 42, line 22
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
specification goes with the stated assumption of having an specification goes with the stated assumption of having an
established trust between the mobile node and the mobile access established trust between the mobile node and the mobile access
gateway, before the protocol operation begins. gateway, before the protocol operation begins.
6.6. Acquiring Mobile Node's Identifier 6.6. Acquiring Mobile Node's Identifier
All the network entities in a Proxy Mobile IPv6 domain MUST be able All the network entities in a Proxy Mobile IPv6 domain MUST be able
to identify a mobile node, using its MN-Identifier. This identifier to identify a mobile node, using its MN-Identifier. This identifier
MUST be stable across the Proxy Mobile IPv6 domain and the entities MUST be stable and unique across the Proxy Mobile IPv6 domain. The
must be able to use this identifier in the signaling messages. mobility entities in the Proxy Mobile IPv6 domain MUST be able to use
Typically, this identifier is obtained as part of the access this identifier in the signaling messages and unambiguously identify
authentication or through other means as specified below. a given mobile node. Following are some of the considerations
related to this MN-Identifier.
o The identifier of the mobile node that the mobile access gateway o The MN-Identifier is typically obtained as part of the access
obtains typically as part of the access authentication or from the authentication or from a notified network attachment event. In
notified network attachment event, can be a temporary identifier cases where the user identifier authenticated during access
and further that temporary identifier may be different at each re- authentication uniquely identifies a mobile node, the MN-
authentication. The mobile access gateway MUST be able to use Identifier MAY be the same as the user identifier. However, the
this temporary identifier and obtain the mobile node's stable user identifier MUST NOT be used if it identifies a user account
that can be used from more than one mobile node operating in the
same Proxy Mobile IPv6 domain.
o In some cases, the obtained identifier as part of the access
authentication can be a temporary identifier and further that
temporary identifier may be different at each re-authentication.
However, the mobile access gateway MUST be able to use this
temporary identifier and obtain the mobile node's stable
identifier from the policy store. For instance, in AAA-based identifier from the policy store. For instance, in AAA-based
systems the RADIUS attribute, Chargeable-User-Identifier [RFC- systems the RADIUS attribute, Chargeable-User-Identifier [RFC-
4372] may be used. 4372] may be used, as long as it uniquely identifies a mobile
node, and not a user account that can be used with multiple mobile
nodes.
o The MN-Identifier that the policy store delivers to the mobile o In some cases and for privacy reasons, the MN-Identifier that the
access gateway may not be the true identifier of the mobile node. policy store delivers to the mobile access gateway may not be the
However, the mobility access gateway MUST be able to use this true identifier of the mobile node. However, the mobility access
identifier in the signaling messages exchanged with the local gateway MUST be able to use this identifier in the signaling
mobility anchor. messages exchanged with the local mobility anchor.
o The mobile access gateway MUST be able to identify the mobile node o The mobile access gateway MUST be able to identify the mobile node
by its MN-Identifier and it MUST be able to associate this by its MN-Identifier and it MUST be able to associate this
identity to the point-to-point link shared with the mobile node. identity to the point-to-point link shared with the mobile node.
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
skipping to change at page 41, line 22 skipping to change at page 43, line 43
messages, the mobile access gateway MAY set the prefix lifetime value messages, the mobile access gateway MAY set the prefix lifetime value
for the advertised prefix to any chosen value at its own discretion. for the advertised prefix to any chosen value at its own discretion.
An implementation MAY choose to tie the prefix lifetime to the mobile An implementation MAY choose to tie the prefix lifetime to the mobile
node's binding lifetime. The prefix lifetime can also be an optional node's binding lifetime. The prefix lifetime can also be an optional
configuration parameter in the mobile node's policy profile. 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 making it believe it is still on the same link. network and thus believe it is still on the same link. Every time
Every time the mobile node attaches to a new link, the event related the mobile node attaches to a new link, the event related to the
to the interface state change will trigger the mobile node to perform interface state change will trigger the mobile node to perform DAD
DAD operation on the link-local and global addresses. However, if operation on the link-local and global addresses. However, if the
the mobile node is DNAv6 enabled, as specified in [ID-DNAV6], it may mobile node is DNAv6 enabled, as specified in [ID-DNAV6], it may not
not detect the link change due to DNAv6 optimizations and may not detect the link change due to DNAv6 optimizations and may not trigger
trigger the duplicate address detection (DAD) procedure for the duplicate address detection (DAD) procedure for its existing
establishing the link-local address uniqueness on that new link. addresses, which may potentially lead to address collisions after the
This leaves a room for link-local address collision between the two mobile node's handoff to a new link.
neighbors on that access link.
For solving this problem, this specification allows the mobile access
gateway to upload the mobile node's link-local address to the local
mobility anchor using the Link-local Address option, exchanged in the
binding registration messages. The mobile access gateway can learn
the mobile node's link-local address, by snooping the DAD messages
sent by the mobile node for establishing the link-local address
uniqueness on the access link. Subsequently, at each handoff, the
mobile access gateway can obtain this address from the local mobility
anchor to ensure link-local address uniqueness and change its own
link-local address, if it detects a collision.
Alternatively, one of the workarounds for this issue is to set the The issue of address collision is not relevant to the mobile node's
DNAv6 configuration parameter, DNASameLinkDADFlag to TRUE and that global address(es). Since there is a unique home network prefix
will force the mobile node to redo DAD operation on the global and assigned for each mobile node, no other node shares an address (other
link-local addresses every time the interface detects an handoff, than Subnet-Router anycast address which is configured by the mobile
even when DNAv6 does not detect a link change. access gateway) from that prefix and so the uniqueness for the mobile
node's global address is assured on the access link.
However, this issue may not impact point-to-point links based on PPP. The issue of address collision is however relevant to the mobile
Each time the mobile node moves and attaches to a new mobile access node's link-local addresses since the mobile access gateway and the
gateway, the PPP session [RFC-1661] can be re-established, or if mobile node will have link-local addresses configured from the same
there are context transfer procedures in place, the entire PPP link-local prefix (FE80::/64). This leaves a room for link-local
session can be moved to the new link and the link-local addresses of address collision between the two neighbors (i.e., the mobile node
both the peers will continue to remain the same. In either of these and the mobile access gateway) on that access link. For solving this
approaches, the link-local address uniqueness on the link is assured. problem, this specification requires that the link-local address that
The specific details of how the PPP session is re-established without the mobile access gateway configures on the point-to-point link
impacting any layer-3 sessions or how the PPP session can be moved shared with a given mobile node be generated by the local mobility
between the mobile access gateways is outside the scope of this anchor and be stored in the mobile node's Binding Cache entry. This
document. address will not change for the duration of that mobile node's
session and can be provided to the serving mobile access gateway at
every mobile node's handoff, as part of the Proxy Mobile IPv6
signaling messages. The specific method by which the local mobility
anchor generates the link-local addresses is out of scope for this
specification.
The issue of address collision is not relevant to the mobile node's Optionally, implementations MAY choose to configure a fixed link-
global address. Since there is a unique home network prefix assigned local address across all the access links in a Proxy Mobile IPv6
for each mobile node, the uniqueness for the mobile node's global domain and without a need for carrying this address from the local
address is assured on the access link. mobility anchor to the mobile access gateway in the Proxy Mobile IPv6
signaling messages.
6.9. Signaling Considerations 6.9. Signaling Considerations
6.9.1. Binding Registrations 6.9.1. Binding Registrations
6.9.1.1. Mobile Node Attachment and Initial Binding Registration 6.9.1.1. Mobile Node Attachment and Initial Binding Registration
1. After detecting a new mobile node on its access link, the mobile 1. After detecting a new mobile node on its access link, the mobile
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
skipping to change at page 43, line 10 skipping to change at page 45, line 25
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
node's current attachment to the network over this interface node's current attachment to the network over this interface
is not as a result of an handoff of an existing mobility is not as a result of a handoff of an existing mobility
session (over the same interface or through a different session (over the same interface or through a different
interface), but as a result of an attachment over a new interface), but as a result of an attachment over a new
interface. This essentially serves as a request to the local interface. This essentially serves as a request to the local
mobility anchor to create a new mobility session and not mobility anchor to create a new mobility session and not
update any existing Binding Cache entry created for the same update any existing Binding Cache entry created for the same
mobile node connected to the Proxy Mobile IPv6 domain through mobile node connected to the Proxy Mobile IPv6 domain through
a different interface. a different interface.
* The Handoff Indicator field MUST be set to value 2 (Handoff * The Handoff Indicator field MUST be set to value 2 (Handoff
between two different interfaces of the mobile node), if the between two different interfaces of the mobile node), if the
mobile access gateway definitively knows the mobile node's mobile access gateway definitively knows the mobile node's
current attachment is due to an handoff of an existing current attachment is due to a handoff of an existing
mobility session, between two different interfaces of the mobility session, between two different interfaces of the
mobile node. mobile node.
* The Handoff Indicator field MUST be set to value 3 (Handoff * The Handoff Indicator field MUST be set to value 3 (Handoff
between mobile access gateways for the same interface), if between mobile access gateways for the same interface), if
the mobile access gateway definitively knows the mobile the mobile access gateway definitively knows the mobile
node's current attachment is due to an handoff of an existing node's current attachment is due to a handoff of an existing
mobility session between two mobile access gateways and for mobility session between two mobile access gateways and for
the same interface of the mobile node. the same interface of the mobile node.
* The Handoff Indicator field MUST be set to value 4 (Handoff * The Handoff Indicator field MUST be set to value 4 (Handoff
state unknown), if the mobile access gateway cannot determine state unknown), if the mobile access gateway cannot determine
if the mobile node's current attachment is due to an handoff if the mobile node's current attachment is due to a handoff
of an existing mobility session. of an existing mobility session.
5. The mobile access gateway MUST apply the below considerations 5. The mobile access gateway MUST apply the below considerations
when choosing the value for the Handoff Indicator field. when choosing the value for the Handoff Indicator field.
* The mobile access gateway can choose to use the value 2 * The mobile access gateway can choose to use the value 2
(Handoff between two different interfaces of the mobile (Handoff between two different interfaces of the mobile
node), only when it knows that the mobile node has on purpose node), only when it knows that the mobile node has on purpose
switched from one interface to another, and the previous switched from one interface to another, and the previous
interface is going to be disabled. It may know this due to a interface is going to be disabled. It may know this due to a
number of factors. For instance, most cellular networks have number of factors. For instance, most cellular networks have
controlled handovers where the network knows that the host is controlled handovers where the network knows that the host is
moving from one attachment to another. In this situation the moving from one attachment to another. In this situation the
link layer mechanism can inform the mobility functions that link layer mechanism can inform the mobility functions that
this is indeed a movement, not a new attachment. this is indeed a movement, not a new attachment.
* Some link layers have interface identifiers that can be used * Some link layers have link-layer identifiers that can be used
to distinguish (a) the movement of a particular interface to to distinguish (a) the movement of a particular interface to
a new attachment from (b) the attachment of new interface a new attachment from (b) the attachment of a new interface
from the same host. Option value 3 (Handoff between mobile from the same host. Option value 3 (Handoff between mobile
access gateways for the same interface)is appropriate in case access gateways for the same interface)is appropriate in case
a and value of 1 (Attachment over a new interface) in case b. a and value of 1 (Attachment over a new interface) in case b.
* The mobile access gateway MUST NOT set the option value to 2 * The mobile access gateway MUST NOT set the option value to 2
(Handoff between two different interfaces of the mobile node) (Handoff between two different interfaces of the mobile node)
or 3 (Handoff between mobile access gateways for the same or 3 (Handoff between mobile access gateways for the same
interface) if it can not be determined that the mobile node interface) if it can not be determined that the mobile node
can move the address between the interfaces involved in the can move the address between the interfaces involved in the
handover or that it is the same interface that has moved. handover or that it is the same interface that has moved.
Otherwise Proxy Mobile IPv6-unaware hosts that have multiple Otherwise Proxy Mobile IPv6-unaware hosts that have multiple
physical interfaces to the same domain may suffer unexpected physical interfaces to the same domain may suffer unexpected
failures. failures.
* Where no support from link-layer exists, the host and the * Where no support from the link layer exists, the host and the
network would need to inform each other about the intended network would need to inform each other about the intended
movement. Proxy Mobile IPv6 protocol does not specify this movement. The Proxy Mobile IPv6 protocol does not specify
and simply requires that knowledge about movements can be this and simply requires that knowledge about movements can
derived either from the link-layer or from somewhere else. be derived either from the link-layer or from somewhere else.
The method by which this is accomplished is outside the scope The method by which this is accomplished is outside the scope
of this specification. of this specification.
6. Either the Timestamp option or a valid sequence number 6. Either the Timestamp option or a valid sequence number
maintained on a per mobile node basis (if Sequence Number based maintained on a per mobile node basis (if the Sequence Number
scheme is in use) MUST be present. When Timestamp option is based scheme is in use) MUST be present. When Timestamp option
added to the message, the mobile access gateway SHOULD also set is added to the message, the mobile access gateway SHOULD also
the Sequence Number field to a value of a monotonically set the Sequence Number field to a value of a monotonically
increasing counter (not to be confused with the per mobile node increasing counter (not to be confused with the per mobile node
sequence number specified [RFC-3775]). The local mobility sequence number specified in [RFC-3775]). The local mobility
anchor will ignore this field when there is a Timestamp option anchor will ignore this field when there is a Timestamp option
present in the request, but will return the same value in the present in the request, but will return the same value in the
Proxy Binding Acknowledgement message. This will be useful for Proxy Binding Acknowledgement message. This will be useful for
matching the reply to the request message. matching the reply to the request message.
7. The Mobile Node Interface Identifier option carrying the 7. The Mobile Node Link-layer Identifier option carrying the link-
interface identifier of the currently attached interface MUST be layer identifier of the currently attached interface MUST be
present in the Proxy Binding Update message, if the mobile present in the Proxy Binding Update message, if the mobile
access gateway knows the interface identifier of the mobile access gateway is aware of the same. If the link-layer
node's currently attached interface. If the interface identifier of the currently attached interface is not known or
identifier is not known or if the identifier value is ALL_ZERO, if the identifier value is ALL_ZERO, this option MUST NOT be
this option MUST NOT be present. present.
8. The Access Technology Type option MUST be present in the Proxy 8. The Access Technology Type option MUST be present in the Proxy
Binding Update message. The access technology type field in the Binding Update message. The access technology type field in the
option SHOULD be set to the type of access technology using option SHOULD be set to the type of access technology using
which the mobile node is currently attached to the mobile access which the mobile node is currently attached to the mobile access
gateway. gateway.
9. The Link-local Address option MAY be present in the Proxy 9. The Link-local Address option MAY be present in the Proxy
Binding Update message. Considerations from Section 6.8 MUST be Binding Update message. Considerations from Section 6.8 MUST be
applied when using the link-local address option. applied when using the link-local address option.
* When querying the local mobility anchor for the link-local
address that it should use on the point-to-point link shared
with the mobile node, this option MUST be set to ALL_ZERO.
This essentially serves as a request to the local mobility
anchor to return the link-local address of the mobile access
gateway stored in the binding cache entry associated with
this mobility session.
* When uploading the link-local address to the local mobility * When uploading the link-local address to the local mobility
anchor, the value in the option MUST be set to the link-local anchor, the value in the option MUST be set to the link-local
address that is configured on the currently attached address that is configured on the point-to-point link shared
interface of the mobile node. with the mobile node. This is allowed only during an initial
mobile node's attachment.
* When querying the local mobility anchor for the mobile node's
link-local address, the option MUST be set to ALL_ZERO value.
This essentially serves as a request to the local mobility
anchor to return the link-local address of the mobile node
from the binding cache entry corresponding to this mobility
session.
10. The Proxy Binding Update message MUST be constructed as 10. The Proxy Binding Update message MUST be constructed as
specified in Section 6.9.1.5. specified in Section 6.9.1.5.
11. If there is no existing Binding Update List entry for that 11. If there is no existing Binding Update List entry for that
mobile node, the mobile access gateway MUST create a Binding mobile node, the mobile access gateway MUST create a Binding
Update List entry for the mobile node upon sending the Proxy Update List entry for the mobile node upon sending the Proxy
Binding Update request. Binding Update request.
6.9.1.2. Receiving Binding Registration Reply 6.9.1.2. Receiving Binding Registration Reply
skipping to change at page 45, line 46 skipping to change at page 48, line 20
1. The received Proxy Binding Acknowledgement message (a Binding 1. The received Proxy Binding Acknowledgement message (a Binding
Acknowledgement message with the 'P' flag set to value of 1) Acknowledgement message with the 'P' flag set to value of 1)
MUST be authenticated as described in Section 4. When IPsec is MUST be authenticated as described in Section 4. When IPsec is
used for message authentication, the SPI in the IPsec header used for message authentication, the SPI in the IPsec header
[RFC-4306] of the received packet is needed for locating the [RFC-4306] of the received packet is needed for locating the
security association, for authenticating the Proxy Binding security association, for authenticating the Proxy Binding
Acknowledgement message . Acknowledgement message .
2. The mobile access gateway MUST observe the rules described in 2. The mobile access gateway MUST observe the rules described in
Section 9.2 [RFC-3775] when processing Mobility Headers in the Section 9.2 of [RFC-3775] when processing Mobility Headers in
received Proxy Binding Acknowledgement message. the received Proxy Binding Acknowledgement message.
3. The mobile access gateway MUST apply the considerations 3. The mobile access gateway 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 message. field and the Timestamp option (if present), in the message.
4. The mobile access gateway MUST ignore any checks, specified in 4. The mobile access gateway MUST ignore any checks, specified in
[RFC-3775] related to the presence of Type 2 Routing header in [RFC-3775] related to the presence of a Type 2 Routing header in
the Proxy Binding Acknowledgement message. the Proxy Binding Acknowledgement message.
5. The mobile access gateway MAY use the mobile node identifier 5. The mobile access gateway MAY use the mobile node identifier
present in the Mobile Node Identifier option for matching the present in the Mobile Node Identifier option for matching the
response to the request messages that it sent recently . response to the request messages that it sent recently .
However, if there are more than one request message in its However, if there is more than one request message in its
request queue for the same mobile node, the sequence number request queue for the same mobile node, the sequence number
field can be used for identifying the exact message from those field can be used for identifying the exact message from those
messages. There are other ways to achieve this and messages. There are other ways to achieve this and
implementations are free to adopt the best approach that suits implementations are free to adopt the best approach that suits
their implementation. Additionally, if the received Proxy their implementation. Additionally, if the received Proxy
Binding Acknowledgement message does not match any of the Proxy Binding Acknowledgement message does not match any of the Proxy
Binding Update messages that it sent recently, the message MUST Binding Update messages that it sent recently, the message MUST
be ignored. be ignored.
6. If the received Proxy Binding Acknowledgement message has any 6. If the received Proxy Binding Acknowledgement message has any
one or more of the following options, Handoff Indicator option, one or more of the following options, Handoff Indicator option,
Access Technology Type option, Mobile Node Interface Identifier Access Technology Type option, Mobile Node Link-layer Identifier
option, Mobile Node Identifier option, carrying option values option, Mobile Node Identifier option, carrying option values
that are different from the option values present in the that are different from the option values present in the
corresponding request (Proxy Binding Update) message, the corresponding request (Proxy Binding Update) message, the
message MUST be ignored as the local mobility anchor is expected message MUST be ignored as the local mobility anchor is expected
to echo back all these listed options and with the same option to echo back all these listed options and with the same option
values in the reply message. Further, the mobile access gateway values in the reply message. Further, the mobile access gateway
MUST NOT retransmit the Proxy Binding Update message till an MUST NOT retransmit the Proxy Binding Update message till an
administrative action is taken. administrative action is taken.
7. If the received Proxy Binding Acknowledgement message has the 7. If the received Proxy Binding Acknowledgement message has the
skipping to change at page 47, line 27 skipping to change at page 49, line 45
prefix), the mobile access gateway SHOULD NOT request for the prefix), the mobile access gateway SHOULD NOT request for the
same prefix again, but can request the local mobility anchor to same prefix again, but can request the local mobility anchor to
dynamically assign a prefix, by specifying a ALL_ZERO value in dynamically assign a prefix, by specifying a ALL_ZERO value in
the Home Network Prefix option carried in the subsequent Proxy the Home Network Prefix option carried in the subsequent Proxy
Binding Update message. Binding Update message.
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 in the
Router Advertisements sent on that access link and there by Router Advertisements sent on that access link and MUST deny the
denying mobility service to the mobile node. mobility service to the mobile node by not forwarding any
packets using the source address from that home network prefix
and originating from that point-to-point link.
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 update the routing state, as
explained in section 6.10, and MUST also update the Binding explained in section 6.10, and MUST also update the Binding
Update List entry for reflecting the accepted binding Update List entry for reflecting the accepted binding
registration status. registration status.
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 value that address in the Link-local Address option set to a NON_ZERO
matches its own link-local address on that access interface value, the mobile access gateway MUST configure that link-local
where the mobile node is anchored, the mobile access gateway address on that point-to-point link and MUST NOT configure any
MUST change its link-local address on that interface, to avoid other link-local address on that point-to-point link. This will
link-local address collision on that access link. avoid any link-local address collisions 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. The prefix value in the Home Network Prefix option MUST be set to
the currently assigned home network prefix. the currently assigned home network prefix.
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).
4. The value in the Link-local Address option (if the option was
present in the initial registration message) MUST be set to the
link-local address of the mobile node's attached interface.
6.9.1.4. Mobile Node Detachment and Binding De-Registration 6.9.1.4. Mobile Node Detachment and Binding De-Registration
1. 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. The prefix value in the Home Network Prefix option MUST be set to
the currently assigned home network prefix. the currently assigned home network prefix.
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).
4. The value in the Link-local Address option (if the option was
present in the initial registration message) MUST be set to the
link-local address of the mobile node's attached interface.
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
from its Binding Update List. from its Binding Update List.
2. It MUST withdraw the mobile node's home network prefix as the 2. It MUST remove the created routing state for tunneling the mobile
hosted on-link prefix, by sending a Router Advertisement message
with the prefix lifetime value set to zero.
3. It MUST remove the created routing state for tunneling the mobile
node's traffic. node's traffic.
4. It SHOULD teardown the point-to-point link shared with the mobile 3. If there is a dynamically created tunnel to the mobile node's
local mobility anchor and if there are not other mobile nodes for
which the tunnel is being used, then the tunnel MUST be deleted.
4. It MUST tear down the point-to-point link shared with the mobile
node. This action will force the mobile node to remove any IPv6 node. This action will force the mobile node to remove any IPv6
address configuration on the interface connected to this point- address configuration on the interface connected to this point-
to-point link. to-point link.
6.9.1.5. Constructing the Proxy Binding Update Message 6.9.1.5. Constructing the Proxy Binding Update Message
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 (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 Interface 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 11: 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 address configured on the interface of the mobile set to the global address configured on the egress interface of
access gateway. When there is no Alternate Care-of Address option the mobile access gateway. When there is no Alternate Care-of
present in the request, this address will be considered as the Address option present in the request, this address will be
Proxy-CoA address for this binding registration request. However, considered as the Proxy-CoA address for this binding registration
when there is Alternate Care-of Address option present in the request. However, when there is Alternate Care-of Address option
request, this address will be not be considered as the Proxy-CoA present in the request, this address will be not be considered as
address, but the address in the alternate Care-of Address option the Proxy-CoA address, but the address in the alternate Care-of
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 The 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 Interface 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.
o If IPsec is used for protecting the signaling messages, the o If IPsec is used for protecting the signaling messages, the
message MUST be protected, using the security association existing message MUST be protected, using the security association existing
between the local mobility anchor and the mobile access gateway. between the local mobility anchor and the mobile access gateway.
o Unlike in Mobile IPv6 [RFC-3775], the Home Address option [RFC- o Unlike in Mobile IPv6 [RFC-3775], the Home Address option [RFC-
3775] MUST NOT be present in the IPv6 Destination Options 3775] MUST NOT be present in the IPv6 Destination Options
extension header of the Proxy Binding Update message. extension header of the Proxy Binding Update message.
6.9.2. Router Solicitation Messages 6.9.2. Router Solicitation Messages
The mobile node may send a Router Solicitation message on the access A mobile node may send a Router Solicitation message on the access
link whenever the link-layer detects a media change. The Source link shared with the mobile access gateway. The Router Solicitation
Address in the IPv6 header of the Router Solicitation message may message that the mobile node sends is as specified in [RFC-4861].
either be the link-local address of the mobile node or an unspecified The mobile access gateway on receiving the Router Solicitation
address (::). The Router Solicitation message that the mobile node message or before sending a Router Advertisement message MUST apply
sends is as specified in [RFC-4861]. 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 containing the mobile
node's home network prefix as the on-link prefix. However, node's home network prefix as the on-link prefix. However,
before sending the Router Advertisement message containing the before sending the Router Advertisement message containing the
mobile node's home network prefix, it SHOULD complete the binding mobile node's home network prefix, it SHOULD complete the binding
registration process with the mobile node's local mobility registration process with the mobile node's local mobility
anchor. 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 reasons, 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 in the Router Advertisement messages that it sends on the
access link. However, it MAY choose to advertise a local visited access link. However, it MAY choose to advertise a local visited
network prefix to enable the mobile node for regular IPv6 access. network prefix to enable the mobile node for regular IPv6 access.
6.9.3. Default-Router Lifetime 3. The mobile access gateway SHOULD add the MTU option, as specified
in [RFC-4861], to the Router Advertisement messages that it sends
In Proxy Mobile IPv6, the mobile access gateway is typically the IPv6 on the access link. This will ensure the mobile node on the link
default-router for the mobile node on the access link, as it is the uses the advertised MTU value. The MTU value MUST reflect the
entity that sends the Router Advertisements on the access link. tunnel MTU for the bi-directional tunnel between the mobile
However, as the mobile node moves from one access link to another, access gateway and the local mobility anchor.
the serving mobile access gateway on those respective links will send
the Router Advertisements and using their own link-local address.
The mobile node on each of the attached links will receive Router
Advertisement messages with a different source address and this makes
the mobile node believe that there is a new default-router on that
access link.
The mobile node will certainly detect the previous default-router
loss by performing the Neighbor Unreachability Detection procedure
per the standard IPv6 ND mechanisms, but it is important that the
mobile access gateway enables the mobile node to withdraw the
previous default-router entry at the earliest. This action will help
in minimizing packet losses during a hand off switch. Following are
some considerations that implementations can apply.
The Router Lifetime field in the Router Advertisement messages that
the mobile access gateway sends on the access link SHOULD be kept to
low.
In access networks where SEND [RFC-3971] is not deployed, the mobile 6.9.3. Default-Router
access gateway can withdraw the previous default-router entry, by
sending a Router Advertisement using the link-local address that of
the previous mobile access gateway and with the Router Lifetime field
set to value zero, then this will force the flush of the previous
default-router entry from the mobile node's cache, as specified in
Section 6.3.5 [RFC-4861]. However, this approach requires the
serving mobile access gateway to learn the link-local address of the
previous mobile access gateway where the mobile node was handed off.
There are other solutions possible for this problem, including the In Proxy Mobile IPv6, the mobile access gateway is the IPv6 default-
assignment of a fixed link-local address for all the mobility router for the mobile node on the access link, as it is the entity
entities in a Proxy Mobile IPv6 domain and where SEND [RFC-3971] is that sends the Router Advertisements on the access link. However, as
not deployed. In such scenario, the mobile node is not required to the mobile node moves from one access link to another, the serving
update the default-router entry. However, this is an implementation mobile access gateway on those respective links will send the Router
choice and has no bearing on the protocol interoperability. Advertisements. If these Router Advertisements are sent using a
Implementations are free to adopt the best approach that suits their different link-local address or a different link-layer address, the
target deployments. mobile node will always detect a new default-router after every
handoff. For solving this problem, this specification requires all
the mobile access gateways in the Proxy Mobile IPv6 domain to use the
same link-local and link-layer address on any of the access links
where ever the mobile node attaches. The link-layer address can be a
fixed address across that all the mobile access gateways can use on
any of the point-to-point links. However, the link-local address can
be an address provided by the local mobility anchor, or a fixed
address.
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 52, line 23 skipping to change at page 54, line 14
of InitialBindackTimeoutFirstReg as specified in [RFC-3775] for of InitialBindackTimeoutFirstReg as specified in [RFC-3775] for
the initial binding registration request. the initial binding registration request.
2. If the mobile access gateway fails to receive a valid matching 2. If the mobile access gateway fails to receive a valid matching
response for a registration or re-registration message within the response for a registration or re-registration message within the
retransmission interval, it SHOULD retransmit the message until a retransmission interval, it SHOULD retransmit the message until a
response is received. However, the mobile access gateway MUST response is received. However, the mobile access gateway MUST
ensure the mobile node is still attached to the connected link ensure the mobile node is still attached to the connected link
before retransmitting the message. before retransmitting the message.
3. As specified in Section 11.8 [RFC-3775], the mobile access 3. As specified in Section 11.8 of [RFC-3775], the mobile access
gateway MUST use an exponential back-off process in which the gateway MUST use an exponential back-off process in which the
timeout period is doubled upon each retransmission, until either timeout period is doubled upon each retransmission, until either
the node receives a response or the timeout period reaches the the node receives a response or the timeout period reaches the
value MAX_BINDACK_TIMEOUT [RFC-3775]. The mobile access gateway value MAX_BINDACK_TIMEOUT [RFC-3775]. The mobile access gateway
MAY continue to send these messages at this slower rate MAY continue to send these messages at this slower rate
indefinitely. indefinitely.
4. If 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 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.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
interface. 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 12: Proxy Mobile IPv6 Tunnel
6.10.1. Transport Network 6.10.1. Transport Network
The transport network between the local mobility anchor and the As per this specification, the transport network between the local
mobile access gateway can be either an IPv6 or IPv4 network. mobility anchor and the mobile access gateway is an IPv6 network.
However, this specification only deals with the IPv6 transport and 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 for supporting this protocol operation. encapsulation mode.
6.10.2. Tunneling & Encapsulation Modes 6.10.2. Tunneling & Encapsulation Modes
The IPv6 address that a mobile node uses from its home network prefix Each IPv6 address that a mobile node uses from its home network
is topologically anchored at the local mobility anchor. For a mobile prefix is topologically anchored at the local mobility anchor. For a
node to use this address from an access network attached to a mobile mobile node to use this address from an access network attached to a
access gateway, proper tunneling techniques have to be in place. mobile access gateway, proper tunneling techniques have to be in
Tunneling hides the network topology and allows the mobile node's place. Tunneling hides the network topology and allows the mobile
IPv6 datagram to be encapsulated as a payload of another IPv6 packet node's IPv6 datagram to be encapsulated as a payload of another IPv6
and to be routed between the local mobility anchor and the mobile packet and to be routed between the local mobility anchor and the
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, between the home agent
and the mobile node and this specification extends the use of the and the mobile node and this specification extends the use of the
same tunneling mechanism between the local mobility anchor and the same tunneling mechanism between the local mobility anchor and the
mobile access gateway. mobile access gateway.
On most operating systems, tunnels are 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 and the addresses as specified for that point to point
tunnel interface. For creating a point to point tunnel to any local tunnel interface. For creating a point to point tunnel to any local
mobility anchor, the mobile access gateway may implement a tunnel mobility anchor, the mobile access gateway may implement a tunnel
interface with the source address field set to its Proxy-CoA address interface with the source address field set to its Proxy-CoA address
and the destination address field set to the LMA address. and the destination address field set to the LMA address.
The following are the supported packet encapsulation modes that can The following is the supported packet encapsulation mode that can be
be used by the mobile access gateway and the local mobility anchor used by the mobile access gateway and the local mobility anchor for
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
modes for supporting IPv4 transport.
o IPv6-In-IPv4 - IPv6 datagram encapsulation in an IPv4 packet. The o IPv6-In-IPv4 - IPv6 datagram encapsulation in an IPv4 packet. The
details on how this mode is negotiated is specified in [ID-IPV4- details on how this mode is negotiated is specified in [ID-IPV4-
PMIP6]. PMIP6].
o IPv6-In-IPv4-UDP - IPv6 datagram encapsulation in an IPv4 UDP o IPv6-In-IPv4-UDP - IPv6 datagram encapsulation in an IPv4 UDP
packet. This mode is specified in [ID-IPV4-PMIP6]. packet. This mode is specified in [ID-IPV4-PMIP6].
o IPv6-In-IPv4-UDP-TLV - IPv6 datagram encapsulation in an IPv4 UDP
packet with a TLV header. This mode is specified in [ID-IPV4-
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 configuration variable, EnableMAGLocalRouting MAY be
used for controlling this aspect. However, in some systems, this may used for controlling this aspect. However, in some systems, this may
have an implication on the mobile node's accounting and policy have an implication on the mobile node's accounting and policy
skipping to change at page 54, line 42 skipping to change at page 56, line 39
6.10.5. Forwarding Rules 6.10.5. Forwarding Rules
Forwarding Packets sent to the Mobile Node's Home Network: Forwarding Packets sent to the Mobile Node's Home Network:
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. If the mobile access gateway header before forwarding the packet. Considerations from [RFC-
cannot find the connected interface for that destination address, 2473] MUST be applied for IPv6 decapsulation. If the mobile
it MUST silently drop the packet. For reporting an error in such access gateway cannot find the connected interface for that
a scenario, in the form of ICMP control message, the destination address, it MUST silently drop the packet. For
considerations from Generic Packet Tunneling specification [RFC- reporting an error in such a scenario, in the form of ICMP control
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 configuration variable, EnableMAGLocalRouting, to
ensure the mobile access gateway is allowed to route the packet ensure the mobile access gateway is allowed to route the packet
directly to the mobile node. If the mobile access gateway is not directly to the mobile node. If the mobile access gateway is not
allowed to route the packet directly, it MUST route the packet allowed to route the packet directly, it MUST route the packet
through the bi-directional tunnel established between itself and through the bi-directional tunnel established between itself and
the mobile node's local mobility anchor. Otherwise, it can route the mobile node's local mobility anchor. Otherwise, it can route
skipping to change at page 55, line 36 skipping to change at page 57, line 33
it MUST route the packet through the bi-directional tunnel it MUST route the packet through the bi-directional tunnel
established between itself and the mobile node's local mobility established between itself and the mobile node's local mobility
anchor. Otherwise, it can route the packet directly to the anchor. Otherwise, it can route 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 the 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. The with the link-local source address MUST NOT be forwarded.
format of the tunneled packet is shown below. Additionally, when
using IPv4 transport, the format of the tunneled packet is as o The format of the tunneled packet is shown below. Considerations
described in [ID-IPV4-PMIP6]. from [RFC-2473] MUST be applied for IPv6 encapsulation.
Additionally, when using IPv4 transport, the format of the
tunneled packet is as 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 13: Tunneled Packets from MAG to LMA
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 access link attached to a mobile access gateway can be enabled on the point-to-point link between the mobile node and
and how a mobile node attached to that link can obtain an address the mobile access gateway and how a mobile node attached to that link
from its home network prefix 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 [RFC-3315], the DHCPv6 relay Further, as specified in Section 20 of [RFC-3315], the DHCPv6
agent should be configured to use a list of destination addresses, relay agent should be configured to use a list of destination
which MAY include unicast addresses, the All_DHCP_Servers addresses, which MAY include unicast addresses, the
multicast address, or other addresses selected by the network All_DHCP_Servers multicast address, or other addresses selected by
administrator. the network administrator.
o The DHCPv6 server in the Proxy Mobile IPv6 domain can be o A DHCPv6 server in the Proxy Mobile IPv6 domain can be configured
configured with a list of prefix pools (P1, P2, ..., Pn). Each with a set of prefixes (P1, P2, ..., Pn). Each one of these
one of these prefix pools corresponds to a home network prefix prefixes in this prefix list is a home network prefix that the
that a local mobility anchor allocates to a mobile node in that local mobility anchor(s) can assign to any mobile node. However,
domain. However, the DHCPv6 server will not know the relation the DHCPv6 server will not know the relation between a given
between a given address pool and a mobile node to which the prefix and a mobile node to which the corresponding prefix is
corresponding prefix is allocated. It just views these pools as allocated. It just views these prefixes as hosted prefixes on
prefixes hosted on different links in that domain. different links in that domain and assigns individual addresses
from the respective prefixes based on the prefix value present in
the link-address option of the received DHCPv6 request.
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 access link will set the link-address relay agent function on the mobile access gateway will set the
field in the DHCPv6 message to an address in the mobile node's link-address field in the DHCPv6 message to an address in the
home network prefix. The address is generated as per [RFC-4862] mobile node's home network prefix. The address is generated as
by combining the mobile node's home network prefix (assigned by per [RFC-4862] by combining the mobile node's home network prefix
the local mobility anchor for this mobility session) and its own (assigned by the local mobility anchor for this mobility session)
interface identifier on the access link shared with the mobile and its own interface identifier on the access link shared with
node, so as to provide a prefix hint to the DHCPv6 Server for the the mobile node, so as to provide a prefix hint to the DHCPv6
address pool selection. The DHCPv6 server on receiving the Server for the prefix selection. The DHCPv6 server on receiving
request from the mobile node, will allocate an address from the the request from the mobile node, will allocate an address from
prefix pool pointed to by the link-address field of the request. the prefix pointed to by 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 an address and moves to a different
link and sends a DHCPv6 request, the DHCPv6 relay agent on the new link and sends a DHCPv6 request (at any time) for extending the
link will set the prefix hint in the DHCPv6 message to the mobile DHCP lease, the DHCPv6 relay agent on the new link will set the
node's home network prefix (assigned by the local mobility anchor prefix hint in the DHCPv6 message to the mobile node's home
for this mobility session). The DHCPv6 server will identify the network prefix (assigned by the local mobility anchor for this
client from the Client-DUID option and present in the request and mobility session). The DHCPv6 server will identify the client
will allocate the same address as before. from the Client-DUID option present in the request and will
allocate the same address 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. DHCPv6 server or by a server from the same group of coordinated
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. deletes the mobile node's binding cache entry. It is recommended
that the configured lease time be lower than the accepted 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 gets renumbered or becomes
invalid during the middle of a mobility session, the mobile access invalid during the middle of a mobility session, the mobile access
gateway MUST withdraw the prefix by sending a Router Advertisement on gateway MUST withdraw the prefix by sending a Router Advertisement on
the access link with zero prefix lifetime for the mobile node's home the access link with zero prefix lifetime for the mobile node's home
network prefix. Also, the local mobility anchor and the mobile network prefix. Also, the local mobility anchor and the mobile
access gateway MUST delete the routing state for that prefix. access gateway MUST delete the routing state for that prefix.
However, the specific details on how the local mobility anchor However, the specific details on how the local mobility anchor
skipping to change at page 57, line 36 skipping to change at page 59, line 43
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.
Further, in such scenario, the mobile access gateway SHOULD terminate Further, in such a scenario, the mobile access gateway SHOULD
the binding of the mobile node by sending a Proxy Binding Update terminate the binding of the mobile node by sending a Proxy Binding
message to the mobile node's local mobility anchor with lifetime Update message to the mobile node's local mobility anchor with
value set to 0. It MUST also remove any local state such as the lifetime value set to 0. It MUST also remove any local state such as
Binding Update List entry created for that mobile node. the Binding Update List entry created for that mobile node.
The specific detection mechanism of the loss of a visiting mobile The specific detection mechanism of the loss of a visiting mobile
node on the connected link is specific to the access link between the node on the connected link is specific to the access link between the
mobile node and the mobile access gateway and is outside the scope of mobile node and the mobile access gateway and is outside the scope of
this document. Typically, there are various link-layer specific this document. Typically, there are various link-layer specific
events specific to each access technology that the mobile access events specific to each access technology that the mobile access
gateway can depend on for detecting the node loss. In general, the gateway can depend on for detecting the node loss. In general, the
mobile access gateway can depend on one or more of the following mobile access gateway can depend on one or more of the following
methods for the detection presence of the mobile node on the methods for the detection presence of the mobile node on the
connected link: connected link:
skipping to change at page 58, line 34 skipping to change at page 60, line 39
considerations, the mobile access gateway MUST determine if network- considerations, the mobile access gateway MUST determine if network-
based mobility management service should be offered to that mobile based mobility management service should be offered to that mobile
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 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 an IPv6 address using normal IPv6 address configuration
procedures. The obtained address must be from a local visitor procedures. The obtained address must be from a local visitor
network prefix. This essentially ensures that the mobile access network prefix. 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 with out impacting its host-based mobility to its access link and with out impacting its host-based mobility
protocol operation. protocol operation.
7. Mobile Node Operation 7. Mobile Node Operation
skipping to change at page 59, line 11 skipping to change at page 61, line 17
When a mobile node enters a Proxy Mobile IPv6 domain and attaches to When a mobile node enters a Proxy Mobile IPv6 domain and attaches to
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 setup the data path for gateway will create the required state and setup 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 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. The Router
Advertisement will have the mobile node's home network prefix, Advertisement will have the mobile node's home network prefix,
default-router address and other address configuration parameters. 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 completed 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 and
may not be able to emulate the mobile node's home link on the access may not be able to emulate the mobile node's home link on the access
link. In such scenario, the mobile node may notice a slight delay link. In such a scenario, the mobile node may notice a slight delay
before it receives a Router Advertisement message. before it receives a Router Advertisement message.
If the received Router Advertisement has the Managed Address If the received Router Advertisement 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 will obtain
its IPv6 address as a lease from its home network prefix. its IPv6 address as a lease from its home network prefix.
If the received Router Advertisement does not have the Managed If the received Router Advertisement does not have the Managed
Address Configuration flag set and if the mobile node is allowed to Address Configuration flag set and if the mobile node is allowed to
use an autoconfigured address, the mobile node will be able to obtain use an autoconfigured address, the mobile node will be able to obtain
an IPv6 address using an interface identifier generated as per the an IPv6 address using any of the standard IPv6 address configuration
Autoconf specification [RFC-4862] or as per the Privacy Extensions mechanisms permitted for that mode.
specification [RFC-4941].
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
network 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 link, where it obtained its initial node will always detect the same default-router advertising the
address configuration. If the mobile node performs DHCP operation, mobile node's home network prefix on each connected link. If the
it will always obtain the same address as before. mobile node performs DHCP operation, it will always obtain the same
address as before.
However, the mobile node will always detect a new default-router on
each connected link, but still advertising the mobile node's home
network prefix as the on-link prefix and with the other configuration
parameters consistent with its home link properties.
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 61, line 18 skipping to change at page 63, line 18
indicate to the local mobility anchor that the Binding Update indicate to the local mobility anchor that the Binding Update
message is a proxy registration. The flag MUST be set to the message is a proxy registration. The flag MUST be set to the
value of 1 for proxy registrations and MUST be set to 0 for direct value of 1 for proxy registrations and MUST be set to 0 for direct
registrations sent by a mobile node. registrations sent by a mobile node.
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 [RFC- and format of defined options are described in Section 6.2 of
3775]. The local mobility anchor MUST ignore and skip any options [RFC-3775]. The local mobility anchor MUST ignore and skip any
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: valid in a Proxy Binding Update message. There can be only one
instance of each of these options present in the message and in
any order.
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 Interface Identifier option Mobile Node Link-layer Identifier option
Link-local Address option Link-local Address option
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 [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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # | Lifetime | | Sequence # | Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 62, line 42 skipping to change at page 64, line 42
corresponding Proxy Binding Update message supports proxy corresponding Proxy Binding Update message supports proxy
registrations. The flag is set to value of 1 only if the registrations. The flag is set to value of 1 only if the
corresponding Proxy Binding Update had the Proxy Registration Flag corresponding Proxy Binding Update had the Proxy Registration Flag
(P) set to value of 1. (P) set to value of 1.
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 [RFC- and format of defined options are described in Section 6.2 of
3775]. The mobile access gateway MUST ignore and skip any options [RFC-3775]. The mobile access gateway MUST ignore and skip any
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: valid in a Proxy Binding Acknowledgement message. There can be
only one instance of each of these options present in the message
and in any order.
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 Interface Identifier option Mobile Node Link-layer Identifier option
Link-local Address option Link-local Address option
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 [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.
The Home Network Prefix Option has an alignment requirement of 8n+4. The Home Network Prefix Option has an alignment requirement of 8n+4.
skipping to change at page 65, line 33 skipping to change at page 67, line 33
Reserved (R) Reserved (R)
This 8-bit field is unused for now. The value MUST be This 8-bit field is unused for now. The value MUST be
initialized to 0 by the sender and MUST be ignored by the initialized to 0 by the sender and MUST be ignored by the
receiver. receiver.
Handoff Indicator (HI) Handoff Indicator (HI)
A 8-bit field that specifies the type of handoff. The values A 8-bit field that specifies the type of handoff. The values
(0 - 255) will be allocated and managed by IANA. The following (0 - 255) will be allocated and managed by IANA. The following
values are currently reserved. values are currently defined.
0: Reserved 0: Reserved
1: Attachment over a new interface 1: Attachment over a new interface
2: Handoff between two different interfaces of the mobile node 2: Handoff between two different interfaces of the mobile node
3: Handoff between mobile access gateways for the same interface 3: Handoff between mobile access gateways for the same interface
4: Handoff state unknown 4: Handoff state unknown
5: Handoff state not changed (Re-registration) 5: Handoff state not changed (Re-registration)
8.5. Access Technology Type Option 8.5. Access Technology Type Option
skipping to change at page 67, line 5 skipping to change at page 69, line 5
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
1: Virtual 1: Virtual
2: PPP 2: PPP
3: 802.3 (Ethernet) 3: 802.3 (Ethernet)
4: 802.11a/b/g 4: 802.11a/b/g
5: 802.16e 5: 802.16e
8.6. Mobile Node Interface Identifier Option 8.6. Mobile Node Link-layer Identifier Option
A new option, Mobile Node Interface 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 interface identifier. mobile node's link-layer identifier.
The format of the Interface Identifier option when the interface The format of the Link-layer Identifier option is shown below. Based
identifier is 8 bytes is shown below. When the size is different, on the size of the identifier, the option MUST be aligned
the option MUST be aligned appropriately, as per mobility option appropriately, as per mobility option alignment requirements
alignment requirements specified in [RFC-3775]. specified in [RFC-3775].
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 | | Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Interface Identifier + + Link-layer Identifier +
. ... . . ... .
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
<IANA> <IANA>
Length Length
8-bit unsigned integer indicating the length of the option 8-bit unsigned integer indicating the length of the option
in octets, excluding the type and length fields. in octets, excluding the type and length fields.
Reserved Reserved
This field is unused for now. The value MUST be initialized to This field is unused for now. The value MUST be initialized to
0 by the sender and MUST be ignored by the receiver. 0 by the sender and MUST be ignored by the receiver.
Interface Identifier Link-layer Identifier
A variable length field containing the mobile node's interface A variable length field containing the mobile node's link-layer
identifier. identifier.
The content and format of this field (including byte and bit The content and format of this field (including byte and bit
ordering) is as specified in Section 4.6 [RFC-4861] for ordering) is as specified in Section 4.6 of [RFC-4861] for
carrying Link-Layer Address. carrying Link-Layer Address. On certain access links, where
the link-layer address is not used or cannot be determined,
this option cannot be used.
8.7. Link-local Address Option 8.7. Link-local Address Option
A new option, Link-local Address Option is defined for using it in A new option, Link-local Address 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 link- gateway. This option is used for exchanging the link-local address
local address. of the mobile access gateway.
The Link-local Address option has an alignment requirement of 8n+6. The Link-local Address option has an alignment requirement of 8n+6.
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 | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
skipping to change at page 69, line 40 skipping to change at page 71, line 45
indicates the number of seconds since January 1, 1970, 00:00 UTC, indicates the number of seconds since January 1, 1970, 00:00 UTC,
by using a fixed point format. In this format, the integer number by using a fixed point format. In this format, the integer number
of seconds is contained in the first 48 bits of the field, and the of seconds is contained in the first 48 bits of the field, and the
remaining 16 bits indicate the number of 1/65536 fractions of a remaining 16 bits indicate the number of 1/65536 fractions of a
second. second.
8.9. Status Values 8.9. Status Values
This document defines the following new Status values for use in This document defines the following new Status values for use in
Proxy Binding Acknowledgement message. These values are to be Proxy Binding Acknowledgement message. These values are to be
allocated from the same number space, as defined in Section 6.1.8 allocated from the same number space, as defined in Section 6.1.8 of
[RFC-3775]. [RFC-3775].
Status values less than 128 indicate that the Proxy Binding Update Status values less than 128 indicate that the Proxy Binding Update
request was accepted by the local mobility anchor. Status values request was accepted by the local mobility anchor. Status values
greater than 128 indicate that the Proxy Binding Update was rejected greater than 128 indicate that the Proxy Binding Update was rejected
by the local mobility anchor. by the local mobility anchor.
PROXY_REG_NOT_ENABLED: PROXY_REG_NOT_ENABLED: IANA
Proxy registration not enabled for the mobile node Proxy registration not enabled for the mobile node
NOT_LMA_FOR_THIS_MOBILE_NODE: NOT_LMA_FOR_THIS_MOBILE_NODE: IANA
Not local mobility anchor for this mobile node Not local mobility anchor for this mobile node
MAG_NOT_AUTHORIZED_FOR_PROXY_REG: 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 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 the requesting home network
prefix prefix
TIMESTAMP_MISMATCH: 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: 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 MISSING_HOME_NETWORK_PREFIX_OPTION: IANA
Missing home network prefix option Missing home network prefix option
MISSING_MN_IDENTIFIER_OPTION: MISSING_MN_IDENTIFIER_OPTION: IANA
Missing mobile node identifier option Missing mobile node identifier option
MISSING_HANDOFF_INDICATOR_OPTION MISSING_HANDOFF_INDICATOR_OPTION: IANA
Missing handoff indicator option Missing handoff indicator option
MISSING_ACCESS_TECH_TYPE_OPTION MISSING_ACCESS_TECH_TYPE_OPTION: IANA
Missing access technology type option Missing access technology type option
Additionally, the following Status values defined in [RFC-3775] can Additionally, the following Status values defined in [RFC-3775] can
also be used in Proxy Binding Acknowledgement message. also be used in Proxy Binding Acknowledgement message.
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
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. configured by the system management. The configured values for these
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.
During this wait time, if the local mobility anchor receives a During this wait time, if the local mobility anchor receives a
Proxy Binding Update for the same mobility binding, with lifetime Proxy Binding Update for the same mobility binding, with lifetime
value greater than 0, then it must update the binding cache entry value greater than 0, then it must update the binding cache entry
skipping to change at page 72, line 16 skipping to change at page 74, line 20
TimestampValidityWindow TimestampValidityWindow
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.
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. configured by the system management. The configured values for these
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.
The correspondent node can be another visiting mobile node as The correspondent node can be another visiting mobile node as
well, or a local fixed node. well, or a local fixed node.
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
skipping to change at page 72, line 44 skipping to change at page 75, line 4
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.
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, Interface Identifier option, Link-local Address option Type option, Mobile Node Link-layer Identifier option, Link-local
and Timestamp option. These options are described in Section 8. The Address option and Timestamp option. These options are described in
Type value for these options needs to be assigned from the same Section 8. The Type value for these options needs to be assigned
numbering space as allocated for the other mobility options, as from the same numbering space as allocated for the other mobility
defined in [RFC-3775]. options, as defined in [RFC-3775].
The Handoff Indicator option defined in Section 8.4 of this document The Handoff Indicator option defined in Section 8.4 of this document
introduces a new Handoff Indicator (HI) numbering space, where the introduces a new Handoff Indicator (HI) numbering space, where the
values from 0 to 5 have been reserved by this document. Approval of values from 0 to 5 have been reserved by this document. Approval of
new Handoff Indicator type values are to be made through IANA Expert new Handoff Indicator type values are to be made through IANA Expert
Review. Review.
The Access Technology Type option defined in Section 8.5 of this The Access Technology Type option defined in Section 8.5 of this
document introduces a new Access Technology type (ATT) numbering document introduces a new Access Technology type (ATT) numbering
space, where the values from 0 to 5 have been reserved by this space, where the values from 0 to 5 have been reserved by this
document. Approval of new Access Technology type values are to be document. Approval of new Access Technology type values are to be
made through IANA Expert Review. made through IANA Expert Review.
This document also defines new Binding Acknowledgement status values This document also defines new Binding Acknowledgement status values
as described in Section 8.9. The status values MUST be assigned from as described in Section 8.9. The status values MUST be assigned from
the same number space used for Binding Acknowledgement status values, the same number space used for Binding Acknowledgement status values,
as defined in [RFC-3775]. The allocated values for each of these as defined in [RFC-3775]. The allocated values for each of these
status values MUST be greater than 128. status values must be greater than 128.
11. Security Considerations 11. Security Considerations
The potential security threats against any network-based mobility The potential security threats against any network-based mobility
management protocol are described in [RFC-4832]. This section management protocol are described in [RFC-4832]. This section
explains how Proxy Mobile IPv6 protocol defends itself against those explains how Proxy Mobile IPv6 protocol defends itself against those
threats. threats.
Proxy Mobile IPv6 protocol requires the signaling messages, Proxy Proxy Mobile IPv6 protocol requires the signaling messages, Proxy
Binding Update and Proxy Binding Acknowledgement, exchanged between Binding Update and Proxy Binding Acknowledgement, exchanged between
skipping to change at page 74, line 23 skipping to change at page 76, line 29
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 Julien Laganier, Christian
Vogt, Pete McCann, Brian Haley, Ahmad Muhanna, JinHyeock Choi, Jari Vogt, Dave Thaler, Pete McCann, Brian Haley, Ahmad Muhanna, JinHyeock
Arkko and Elwyn Davies for their thorough review of this document. Choi, Jari Arkko and Elwyn Davies for their 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, Marco Liebsch, Mohamed Khalil, Nishida Katsutoshi, Phil
Roberts, Ryuji Wakikawa, Sangjin Jeong, Suresh Krishnan, Uri Roberts, Ryuji Wakikawa, Sangjin Jeong, Suresh Krishnan, Uri
Blumenthal, Ved Kafle, Vidya Narayanan, Youn-Hee Han and many others Blumenthal, Ved Kafle, Vidya Narayanan, Youn-Hee Han and many others
for their passionate discussions in the working group mailing list on for their passionate discussions in the working group mailing list on
the topic of localized mobility management solutions. These the topic of localized mobility management solutions. These
discussions stimulated much of the thinking and shaped the draft to discussions stimulated much of the thinking and shaped the draft to
the current form. We acknowledge that ! 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 75, line 19 skipping to change at page 77, line 26
M.Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", M.Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 3315, July 2003. RFC 3315, July 2003.
[RFC-3775] Johnson, D., Perkins, C., Arkko, J., "Mobility Support in [RFC-3775] Johnson, D., Perkins, C., Arkko, J., "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[RFC-3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. [RFC-3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P.
Thubert, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963, Thubert, "Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
January 2005. January 2005.
[RFC-4140] Soliman, H., Castelluccia, C., El Malki, K., and L.
Bellier, "Hierarchical Mobile IPv6 Mobility Management (HMIPv6)", RFC
4140, August 2005.
[RFC-4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, "The
Network Access Identifier", RFC 4282, December 2005.
[RFC-4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC-4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6", RFC 4283, Chowdhury, "Mobile Node Identifier Option for Mobile IPv6", RFC 4283,
November 2005. November 2005.
[RFC-4291] Hinden, R., Deering, S., "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[RFC-4301] Kent, S. and Atkinson, R., "Security Architecture for the [RFC-4301] Kent, S. and Atkinson, R., "Security Architecture for the
Internet Protocol", RFC 4301, December 2005. Internet Protocol", RFC 4301, December 2005.
[RFC-4303] Kent, S. "IP Encapsulating Security Protocol (ESP)", RFC [RFC-4303] Kent, S. "IP Encapsulating Security Protocol (ESP)", RFC
4303, December 2005. 4303, December 2005.
[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-2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June
2000.
[RFC-3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
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-4140] Soliman, H., Castelluccia, C., El Malki, K., and L.
Bellier, "Hierarchical Mobile IPv6 Mobility Management (HMIPv6)", RFC
4140, August 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-4830] Kempf, J., Leung, K., Roberts, P., Nishida, K., Giaretta, [RFC-4830] Kempf, J., Leung, K., Roberts, P., Nishida, K., Giaretta,
skipping to change at page 76, line 28 skipping to change at page 78, line 52
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.
[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] Kempf, J., et al "Detecting Network Attachment in IPv6 [ID-DNAV6] Narayanan, S., et al "Detecting Network Attachment in IPv6
Networks (DNAv6)", draft-ietf-dna-protocol-06.txt, October 2006. 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, permitted address configuration
modes, roaming policy and other parameters that are essential for modes, roaming policy and other parameters that are essential for
providing network-based mobility service. This information is providing network-based mobility service. This information is
typically configured in AAA. It is possible the home network prefix typically configured in AAA. It is possible the home network prefix
is dynamically allocated for the mobile node when it boots up for the is dynamically allocated for the mobile node when it boots up for the
first time in the network, or it could be a statically configured first time in the network, or it could be a statically configured
value on per mobile node basis. However, for all practical purposes, value on per mobile node basis. However, for all practical purposes,
the network entities in the proxy Mobile IPv6 domain, while serving a the network entities in the proxy Mobile IPv6 domain, while serving a
mobile node will have access to this profile and these entities can mobile node will have access to this profile and these entities can
query this information using RADIUS/DIAMETER protocols. query this information using RADIUS [RFC-2865] or DIAMETER [RFC-3588]
protocols.
Appendix B. Supporting Shared-Prefix Model using DHCPv6
This specification supports Per-MN-Prefix model. However, it is
possible to support Shared-Prefix model under the following
guidelines.
The mobile node is allowed to use stateful address configuration
using DHCPv6 for obtaining its address configuration. The mobile
node is not allowed to use any of the stateless autoconfiguration
techniques. The permitted address configuration models for the
mobile node on the access link can be enforced by the mobile access
gateway, by setting the relevant flags in the Router Advertisements,
as per [RFC-4861].
The Home Network Prefix option that is sent by the mobile access
gateway in the Proxy Binding Update message, must contain the 128-bit
host address that the mobile node obtained via DHCPv6.
Routing state at the mobile access gateway:
For all IPv6 traffic from the source MN-HoA::/128 to
_ANY_DESTINATION_, route via tunnel0, next-hop LMAA, where tunnel0 is
the MAG to LMA tunnel.
Routing state at the local mobility anchor:
For all IPv6 traffic to destination MN-HoA::/128, route via tunnel0,
next-hop Proxy-CoA, where tunnel0 is the LMA to MAG tunnel.
Appendix C. 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 for a mobile node on
the mobile access gateway. This routing state reflects only one the mobile access gateway. This routing state reflects only one
specific way of implementation and one MAY choose to implement it in specific way of implementation and one MAY choose to implement it in
other ways. The policy based route defined below acts as a traffic other ways. The policy based route defined below acts as a traffic
selection rule for routing a mobile node's traffic through a specific selection rule for routing a mobile node's traffic through a specific
tunnel created between the mobile access gateway and that mobile tunnel created between the mobile access gateway and that mobile
node's local mobility anchor and with the specific encapsulation node's local mobility anchor and with the specific encapsulation
mode, as negotiated. mode, as negotiated.
skipping to change at page 78, line 26 skipping to change at page 80, line 24
| Input Interface | Locally Connected | direct | | Input Interface | Locally Connected | direct |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 22: 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 |IPv4-Proxy-CoA | IPv4-LMA2 | IPv6-in-IPv4 | | Tunnel1 | Proxy-CoA | LMAA2 | IPv6-in-IPv6 |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 23: Example - Tunnel Interface Table Figure 23: 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
 End of changes. 221 change blocks. 
710 lines changed or deleted 731 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/