draft-ietf-dmm-distributed-mobility-anchoring-10.txt   draft-ietf-dmm-distributed-mobility-anchoring-11.txt 
DMM H. Chan, Ed. DMM H. Chan, Ed.
Internet-Draft X. Wei Internet-Draft X. Wei
Intended status: Informational Huawei Technologies Intended status: Informational Huawei Technologies
Expires: January 3, 2019 J. Lee Expires: March 2, 2019 J. Lee
Sangmyung University Sangmyung University
S. Jeon S. Jeon
Sungkyunkwan University Sungkyunkwan University
CJ. Bernardos, Ed. CJ. Bernardos, Ed.
UC3M UC3M
July 2, 2018 August 29, 2018
Distributed Mobility Anchoring Distributed Mobility Anchoring
draft-ietf-dmm-distributed-mobility-anchoring-10 draft-ietf-dmm-distributed-mobility-anchoring-11
Abstract Abstract
This document defines distributed mobility anchoring in terms of the This document defines distributed mobility anchoring in terms of the
different configurations and functions to provide IP mobility different configurations and functions to provide IP mobility
support. A network may be configured with distributed mobility support. A network may be configured with distributed mobility
anchoring functions for both network-based or host-based mobility anchoring functions for both network-based or host-based mobility
support according to the needs of mobility support. In the support according to the needs of mobility support. In the
distributed mobility anchoring environment, multiple anchors are distributed mobility anchoring environment, multiple anchors are
available for mid-session switching of an IP prefix anchor. To start available for mid-session switching of an IP prefix anchor. To start
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on January 3, 2019. This Internet-Draft will expire on March 2, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 34 skipping to change at page 2, line 34
3. Distributed Mobility Anchoring . . . . . . . . . . . . . . . 5 3. Distributed Mobility Anchoring . . . . . . . . . . . . . . . 5
3.1. Configurations for Different Networks . . . . . . . . . . 5 3.1. Configurations for Different Networks . . . . . . . . . . 5
3.1.1. Network-based DMM . . . . . . . . . . . . . . . . . . 5 3.1.1. Network-based DMM . . . . . . . . . . . . . . . . . . 5
3.1.2. Client-based DMM . . . . . . . . . . . . . . . . . . 6 3.1.2. Client-based DMM . . . . . . . . . . . . . . . . . . 6
4. IP Mobility Handling in Distributed Anchoring Environments - 4. IP Mobility Handling in Distributed Anchoring Environments -
Mobility Support Only When Needed . . . . . . . . . . . . . . 7 Mobility Support Only When Needed . . . . . . . . . . . . . . 7
4.1. Nomadic case (no need of IP mobility): Changing to new IP 4.1. Nomadic case (no need of IP mobility): Changing to new IP
prefix/address . . . . . . . . . . . . . . . . . . . . . 8 prefix/address . . . . . . . . . . . . . . . . . . . . . 8
4.2. Mobility case, traffic redirection . . . . . . . . . . . 10 4.2. Mobility case, traffic redirection . . . . . . . . . . . 10
4.3. Mobility case, anchor relocation . . . . . . . . . . . . 12 4.3. Mobility case, anchor relocation . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 16 8.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
A key requirement in distributed mobility management [RFC7333] is to A key requirement in distributed mobility management [RFC7333] is to
enable traffic to avoid traversing a single mobility anchor far from enable traffic to avoid traversing a single mobility anchor far from
an optimal route. This document defines different configurations, an optimal route. This document defines different configurations,
functional operations and parameters for distributed mobility functional operations and parameters for distributed mobility
anchoring and explains how to use them to make the route changes to anchoring and explains how to use them to make the route changes to
avoid unnecessarily long routes. avoid unnecessarily long routes.
skipping to change at page 3, line 20 skipping to change at page 3, line 20
[I-D.sarikaya-dmm-for-wifi], [I-D.yhkim-dmm-enhanced-anchoring], and [I-D.sarikaya-dmm-for-wifi], [I-D.yhkim-dmm-enhanced-anchoring], and
[I-D.matsushima-stateless-uplane-vepc]. [I-D.matsushima-stateless-uplane-vepc].
Distributed mobility anchoring employs multiple anchors in the data Distributed mobility anchoring employs multiple anchors in the data
plane. In general, control plane functions may be separated from plane. In general, control plane functions may be separated from
data plane functions and be centralized but may also be co-located data plane functions and be centralized but may also be co-located
with the data plane functions at the distributed anchors. Different with the data plane functions at the distributed anchors. Different
configurations of distributed mobility anchoring are described in configurations of distributed mobility anchoring are described in
Section 3.1. Section 3.1.
As an MN attaches to an access router and establishes a link between As a Mobile Node (MN) attaches to an access router and establishes a
them, a /64 IPv6 prefix anchored to the router may be assigned to the link between them, a /64 IPv6 prefix anchored to the router may be
link for exclusive use by the MN [RFC6459]. The MN may then assigned to the link for exclusive use by the MN [RFC6459]. The MN
configure a global IPv6 address from this prefix and use it as the may then configure a global IPv6 address from this prefix and use it
source IP address in a flow to communicate with its correspondent as the source IP address in a flow to communicate with its
node (CN). When there are multiple mobility anchors assigned to the correspondent node (CN). When there are multiple mobility anchors
same MN, an address selection for a given flow is first required assigned to the same MN, an address selection for a given flow is
before the flow is initiated. Using an anchor in an MN's network of first required before the flow is initiated. Using an anchor in a
attachment has the advantage that the packets can simply be forwarded MN's network of attachment has the advantage that the packets can
according to the forwarding table. However, after the flow has been simply be forwarded according to the forwarding table. However,
initiated, the MN may later move to another network which assigns a after the flow has been initiated, the MN may later move to another
new mobility anchor to the MN. Since the new anchor is located in a network which assigns a new mobility anchor to the MN. Since the new
different network, the MN's assigned prefix and the built MN IP anchor is located in a different network, the MN's assigned prefix
address does not belong to the network where the MN is currently and the built MN IP address do not belong to the network where the MN
attached. is currently attached.
When the MN wants to continue using its assigned prefix and IP When the MN wants to continue using its assigned prefix and IP
address, e.g., to complete ongoing data sessions after it moved to a address to complete ongoing data sessions after it moved to a new
new network, the network needs to provide support for IP address- and network, the network needs to provide support for IP address- and
session continuity, since routing packets to the MN through the new session continuity, since routing packets to the MN through the new
network deviates from applying default routes. The IP session network deviates from applying default routes. The IP session
continuity needs of a flow (application) determines the how the IP continuity needs of a flow (application) determines the how the IP
address used by the traffic of this flow has to be anchored. If the address used by the traffic of this flow has to be anchored. If the
ongoing IP flow can cope with an IP prefix/address change, the flow ongoing IP flow can cope with an IP prefix/address change, the flow
can be reinitiated with a new IP address anchored in the new network. can be reinitiated with a new IP address anchored in the new network.
On the other hand, if the ongoing IP flow cannot cope with such On the other hand, if the ongoing IP flow cannot cope with such
change, mobility support is needed. A network supporting a mix of change, mobility support is needed. A network supporting a mix of
flows both requiring and not requiring IP mobility support will need flows both requiring and not requiring IP mobility support will need
to distinguish these flows. to distinguish these flows.
skipping to change at page 4, line 38 skipping to change at page 4, line 38
assigned IP address/prefix must traverse the anchor node. We can assigned IP address/prefix must traverse the anchor node. We can
refer to the function performed by IP anchor node as anchoring, refer to the function performed by IP anchor node as anchoring,
which is a data plane function. which is a data plane function.
Location Management (LM) function: control plane function that keeps Location Management (LM) function: control plane function that keeps
and manages the network location information of an MN. The and manages the network location information of an MN. The
location information may be a binding of the advertised IP location information may be a binding of the advertised IP
address/prefix, e.g., HoA or HNP, to the IP routing address of the address/prefix, e.g., HoA or HNP, to the IP routing address of the
MN or of a node that can forward packets destined to the MN. MN or of a node that can forward packets destined to the MN.
When the MN is a mobile router (MR) carrying a mobile network of When the MN is a mobile router (MR) providing a mobile network of
mobile network nodes (MNN), the location information will also mobile network nodes (MNN), the location information will also
include the mobile network prefix (MNP), which is the aggregate IP include the mobile network prefix (MNP), which is the aggregate IP
prefix delegated to the MR to assign IP prefixes for use by the prefix delegated to the MR to assign IP prefixes for use by the
MNNs in the mobile network. MNNs in the mobile network.
In a client-server protocol model, location query and update In a client-server protocol model, location query and update
messages may be exchanged between a Location Management client messages may be exchanged between a Location Management client
(LMc) and a Location Management server (LMs), where the location (LMc) and a Location Management server (LMs), where the location
information can be updated to or queried from the LMc. information can be updated to or queried from the LMc.
Optionally, there may be a Location Management proxy (LMp) between Optionally, there may be a Location Management proxy (LMp) between
skipping to change at page 5, line 45 skipping to change at page 5, line 45
separated, as described in [I-D.ietf-dmm-deployment-models]. separated, as described in [I-D.ietf-dmm-deployment-models].
3.1.1. Network-based DMM 3.1.1. Network-based DMM
Figure 1 shows a general scenario for network-based distributed Figure 1 shows a general scenario for network-based distributed
mobility management. mobility management.
The main characteristics of a network-based DMM solution are: The main characteristics of a network-based DMM solution are:
o There are multiple data plane anchors (i.e., DPA instances), each o There are multiple data plane anchors (i.e., DPA instances), each
with an FM-DP function. with a FM-DP function.
o The control plane may either be distributed (not shown in the o The control plane may either be distributed (not shown in the
figure) or centralized (as shown in the figure). figure) or centralized (as shown in the figure).
o The control plane and the data plane (Control Plane Anchor -- CPA o The control plane and the data plane (Control Plane Anchor -- CPA
-- and Data Plane Anchor -- DPA) may be co-located or not. If the -- and Data Plane Anchor -- DPA) may be co-located or not. If the
CPA is co-located with the distributed DPAs, then there are CPA is co-located with the distributed DPAs, then there are
multiple co-located CPA-DPA instances (not shown in the figure). multiple co-located CPA-DPA instances (not shown in the figure).
o An IP prefix/address IP1 (anchored to the DPA with IP address o An IP prefix/address IP1 (anchored to the DPA with IP address
IPa1) is assigned for use by an MN. The MN uses this IP1 address IPa1) is assigned for use to a MN. The MN uses this IP1 address
to communicate with CNs (not shown in the figure). to communicate with CNs (not shown in the figure).
o The location management (LM) function may be co-located or split o The location management (LM) function may be co-located or split
(as shown in the figure) into a separate server (LMs) and a client (as shown in the figure) into a separate server (LMs) and a client
(LMc). In this case, the LMs may be centralized whereas the LMc (LMc). In this case, the LMs may be centralized whereas the LMc
may be distributed or centralized. may be distributed or centralized.
____________ Network ____________ Network
___/ \___________ ___/ \___________
/ +-----+ \___ / +-----+ \___
( |LMs | Control \ ( |LMs | Control \
skipping to change at page 6, line 49 skipping to change at page 6, line 49
+------------+ +------------+
Figure 1: Network-based DMM configuration Figure 1: Network-based DMM configuration
3.1.2. Client-based DMM 3.1.2. Client-based DMM
Figure 2 shows a general scenario for client-based distributed Figure 2 shows a general scenario for client-based distributed
mobility management. In this configuration, the mobile node performs mobility management. In this configuration, the mobile node performs
Control Plane Node (CPN) and Data Plane Node (DPN) mobility Control Plane Node (CPN) and Data Plane Node (DPN) mobility
functions, namely the forwarding management and location management functions, namely the forwarding management and location management
(client role) ones. (client) roles.
+-----+ +-----+
|LMs | |LMs |
+-.---+ +-.---+
+--------.---+ +--------.---+
|CPA: . | |CPA: . |
|FM-CP, LMp | |FM-CP, LMp |
+------------+ +------------+
. . . .
. . . .
skipping to change at page 7, line 52 skipping to change at page 7, line 52
traffic using the old IP address, and forwards it to the new MN's traffic using the old IP address, and forwards it to the new MN's
location. The MN obtains a new IP address anchored at the new location. The MN obtains a new IP address anchored at the new
location, and preferably uses it for new communications, location, and preferably uses it for new communications,
established while connected at the new location. established while connected at the new location.
o Mobility case, anchor relocation: address continuity is required. o Mobility case, anchor relocation: address continuity is required.
In this case the route followed by the traffic is optimized, by In this case the route followed by the traffic is optimized, by
using some means for traffic indirection to deviate from default using some means for traffic indirection to deviate from default
routes. routes.
A straightforward choice of mobility anchoring is the following: the A straightforward choice of mobility anchoring is the following: the
MN's choses as source IP address of packets belonging to an IP flow, MN's chooses as source IP address of packets belonging to an IP flow,
an address allocated by the network the MN is attached to when the an address allocated by the network the MN is attached to when the
flow was initiated. As such, traffic belonging to this flow flow was initiated. As such, traffic belonging to this flow
traverses the MN's mobility anchor [I-D.seite-dmm-dma] traverses the MN's mobility anchor [I-D.seite-dmm-dma]
[I-D.bernardos-dmm-pmipv6-dlif]. [I-D.bernardos-dmm-pmipv6-dlif].
The IP prefix/address at the MN's side of a flow may be anchored at The IP prefix/address at the MN's side of a flow may be anchored at
the access router to which the MN is attached. For example, when an the access router to which the MN is attached. For example, when a
MN attaches to a network (Net1) or moves to a new network (Net2), an MN attaches to a network (Net1) or moves to a new network (Net2), an
IP prefix from the attached network is assigned to the MN's IP prefix from the attached network is assigned to the MN's
interface. In addition to configuring new link-local addresses, the interface. In addition to configuring new link-local addresses, the
MN configures from this prefix an IP address which is typically a MN configures from this prefix an IP address which is typically a
dynamic IP address. It then uses this IP address when a flow is dynamic IP address. It then uses this IP address when a flow is
initiated. Packets to the MN in this flow are simply forwarded initiated. Packets to the MN in this flow are simply forwarded
according to the forwarding table. according to the forwarding table.
There may be multiple IP prefixes/addresses that an MN can select There may be multiple IP prefixes/addresses that an MN can select
when initiating a flow. They may be from the same access network or when initiating a flow. They may be from the same access network or
skipping to change at page 9, line 47 skipping to change at page 9, line 47
enabled using a higher layer mobility support which is not in the enabled using a higher layer mobility support which is not in the
scope of this document. scope of this document.
In Figure 3, a flow initiated while the MN was using the IP prefix In Figure 3, a flow initiated while the MN was using the IP prefix
IP1 anchored to a previous access router AR1 in network Net1 has IP1 anchored to a previous access router AR1 in network Net1 has
terminated before the MN moves to a new network Net2. After moving terminated before the MN moves to a new network Net2. After moving
to Net2, the MN uses the new IP prefix IP2 anchored to a new access to Net2, the MN uses the new IP prefix IP2 anchored to a new access
router AR2 in network Net2 to start a new flow. The packets may then router AR2 in network Net2 to start a new flow. The packets may then
be forwarded without requiring IP layer mobility support. be forwarded without requiring IP layer mobility support.
An example call flow is outlined in Figure 4 An example call flow is outlined in Figure 4. MN attaches to a
network and AR1 sends a router advertisement (RA) including
information about the prefix assigned to MN, from which MN configures
the IP address to use (IP1). This address is used for new
communications, for example with a correspondent node (CN). If the
MN moves to a new network and attaches to AR2, the process is
repeated (MN obtains a new IP address, IP2, from AR2). Since the IP
address (IP1) configured at the previously visited network is not
valid at the current attachment point, any existing flows have to be
reestablished using IP2.
MN AR1 AR2 CN MN AR1 AR2 CN
|MN attaches to AR1: | | | |MN attaches to AR1: | | |
|acquire MN-ID and profile | | |acquire MN-ID and profile | |
|--RS---------------->| | | |--RS---------------->| | |
| | | | | | | |
|<----------RA(IP1)---| | | |<----------RA(IP1)---| | |
| | | | | | | |
Assigned prefix IP1 | | | Assigned prefix IP1 | | |
IP1 address configuration | | IP1 address configuration | |
| | | | | | | |
skipping to change at page 10, line 40 skipping to change at page 10, line 45
4.2. Mobility case, traffic redirection 4.2. Mobility case, traffic redirection
When IP mobility is needed for a flow, the LM and FM functions in When IP mobility is needed for a flow, the LM and FM functions in
Section 3.1 are utilized. There are two possible cases: (i) the Section 3.1 are utilized. There are two possible cases: (i) the
initial anchor remains the anchor and forwards traffic to a new initial anchor remains the anchor and forwards traffic to a new
locator in the new network, and (ii) the mobility anchor (data plane locator in the new network, and (ii) the mobility anchor (data plane
function) is changed but binds the MN's transferred IP address/ function) is changed but binds the MN's transferred IP address/
prefix. The latter enables optimized routes but requires some data prefix. The latter enables optimized routes but requires some data
plane node that enforces rules for traffic indirection. Next, we plane node that enforces rules for traffic indirection. Next, we
focus on the first case. focus on the first case. The second one is addressed in Section 4.3.
Mobility support can be provided by using mobility management methods Mobility support can be provided by using mobility management methods
such as ([Paper-Distributed.Mobility], such as ([Paper-Distributed.Mobility],
[Paper-Distributed.Mobility.PMIP] and [Paper-Distributed.Mobility.PMIP] and
[Paper-Distributed.Mobility.Review]). After moving, a certain MN's [Paper-Distributed.Mobility.Review]). After moving, a certain MN's
traffic flow may continue using the IP prefix from the prior network traffic flow may continue using the IP prefix from the prior network
of attachment. Yet some time later, the user application for the of attachment. Yet some time later, the user application for the
flow may be closed. If the application is started again, the new flow may be closed. If the application is started again, the new
flow may not need to use the prior network's IP address to avoid flow may not need to use the prior network's IP address to avoid
having to invoke IP mobility support. This may be the case where a having to invoke IP mobility support. This may be the case where a
dynamic IP prefix/address rather than a permanent one is used. The dynamic IP prefix/address rather than a permanent one is used. The
flow may then use the new IP prefix in the network where the flow is flow may then use the new IP prefix in the network where the flow is
being initiated. Routing is again kept simpler without employing IP being initiated. Routing is again kept simpler without employing IP
mobility and will remain so as long as the MN which is now in the new mobility and will remain so as long as the MN which is now in the new
network has not moved again and left to another new network. network has not moved again and left to another new network.
An example call flow in this case is outlined in Figure 6. In this
example, the AR1 plays the role of FM-DP entity and redirects the
traffic (e.g., using an IP tunnel) to AR2. Another solution could be
to place an FM-DP entity closer to the CN network to perform traffic
steering to deviate from default routes (which will bring the packet
to AR1 per default routing). The LM and FM functions are implemented
as shown in Figure 5.
Net1 Net2
+---------------+ +---------------+
|AR1 | |AR2 |
+---------------+ +---------------+
|CPA: | |CPA: |
| | |LM:IP1 at IPa1 |
|---------------| IP1 (anchored at Net1) |---------------|
|DPA(IPa1): | is redirected to Net2 |DPA(IPa2): |
|anchors IP1 | =======> |anchors IP2 |
+---------------+ +---------------+
+...............+ +---------------+
.MN(IP1) . MN moves |MN(IP2,IP1) |
.flow(IP1,...) . =======> |flow(IP1,...) |
. . |flow(IP2,...) |
+...............+ +---------------+
Figure 5: Anchor redirection
MN AR1 AR2 CN MN AR1 AR2 CN
|MN attaches to AR1: | | | |MN attaches to AR1: | | |
|acquire MN-ID and profile | | |acquire MN-ID and profile | |
|--RS---------------->| | | |--RS---------------->| | |
| | | | | | | |
|<----------RA(IP1)---| | | |<----------RA(IP1)---| | |
| | | | | | | |
Assigned prefix IP1 | | | Assigned prefix IP1 | | |
IP1 address configuration | | IP1 address configuration | |
| | | | | | | |
skipping to change at page 12, line 36 skipping to change at page 11, line 45
|<-Flow(IP1,IPcn,...)-------------->+ | |<-Flow(IP1,IPcn,...)-------------->+ |
| | | | | | | |
Assigned prefix IP2 | | | Assigned prefix IP2 | | |
IP2 address configuration | | IP2 address configuration | |
| | | | | | | |
Flow(IP1,IPcn) terminates | | Flow(IP1,IPcn) terminates | |
| | | | | | | |
|<-new Flow(IP2,IPcn,...)-----------+---------------------------->| |<-new Flow(IP2,IPcn,...)-----------+---------------------------->|
| | | | | | | |
Figure 6: A flow continues to use the IP prefix from its home network Figure 5: A flow continues to use the IP prefix from its home network
after MN has moved to a new network after MN has moved to a new network
An example call flow in this case is outlined in Figure 5. In this
example, the AR1 plays the role of FM-DP entity and redirects the
traffic (e.g., using an IP tunnel) to AR2. Another solution could be
to place an FM-DP entity closer to the CN network to perform traffic
steering to deviate from default routes (which will bring the packet
to AR1 per default routing). The LM and FM functions are implemented
as shown in Figure 6.
Net1 Net2
+---------------+ +---------------+
|AR1 | |AR2 |
+---------------+ +---------------+
|CPA: | |CPA: |
| | |LM:IP1 at IPa1 |
|---------------| IP1 (anchored at Net1) |---------------|
|DPA(IPa1): | is redirected to Net2 |DPA(IPa2): |
|anchors IP1 | =======> |anchors IP2 |
+---------------+ +---------------+
+...............+ +---------------+
.MN(IP1) . MN moves |MN(IP2,IP1) |
.flow(IP1,...) . =======> |flow(IP1,...) |
. . |flow(IP2,...) |
+...............+ +---------------+
Figure 6: Anchor redirection
Multiple instances of DPAs (at access routers), which are providing Multiple instances of DPAs (at access routers), which are providing
IP prefix to the MNs, are needed to provide distributed mobility IP prefix to the MNs, are needed to provide distributed mobility
anchoring in an appropriate configuration such as those described in anchoring in an appropriate configuration such as those described in
Figure 1 (Section 3.1.1) for network-based distributed mobility or in Figure 1 (Section 3.1.1) for network-based distributed mobility or in
Figure 2 (Section 3.1.2) for client-based distributed mobility. Figure 2 (Section 3.1.2) for client-based distributed mobility.
4.3. Mobility case, anchor relocation 4.3. Mobility case, anchor relocation
We focus next on the case where the mobility anchor (data plane We focus next on the case where the mobility anchor (data plane
function) is changed but binds the MN's transferred IP address/ function) is changed but binds the MN's transferred IP address/
skipping to change at page 13, line 47 skipping to change at page 13, line 36
.MN(IP1) . MN moves |MN(IP2,IP1) | .MN(IP1) . MN moves |MN(IP2,IP1) |
.flow(IP1,...) . =======> |flow(IP1,...) | .flow(IP1,...) . =======> |flow(IP1,...) |
+...............+ +---------------+ +...............+ +---------------+
Figure 7: Anchor mobility Figure 7: Anchor mobility
As an MN with an ongoing session moves to a new network, the flow may As an MN with an ongoing session moves to a new network, the flow may
preserve IP session continuity by moving the anchoring of the preserve IP session continuity by moving the anchoring of the
original IP prefix/address of the flow to the new network. original IP prefix/address of the flow to the new network.
One way to accomplish such move is to use a centralized routing One way to accomplish such a move is to use a centralized routing
protocol, but note that this solution presents some scalability protocol, but such a solution presents some scalability concerns and
concerns and its applicability is typically limited to small its applicability is typically limited to small networks.
networks.
5. Security Considerations 5. Security Considerations
Security protocols and mechanisms are employed to secure the network Security protocols and mechanisms are employed to secure the network
and to make continuous security improvements, and a DMM solution is and to make continuous security improvements, and a DMM solution is
required to support them [RFC7333]. required to support them [RFC7333].
In a DMM deployment [I-D.ietf-dmm-deployment-models] various attacks In a DMM deployment [I-D.ietf-dmm-deployment-models] various attacks
such as impersonation, denial of service, man-in-the-middle attacks such as impersonation, denial of service, man-in-the-middle attacks
need to be prevented. need to be prevented.
skipping to change at page 14, line 39 skipping to change at page 14, line 29
mobility support in enterprise network. These works have been mobility support in enterprise network. These works have been
referenced. While some of these authors have taken the work to referenced. While some of these authors have taken the work to
jointly write this document, others have contributed at least jointly write this document, others have contributed at least
indirectly by writing these drafts. The latter include Philippe indirectly by writing these drafts. The latter include Philippe
Bertin, Dapeng Liu, Satoru Matushima, Pierrick Seite, Jouni Korhonen, Bertin, Dapeng Liu, Satoru Matushima, Pierrick Seite, Jouni Korhonen,
and Sri Gundavelli. and Sri Gundavelli.
Valuable comments have been received from John Kaippallimalil, Valuable comments have been received from John Kaippallimalil,
ChunShan Xiong, and Dapeng Liu. Dirk von Hugo, Byju Pularikkal, ChunShan Xiong, and Dapeng Liu. Dirk von Hugo, Byju Pularikkal,
Pierrick Seite have generously provided careful review with helpful Pierrick Seite have generously provided careful review with helpful
corrections and suggestions. Marco Liebsch also performed a very corrections and suggestions. Marco Liebsch and Lyle Bertz also
detailed and helpful review of this document. performed very detailed and helpful reviews of this document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.bernardos-dmm-pmipv6-dlif] [I-D.bernardos-dmm-pmipv6-dlif]
Bernardos, C., Oliva, A., Giust, F., Zuniga, J., and A. Bernardos, C., Oliva, A., Giust, F., Zuniga, J., and A.
Mourad, "Proxy Mobile IPv6 extensions for Distributed Mourad, "Proxy Mobile IPv6 extensions for Distributed
Mobility Management", draft-bernardos-dmm-pmipv6-dlif-01 Mobility Management", draft-bernardos-dmm-pmipv6-dlif-01
(work in progress), March 2018. (work in progress), March 2018.
skipping to change at page 15, line 19 skipping to change at page 15, line 8
[I-D.ietf-dmm-fpc-cpdp] [I-D.ietf-dmm-fpc-cpdp]
Matsushima, S., Bertz, L., Liebsch, M., Gundavelli, S., Matsushima, S., Bertz, L., Liebsch, M., Gundavelli, S.,
Moses, D., and C. Perkins, "Protocol for Forwarding Policy Moses, D., and C. Perkins, "Protocol for Forwarding Policy
Configuration (FPC) in DMM", draft-ietf-dmm-fpc-cpdp-12 Configuration (FPC) in DMM", draft-ietf-dmm-fpc-cpdp-12
(work in progress), June 2018. (work in progress), June 2018.
[I-D.ietf-dmm-ondemand-mobility] [I-D.ietf-dmm-ondemand-mobility]
Yegin, A., Moses, D., Kweon, K., Lee, J., Park, J., and S. Yegin, A., Moses, D., Kweon, K., Lee, J., Park, J., and S.
Jeon, "On Demand Mobility Management", draft-ietf-dmm- Jeon, "On Demand Mobility Management", draft-ietf-dmm-
ondemand-mobility-14 (work in progress), March 2018. ondemand-mobility-15 (work in progress), July 2018.
[I-D.matsushima-stateless-uplane-vepc] [I-D.matsushima-stateless-uplane-vepc]
Matsushima, S. and R. Wakikawa, "Stateless user-plane Matsushima, S. and R. Wakikawa, "Stateless user-plane
architecture for virtualized EPC (vEPC)", draft- architecture for virtualized EPC (vEPC)", draft-
matsushima-stateless-uplane-vepc-06 (work in progress), matsushima-stateless-uplane-vepc-06 (work in progress),
March 2016. March 2016.
[I-D.mccann-dmm-prefixcost] [I-D.mccann-dmm-prefixcost]
McCann, P. and J. Kaippallimalil, "Communicating Prefix McCann, P. and J. Kaippallimalil, "Communicating Prefix
Cost to Mobile Nodes", draft-mccann-dmm-prefixcost-03 Cost to Mobile Nodes", draft-mccann-dmm-prefixcost-03
 End of changes. 22 change blocks. 
67 lines changed or deleted 76 lines changed or added

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