draft-ietf-netlmm-proxymip6-02.txt   draft-ietf-netlmm-proxymip6-03.txt 
NETLMM WG S. Gundavelli NETLMM WG S. Gundavelli
Internet-Draft K. Leung Internet-Draft K. Leung
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: March 7, 2008 V. Devarapalli Expires: March 8, 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
September 4, 2007 September 5, 2007
Proxy Mobile IPv6 Proxy Mobile IPv6
draft-ietf-netlmm-proxymip6-02.txt draft-ietf-netlmm-proxymip6-03.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 March 7, 2008. This Internet-Draft will expire on March 8, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
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
Protocol [RFC-3775]. This protocol enables mobility support to a [RFC-3775]. This protocol enables mobility support to a host without
host within a domain and without requiring its participation in any requiring its participation in any mobility related signaling. The
mobility related signaling. The design principle in the case of design principle in the case of network-based mobility management
network-based mobility management protocol relies on the network protocol relies on the network being in control of the mobility
being in control of the mobility management. management. The mobility entities in the network are responsible for
tracking the movements of the host and initiating the required
mobility signaling on its behalf.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 5 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . . . 8
4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 11 4. Proxy Mobile IPv6 Protocol Security . . . . . . . . . . . . . 11
4.1. Peer Authorization Database Entries . . . . . . . . . . . 12 4.1. Peer Authorization Database Entries . . . . . . . . . . . 12
4.2. Security Policy Database Entries . . . . . . . . . . . . . 13 4.2. Security Policy Database Entries . . . . . . . . . . . . . 13
5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 13 5. Local Mobility Anchor Operation . . . . . . . . . . . . . . . 13
5.1. Extensions to Binding Cache Entry Data Structure . . . . . 14 5.1. Extensions to Binding Cache Entry Data Structure . . . . . 14
5.2. Supported Home Network Prefix Models . . . . . . . . . . . 14 5.2. Supported Home Network Prefix Models . . . . . . . . . . . 14
5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 15 5.3. Signaling Considerations . . . . . . . . . . . . . . . . . 15
5.3.1. Processing Binding Registrations . . . . . . . . . . . 15
5.4. Timestamp Option for Message Ordering . . . . . . . . . . 19 5.4. Timestamp Option for Message Ordering . . . . . . . . . . 19
5.5. Routing Considerations . . . . . . . . . . . . . . . . . . 21 5.5. Routing Considerations . . . . . . . . . . . . . . . . . . 21
5.5.1. Bi-Directional Tunnel Management . . . . . . . . . . . 21 5.5.1. Bi-Directional Tunnel Management . . . . . . . . . . . 21
5.5.2. Forwarding Considerations . . . . . . . . . . . . . . 22 5.5.2. Forwarding Considerations . . . . . . . . . . . . . . 22
5.6. Local Mobility Anchor Address Discovery . . . . . . . . . 23 5.6. Local Mobility Anchor Address Discovery . . . . . . . . . 23
5.7. Mobile Prefix Discovery Considerations . . . . . . . . . . 23 5.7. Mobile Prefix Discovery Considerations . . . . . . . . . . 23
5.8. Route Optimizations Considerations . . . . . . . . . . . . 24 5.8. Route Optimizations Considerations . . . . . . . . . . . . 24
6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 24 6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 24
6.1. Extensions to Binding Update List Entry Data Structure . . 25 6.1. Extensions to Binding Update List Entry Data Structure . . 25
6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 26 6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 26
6.3. Supported Access Link Types . . . . . . . . . . . . . . . 26 6.3. Supported Access Link Types . . . . . . . . . . . . . . . 26
6.4. Supported Address Configuration Models . . . . . . . . . . 26 6.4. Supported Address Configuration Models . . . . . . . . . . 26
6.5. Access Authentication & Mobile Node Identification . . . . 27 6.5. Access Authentication & Mobile Node Identification . . . . 27
6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 27 6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 27
6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 28 6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 28
6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 28 6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 28
6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 30 6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 30
6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 32 6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 33
6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 32 6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 33
6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 32 6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 33
6.10.3. Routing State . . . . . . . . . . . . . . . . . . . . 33 6.10.3. Routing State . . . . . . . . . . . . . . . . . . . . 34
6.10.4. Local Routing . . . . . . . . . . . . . . . . . . . . 34 6.10.4. Local Routing . . . . . . . . . . . . . . . . . . . . 35
6.10.5. Tunnel Management . . . . . . . . . . . . . . . . . . 35 6.10.5. Tunnel Management . . . . . . . . . . . . . . . . . . 36
6.10.6. Forwarding Rules . . . . . . . . . . . . . . . . . . . 35 6.10.6. Forwarding Rules . . . . . . . . . . . . . . . . . . . 36
6.11. Interaction with DHCP Relay Agent . . . . . . . . . . . . 35 6.11. Interaction with DHCP Relay Agent . . . . . . . . . . . . 36
6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 36 6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 37
6.13. Mobile Node Detachment Detection and Resource Cleanup . . 36 6.13. Mobile Node Detachment Detection and Resource Cleanup . . 37
6.14. Allowing network access to other IPv6 nodes . . . . . . . 37 6.14. Allowing network access to other IPv6 nodes . . . . . . . 38
7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 37 7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 38
7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 38 7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 39
7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 39 7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 40
7.3. IPv6 Host Protocol Parameters . . . . . . . . . . . . . . 39 7.3. IPv6 Host Protocol Parameters . . . . . . . . . . . . . . 40
8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 40 8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 41
8.1. Proxy Binding Update . . . . . . . . . . . . . . . . . . . 41 8.1. Proxy Binding Update . . . . . . . . . . . . . . . . . . . 42
8.2. Proxy Binding Acknowledgment . . . . . . . . . . . . . . . 42 8.2. Proxy Binding Acknowledgement . . . . . . . . . . . . . . 43
8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 42 8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 43
8.4. Link-local Address Option . . . . . . . . . . . . . . . . 43 8.4. Link-local Address Option . . . . . . . . . . . . . . . . 44
8.5. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 44 8.5. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 45
8.6. Status Values . . . . . . . . . . . . . . . . . . . . . . 45 8.6. Status Values . . . . . . . . . . . . . . . . . . . . . . 46
9. Protocol Configuration Variables . . . . . . . . . . . . . . . 46 9. Protocol Configuration Variables . . . . . . . . . . . . . . . 47
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
11. Security Considerations . . . . . . . . . . . . . . . . . . . 47 11. Security Considerations . . . . . . . . . . . . . . . . . . . 48
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
13.1. Normative References . . . . . . . . . . . . . . . . . . . 49 13.1. Normative References . . . . . . . . . . . . . . . . . . . 50
13.2. Informative References . . . . . . . . . . . . . . . . . . 50 13.2. Informative References . . . . . . . . . . . . . . . . . . 51
Appendix A. Proxy Mobile IPv6 interactions with AAA Appendix A. Proxy Mobile IPv6 interactions with AAA
Infrastructure . . . . . . . . . . . . . . . . . . . 51 Infrastructure . . . . . . . . . . . . . . . . . . . 52
Appendix B. Supporting Shared-Prefix Model using DHCPv6 . . . . . 51 Appendix B. Supporting Shared-Prefix Model using DHCPv6 . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 53
Intellectual Property and Copyright Statements . . . . . . . . . . 54 Intellectual Property and Copyright Statements . . . . . . . . . . 55
1. Introduction 1. Introduction
Mobile IPv6 [RFC-3775] is the enabler for IPv6 mobility. It requires Mobile IPv6 [RFC-3775] is the enabler for IPv6 mobility. It requires
Mobile IPv6 client functionality in the IPv6 stack of a mobile node. Mobile IPv6 client functionality in the IPv6 stack of a mobile node.
Signaling between the mobile node and home agent enables the creation Signaling between the mobile node and home agent enables the creation
and maintenance of a binding between the mobile node's home address and maintenance of a binding between the mobile node's home address
and care-of-address. Mobile IPv6 has been designed to be an integral and care-of-address. Mobile IPv6 has been designed to be an integral
part of the IPv6 stack in a host. However there exist IPv6 stacks part of the IPv6 stack in a host. However there exist IPv6 stacks
today that do not have Mobile IPv6 functionality and there would today that do not have Mobile IPv6 functionality and there would
skipping to change at page 10, line 40 skipping to change at page 10, line 40
IP Address | | IP Address | |
Configuration | | Configuration | |
| | | | | |
Figure 2: Mobile Node Attachment - Signaling Call Flow Figure 2: Mobile Node Attachment - Signaling Call Flow
For updating the local mobility anchor about the current location of For updating the local mobility anchor about the current location of
the mobile node, the mobile access gateway sends a Proxy Binding the mobile node, the mobile access gateway sends a Proxy Binding
Update message to the mobile node's local mobility anchor. Upon Update message to the mobile node's local mobility anchor. Upon
accepting this Proxy Binding Update message, the local mobility accepting this Proxy Binding Update message, the local mobility
anchor sends a Proxy Binding Acknowledgment message including the anchor sends a Proxy Binding Acknowledgement message including the
mobile node's home network prefix. It also creates the binding cache mobile node's home network prefix. It also creates the binding cache
entry and establishes a bi-directional tunnel to the mobile access entry and establishes a bi-directional tunnel to the mobile access
gateway. gateway.
The mobile access gateway on receiving the Proxy Binding The mobile access gateway on receiving the Proxy Binding
Acknowledgment message sets up a bi-directional tunnel to the local Acknowledgement message sets up a bi-directional tunnel to the local
mobility anchor and sets up the data path for the mobile node's mobility anchor and sets up the data path for the mobile node's
traffic. At this point the mobile access gateway will have all the traffic. At this point the mobile access gateway will have all the
required information for emulating the mobile node's home link. It required information for emulating the mobile node's home link. It
sends Router Advertisement messages to the mobile node on the access sends Router Advertisement messages to the mobile node on the access
link advertising the mobile node's home network prefix as the hosted link advertising the mobile node's home network prefix as the hosted
on-link-prefix. on-link-prefix.
The mobile node on receiving these Router Advertisement messages on The mobile node on receiving these Router Advertisement messages on
the access link will attempt to configure its interface either using the access link will attempt to configure its interface either using
stateful or stateless address configuration modes, based on the modes stateful or stateless address configuration modes, based on the modes
skipping to change at page 11, line 40 skipping to change at page 11, line 40
forwards the packet on the access link to the mobile node. forwards the packet on the access link to the mobile node.
The mobile access gateway typically acts as a default router on the The mobile access gateway typically acts as a default router on the
access link and any packet that the mobile node sends to any access link and any packet that the mobile node sends to any
corresponding node is received by the mobile access gateway and it corresponding node is received by the mobile access gateway and it
forwards the packet to its local mobility anchor through the bi- forwards the packet to its local mobility anchor through the bi-
directional tunnel. The local mobility anchor on the other end of directional tunnel. The local mobility anchor on the other end of
the tunnel, after receiving the packet removes the outer header and the tunnel, after receiving the packet removes the outer header and
routes the packet to the destination. routes the packet to the destination.
After obtaining the address configuration, if the mobile node changes
4. Proxy Mobile IPv6 Protocol Security 4. Proxy Mobile IPv6 Protocol Security
The mobile access gateway and the local mobility anchor MUST support The signaling messages, Proxy Binding Update and Proxy Binding
and SHOULD use IPsec to protect the integrity and authenticity of the Acknowledgement, exchanged between the mobile access gateway and the
signaling messages. The signaling messages, Proxy Binding Update and local mobility anchor MUST be protected using IPsec [RFC-4301] and
Proxy Binding Acknowledgement, exchanged between the mobile access using the established security association between them. The
gateway and the local mobility anchor SHOULD be protected using IPsec security association of the specific mobile node for which the
[RFC-4301] and using the established security association between signaling message is initiated is not required for protecting these
them. The security association of the specific mobile node for which messages.
the signaling message is initiated is not required for protecting
these messages.
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 Acknowledgment 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 IKEv2,
for mutual authentication. for mutual authentication.
Mobile IPv6 specification [RFC-3775] requires the home agent to 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, this is not a messages or sending binding updates. Therefore, this is not a
skipping to change at page 13, line 27 skipping to change at page 13, line 24
entries as long as they provide the required security. 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
gateway is assumed to be mag_address_1, and the address of the local gateway is assumed to be mag_address_1, and the address of the local
mobility anchor is assumed to be lma_address_1. mobility anchor is assumed to be lma_address_1.
mobile access gateway SPD-S: mobile access gateway SPD-S:
- IF local_address = mag_address_1 & - IF local_address = mag_address_1 &
remote_address = lma_address_1 & remote_address = lma_address_1 &
proto = MH & local_mh_type = BU & remote_mh_type = BAck proto = MH & local_mh_type = BU & remote_mh_type = BA
Then use SA ESP transport mode Then use SA ESP transport mode
Initiate using IDi = mag_1 to address lma_1 Initiate using IDi = mag_1 to address lma_1
local mobility anchor SPD-S: local mobility anchor SPD-S:
- IF local_address = lma_address_1 & - IF local_address = lma_address_1 &
remote_address = mag_address_1 & remote_address = mag_address_1 &
proto = MH & local_mh_type = BAck & 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
5. Local Mobility Anchor Operation 5. Local Mobility Anchor Operation
For supporting the Proxy Mobile IPv6 protocol specified in this For supporting the Proxy Mobile IPv6 protocol specified in this
document, the home agent function, specified in [RFC-3775] requires document, the home agent function, specified in [RFC-3775] requires
certain functional modifications and enhancements. The home agent certain functional modifications and enhancements. The home agent
with these modifications and enhanced capabilities for supporting with these modifications and enhanced capabilities for supporting
Proxy Mobile IPv6 protocol is referred to as the local mobility Proxy Mobile IPv6 protocol is referred to as the local mobility
anchor. anchor.
skipping to change at page 15, line 14 skipping to change at page 15, line 14
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-2461] for defending the to perform any proxy ND operations [RFC-2461] for defending the
mobile node's home address on the home link. However, from the mobile node's home address on the home link. However, from the
routing perspective, the home network prefix is topologically routing perspective, the home network prefix is topologically
anchored on the local mobility anchor and is the gateway to that home anchored on the local mobility anchor and is the gateway to that home
network prefix. network prefix.
5.3. Signaling Considerations 5.3. Signaling Considerations
5.3.1. Processing Binding Registrations Processing Binding Registrations
Upon receiving a Proxy Binding Update request from a mobile access Upon receiving a Proxy Binding Update request from a mobile access
gateway on behalf of a mobile node, the local mobility anchor MUST gateway on behalf of a mobile node, the local mobility anchor MUST
process the request as defined in Section 10.3 [RFC-3775], with one process the request as defined in Section 10.3 [RFC-3775], with one
exception that this request is a proxy binding registration request exception that this request is a proxy binding registration request
and hence the following additional considerations must be applied. and hence the following additional considerations must be applied.
o The local mobility anchor MUST observe the rules described in o The local mobility anchor MUST observe the rules described in
Section 9.2 [RFC-3775] when processing Mobility Headers in the Section 9.2 [RFC-3775] when processing Mobility Headers in the
received Proxy Binding Update request. received Proxy Binding Update request.
skipping to change at page 17, line 49 skipping to change at page 17, line 49
(Administratively Prohibited). (Administratively Prohibited).
o Upon accepting a Proxy Binding Update request for extending the o Upon accepting a Proxy Binding Update request for extending the
lifetime of a currently active binding for a mobile node, the lifetime of a currently active binding for a mobile node, the
local mobility anchor MUST update the existing Binding Cache entry local mobility anchor MUST update the existing Binding Cache entry
for this mobile node. Unless there exists an established tunnel for this mobile node. Unless there exists an established tunnel
to the mobile access gateway with the same transport and to the mobile access gateway with the same transport and
encapsulation mode, the local mobility anchor MUST create a tunnel encapsulation mode, the local mobility anchor MUST create a tunnel
to the mobile access gateway, as described in [RFC-2473] and also to the mobile access gateway, as described in [RFC-2473] and also
delete the existing tunnel established with the previous mobile delete the existing tunnel established with the previous mobile
access gateway. It MUST also send a Proxy Binding Acknowledgment access gateway. It MUST also send a Proxy Binding Acknowledgement
message to the mobile access gateway with the Status field set to message to the mobile access gateway with the Status field set to
0 (Proxy Binding Update Accepted). 0 (Proxy Binding Update Accepted).
Binding De-Registration: Binding De-Registration:
o If the received Proxy Binding Update request with the lifetime o If the received Proxy Binding Update request with the lifetime
value of 0, has a Source Address in the IPv6 header, different value of 0, has a Source Address in the IPv6 header, different
from what is present in the Proxy-CoA address field in its Binding from what is present in the Proxy-CoA address field in its Binding
Cache entry, the local mobility anchor MAY either choose to ignore Cache entry, the local mobility anchor MAY either choose to ignore
the request or send a valid Proxy Binding Acknowledgement message the request or send a valid Proxy Binding Acknowledgement message
skipping to change at page 18, line 24 skipping to change at page 18, line 24
o Upon accepting the Proxy Binding Update request for a mobile node, o Upon accepting the Proxy Binding Update request for a mobile node,
with the lifetime value of zero, the local mobility anchor MUST with the lifetime value of zero, the local mobility anchor MUST
wait for MinDelayBeforeBCEDelete [Section 9] amount of time, wait for MinDelayBeforeBCEDelete [Section 9] amount of time,
before it deletes the mobile node's Binding Cache entry. Within before it deletes the mobile node's Binding Cache entry. Within
this wait period, if the local mobility anchor receives a Proxy this wait period, if the local mobility anchor receives a Proxy
Binding Update request message for the same mobile node and from a Binding Update request message for the same mobile node and from a
different mobile access gateway, with the lifetime value of different mobile access gateway, with the lifetime value of
greater than zero, and if that request is accepted, then the greater than zero, and if that request is accepted, then the
Binding Cache entry MUST NOT be deleted, but must be updated with Binding Cache entry MUST NOT be deleted, but must be updated with
the new values. However, the local mobile anchor MUST send the the new values. However, the local mobile anchor MUST send the
Proxy Binding Acknowledgment message, immediately upon accepting Proxy Binding Acknowledgement message, immediately upon accepting
the request. the request.
o Upon accepting the request, the local mobility anchor MUST delete o Upon accepting the request, the local mobility anchor MUST delete
the mobile node's Binding Cache entry and remove the Routing state the mobile node's Binding Cache entry and remove the Routing state
for the mobile node's home network prefix. for the mobile node's home network prefix.
Constructing Proxy Binding Acknowledgement Message Constructing the Proxy Binding Acknowledgement Message
o The local mobility anchor when sending the Proxy Binding o The local mobility anchor when sending the Proxy Binding
Acknowledgment message to the mobile access gateway MUST construct Acknowledgement message to the mobile access gateway MUST
the message as specified below. construct the message as specified below.
IPv6 header (src=LMAA, dst=Proxy-CoA) IPv6 header (src=LMAA, dst=Proxy-CoA)
Mobility header Mobility header
-BA /*P flag is set*/ -BA /*P flag is set*/
Mobility Options Mobility Options
- Home Network Prefix Option - Home Network Prefix Option
- Link-local Address Option (optional) - Link-local Address Option (optional)
- Timestamp Option (optional) - Timestamp Option (optional)
- NAI Option - NAI Option
Proxy Binding Acknowledgment message contents Proxy Binding Acknowledgement message format
o The Source Address field in the IPv6 header of the message SHOULD o The Source Address field in the IPv6 header of the message SHOULD
be set to the destination address of the received Proxy Binding be 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
SHOULD be set to the source address of the received Proxy Binding SHOULD be set to the source address of the received Proxy Binding
Update request. Update request.
o If the Status field is set to a value greater less than 128, i.e. o If the Status field is set to a value greater less than 128, i.e.
if the binding request was rejected, then the prefix value in the if the binding request was rejected, then the prefix value in the
skipping to change at page 19, line 37 skipping to change at page 19, line 37
MUST be copied from the Binding Cache entry. MUST be copied from the Binding Cache entry.
o Considerations from Section 5.4 must be applied for constructing o Considerations from Section 5.4 must be applied for constructing
the Timestamp option. the Timestamp option.
o The identifier in the NAI option MUST be copied from the received o The identifier in the NAI option MUST be copied from the received
Proxy Binding Update request. If the Status field value is set to Proxy Binding Update request. If the Status field value is set to
MISSING_MN_IDENTIFIER_OPTION, the NAI option MUST NOT be present MISSING_MN_IDENTIFIER_OPTION, the NAI option MUST NOT be present
in the reply message. in the reply message.
o The message SHOULD be protected by using IPsec ESP, using the o The message MUST be protected by using IPsec, using the security
security association existing between the local mobility anchor association existing between the local mobility anchor and the
and the mobile access gateway, created either dynamically or mobile access gateway, created either dynamically or statically.
statically.
5.4. Timestamp Option for Message Ordering 5.4. Timestamp Option for Message Ordering
Mobile IPv6 [RFC-3775] uses the Sequence Number field in binding Mobile IPv6 [RFC-3775] uses the Sequence Number field in binding
registration messages as a way for the home agent to process the registration messages as a way for the home agent to process the
binding updates in the order they were sent by a mobile node. The binding updates in the order they were sent by a mobile node. The
home agent and the mobile node are required to manage this counter home agent and the mobile node are required to manage this counter
over the lifetime of a binding. However, in Proxy Mobile IPv6, as over the lifetime of a binding. However, in Proxy Mobile IPv6, as
the mobile node moves from one mobile access gateway to another and the mobile node moves from one mobile access gateway to another and
in the absence of context transfer mechanism, the serving mobile in the absence of context transfer mechanism, the serving mobile
skipping to change at page 20, line 34 skipping to change at page 20, line 33
between the serving mobile access gateways. However, the specific between the serving mobile access gateways. However, the specific
details on how a mobile node's sequence number is synchronized details on how a mobile node's sequence number is synchronized
between different mobile access gateways is outside the scope of this between different mobile access gateways is outside the scope of this
document. document.
Using Timestamps based approach: Using Timestamps based approach:
o An implementation MUST support Timestamp option. If the Timestamp o An implementation MUST support Timestamp option. If the Timestamp
option is present in the received Proxy Binding Update request option is present in the received Proxy Binding Update request
message, then the local mobility anchor MUST include a valid message, then the local mobility anchor MUST include a valid
Timestamp option in the Proxy Binding Acknowledgment message that Timestamp option in the Proxy Binding Acknowledgement message that
it sends to the mobile access gateway. it sends to the mobile access gateway.
o All the mobility entities in a Proxy Mobile IPv6 domain, o All the mobility entities in a Proxy Mobile IPv6 domain,
exchanging binding registration messages using Timestamp option exchanging binding registration messages using Timestamp option
must have adequately synchronized time-of-day clocks. These nodes must have adequately synchronized time-of-day clocks. These nodes
SHOULD synchronize their clocks to a common time source, such as SHOULD synchronize their clocks to a common time source, using
using Network Time Protocol [RFC-1305] or in any other ways Network Time Protocol [RFC-1305] or in any other ways suitable for
suitable for that specific deployment. that specific deployment.
o When generating the timestamp value for building the Timestamp
option, the mobility entities MUST ensure that the generated
timestamp is the elapsed time past the the same reference epoch,
as specified in the format for the Timestamp option.
o Upon receipt of a Proxy Binding Update message with the Timestamp o Upon receipt of a Proxy Binding Update message with the Timestamp
option, the local mobility anchor MUST check the timestamp field option, the local mobility anchor MUST check the timestamp field
for validity. In order for it to be considered valid, the for validity. In order for it to be considered valid, the
timestamp value contained in the Timestamp option MUST be close timestamp value contained in the Timestamp option MUST be close
enough to the local mobility anchor's time-of-day clock and the enough to the local mobility anchor's time-of-day clock and the
timestamp MUST be greater than all previously accepted timestamps timestamp MUST be greater than all previously accepted timestamps
in the Proxy Binding Update messages sent for that mobile node. in the Proxy Binding Update messages sent for that mobile node.
o If the Timestamp option is present in the received Proxy Binding o If the Timestamp option is present in the received Proxy Binding
Update message, the local mobility anchor MUST ignore the sequence 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 the Proxy number from the received Proxy Binding Update message to the Proxy
Binding Acknowledgement message. Binding Acknowledgement message.
o If the timestamp value in the received Proxy Binding Update is o If the timestamp value in the received Proxy Binding Update is
valid, the local mobility anchor MUST return the same timestamp valid, the local mobility anchor MUST return the same timestamp
value in the Timestamp option included in the Proxy Binding value in the Timestamp option included in the Proxy Binding
Acknowledgment message that it sends to the mobile access gateway. Acknowledgement message that it sends to the mobile access
gateway.
o If the timestamp value in the received Proxy Binding Update is not o If the timestamp value in the received Proxy Binding Update is not
valid, the local mobility anchor MUST reject the Proxy Binding valid, the local mobility anchor MUST reject the Proxy Binding
Update and send a Proxy Binding Acknowledgement message with Update and send a Proxy Binding Acknowledgement message with
Status field set to TIMESTAMP_MISMATCH (Timestamp mismatch). The Status 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 Sequence Number based approach:
o If the Timestamp option is not present in the received Proxy o If the Timestamp option is not present in the received Proxy
Binding Update request, the local mobility anchor MUST fallback to Binding Update request, the local mobility anchor MUST fallback to
the Sequence Number based scheme. It MUST process the sequence the Sequence Number based scheme. It MUST process the sequence
number field as specified in [RFC-3775]. Also, it MUST NOT number field as specified in [RFC-3775]. Also, it MUST NOT
include the Timestamp option in the Proxy Binding Acknowledgment include the Timestamp option in the Proxy Binding Acknowledgement
messages that it sends to the mobile access gateway. messages that it sends to the mobile access gateway.
5.5. Routing Considerations 5.5. Routing Considerations
5.5.1. Bi-Directional Tunnel Management 5.5.1. Bi-Directional Tunnel Management
o A bi-directional tunnel is established between the local mobility o A bi-directional tunnel is established between the local mobility
anchor and the mobile access gateway with IP-in-IP encapsulation, anchor and the mobile access gateway with IP-in-IP encapsulation,
as described in [RFC-2473]. The tunnel end points are the Proxy- as described in [RFC-2473]. The tunnel end points are the Proxy-
CoA and LMAA. When using IPv4 transport with a specific CoA and LMAA. When using IPv4 transport with a specific
skipping to change at page 25, line 30 skipping to change at page 25, line 38
document. document.
o The Link-layer address of the mobile node. This address can be o The Link-layer address of the mobile node. This address can be
acquired from the received Router Solicitation messages from the acquired from the received Router Solicitation messages from the
mobile node or during the mobile node's attachment to the access mobile node or during the mobile node's attachment to the access
network. network.
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
Acknowledgment 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. policy profile.
o The interface identifier of the access link where the mobile node o The interface identifier of the access link where the mobile node
skipping to change at page 30, line 7 skipping to change at page 30, line 13
can change its own link-local address, if it detects an address can change its own link-local address, if it detects an address
collision. collision.
This issue is not relevant to the mobile node's global address. This issue is not relevant to the mobile node's global address.
Since, there is a unique home network prefix for each mobile node, Since, there is a unique home network prefix for each mobile node,
the uniqueness for the mobile node's global address is assured on the the uniqueness for the mobile node's global address is assured on the
access link. access link.
6.9. Signaling Considerations 6.9. Signaling Considerations
Initial Attachment and binding registration Initial binding registration
o After detecting a new mobile node on its access link, the mobile o After detecting a new mobile node on its access link, the mobile
access gateway MUST send a Proxy Binding Update message to the access gateway must identify the mobile node and acquire its MN-
mobile node's local mobility anchor. Identifier. If it determines that the network-based mobility
management service needs to offered to the mobile node, it MUST
send a Proxy Binding Update message to the local mobility anchor.
o The Proxy Binding Update message that the mobile access gateway o The Proxy Binding Update message MUST have the NAI option,
sends to the mobile node's local mobility anchor MUST have the NAI identifying the mobile node, the Home Network Prefix option,
option, identifying the mobile node, the Home Network Prefix Timestamp option or a valid sequence number and optionally the
option and optionally the Timestamp option or a valid sequence Link-local Address option.
number.
o If the mobile access gateway learns the mobile node's home network o If the mobile access gateway learns the mobile node's home network
prefix either from its policy store or from other means, the prefix either from its policy store or from other means, the
mobile access gateway MAY choose to specify the same in the Home mobile access gateway MAY choose to specify the same in the Home
Network Prefix option for requesting the local mobility anchor to Network Prefix option for requesting the local mobility anchor to
allocate that prefix. If the specified value is 0::/0, then the allocate that prefix. If the specified value is 0::/0, then the
local mobility anchor will consider this as a request for prefix local mobility anchor will consider this as a request for prefix
allocation. allocation.
o If the mobile access gateway receives a Proxy Binding Receiving binding registration reply
Acknowledgment with the Status field value set to 0 (Proxy Binding
Update accepted), the mobile access gateway MUST create Binding
Update List entry for the mobile node and must setup a tunnel to
the mobile node's local mobility anchor, as explained in section
6.10. The mobile access gateway MUST also add a policy route for
tunneling all the packets that it receives from the mobile node to
its local mobility anchor.
o If the mobile access gateway receives a Proxy Binding o The mobile access gateway MUST observe the rules described in
Acknowledgment with the Status field value greater than 128 Section 9.2 [RFC-3775] when processing Mobility Headers in the
(binding request is rejected), the mobile access gateways MUST NOT received Proxy Binding Acknowledgement message.
advertise the mobile node's home network prefix on the access link
and there by denying mobility service to the mobile node.
Extending the binding lifetime o The message MUST be authenticated as described in Section 4.0.
The SPI in the IPSec header [RFC-4306] of the received packet must
be used for locating the security association needed for
authenticating the message.
o The mobile access gateway MUST apply the considerations specified
in Section 5.4, for processing the Sequence Number field and the
Timestamp option, in the message.
o If the received Proxy Binding Acknowledgement message has the
Status field value set to PROXY_REG_NOT_ENABLED (Proxy
registration not enabled for the mobile node), the mobile access
gateway SHOULD not send binding registration requests again for
that mobile node. It must also deny the mobility service to that
mobile node.
o If the received Proxy Binding Acknowledgement message has the
Status field value set to TIMESTAMP_MISMATCH (Invalid Timestamp),
the mobile access gateway SHOULD try to register again only after
it synchronized its clock with the local mobility anchor's system
clock or to a common time source that is used by all mobility
entities in that domain for their clock synchronization.
o If the received Proxy Binding Acknowledgement message has the
Status field value set to NOT_AUTHORIZED_FOR_HOME_NETWORK_PREFIX
(Not authorized for that prefix), the mobile access gateway SHOULD
try to request for that prefix in the binding registration
request, only after it learned the validity of that prefix.
o If the received Proxy Binding Acknowledgement message has the
Status field value set to any value greater than 128 (i.e., the
binding is rejected), the mobile access gateway MUST NOT advertise
the mobile node's home network prefix in the Router Advertisements
sent on that access link and there by denying mobility service to
the mobile node.
o If the received Proxy Binding Acknowledgement message has the
Status field value set to 0 (Proxy Binding Update accepted), the
mobile access gateway MUST create Binding Update List entry for
the mobile node and must setup a tunnel to the mobile node's local
mobility anchor, as explained in section 6.10.
o If the received Proxy Binding Acknowledgement message has the
address in the Link-local Address option set to a value that
matches its own link-local address on that access interface where
the mobile node is anchored, the mobile access gateway MUST change
its link-local address on that interface.
Binding Re-Registration
o For extending the lifetime of a currently existing binding at the o For extending the lifetime of a currently existing binding at the
local mobility, the mobile access gateway MUST send a Proxy local mobility, the mobile access gateway MUST send a Proxy
Binding Update message, before the expiry of the currently Binding Update message to the local mobility anchor. The prefix
accepted binding. value in the Home Network Prefix option present in the request
SHOULD be set to the currently registered home network prefix and
De-Registration of the binding the value in the Link-local Address option may be set to ALL_ZERO
or to the link-local address of the mobile node.
Binding De-Registration
o At any point, the mobile access gateway detects that the mobile o At any point, the mobile access gateway detects that the mobile
node has moved away from its access link, it MUST send a Proxy node has moved away from its access link, it MUST send a Proxy
Binding Update message to the mobile node's local mobility anchor Binding Update message to the local mobility anchor with the
with the lifetime value set to zero. lifetime value set to zero.
o The mobile access gateway MUST also remove the default route over o Either upon receipt of a Proxy Binding Acknowledgement message
the tunnel for that mobile node and delete the Binding Update List from the local mobility anchor or after a certain timeout waiting
for that mobile node, either upon receiving an Proxy Binding for the reply, the mobile access gateway MUST remove the binding
Acknowledgment message from the local mobility anchor or after a entry for that mobile node from its Binding Update List and
certain timeout waiting for the acknowledgment message. withdraw the mobile node's home network prefix as the hosted on-
link prefix on that access link.
Constructing Proxy Binding Update Message 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 are set*/ -BU /*P & A flags are set*/
Mobility Options Mobility Options
- Home Network Prefix option - Home Network Prefix option
- Link-local Address option (Optional) - Link-local Address option (Optional)
- Timestamp Option (optional) - Timestamp Option (optional)
- NAI Option - NAI Option
Proxy Binding Update message contents Proxy Binding Update message format
o The Source Address field in the IPv6 header of the message SHOULD o The Source Address field in the IPv6 header of the message SHOULD
be set to the address of the mobile access gateway. be set to the address of the mobile access gateway.
o The Destination Address field in the IPv6 header of the message o The Destination Address field in the IPv6 header of the message
SHOULD be set to the local mobility anchor address. SHOULD be set to the local mobility anchor address.
o The Home Network Prefix option MUST be present. The prefix value o The Home Network Prefix option MUST be present. The prefix value
may be set 0::/0 or to a specific value. may be set 0::/0 or to a specific prefix value.
o The Link-local Address option MAY be present. The value may be o The Link-local Address option MAY be present. The value may be
set to ALL_ZERO or the mobile node's link-local address. set to ALL_ZERO or the mobile node's link-local address.
o Considerations from Section 5.4 must be applied for constructing o Considerations from Section 5.4 must be applied for constructing
the Timestamp option. the Timestamp option.
o The NAI option MUST be present, the identifier field in the option o The NAI option MUST be present, the identifier field in the option
MUST be set to mobile node's identifier, MN-Identifier. MUST be set to mobile node's identifier, MN-Identifier.
o The message SHOULD be protected by using IPsec ESP, using the o The message MUST be protected by using IPsec, using the security
security association existing between the local mobility anchor association existing between the local mobility anchor and the
and the mobile access gateway, created either dynamically or mobile access gateway, created either dynamically or statically.
statically.
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. interface.
Proxy-CoA LMAA Proxy-CoA LMAA
| | | |
+--+ +---+ +---+ +--+ +--+ +---+ +---+ +--+
skipping to change at page 33, line 31 skipping to change at page 34, line 33
how this mode is negotiated is specified in the companion how this mode is negotiated is specified in the companion
document, IPv4 support for Proxy Mobile IPv6 [ID-IPV4-PMIP6]. document, IPv4 support for Proxy Mobile IPv6 [ID-IPV4-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. The details related to this mode are covered in the packet. The details related to this mode are covered in the
companion document, IPv4 support for Proxy Mobile IPv6 [ID-IPV4- companion document, IPv4 support for Proxy Mobile IPv6 [ID-IPV4-
PMIP6]. PMIP6].
6.10.3. Routing State 6.10.3. Routing State
The following section explain 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.
The below example identifies the routing state for two visiting The below example identifies the routing state for two visiting
mobile nodes, MN1 and MN2 with their respective local mobility mobile nodes, MN1 and MN2 with their respective local mobility
skipping to change at page 42, line 5 skipping to change at page 43, line 5
A new flag (P) is included in the Binding Update message to indicate A new flag (P) is included in the Binding Update message to indicate
to the local mobility anchor that the Binding Update message is a to the local mobility anchor that the Binding Update message is a
proxy registration. The flag MUST be set to the value of 1 for proxy proxy registration. The flag MUST be set to the value of 1 for proxy
registrations and MUST be set to 0 for direct registrations sent by a registrations and MUST be set to 0 for direct registrations sent by a
mobile node. mobile node.
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 [RFC-3775].
8.2. Proxy Binding Acknowledgment 8.2. Proxy Binding Acknowledgement
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 12: Proxy Binding Acknowledgment Message Figure 12: Proxy Binding Acknowledgement Message
A Binding Acknowledgement message that is sent by a local mobility A Binding Acknowledgement message that is sent by a local mobility
anchor to a mobile access gateway is referred to as the "Proxy anchor to a mobile access gateway is referred to as the "Proxy
Binding Acknowledgement" message. A new flag (P) is included in the Binding Acknowledgement" message. A new flag (P) is included in the
Binding Acknowledgment message. The rest of the Binding Binding Acknowledgement message. The rest of the Binding
Acknowledgment message format remains the same as defined in [RFC- Acknowledgement message format remains the same as defined in [RFC-
3775]. 3775].
Proxy Registration Flag (P) Proxy Registration Flag (P)
A new flag (P) is included in the Binding Acknowledgement message to A new flag (P) is included in the Binding Acknowledgement message to
indicate that the local mobility anchor that processed the indicate that the local mobility anchor that processed the
corresponding Proxy Binding Update message supports proxy corresponding Proxy Binding Update message supports proxy
registrations. The flag is set only if the corresponding Proxy registrations. The flag is set only if the corresponding Proxy
Binding Update had the Proxy Registration Flag (P) set to value of 1. Binding Update had the Proxy Registration Flag (P) set to value of 1.
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 [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 Acknowledgment 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.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 43, line 48 skipping to change at page 44, line 48
Home Network Prefix Home Network Prefix
A sixteen-byte field containing the mobile node's IPv6 Home A sixteen-byte field containing the mobile node's IPv6 Home
Network Prefix. Network Prefix.
Figure 13: Home Network Prefix Option Figure 13: Home Network Prefix Option
8.4. Link-local Address Option 8.4. 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 Acknowledgment 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 mobile node's link-
local address. local address.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 45, line 38 skipping to change at page 46, line 38
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/64K fractions of a remaining 16 bits indicate the number of 1/64K fractions of a
second. second.
Figure 15: Timestamp Option Figure 15: Timestamp Option
8.6. Status Values 8.6. 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 Acknowledgment 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
[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
was processed successfully by the local mobility anchor. Status was processed successfully by the local mobility anchor. Status
values greater than 128 indicate that the Proxy Binding Update was values greater than 128 indicate that the Proxy Binding Update was
rejected by the local mobility anchor. rejected by the local mobility anchor.
PROXY_REG_NOT_ENABLED: PROXY_REG_NOT_ENABLED:
 End of changes. 48 change blocks. 
125 lines changed or deleted 169 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/