draft-ietf-netlmm-pmip6-ipv4-support-00.txt   draft-ietf-netlmm-pmip6-ipv4-support-01.txt 
NETLMM Working Group R. Wakikawa NETLMM Working Group R. Wakikawa
Internet-Draft Keio University Internet-Draft Keio University
Intended status: Standards Track S. Gundavelli Intended status: Standards Track S. Gundavelli
Expires: November 2, 2007 Cisco Expires: January 10, 2008 Cisco
July 9, 2007
IPv4 Support for Proxy Mobile IPv6 IPv4 Support for Proxy Mobile IPv6
draft-ietf-netlmm-pmip6-ipv4-support-00.txt draft-ietf-netlmm-pmip6-ipv4-support-01.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 33 skipping to change at page 1, line 35
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 2, 2007. This Internet-Draft will expire on January 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies extensions to the Proxy Mobile IPv6 protocol This document specifies extensions to the Proxy Mobile IPv6 protocol
[ID-PMIP6] for supporting IPv4. The scope of the IPv4 support in [ID-PMIP6] for supporting IPv4. The scope of the IPv4 support in
Proxy Mobile IPv6 includes the support for the mobile node's IPv4 Proxy Mobile IPv6 includes the support for the mobile node's IPv4
skipping to change at page 2, line 28 skipping to change at page 2, line 28
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 6 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 6
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 6 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 6
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
3. IPv4 Home Address Mobility Support . . . . . . . . . . . . . . 7 3. IPv4 Home Address Mobility Support . . . . . . . . . . . . . . 7
3.1. IPv4 Home Address Assignment . . . . . . . . . . . . . . . 7 3.1. IPv4 Home Address Assignment . . . . . . . . . . . . . . . 7
3.2. Extensions to Conceptual Data Structure . . . . . . . . . 9 3.2. Extensions to Conceptual Data Structure . . . . . . . . . 9
3.3. Mobility Options . . . . . . . . . . . . . . . . . . . . . 9 3.3. Mobility Options . . . . . . . . . . . . . . . . . . . . . 9
3.4. Mobile Access Gateway Operation . . . . . . . . . . . . . 10 3.4. Mobile Access Gateway Operation . . . . . . . . . . . . . 9
3.5. Local Mobility Anchor Operation . . . . . . . . . . . . . 11 3.5. Local Mobility Anchor Operation . . . . . . . . . . . . . 11
4. IPv4 Transport Support . . . . . . . . . . . . . . . . . . . . 13 4. IPv4 Transport Support . . . . . . . . . . . . . . . . . . . . 13
4.1. Mobility Options . . . . . . . . . . . . . . . . . . . . . 13 4.1. Mobility Options . . . . . . . . . . . . . . . . . . . . . 13
4.2. Extensions to Conceptual Data Structure . . . . . . . . . 13 4.2. Extensions to Conceptual Data Structure . . . . . . . . . 13
4.3. NAT Detection . . . . . . . . . . . . . . . . . . . . . . 14 4.3. NAT Detection . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Mobile Access Gateway Operation . . . . . . . . . . . . . 14 4.4. Mobile Access Gateway Operation . . . . . . . . . . . . . 14
4.5. Local Mobility Anchor Operation . . . . . . . . . . . . . 16 4.5. Local Mobility Anchor Operation . . . . . . . . . . . . . 16
4.6. Tunnel Management . . . . . . . . . . . . . . . . . . . . 18 4.6. Tunnel Management . . . . . . . . . . . . . . . . . . . . 18
skipping to change at page 4, line 14 skipping to change at page 4, line 14
1. Overview 1. Overview
The transition from IPv4 to IPv6 is a long process and during this The transition from IPv4 to IPv6 is a long process and during this
period of transition, both the protocols will be enabled over the period of transition, both the protocols will be enabled over the
same infrastructure. Thus, it is reasonable to assume that the same infrastructure. Thus, it is reasonable to assume that the
mobile node, mobile access gateway and the local mobility anchor are mobile node, mobile access gateway and the local mobility anchor are
both IPv4 and IPv6 enabled and further it is also reasonable to both IPv4 and IPv6 enabled and further it is also reasonable to
expect the same mobility infrastructure to provide both IPv4 and IPv6 expect the same mobility infrastructure to provide both IPv4 and IPv6
address mobility for a mobile node. The motivation and scope of IPv4 address mobility for a mobile node. The motivation and scope of IPv4
support in Mobile IPv6 is summraized in [ID-DSMIP6-PS]. support in Mobile IPv6 is summarized in [ID-DSMIP6-PS].
The Proxy Mobile IPv6 base specification [ID-PMIP6] defines a The Proxy Mobile IPv6 base specification [ID-PMIP6] defines a
network-based mobility management protocol. The protocol specifies a network-based mobility management protocol. The protocol specifies a
solution for providing IPv6 home address mobility for a mobile node solution for providing IPv6 home address mobility for a mobile node
and over an IPv6 transport network separating the entities involved and over an IPv6 transport network separating the entities involved
in the mobility management. The extensions defined in this document in the mobility management. This specification defines extensions to
are for extending IPv4 support to the Proxy Mobile IPv6 protocol [ID- the Proxy Mobile IPv6 protocol for supporting IPv4. The scope of
PMIP6]. these IPv4 related extensions are the following:
The scope of these efforts include the support for the following:
o IPv4 Home Address Mobility: A mobile node operating in IPv4-only o IPv4 Home Address Mobility: A mobile node operating in IPv4-only
mode or in a dual-stack mode should be able to obtain an IPv4 home mode or in a dual-stack mode should be able to obtain an IPv4 home
address and roam anywhere in that Proxy Mobile IPv6 domain. address and roam anywhere in that Proxy Mobile IPv6 domain.
o IPv4 Transport Network Support: The transport network between the o IPv4 Transport Network Support: The transport network between the
local mobility anchor and the mobile access gateway is an IPv4 local mobility anchor and the mobile access gateway is an IPv4
network and further the local mobility anchor or the mobile access network and further the local mobility anchor or the mobile access
gateway may be using IPv4 private addresses and with NAT gateway may be using IPv4 private addresses and with NAT
translation devices on the path translation devices on the path
The DSMIP6 specification [ID-DSMIP6], extends IPv4 home address The Dual-Stack Mobile IPv6 specification [ID-DSMIP6], extends IPv4
mobility and IPv4 transport network support to the Mobile IPv6 home address mobility and IPv4 transport network support to the
protocol [RFC-3775]. The solution specified in this document Mobile IPv6 protocol [RFC-3775]. The solution specified in this
leverages the DSMIP6 work and extends the IPv4 feature to the Proxy document leverages the DSMIP6 extensions for extending IPv4 support
Mobile IPv6 protocol. The protocol semantics, processing logic and to Proxy Mobile IPv6 protocol. The protocol semantics, processing
mobility header options, such as IPv4 home address option, IPv4 logic and mobility header options, such as IPv4 home address option,
address acknowledgment option and NAT detection option, defined in IPv4 address acknowledgment option and NAT detection option, defined
the DSMIP6 specification, are all applied for Proxy Mobile IPv6 in the DSMIP6 specification, are all applied for Proxy Mobile IPv6
protocol. As specified in DSMIPv6, these two features, IPv4 Home protocol. As specified in DSMIPv6, these two features, IPv4 Home
Address Mobility support and IPv4 transport support, are independent Address Mobility support and IPv4 transport support, are independent
of each other and implementors may choose to implement any one or of each other and implementers may choose to implement any one or
both of these features. Since this specification also inherits Proxy both of these features. Unlike in DSMIP6, a mobile node in Proxy
Mobile IPv6 [ID-PMIP6], only point to point link is assumed between a Mobile domain is NOT required to have an IPv6 home address for
mobile node and a mobile access gateway. obtaining IPv4 home address mobility.
This specification assumes that the local mobility anchor and the As specified in the Proxy Mobile IPv6 specification [ID-PMIP6], this
mobile access gateway are both IPv6 capabled and IPv6 enabled, specification assumes that the link between the mobile access gateway
irrespective of the type of transport network (IPv4 or IPv6), and the local mobility anchor is a point-to-point link. This
connecting these two entities. The signaling protocol is specification also assumes that the local mobility anchor and the
fundamentally based on Mobile IPv6 in this document. mobile access gateway are both IPv6 capable and IPv6 enabled and even
when the network between the mobile access gateway and a local
mobility anchor is IPv4-only network. The signaling protocol is
primarily based on Mobile IPv6 and hence the entities providing the
network-based mobility management service must be IPv6 enabled.
Figure 1 illustrates a Proxy Mobile IPv6 domain supporting IPv4 home Figure 1 illustrates a Proxy Mobile IPv6 domain supporting IPv4 home
address mobility and IPv4 transport network features. The mobile address mobility and IPv4 transport network features. The mobile
nodes MN1, MN2 and MN3 can be operating in IPv4-only, IPv6-only or nodes MN1, MN2 and MN3 can be operating in IPv4-only, IPv6-only or
dual-stack mode, and the transport network between the local mobility dual-stack mode, and the transport network between the local mobility
anchor and the mobile access gateway may be an IPv6 network or an anchor and the mobile access gateway may be an IPv6 network or an
IPv4 network. Further, when the transport network is IPv4, either IPv4 network. Further, when the transport network is IPv4, either
the local mobility anchor or the mobile access gateway, or both can the local mobility anchor or the mobile access gateway, or both can
be behind a NAT translation device and configured with an IPv4 be behind a NAT translation device and configured with an IPv4
private address. private address.
skipping to change at page 7, line 26 skipping to change at page 7, line 26
between access links and as long as the mobile node is in the scope between access links and as long as the mobile node is in the scope
of that Proxy Mobile IPv6 domain. of that Proxy Mobile IPv6 domain.
3.1. IPv4 Home Address Assignment 3.1. IPv4 Home Address Assignment
A mobile node on attaching to an access link connected to a mobile A mobile node on attaching to an access link connected to a mobile
access gateway, and if the network allows the mobile node for IPv4 access gateway, and if the network allows the mobile node for IPv4
home address mobility service, the mobile node using any of the IPv4 home address mobility service, the mobile node using any of the IPv4
address configuration procedures, such as DHCP, IPCP or IKEv2 that address configuration procedures, such as DHCP, IPCP or IKEv2 that
are supported on that access link, will be able to obtain its IPv4 are supported on that access link, will be able to obtain its IPv4
home address configuration. In addition to this, other address home address configuration. The IPv4 home address configuration
configuration mechanisms including static configuration methods includes the IPv4 home address, the IPv4 home network prefix and IPv4
specific to the access link may also be in place. The IPv4 home home network prefix length.
address configuration includes the IPv4 home address, the IPv4 home
network prefix and IPv4 home network prefix length. In this
specification, we support following static and dynamic assignment
schemes.
o Static IPv4 Home Address Assignment: When a mobile node is
configured with a static IPv4 home address, the IPv4 home address
information MUST be stored in the mobile node's policy profile.
The mobile access gateway where the mobile node attached obtains
the static IPv4 home address from the policy profile. The mobile
access gateway MUST set the known IPv4 home prefix to the IPv4
Home Address field and the Pref field of the IPv4 home address
option [ID-DSMIP6]. This option is carried by a proxy binding
update described in [ID-PMIP6].
o Dynamic IPv4 Home Address Assignment from Local Mobility Anchor: Figure 2 shows the operational sequence of the home address mobility
If a local mobility anchor manages the IPv4 home address support when a local mobility anchor assigns an IPv4 Home Address
allocation, a mobile access gateway requests dynamic IPv4 home dynamically to a mobile node. All mobile access gateways SHOULD
address allocation to the local mobility anchor as described in support minimal functionality of DHCP server in order to send DHCP
[ID-DSMIP6]. The mobile access gateway SHOULD support minimal offer and and acknowledgment messages to the mobile node in reply to
functionality of DHCP server in order to send DHCP offer and and the DHCP discovery and request messages. The mobile access gateway
acknowledgment messages to the mobile node in reply to the DHCP is seen as a DHCP server from a mobile node, but it actually obtains
discovery and request messages. The mobile access gateway is seen the IPv4 home address for each mobile node from the local mobility
as DHCP server from a mobile node, but it actually obtains the anchor during proxy binding procedure (set 0.0.0.0 in the the IPv4
IPv4 home address for each mobile node from the local mobility Home Address field of the IPv4 home address option as described in
anchor during proxy binding procedure. Figure 2 shows the [ID-DSMIP]). The mobile access gateway MUST return its own IP
operational sequence of the home address mobility support< in this address in the 'server identifier' option when sending DHCP offer
case. If IPCP is used for address assignment, DHCP events in message to the mobile node. Thus, whenever the mobile node changes
Figure 2 are replaced by PPP events. the attached mobile access gateway, this server identifier must be
updated. The detail can be found in Section 3.4. Any information
carried in DHCP options such as addresses of domain name server, time
server, lpr server, etc. MUST be configured in all the mobile access
gateway (i.e. DHCP server) if necessary. If IPCP is used for
address assignment, DHCP events in Figure 2 are replaced by PPP
events.
MN MAG LMA MN MAG(DHCPS) LMA
|------>| | 1. DHCP discovery |------>| | 1. DHCP discovery
| |------->| 2. Proxy Binding Update | |------->| 2. Proxy Binding Update
| |<-------| 3. Proxy Binding Acknowledgement (IPv4HoA) | |<-------| 3. Proxy Binding Acknowledgement (IPv4HoA)
| |========| 4. Tunnel/Route Setup* | |========| 4. Tunnel/Route Setup*
|<------| | 5. DHCP offer (IPv4 HoA) |<------| | 5. DHCP offer (IPv4 HoA) **
|------>| | 6. DHCP request (IPv4 HoA) |------>| | 6. DHCP request (IPv4 HoA)
|<------| | 7. DHCP acknowledgement |<------| | 7. DHCP acknowledgement
| | | | | |
* Tunnel/Route setup(no.4) and DHCP offer/request/ack(no.5-7) * Tunnel/Route setup(no.4) and DHCP offer/request/ack(no.5-7)
are processed in parallel. are processed in parallel.
** MAG SHOULD return its own IP address in the 'server identifier'
option when sending DHCP offer.
Figure 2: An example when LMA assigns an IPv4 home address Figure 2: An example when LMA assigns an IPv4 home address
o Dynamic IPv4 Home Address Assignment from DHCP Server: If DHCP is In addition to this, other address configuration mechanisms including
used for the IPv4 home address allocation, a mobile access gateway static configuration methods specific to the access link or dynamic
or specifically a DHCP relay agent on the link will ensure the configuration from the DHCP server (without local mobility anchor
mobile node is assigned an address from its home network prefix, involvmenet) may also be in place. Several other assignment schems
by marking the DHCP request with the mobile node's IPv4 home are listed:
network prefix hint. A DHCP relay and a mobile access gateway can
be co-located. The mobile access gateway learns the IPv4 home
address from the DHCP reply and sends that information to the
mobile node by DHCP offer message. Meanwhile, it notifies the
assigned IPv4 home address by an IPv4 home address option in a
proxy binding update to the local mobility anchor. In this case,
the local mobility anchor does not allocate any address, but only
deals with route setup and tunnel setup for the requested home
address. Note that all the IPv4 home addresses managed in the
DHCP server must be reachable via local mobility anchor so that
local mobility anchor intercepts packets meant for an IPv4 home
address and tunnels them to the mobile node via corresponding
mobile access gateway. More remarks can be found in Section 6.
Figure 3 are the sequence of the home address mobility support.
MN MAG(DHCPR) DHCPS LMA
|------>|------->| | 1. DHCP discovery and Relay
| |<-------| | 2. DHCP offer (IPv4 HoA)
| |--------------->| 3. Proxy Binding Update
| |<---------------| 4. Proxy Binding Acknowledgement
| |================| 5. Tunnel/Route Setup
|<------| | | 6. DHCP offer (IPv4 HoA) Relay
|------>|------->| | 7. DHCP request (IPv4 HoA) and Relay
|<------|<-------| | 8. DHCP acknowledgement and Relay
| | | |
DHCPS: DHCP Server o Static IPv4 Home Address Assignment: When a mobile node is
DHCPR: DHCP Relay configured with a static IPv4 home address, the IPv4 home address
* Tunnel setup(no.5) and DHCP offer/request/ack(no.6-8) information MUST be stored in the mobile node's policy profile.
are processed in parallel. The mobile access gateway where the mobile node attached obtains
the static IPv4 home address from the policy profile. The mobile
access gateway MUST set the known IPv4 home prefix to the IPv4
Home Address field and the Pref field of the IPv4 home address
option [ID-DSMIP6]. This option is carried by a proxy binding
update described in [ID-PMIP6].
Figure 3: An example when DHCP Server assigns an IPv4 home address o Dynamic IPv4 Home Address Assignment from DHCP Server: If DHCP is
used for the IPv4 home address allocation, a DHCP server and a
DHCP relay agent on the link will ensure the mobile node is
assigned an address from its home network prefix. In this case,
the local mobility anchor only deals with route setup and tunnel
setup for the requested home address. A DHCP relay and a mobile
access gateway should be co-located. Otherwise, the mobile access
gateway MUST learn the IPv4 home address from the DHCP reply.
Meanwhile, it notifies the assigned IPv4 home address by an IPv4
home address option in a proxy binding update to the local
mobility anchor. Some remarks can be found in Section 6.
3.2. Extensions to Conceptual Data Structure 3.2. Extensions to Conceptual Data Structure
There are certain extensions defined in DSMIP specification [DSMIP6] There are certain extensions defined in DSMIP specification [DSMIP6]
for supporting IPv4 home address mobility support. A mobile node can for supporting IPv4 home address mobility support. A mobile node can
obtain only IPv4 home address by this specification, while DSMIP obtain only IPv4 home address by this specification, while DSMIP
requires IPv6 home address for IPv4 home address support. Thus, a requires IPv6 home address for IPv4 home address support. Thus, a
mobile access gateway and a local mobility agent MUST create a mobile access gateway and a local mobility agent MUST create a
binding update list and a binding cache only for IPv4 home address binding update list and a binding cache only for IPv4 home address
assigned to a mobile node. assigned to a mobile node.
skipping to change at page 10, line 18 skipping to change at page 9, line 43
Proxy Mobile IPv6 specification apply here. Proxy Mobile IPv6 specification apply here.
o When a mobile node attached to an access link and attempts to o When a mobile node attached to an access link and attempts to
obtain an IPv4 address configuration, using DHCP or other obtain an IPv4 address configuration, using DHCP or other
procedures, it will get an IPv4 address as a IPv4 home address procedures, it will get an IPv4 address as a IPv4 home address
from its home network prefix as discussed in Section 3.1. The from its home network prefix as discussed in Section 3.1. The
mobile access gateway on the access link where mobile node is mobile access gateway on the access link where mobile node is
attached, will register this address with the local mobility attached, will register this address with the local mobility
anchor using the IPv4 Home Address option, defined in Section anchor using the IPv4 Home Address option, defined in Section
3.1.1 of [ID-DSMIP6]. The IPv4 Home Address option is sent with a 3.1.1 of [ID-DSMIP6]. The IPv4 Home Address option is sent with a
proxy binding update as shown in Figure 4. The proxy binding proxy binding update as shown in Figure 3. The proxy binding
update MUST be protected by IPsec ESP. How to build the IPv4 home update MUST be protected by IPsec ESP. How to build the IPv4 home
address option is varied as follows: address option is varied as follows:
* If a mobile access gateway needs to request dynamic IPv4 home * If a mobile access gateway needs to request dynamic IPv4 home
address allocation to the local mobility anchor, it MUST set address allocation to the local mobility anchor, it MUST set
0.0.0.0 in the the IPv4 Home Address field of the IPv4 home 0.0.0.0 in the the IPv4 Home Address field of the IPv4 home
address option as described in [ID-DSMIP] and send this option address option as described in [ID-DSMIP] and send this option
by the proxy binding update. by the proxy binding update.
* If a mobile access gateway knows the IPv4 home prefix (or home * If a mobile access gateway knows the IPv4 home prefix (or home
skipping to change at page 10, line 46 skipping to change at page 10, line 23
Mobility header Mobility header
-BU /*P flag is set*/ -BU /*P flag is set*/
Mobility Options Mobility Options
-HNP* /*IPv6 home address*/ -HNP* /*IPv6 home address*/
-TSO* -TSO*
-IPv4-HAO -IPv4-HAO
*HNP: Home Network Prefix Option *HNP: Home Network Prefix Option
*TSO: Time Stamp Option *TSO: Time Stamp Option
Figure 4: Proxy Binding Update for IPv4 Home Address Support Figure 3: Proxy Binding Update for IPv4 Home Address Support
o When a mobile node gets IPv4 home address from Local Mobility
Anchor through DHCP interaction with MAG that supports DHCP server
functionality, the DHCP client in the mobile node recognizes MAG's
IP address as DHCP server's IP address. Thus, the DHCP client
unicasts DHCP renew to the MAG, when the DHCP client goes into the
DHCP RENEWING state [RFC2131]. However, when the mobile node
handovers to a new MAG, the mobile node does not know the link
change and the DHCP client would unicast DHCP request to the
previous MAG whose IP address was acquired from DHCP offer. So,
DHCP client in the mobile node needs to reconfigure its local
configuration parameters. Therefore, MAG SHOULD discard any DHCP
request message that does not belong to the MAG itself, so that
the mobile node should go into the DHCP REBINDING state and
broadcast DHCP request without server identifier.
o A proxy binding acknowledgment will be returned by the local o A proxy binding acknowledgment will be returned by the local
mobility anchor. In the proxy binding acknowledgment, an IPv4 mobility anchor. In the proxy binding acknowledgment, an IPv4
address acknowledgment option MUST be presented in reply to the address acknowledgment option MUST be presented in reply to the
IPv4 home address option. The processing of this IPv4 home IPv4 home address option. The processing of this IPv4 home
acknowledgment option is found in DSMIP6 specification [ID- acknowledgment option is found in DSMIP6 specification [ID-
DSMIP6]. DSMIP6].
o After receiving a Proxy Binding Acknowledgment message with the o After receiving a Proxy Binding Acknowledgment message with the
IPv4 Address Acknowledgment Option and if the status code in the IPv4 Address Acknowledgment Option and if the status code in the
Binding Acknowledgment and Status field in the IPv4 Address Binding Acknowledgment and Status field in the IPv4 Address
skipping to change at page 11, line 49 skipping to change at page 11, line 39
Mobility header Mobility header
-BA /*P flag is set*/ -BA /*P flag is set*/
Mobility Options Mobility Options
-HNP* /*IPv6 home address*/ -HNP* /*IPv6 home address*/
-TSO* -TSO*
-IPv4-ACK -IPv4-ACK
-IPv4-DRA -IPv4-DRA
*HNP: Home Network Prefix Option *HNP: Home Network Prefix Option
*TSO: Time Stamp Option *TSO: Time Stamp Option
Figure 5: Proxy Binding Acknowledgement for IPv4 Home Address Figure 4: Proxy Binding Acknowledgement for IPv4 Home Address
Support Support
o After accepting the registration for the mobile node's IPv4 home o After accepting the registration for the mobile node's IPv4 home
address, the local mobility anchor will add an IPv4 host route address, the local mobility anchor will add an IPv4 host route
over the tunnel to the mobile access gateway. Any IPv4 packets over the tunnel to the mobile access gateway. Any IPv4 packets
that the local mobility anchor receives from a correspondent node that the local mobility anchor receives from a correspondent node
will be tunneled to the mobile access gateway over the bi- will be tunneled to the mobile access gateway over the bi-
directional tunnel, and then routed accordingly after removing the directional tunnel, and then routed accordingly after removing the
tunnel header. The encapsulation modes for the bi-directional tunnel header. The encapsulation modes for the bi-directional
tunnel may be as specified in Section 5.3 of Proxy Mobile IPv6 tunnel may be as specified in Section 5.3 of Proxy Mobile IPv6
skipping to change at page 14, line 44 skipping to change at page 14, line 44
mobile access gateway does not have connectivity to the IPv6 mobile access gateway does not have connectivity to the IPv6
network, it MUST configure with an IPv6 address for sending the network, it MUST configure with an IPv6 address for sending the
proxy binding registration to the local mobility anchor. proxy binding registration to the local mobility anchor.
o As explained in Section 4.1, of the DSMIPv6 specification, the o As explained in Section 4.1, of the DSMIPv6 specification, the
mobile access gateway can encapsulate a Proxy Binding Update mobile access gateway can encapsulate a Proxy Binding Update
message and carry it in IPv4 and UDP packet. The processing logic message and carry it in IPv4 and UDP packet. The processing logic
for handling the NAT detection at the mobile node is applicable to for handling the NAT detection at the mobile node is applicable to
the mobile access gateway as described in Section 4.3. An example the mobile access gateway as described in Section 4.3. An example
of proxy binding update sent by mobile access gateway is shown in of proxy binding update sent by mobile access gateway is shown in
Figure 6. Note that the source address of the inner IPv6 header Figure 5. Note that the source address of the inner IPv6 header
MUST set to the IPv6 address assigned to the mobile access gateway MUST set to the IPv6 address assigned to the mobile access gateway
and the destination address MUST be the local mobility anchor's and the destination address MUST be the local mobility anchor's
IPv6 address (LMAA). The source address of the outer packet MUST IPv6 address (LMAA). The source address of the outer packet MUST
be the IPv4-proxy-CoA and the destination MUST be the local be the IPv4-proxy-CoA and the destination MUST be the local
mobility anchor's IPv4 address (IPv4-LMAA). For the NAT handling, mobility anchor's IPv4 address (IPv4-LMAA). For the NAT handling,
UDP header MUST be always used for the proxy binding update. The UDP header MUST be always used for the proxy binding update. The
UDP port number is defined in [ID-DSMIP6]. The proxy binding UDP port number is defined in [ID-DSMIP6]. The proxy binding
update MUST be protected by IPsec ESP. The security association update MUST be protected by IPsec ESP. The security association
for IPv4 addresses of the mobile access gateway and local mobility for IPv4 addresses of the mobile access gateway and local mobility
anchor are pre-established. anchor are pre-established.
IPv4 header (src=IPv4-proxy-CoA, dst=IPv4-LMAA) IPv4 header (src=IPv4-proxy-CoA, dst=IPv4-LMAA)
UDP header UDP header
IPv6 header (src=v6MAG*, dst=LMAA) IPv6 header (src=v6MAG*, dst=LMAA)
Mobility header Mobility header
-BU /*P flag is set*/ -BU /*P flag is set*/
Mobility Options Mobility Options
-HNP* /*IPv6 home address*/ -HNP* /*IPv6 home address*/
-TSO* -TSO*
-IPv4-HAO /*if IPv4 HoA is required*/ -IPv4-HAO /*if IPv4 HoA is required*/
-NAI /* NAI Option */
*HNP: Home Network Prefix Option *HNP: Home Network Prefix Option
*TSO: Time Stamp Option *TSO: Time Stamp Option
*v6MAG: IPv6 address assigned to the mobile access gateway. *v6MAG: IPv6 address assigned to the mobile access gateway.
*NAI: NAI Option
Figure 6: Proxy Binding Update from mobile access gateway in IPv4 Figure 5: Proxy Binding Update from mobile access gateway in IPv4
network network
o After receiving a Proxy Binding Acknowledgment message o After receiving a Proxy Binding Acknowledgment message
encapsulated in an IPv4 packet, the mobile access gateway MUST encapsulated in an IPv4 packet, the mobile access gateway MUST
verify the Proxy Binding Acknowledgment according to the Section verify the Proxy Binding Acknowledgment according to the Section
4.3 of DSMIP6 specification [ID-DSMIP6]. 4.3 of DSMIP6 specification [ID-DSMIP6].
o If the Status field indicates Success, the mobile access gateway o If the Status field indicates Success, the mobile access gateway
MUST setup a tunnel to the local mobility anchor and add a default MUST setup a tunnel to the local mobility anchor and add a default
route over the tunnel for all the mobile node's IPv6 traffic. If route over the tunnel for all the mobile node's IPv6 traffic. If
skipping to change at page 15, line 46 skipping to change at page 15, line 48
The detailed operation can be found in DSMIP6 specification [ID- The detailed operation can be found in DSMIP6 specification [ID-
DSMIP6]. DSMIP6].
o If the Status field in the proxy binding acknowledgment indicates o If the Status field in the proxy binding acknowledgment indicates
the rejection of the binding registration, the mobile access the rejection of the binding registration, the mobile access
gateway MUST not enable IPv4 transport for the mobile node's gateway MUST not enable IPv4 transport for the mobile node's
traffic. traffic.
o On receiving any packets from the mobile node's IPv6 home address o On receiving any packets from the mobile node's IPv6 home address
and/or IPv4 home address, the mobile access gateway tunnels the and/or IPv4 home address, the mobile access gateway tunnels the
packets to local mobility anchor as shown in Figure 7 packets to local mobility anchor as shown in Figure 6
IPv4 header (src=IPv4-Proxy-CoA, dst=IPv4-LMAA) IPv4 header (src=IPv4-Proxy-CoA, dst=IPv4-LMAA)
UDP header /*Only if NAT is detected*/ UDP header /*Only if NAT is detected*/
union { /*following either v6 or v4 header */ union { /*following either v6 or v4 header */
IPv4 header (src=MN's IPv4-HoA, dst=IPv4 CN) IPv4 header (src=MN's IPv4-HoA, dst=IPv4 CN)
IPv6 header (src=MN's IPv6-HoA, dst=IPv6 CN) IPv6 header (src=MN's IPv6-HoA, dst=IPv6 CN)
} }
Upper layer protocols /*TCP,UDP,SCTP*/ Upper layer protocols /*TCP,UDP,SCTP*/
Figure 7: Tunneled Packets from MAG to LMA Figure 6: Tunneled Packets from MAG to LMA
4.5. Local Mobility Anchor Operation 4.5. Local Mobility Anchor Operation
When a mobile node is attached to a mobile access gateway that is When a mobile node is attached to a mobile access gateway that is
reachable only through an IPv4 transport network, the local mobility reachable only through an IPv4 transport network, the local mobility
anchor must establish an IPv4 tunnel for routing the mobile node's anchor must establish an IPv4 tunnel for routing the mobile node's
IPv4 and IPv6 home address traffic. The DSMIPv6 specification IPv4 and IPv6 home address traffic. The DSMIPv6 specification
provides the semantics on how the IPv4 tunnel needs to be negotiated provides the semantics on how the IPv4 tunnel needs to be negotiated
and the detection logic of the NAT devices. This specification and the detection logic of the NAT devices. This specification
leverages the NAT Detection Option, defined in the DSMIP6 leverages the NAT Detection Option, defined in the DSMIP6
skipping to change at page 17, line 15 skipping to change at page 17, line 15
IPv4 header (src=IPv4-LMAA, dst=IPv4-proxy-CoA) IPv4 header (src=IPv4-LMAA, dst=IPv4-proxy-CoA)
UDP header /*Only if NAT is detected*/ UDP header /*Only if NAT is detected*/
IPv6 header (src=LMAA, dst=v6MAG) IPv6 header (src=LMAA, dst=v6MAG)
Mobility header Mobility header
-BA /*P flag is set */ -BA /*P flag is set */
Mobility Options Mobility Options
-HNP* /* IPv6-MN-HoA */ -HNP* /* IPv6-MN-HoA */
-TSO* -TSO*
-IPv4-ACK /* Only if IPv4 HoA is required */ -IPv4-ACK /* Only if IPv4 HoA is required */
-NAT-DET /* Only if NAT is detected */ -NAT-DET /* Only if NAT is detected */
-NAI /*NAI Option */
*HNP: Home Network Prefix Option *HNP: Home Network Prefix Option
*TSO: Time Stamp Option *TSO: Time Stamp Option
*v6MAG: IPv6 address assigned to the mobile access gateway. *v6MAG: IPv6 address assigned to the mobile access gateway.
Figure 8: Proxy Binding Acknowledgment in IPv4 network Figure 7: Proxy Binding Acknowledgment in IPv4 network
o After accepting the registration from the mobile access gateway o After accepting the registration from the mobile access gateway
locating at the IPv4 only network, the local mobility anchor MUST locating at the IPv4 only network, the local mobility anchor MUST
setup a tunnel to the mobile access gateway. The tunnel is setup a tunnel to the mobile access gateway. The tunnel is
established between the v4-LMAA and the IPv4-Proxy-CoA of the established between the v4-LMAA and the IPv4-Proxy-CoA of the
mobile access gateway. If the NAT is available and the NAT mobile access gateway. If the NAT is available and the NAT
detection option is included in the Proxy Binding Acknowledgment, detection option is included in the Proxy Binding Acknowledgment,
the local mobility anchor MUST use UDP encapsulation for the the local mobility anchor MUST use UDP encapsulation for the
tunnel. The local mobility anchor also setup a host routes for tunnel. The local mobility anchor also setup a host routes for
the IPv4 home address and the IPv6 home address of the mobile node the IPv4 home address and the IPv6 home address of the mobile node
over the tunnel to the mobile access gateway. Any traffic that over the tunnel to the mobile access gateway. Any traffic that
the local mobility anchor receives from a correspondent node will the local mobility anchor receives from a correspondent node will
be tunneled to the mobile access gateway over the bi-directional be tunneled to the mobile access gateway over the bi-directional
tunnel and then routed accordingly after removing the tunnel tunnel and then routed accordingly after removing the tunnel
headers. The encapsulation modes for the bi-directional tunnel headers. The encapsulation modes for the bi-directional tunnel
may be as specified in Section 5.3 of Proxy Mobile IPv6 may be as specified in Section 5.3 of Proxy Mobile IPv6
specification [ID-PMIP6] and as in this specification. specification [ID-PMIP6] and as in this specification.
o When sending any packets meant to a mobile node's IPv4 home o When sending any packets meant to a mobile node's IPv4 home
address or IPv6 home address, the local mobility anchor tunnels address or IPv6 home address, the local mobility anchor tunnels
the packet to mobile access gateway as shown in Figure 9 the packet to mobile access gateway as shown in Figure 8
IPv4 header (src=IPv4-LMAA, dst=IPv4-Proxy-CoA) IPv4 header (src=IPv4-LMAA, dst=IPv4-Proxy-CoA)
UDP header /*Only if NAT is detected*/ UDP header /*Only if NAT is detected*/
union { /*following either v6 or v4 header */ union { /*following either v6 or v4 header */
IPv4 header (src=IPv4-CN, dst=IPv4-HoA) IPv4 header (src=IPv4-CN, dst=IPv4-HoA)
IPv6 header (src=IPv6-CN, dst=IPv6-HoA) IPv6 header (src=IPv6-CN, dst=IPv6-HoA)
} }
Upper layer protocols /*TCP,UDP,SCTP*/ Upper layer protocols /*TCP,UDP,SCTP*/
Figure 9: Tunneled Packets from LMA to MAG Figure 8: Tunneled Packets from LMA to MAG
4.6. Tunnel Management 4.6. Tunnel Management
As specified in the Proxy Mobile IPv6 specification, the bi- As specified in the Proxy Mobile IPv6 specification, the bi-
directional tunnel between the local mobility anchor and the mobile directional tunnel between the local mobility anchor and the mobile
access gateway, is a shared tunnel and all the considerations from access gateway, is a shared tunnel and all the considerations from
Section 6.6 of Proxy Mobile IPv6 [ID-PMIP6] apply for IPv4 transport Section 6.6 of Proxy Mobile IPv6 [ID-PMIP6] apply for IPv4 transport
as well. as well.
5. IANA Considerations 5. IANA Considerations
skipping to change at page 20, line 15 skipping to change at page 20, line 15
6. Security Considerations 6. Security Considerations
This specification describes the use of IPv4 transport network This specification describes the use of IPv4 transport network
between the local mobility anchor and the mobile access gateway. All between the local mobility anchor and the mobile access gateway. All
the signaling messages exchanged between the mobile access gateway the signaling messages exchanged between the mobile access gateway
and the local mobility anchor over the IPv4 transport MUST be and the local mobility anchor over the IPv4 transport MUST be
protected using IPsec, just as the messages must be protected when protected using IPsec, just as the messages must be protected when
using IPv6 transport and as specified in the Section 4.0, of the using IPv6 transport and as specified in the Section 4.0, of the
Proxy Mobile IPv6 specification [ID-PMIP6]. Proxy Mobile IPv6 specification [ID-PMIP6].
When supporting IPv4 address assignment from a DHCP server, the local When supporting IPv4 address assignment from a DHCP server, all the
mobility anchor MUST be the prefix owner and the topological anchor IPv4 home addresses managed in the DHCP server must be reachable via
point for the address pools that are configured on the DHCP server local mobility anchor so that local mobility anchor intercepts
for allocation for the mobile nodes. packets meant for an IPv4 home address and tunnels them to the mobile
node via corresponding mobile access gateway. Moreover, all the DHCP
messages between a DHCP relay and the DHCP server SHOULD be securely
exchanged.
After receiving a Proxy Binding Update message with an IPv4 Home After receiving a Proxy Binding Update message with an IPv4 Home
Address Option, the local mobility anchor MUST be able to verify that Address Option, the local mobility anchor MUST be able to verify that
the mobile node is authorized to use that address before setting up the mobile node is authorized to use that address before setting up
forwarding for that host route. forwarding for that host route.
When supporting dynamic IPv4 address assignment by DHCP and also from When supporting dynamic IPv4 address assignment by DHCP and also from
local mobility anchor, it should be ensured both the entities are local mobility anchor, it should be ensured both the entities are
configured with different address pools, so as to avoid both entities configured with different address pools, so as to avoid both entities
do not allocate the same address to different mobile nodes. do not allocate the same address to different mobile nodes.
skipping to change at page 21, line 20 skipping to change at page 21, line 20
Kuntal Chowdhury Kuntal Chowdhury
kchowdhury@starentnetworks.com kchowdhury@starentnetworks.com
Vijay Devarapalli Vijay Devarapalli
vijay.devarapalli@azairenet.com vijay.devarapalli@azairenet.com
Sangjin Jeong Sangjin Jeong
sjjeong@gmail.com sjjeong@etri.re.kr
Basavaraj Patil Basavaraj Patil
basavaraj.patil@nsn.com basavaraj.patil@nsn.com
Myungki Shin Myungki Shin
myungki.shin@gmail.com myungki.shin@gmail.com
8. Acknowledgments 8. Acknowledgments
skipping to change at page 22, line 38 skipping to change at page 22, line 38
[ID-DSMIP6] Soliman, H. et al, "Mobile IPv6 support for dual stack [ID-DSMIP6] Soliman, H. et al, "Mobile IPv6 support for dual stack
Hosts and Routers (DSMIPv6)", draft-ietf-mip6-nemo-v4traversal-03.txt Hosts and Routers (DSMIPv6)", draft-ietf-mip6-nemo-v4traversal-03.txt
,October 2006. ,October 2006.
[ID-MIP6-IKEV2] Devarapalli, V. and Dupont, F., "Mobile IPv6 [ID-MIP6-IKEV2] Devarapalli, V. and Dupont, F., "Mobile IPv6
Operation with IKEv2 and the revised IPsec Architecture", Operation with IKEv2 and the revised IPsec Architecture",
draft-ietf-mip6-ikev2-ipsec-08.txt, December 2006. draft-ietf-mip6-ikev2-ipsec-08.txt, December 2006.
[ID-PMIP6] Gundavelli, S., et.al, "Proxy Mobile IPv6", [ID-PMIP6] Gundavelli, S., et.al, "Proxy Mobile IPv6",
draft-sgundave-mip6-proxymip6-02.txt, March 2007. draft-ietf-netlmm-proxymip6-01.txt, December 2007.
9.2. Informative References 9.2. Informative References
[RFC-2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC-2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC-2461] Narten, T., Nordmark, E. and W. Simpson, "Neighbor [RFC-2461] Narten, T., Nordmark, E. and W. Simpson, "Neighbor
Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998. Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998.
[RFC-2462] Thompson, S., Narten, T., "IPv6 Stateless Address [RFC-2462] Thompson, S., Narten, T., "IPv6 Stateless Address
 End of changes. 33 change blocks. 
111 lines changed or deleted 121 lines changed or added

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