draft-ietf-netlmm-proxymip6-14.txt   draft-ietf-netlmm-proxymip6-15.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: November 14, 2008 V. Devarapalli Expires: November 17, 2008 V. Devarapalli
Wichorus Wichorus
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
B. Patil B. Patil
Nokia Siemens Networks Nokia Siemens Networks
May 13, 2008 May 16, 2008
Proxy Mobile IPv6 Proxy Mobile IPv6
draft-ietf-netlmm-proxymip6-14.txt draft-ietf-netlmm-proxymip6-15.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 November 14, 2008. This Internet-Draft will expire on November 17, 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 49 skipping to change at page 2, line 49
5.8. Mobile Prefix Discovery Considerations . . . . . . . . . . 39 5.8. Mobile Prefix Discovery Considerations . . . . . . . . . . 39
5.9. Route Optimization Considerations . . . . . . . . . . . . 39 5.9. Route Optimization Considerations . . . . . . . . . . . . 39
6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 39 6. Mobile Access Gateway Operation . . . . . . . . . . . . . . . 39
6.1. Extensions to Binding Update List Entry Data Structure . . 40 6.1. Extensions to Binding Update List Entry Data Structure . . 40
6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 41 6.2. Mobile Node's Policy Profile . . . . . . . . . . . . . . . 41
6.3. Supported Access Link Types . . . . . . . . . . . . . . . 42 6.3. Supported Access Link Types . . . . . . . . . . . . . . . 42
6.4. Supported Address Configuration Modes . . . . . . . . . . 42 6.4. Supported Address Configuration Modes . . . . . . . . . . 42
6.5. Access Authentication & Mobile Node Identification . . . . 43 6.5. Access Authentication & Mobile Node Identification . . . . 43
6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 43 6.6. Acquiring Mobile Node's Identifier . . . . . . . . . . . . 43
6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 44 6.7. Home Network Emulation . . . . . . . . . . . . . . . . . . 44
6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 44 6.8. Link-Local and Global Address Uniqueness . . . . . . . . . 45
6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 45 6.9. Signaling Considerations . . . . . . . . . . . . . . . . . 46
6.9.1. Binding Registrations . . . . . . . . . . . . . . . . 45 6.9.1. Binding Registrations . . . . . . . . . . . . . . . . 46
6.9.2. Router Solicitation Messages . . . . . . . . . . . . . 54 6.9.2. Router Solicitation Messages . . . . . . . . . . . . . 54
6.9.3. Default-Router . . . . . . . . . . . . . . . . . . . . 55 6.9.3. Default-Router . . . . . . . . . . . . . . . . . . . . 55
6.9.4. Retransmissions and Rate Limiting . . . . . . . . . . 55 6.9.4. Retransmissions and Rate Limiting . . . . . . . . . . 56
6.9.5. Path MTU Discovery . . . . . . . . . . . . . . . . . . 56 6.9.5. Path MTU Discovery . . . . . . . . . . . . . . . . . . 56
6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 57 6.10. Routing Considerations . . . . . . . . . . . . . . . . . . 57
6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 57 6.10.1. Transport Network . . . . . . . . . . . . . . . . . . 58
6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 58 6.10.2. Tunneling & Encapsulation Modes . . . . . . . . . . . 58
6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . . 59 6.10.3. Local Routing . . . . . . . . . . . . . . . . . . . . 59
6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . . 59 6.10.4. Tunnel Management . . . . . . . . . . . . . . . . . . 59
6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . . 59 6.10.5. Forwarding Rules . . . . . . . . . . . . . . . . . . . 59
6.11. Supporting DHCPv6 based Address Configuration on the 6.11. Supporting DHCPv6 based Address Configuration on the
Access Link . . . . . . . . . . . . . . . . . . . . . . . 61 Access Link . . . . . . . . . . . . . . . . . . . . . . . 61
6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 62 6.12. Home Network Prefix Renumbering . . . . . . . . . . . . . 63
6.13. Mobile Node Detachment Detection and Resource Cleanup . . 63 6.13. Mobile Node Detachment Detection and Resource Cleanup . . 63
6.14. Allowing network access to other IPv6 nodes . . . . . . . 63 6.14. Allowing network access to other IPv6 nodes . . . . . . . 64
7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 64 7. Mobile Node Operation . . . . . . . . . . . . . . . . . . . . 64
7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 64 7.1. Moving into a Proxy Mobile IPv6 Domain . . . . . . . . . . 64
7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 65 7.2. Roaming in the Proxy Mobile IPv6 Domain . . . . . . . . . 65
8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 65 8. Message Formats . . . . . . . . . . . . . . . . . . . . . . . 66
8.1. Proxy Binding Update Message . . . . . . . . . . . . . . . 66 8.1. Proxy Binding Update Message . . . . . . . . . . . . . . . 66
8.2. Proxy Binding Acknowledgement Message . . . . . . . . . . 67 8.2. Proxy Binding Acknowledgement Message . . . . . . . . . . 68
8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 69 8.3. Home Network Prefix Option . . . . . . . . . . . . . . . . 69
8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . . 70 8.4. Handoff Indicator Option . . . . . . . . . . . . . . . . . 70
8.5. Access Technology Type Option . . . . . . . . . . . . . . 71 8.5. Access Technology Type Option . . . . . . . . . . . . . . 71
8.6. Mobile Node Link-layer Identifier Option . . . . . . . . . 73 8.6. Mobile Node Link-layer Identifier Option . . . . . . . . . 73
8.7. Link-local Address Option . . . . . . . . . . . . . . . . 74 8.7. Link-local Address Option . . . . . . . . . . . . . . . . 74
8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 75 8.8. Timestamp Option . . . . . . . . . . . . . . . . . . . . . 75
8.9. Status Values . . . . . . . . . . . . . . . . . . . . . . 75 8.9. Status Values . . . . . . . . . . . . . . . . . . . . . . 75
9. Protocol Configuration Variables . . . . . . . . . . . . . . . 77 9. Protocol Configuration Variables . . . . . . . . . . . . . . . 77
9.1. Local Mobility Anchor - Configuration Variables . . . . . 77 9.1. Local Mobility Anchor - Configuration Variables . . . . . 77
9.2. Mobile Access Gateway - Configuration Variables . . . . . 78 9.2. Mobile Access Gateway - Configuration Variables . . . . . 78
9.3. Proxy Mobile IPv6 Domain - Configuration Variables . . . . 79 9.3. Proxy Mobile IPv6 Domain - Configuration Variables . . . . 79
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 79 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 79
11. Security Considerations . . . . . . . . . . . . . . . . . . . 80 11. Security Considerations . . . . . . . . . . . . . . . . . . . 80
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 81 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 81
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 81 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 81
13.1. Normative References . . . . . . . . . . . . . . . . . . . 81 13.1. Normative References . . . . . . . . . . . . . . . . . . . 82
13.2. Informative References . . . . . . . . . . . . . . . . . . 82 13.2. Informative References . . . . . . . . . . . . . . . . . . 82
Appendix A. Proxy Mobile IPv6 interactions with AAA Appendix A. Proxy Mobile IPv6 interactions with AAA
Infrastructure . . . . . . . . . . . . . . . . . . . 84 Infrastructure . . . . . . . . . . . . . . . . . . . 84
Appendix B. Routing State . . . . . . . . . . . . . . . . . . . . 84 Appendix B. Routing State . . . . . . . . . . . . . . . . . . . . 84
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 85
Intellectual Property and Copyright Statements . . . . . . . . . . 87 Intellectual Property and Copyright Statements . . . . . . . . . . 87
1. Introduction 1. Introduction
IP mobility for IPv6 hosts is specified in Mobile IPv6 [RFC-3775]. IP mobility for IPv6 hosts is specified in Mobile IPv6 [RFC-3775].
skipping to change at page 42, line 20 skipping to change at page 42, line 20
they all are part of one mobility session. they all are part of one mobility session.
o Supported address configuration procedures (Stateful, Stateless or o Supported address configuration procedures (Stateful, Stateless or
both) for the mobile node in the Proxy Mobile IPv6 domain both) for the mobile node in the Proxy Mobile IPv6 domain
6.3. Supported Access Link Types 6.3. Supported Access Link Types
This specification supports only point-to-point access link types and This specification supports only point-to-point access link types and
thus it assumes that the mobile node and the mobile access gateway thus it assumes that the mobile node and the mobile access gateway
are the only two nodes on the access link. The link is assumed to are the only two nodes on the access link. The link is assumed to
have multicast capability. This protocol may also be used on other have multicast capability.
link types, as long as the link is configured in such a way that it
emulates point-to-point delivery between the mobile node and the This protocol may also be used on other link types, as long as the
mobile access gateway for all the protocol traffic. link is configured in such a way that it emulates point-to-point
delivery between the mobile node and the mobile access gateway for
all the protocol traffic.
It is also necessary to be able to identify mobile nodes attaching to
the link. Requirements relating to this are covered in Section 6.6.
Finally, while this specification can operate without link layer
indications of node attachment and detachment to the link, the
existence of such indications either on the network or mobile node
side improves the resulting performance.
6.4. Supported Address Configuration Modes 6.4. Supported Address Configuration Modes
A mobile node in the Proxy Mobile IPv6 domain can configure one or A mobile node in the Proxy Mobile IPv6 domain can configure one or
more global IPv6 addresses on its interface (using Stateless, more global IPv6 addresses on its interface (using Stateless,
Stateful or manual address autoconfiguration procedures) from the Stateful or manual address autoconfiguration procedures) from the
hosted prefix(es) on that link. The Router Advertisement messages hosted prefix(es) on that link. The Router Advertisement messages
sent on the access link specify the address configuration methods sent on the access link specify the address configuration methods
permitted on that access link for that mobile node. However, the permitted on that access link for that mobile node. However, the
advertised flags with respect to the address configuration will be advertised flags with respect to the address configuration will be
skipping to change at page 61, line 15 skipping to change at page 61, line 21
IPv6 header (src= Proxy-CoA, dst= LMAA /* Tunnel Header */ IPv6 header (src= Proxy-CoA, dst= LMAA /* Tunnel Header */
ESP Header in tunnel mode /* ESP Header */ ESP Header in tunnel mode /* ESP 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 15: Tunneled Packet from MAG to LMA with Payload Protection Figure 15: Tunneled Packet from MAG to LMA with Payload Protection
6.11. Supporting DHCPv6 based Address Configuration on the Access Link 6.11. Supporting DHCPv6 based Address Configuration on the Access Link
This section explains how Stateful Address Configuration using DHCPv6 This section explains how Stateful Address Configuration using DHCPv6
can be enabled on the point-to-point link between the mobile node and support can be enabled in a Proxy Mobile IPv6 domain. It also
the mobile access gateway and how a mobile node attached to that link identifies the required configuration in DHCP and mobility
can obtain an address from its home network prefix and using DHCPv6. infrastructures for supporting this address configuration mode and
also identifies the protocol interactions between these two systems.
o For supporting Stateful Address Configuration using DHCPv6, the o For supporting Stateful Address Configuration using DHCP, the DHCP
DHCPv6 relay agent [RFC-3315] service MUST be configured on each relay agent [RFC-3315] service MUST be configured on all the
of the mobile access gateways in the Proxy Mobile IPv6 domain. mobile access gateways in the Proxy Mobile IPv6 domain. Further,
Further, as specified in Section 20 of [RFC-3315], the DHCPv6 as specified in Section 20 of [RFC-3315], the DHCP relay agent
relay agent should be configured to use a list of destination should be configured to use a list of destination addresses, which
addresses, which MAY include unicast addresses, the MAY include unicast addresses, the All_DHCP_Servers multicast
All_DHCP_Servers multicast address, or other addresses selected by address, or other addresses as required in a given deployment.
the network administrator.
o The DHCPv6 server in the Proxy Mobile IPv6 domain MUST be o The DHCP infrastructure needs to be configured with different IPv6
configured with prefix groups, One Prefix Group: ([P1], [P2], .. , prefix groups, each group MUST represent a link in that Proxy
[Pn]), Two Prefix Group: ([P5,P6], [P7,P8] .. [Pm-1, Pm]. Each Mobile IPv6 domain on which those respective prefixes are hosted.
of the entries represent a link on which the prefix(es) are In essence the DHCP infrastructure is aware of all the links in
hosted. The local mobility anchor(s) will assign all the that domain along with the associated IPv6 prefixes with each one
prefix(es) under a given entry to a mobile node's interface. The of those links. This configuration requirement is identical to
prefixes under a given entry always go as a group and cannot be the fixed infrastructure configuration except with the key
mixed in any order and can only be assigned to only one mobile difference that these links are mobile in nature, a link along
node's interface. If the Proxy Mobile IPv6 domain support only with its prefixes associated with a given mobile node and a mobile
single prefix for a given mobile node's interface, then the DHCPv6 access gateway pair at a point of time may be associated with a
server need to maintain just one group of single prefixes. different mobile access gateway and mobile node pair at a later
point of time. However, from the perspective of the DHCP server,
this aspect of prefix mobility will not be visible to it.
o The DHCPv6 server will not know the relation between the o The local mobility anchor needs to have the same awareness with
prefix(es) listed under an entry and a mobile node to which the respect to the links along with the associated prefixes in a Proxy
corresponding prefixes are allocated. It just views these Mobile IPv6 domain. When a local mobilty anchor assigns
prefixes as hosted prefixes on a given link in that domain. Based prefix(es) to a mobile node, it MUST assign all the prefixes
on the prefix value present in the link-address option of the associated with a given link and all of those assigned prefixes
received DHCPv6 request, the DHCPv6 server assigns addresses from will remain as the home network prefixes for that mobile node
all of the prefixes associated with that link, through out the life of that mobility session. The serving mobile
access gateway that hosts these prefixes is physically connected
to that link and can function as the DHCP relay agent. This
common understanding between DHCP and mobility entities about all
the links in the domain along with the associated prefixes,
provides the required coordination for allowing mobility entities
to perform prefix assignment dynamically to a mobile node and
still allowing DHCP infrastructure to perform address assignment
for that mobile node only from its home network prefixes.
o When a mobile node sends a DHCPv6 request message, the DHCPv6 o When a mobile node sends a DHCP request message, the DHCP relay
relay agent function on the mobile access gateway will set the agent function on the mobile access gateway will set the link-
link-address field in the DHCPv6 message to an address in the address field in the DHCP message to an address in the mobile
mobile node's home network prefix (any one of the mobile node's node's home network prefix (any one of the mobile node's home
home network prefixes assigned to that mobile node's attached network prefixes assigned to that mobile node's attached
interface). The address is generated as per [RFC-4862] by interface). The address can be generated as per [RFC-4862] by
combining that mobile node's home network prefix and its own combining that mobile node's home network prefix and its own
interface identifier on the access link shared with the mobile interface identifier on that access link shared with the mobile
node, so as to provide a hint to the DHCPv6 Server for the link node, so as to provide a hint to the DHCP Server for the link
identification. The DHCPv6 server on receiving the request from identification. The DHCP server on receiving the request from the
the mobile node, will allocate address(es) from the prefixes mobile node, will allocate addresses from all the prefixes
associated with that link (identified using the link-address field associated with that link (identified using the link-address field
of the request). of the request).
o Once the mobile node obtains address(es) and moves to a different o Once the mobile node obtains address(es) and moves to a different
link and sends a DHCPv6 request (at any time) for extending the link and sends a DHCP request (at any time) for extending the DHCP
DHCP lease, the DHCPv6 relay agent on the new link will set the lease, the DHCP relay agent on the new link will set the prefix
prefix hint in the DHCPv6 message to one of the mobile node's home hint in the DHCP message to one of the mobile node's home network
network prefix (assigned by the local mobility anchor for this prefixes. The DHCP server will identify the client from the
mobility session). The DHCPv6 server will identify the client Client-DUID option and will identify the link from the link-
from the Client-DUID option present in the request and will address option present in the request and will allocate the same
allocate the same address(es) as before. address(es) as before.
o The DHCPv6 based address configuration is not recommended for o The DHCP 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 gateway are located in different administrative domains. For this
this configuration to work, all the mobile access gateways in the configuration to work, all the mobile access gateways in the Proxy
Proxy Mobile IPv6 domain should be able to ensure that the DHCPv6 Mobile IPv6 domain should be able to ensure that the DHCP request
request messages from a given mobile node anchored on any of the messages from a given mobile node anchored on any of the access
access links in that domain, will always be handled by the same links in that domain, will always be handled by the same DHCP
DHCPv6 server or by a server from the same group of coordinated server or by a server from the same group of coordinated DHCP
DHCPv6 servers serving that domain. servers serving that domain.
o The DHCPv6 server should be configured to offer low address lease o The DHCP infrastructure should be configured to offer low address
times. A lease time that is too large prevents the DHCPv6 server lease reclaiming the address even after the local mobility anchor
from reclaiming the address even after the local mobility anchor
deletes the mobile node's binding cache entry. It is recommended deletes the mobile node's binding cache entry. It is recommended
that the configured lease time be lower than the accepted binding that the configured lease time be lower than the accepted binding
lifetime for any mobility binding. lifetime for any mobility binding.
6.12. Home Network Prefix Renumbering 6.12. Home Network Prefix Renumbering
If the mobile node's home network prefix(es) gets renumbered or If the mobile node's home network prefix(es) gets renumbered or
becomes invalid during the middle of a mobility session, the mobile becomes invalid during the middle of a mobility session, the mobile
access gateway MUST withdraw the prefix(es) by sending a Router access gateway MUST withdraw the prefix(es) by sending a Router
Advertisement message on the access link with zero prefix lifetime Advertisement message on the access link with zero prefix lifetime
skipping to change at page 64, line 49 skipping to change at page 65, line 19
Solicitation message with a Router Advertisement message. The Router Solicitation message with a Router Advertisement message. The Router
Advertisement message will carry the mobile node's home network Advertisement message will carry the mobile node's home network
prefix(es), default-router address and other address configuration prefix(es), default-router address and other address configuration
Parameters. Parameters.
If the mobile access gateway on the access link receives a Router If the mobile access gateway on the access link receives a Router
Solicitation message from the mobile node, before it completes the Solicitation message from the mobile node, before it completes the
signaling with the mobile node's local mobility anchor, the mobile signaling with the mobile node's local mobility anchor, the mobile
access gateway may not know the mobile node's home network prefix(es) access gateway may not know the mobile node's home network prefix(es)
and may not be able to emulate the mobile node's home link on the and may not be able to emulate the mobile node's home link on the
access link. In such a scenario, the mobile node may notice a slight access link. In such a scenario, the mobile node may notice a delay
delay before it receives a Router Advertisement message. before it receives a Router Advertisement message. This will also
affect mobile nodes that would be capable of handling their own
mobility, or mobile nodes that do not need to maintain the same IP
address through movements.
If the received Router Advertisement message has the Managed Address If the received Router Advertisement message has the Managed Address
Configuration flag set, the mobile node, as it would normally do, Configuration flag set, the mobile node, as it would normally do,
will send a DHCPv6 Request [RFC-3315]. The DHCP relay service will send a DHCPv6 Request [RFC-3315]. The DHCP relay service
enabled on that access link will ensure the mobile node can obtain enabled on that access link will ensure the mobile node can obtain
one or more addresses and from its home network prefix(es). one or more addresses and from its home network prefix(es).
If the received Router Advertisement message does not have the If the received Router Advertisement message does not have the
Managed Address Configuration flag set and if the mobile node is Managed Address Configuration flag set and if the mobile node is
allowed to use autoconfigured address(es), the mobile node will be allowed to use autoconfigured address(es), the mobile node will be
skipping to change at page 81, line 32 skipping to change at page 81, line 32
Laganier, Christian Vogt, Dave Thaler, Pasi Eronen, Pete McCann, Laganier, Christian Vogt, Dave Thaler, Pasi Eronen, Pete McCann,
Brian Haley, Ahmad Muhanna, JinHyeock Choi and Elwyn Davies for their Brian Haley, Ahmad Muhanna, JinHyeock Choi and Elwyn Davies for their
thorough review of this document. thorough review of this document.
The authors would also like to thank Alex Petrescu, Alice Qinxia, The authors would also like to thank Alex Petrescu, Alice Qinxia,
Alper Yegin, Ashutosh Dutta, Behcet Sarikaya, Fred Templin, Genadi Alper Yegin, Ashutosh Dutta, Behcet Sarikaya, Fred Templin, Genadi
Velev, George Tsirtsis, Gerardo Giaretta, Henrik Levkowetz, Hesham Velev, George Tsirtsis, Gerardo Giaretta, Henrik Levkowetz, Hesham
Soliman, James Kempf, Jean-Michel Combes, Jun Awano, John Zhao, Jong- Soliman, James Kempf, Jean-Michel Combes, Jun Awano, John Zhao, Jong-
Hyouk Lee, Jonne Soininen, Jouni Korhonen, Kalin Getov, Kilian Hyouk Lee, Jonne Soininen, Jouni Korhonen, Kalin Getov, Kilian
Weniger, Lars Eggert, Magnus Westerlund, Marco Liebsch, Mohamed Weniger, Lars Eggert, Magnus Westerlund, Marco Liebsch, Mohamed
Khalil, Nishida Katsutoshi, Phil Roberts, Ryuji Wakikawa, Sangjin Khalil, Nishida Katsutoshi, Phil Roberts, Ralph Droms, Ryuji
Jeong, Suresh Krishnan, Uri Blumenthal, Ved Kafle, Vidya Narayanan, Wakikawa, Sangjin Jeong, Suresh Krishnan, Uri Blumenthal, Ved Kafle,
Youn-Hee Han and many others for their passionate discussions in the Vidya Narayanan, Youn-Hee Han and many others for their passionate
working group mailing list on the topic of localized mobility discussions in the working group mailing list on the topic of
management solutions. These discussions stimulated much of the localized mobility management solutions. These discussions
thinking and shaped the draft to the current form and we acknowledge stimulated much of the thinking and shaped the draft to the current
that ! 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, Tim
Tim Stammers for their input on this document. Stammers, Bernie Volz and Josh Littlefield 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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2473] Conta, A. and S. Deering, "Generic Packet Tunneling in [RFC-2473] Conta, A. and S. Deering, "Generic Packet Tunneling in
IPv6 Specification", RFC 2473, December 1998. IPv6 Specification", RFC 2473, December 1998.
skipping to change at page 82, line 19 skipping to change at page 82, line 24
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 [RFC-4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, "The
Network Access Identifier", RFC 4282, December 2005. 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 [RFC-4291] Hinden, R., Deering, S., "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
skipping to change at page 82, line 45 skipping to change at page 82, line 46
[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
51, RFC 1661, July 1994.
[RFC-1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery [RFC-1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery
for IP version 6", RFC 1981, August 1996. for IP version 6", RFC 1981, August 1996.
[RFC-2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC-2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June
2000. 2000.
[RFC-3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC-3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC-3971] Arkko, J., Ed., Kempf, J., Sommerfeld, B., Zill, B., and [RFC-3971] Arkko, J., Ed., Kempf, J., Sommerfeld, B., Zill, B., and
P. Nikander, "SEcure Neighbor Discovery (SEND)", RFC 3971, March P. Nikander, "SEcure Neighbor Discovery (SEND)", RFC 3971, March
2005. 2005.
[RFC-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-4821] Mathis, M. and Heffner, J., "Packetization Layer Path MTU [RFC-4821] Mathis, M. and Heffner, J., "Packetization Layer Path MTU
 End of changes. 29 change blocks. 
93 lines changed or deleted 113 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/