draft-ietf-dmm-distributed-mobility-anchoring-04.txt   draft-ietf-dmm-distributed-mobility-anchoring-05.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: October 13, 2017 J. Lee Expires: November 10, 2017 J. Lee
Sangmyung University Sangmyung University
S. Jeon S. Jeon
Sungkyunkwan University Sungkyunkwan University
A. Petrescu A. Petrescu
CEA, LIST CEA, LIST
F. Templin F. Templin
Boeing Research and Technology Boeing Research and Technology
April 11, 2017 May 9, 2017
Distributed Mobility Anchoring Distributed Mobility Anchoring
draft-ietf-dmm-distributed-mobility-anchoring-04 draft-ietf-dmm-distributed-mobility-anchoring-05
Abstract Abstract
This document defines distributed mobility anchoring in terms of the This document defines distributed mobility anchoring in terms of the
different configurations, operations and parameters of mobility different configurations, operations and parameters of mobility
functions to provide different IP mobility support for the diverse functions to provide different IP mobility support for the diverse
mobility needs in 5G Wireless and beyond. A network or network slice mobility needs in 5G Wireless and beyond. A network or network slice
may be configured with distributed mobility anchoring functions may be configured with distributed mobility anchoring functions
according to the needs of mobility support. In the distributed according to the needs of mobility support. In the distributed
mobility anchoring environment, multiple anchors are available for mobility anchoring environment, multiple anchors are available for
mid-session switching of an IP prefix anchor. To start a new flow or mid-session switching of an IP prefix anchor. To start a new flow or
to handle a flow not requiring IP session continuity as a mobile node to handle a flow not requiring IP session continuity as a mobile node
moves to a new network, the flow can be started or re-started using a moves to a new network, the flow can be started or re-started using a
new IP prefix which is allocated from and is therefore anchored to new IP address configured from the new IP prefix which is anchored to
the new network. For a flow requiring IP session continuity, the the new network. For a flow requiring IP session continuity, the
anchoring of the prior IP prefix may be moved to the new network. anchoring of the prior IP prefix may be moved to the new network.
The mobility functions and their operations and parameters are The mobility functions and their operations and parameters are
general for different configurations. The mobility signaling may be general for different configurations. The mobility signaling may be
between anchors and nodes in the network in a network-based mobility between anchors and nodes in the network in a network-based mobility
solution. It may also be between the anchors and the mobile node in solution. It may also be between the anchors and the mobile node in
a host-based solution. The mobile node may be a host, but may also a host-based solution. The mobile node may be a host, but may also
be a router carrying a network requiring network mobility support. be a router carrying a network requiring network mobility support.
Status of This Memo Status of This Memo
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 October 13, 2017. This Internet-Draft will expire on November 10, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 35 skipping to change at page 2, line 35
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
3. Distributed Mobility Anchoring . . . . . . . . . . . . . . . 7 3. Distributed Mobility Anchoring . . . . . . . . . . . . . . . 7
3.1. Configurations for Different Networks or Network Slices . 7 3.1. Configurations for Different Networks or Network Slices . 7
3.1.1. Network-based Mobility Support for a Flat Network . . 7 3.1.1. Network-based Mobility Support for a Flat Network . . 7
3.1.2. Network-based Mobility Support for a Hierarchical 3.1.2. Network-based Mobility Support for a Hierarchical
Network . . . . . . . . . . . . . . . . . . . . . . . 9 Network . . . . . . . . . . . . . . . . . . . . . . . 8
3.1.3. Host-based Mobility Support . . . . . . . . . . . . . 11 3.1.3. Host-based Mobility Support . . . . . . . . . . . . . 11
3.1.4. NEtwork MObility (NEMO) Basic Support . . . . . . . . 13 3.1.4. NEtwork MObility (NEMO) Basic Support . . . . . . . . 11
3.2. Operations and Parameters . . . . . . . . . . . . . . . . 15 3.2. Operations and Parameters . . . . . . . . . . . . . . . . 13
3.2.1. Location Management . . . . . . . . . . . . . . . . . 16 3.2.1. Location Management . . . . . . . . . . . . . . . . . 13
3.2.2. Forwarding Management . . . . . . . . . . . . . . . . 18 3.2.2. Forwarding Management . . . . . . . . . . . . . . . . 16
4. IP Mobility Handling in Distributed Anchoring Environments - 4. IP Mobility Handling in Distributed Anchoring Environments -
Mobility Support Only When Needed . . . . . . . . . . . . . . 26 Mobility Support Only When Needed . . . . . . . . . . . . . . 24
4.1. No Need of IP Mobility: Changing to New IP Prefix/Address 27 4.1. No Need of IP Mobility: Changing to New IP Prefix/Address 24
4.1.1. Guidelines for IPv6 Nodes: Changing to New IP 4.1.1. Guidelines for IPv6 Nodes: Changing to New IP
Prefix/Address . . . . . . . . . . . . . . . . . . . 29 Prefix/Address . . . . . . . . . . . . . . . . . . . 26
4.2. Need of IP Mobility . . . . . . . . . . . . . . . . . . . 30 4.2. Need of IP Mobility . . . . . . . . . . . . . . . . . . . 28
4.2.1. Guidelines for IPv6 Nodes: Need of IP Mobility . . . 31 4.2.1. Guidelines for IPv6 Nodes: Need of IP Mobility . . . 29
5. IP Mobility Handling in Distributed Mobility Anchoring 5. IP Mobility Handling in Distributed Mobility Anchoring
Environments - Anchor Switching to the New Network . . . . . 33 Environments - Anchor Switching to the New Network . . . . . 31
5.1. IP Prefix/Address Anchor Switching for Flat Network . . . 33 5.1. IP Prefix/Address Anchor Switching for Flat Network . . . 31
5.1.1. Guidelines for IPv6 Nodes: Switching Anchor for Flat 5.1.1. Guidelines for IPv6 Nodes: Switching Anchor for Flat
Network . . . . . . . . . . . . . . . . . . . . . . . 34 Network . . . . . . . . . . . . . . . . . . . . . . . 32
5.2. IP Prefix/Address Anchor Switching for Flat Network with 5.2. IP Prefix/Address Anchor Switching for Flat Network with
Centralized Control Plane . . . . . . . . . . . . . . . . 36 Centralized Control Plane . . . . . . . . . . . . . . . . 34
5.2.1. Additional Guidelines for IPv6 Nodes: Switching 5.2.1. Additional Guidelines for IPv6 Nodes: Switching
Anchor with Centralized CP . . . . . . . . . . . . . 39 Anchor with Centralized CP . . . . . . . . . . . . . 36
5.3. Hierarchical Network . . . . . . . . . . . . . . . . . . 40 5.3. Hierarchical Network . . . . . . . . . . . . . . . . . . 37
5.3.1. Additional Guidelines for IPv6 Nodes: Hierarchical 5.3.1. Additional Guidelines for IPv6 Nodes: Hierarchical
Network with No Anchor Relocation . . . . . . . . . . 42 Network with No Anchor Relocation . . . . . . . . . . 39
5.4. IP Prefix/Address Anchor Switching for a Hierarchical 5.4. IP Prefix/Address Anchor Switching for a Hierarchical
Network . . . . . . . . . . . . . . . . . . . . . . . . . 42 Network . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.4.1. Additional Guidelines for IPv6 Nodes: Switching 5.4.1. Additional Guidelines for IPv6 Nodes: Switching
Anchor with Hierarchical Network . . . . . . . . . . 45 Anchor with Hierarchical Network . . . . . . . . . . 41
5.5. Network Mobility . . . . . . . . . . . . . . . . . . . . 45 5.5. Network Mobility . . . . . . . . . . . . . . . . . . . . 41
5.5.1. Additional Guidelines for IPv6 Nodes: Network 5.5.1. Additional Guidelines for IPv6 Nodes: Network
mobility . . . . . . . . . . . . . . . . . . . . . . 47 mobility . . . . . . . . . . . . . . . . . . . . . . 43
6. Security Considerations . . . . . . . . . . . . . . . . . . . 48 6. Security Considerations . . . . . . . . . . . . . . . . . . . 44
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 49 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 45
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.1. Normative References . . . . . . . . . . . . . . . . . . 49 9.1. Normative References . . . . . . . . . . . . . . . . . . 45
9.2. Informative References . . . . . . . . . . . . . . . . . 51 9.2. Informative References . . . . . . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48
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. Distributed mobility management solutions do not an optimal route. The traffic of a flow SHOULD then be able to
rely on a centrally deployed mobility anchor in the data plane change from traversing one mobility anchor to traversing another
[Paper-Distributed.Mobility]. As such, the traffic of a flow SHOULD mobility anchor as a mobile node (MN) moves, or when changing
be able to change from traversing one mobility anchor to traversing
another mobility anchor as a mobile node (MN) moves, or when changing
operation and management requirements call for mobility anchor operation and management requirements call for mobility anchor
switching, thus avoiding non-optimal routes. switching, thus avoiding non-optimal routes.
Companion distributed mobility management documents are already Companion distributed mobility management documents are already
addressing the architecture and deployment addressing the architecture and deployment
[I-D.ietf-dmm-deployment-models], source address selection [I-D.ietf-dmm-deployment-models], source address selection
[I-D.ietf-dmm-ondemand-mobility], and control-plane data-plane [I-D.ietf-dmm-ondemand-mobility], and control-plane data-plane
signaling [I-D.ietf-dmm-fpc-cpdp]. Yet in 5G Wireless and beyond, signaling [I-D.ietf-dmm-fpc-cpdp]. Yet in 5G Wireless and beyond,
the mobility requirements are diverse, and IP mobility support is no the mobility requirements are diverse, and IP mobility support is no
longer by default with a one-size-fit-all solution. In different longer by default with a one-size-fit-all solution. In different
networks or network slices, different kinds of mobility support are networks or network slices [I-D.geng-netslices-architecture],
possible depending on the needs. It may not always be obvious on how different kinds of mobility support are possible depending on the
to best configure and use only the needed mobility functions to needs. It may not always be obvious on how to best configure and use
provide the specific mobility support. This draft defines different only the needed mobility functions to provide the specific mobility
configurations, functional operations and parameters for distributed support. This draft defines different configurations, functional
mobility anchoring and explains how to use them to make the route operations and parameters for distributed mobility anchoring and
changes to avoid unnecessarily long routes. explains how to use them to make the route changes to avoid
unnecessarily long routes.
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 separate from data plane. In general, control plane functions may be separate from data
plane functions and be centralized but may also be co-located with plane functions and be centralized but may also be co-located with
the data plane functions at the distributed anchors. Different 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. For instance, the configurations for network-based Section 3.1. For instance, the configurations for network-based
mobility support in a flat network, for network-based mobility mobility support in a flat network, for network-based mobility
support in a hierarchical network, for host-based mobility support, support in a hierarchical network, for host-based mobility support,
and for NEtwork MObility (NEMO) basic support are described and for NEtwork MObility (NEMO) basic support are described
respectively in Section 3.1.1, Section 3.1.2, Section 3.1.3 and respectively in Section 3.1.1, Section 3.1.2, Section 3.1.3 and
Section 3.1.4. Required operations and parameters for distributed Section 3.1.4. Required operations and parameters for distributed
mobility anchoring are presented in Section 3.2. For instance, mobility anchoring are presented in Section 3.2. For instance,
location management is described in Section 3.2.1, forwarding location management is described in Section 3.2.1, forwarding
management is described in Section 3.2.2. management is described in Section 3.2.2.
An MN attached to an access router of a network or network slice may As an MN attaches to an access router and establishes a link between
be allocated an IP prefix which is anchored to that router. It may them, a /64 IPv6 prefix anchored to the router may be assigned to the
then use an IP address configured from this prefix as the source IP link for exclusive use by the MN [RFC6459]. The MN may then
address to run a flow with its correspondent node (CN). When there configure a global IPv6 address from this prefix and use it as the
are multiple mobility anchors, an address selection for a given flow source IP address in a flow to communicate with with its
is first required before the flow is initiated. Using an anchor in correspondent node (CN). When there are multiple mobility anchors,
an MN's network of attachment has the advantage that the packets can an address selection for a given flow is first required before the
simply be forwarded according to the forwarding table. Although the flow is initiated. Using an anchor in an MN's network of attachment
anchor is in the MN's network of attachment when the flow was has the advantage that the packets can simply be forwarded according
initiated, the MN may later move to another network, so that the IP to the forwarding table. However, after the flow has been initiated,
address no longer belongs to the current network of attachment of the the MN may later move to another network, so that the IP address no
MN. longer belongs to the current network of attachment of the MN.
Whether the flow needs IP session continuity will determine how to Whether the flow needs IP session continuity will determine how to
ensure that the IP address of the flow will be anchored to the new ensure that the IP address of the flow will be anchored to the new
network of attachment. If the ongoing IP flow can cope with an IP network of attachment. If the ongoing IP flow can cope with an IP
prefix/address change, the flow can be reinitiated with a new IP prefix/address change, the flow can be reinitiated with a new IP
address anchored in the new network as shown in Section 4.1. On the address anchored in the new network as shown in Section 4.1. On the
other hand, if the ongoing IP flow cannot cope with such change, other hand, if the ongoing IP flow cannot cope with such change,
mobility support is needed as shown in Section 4.2. A network or mobility support is needed as shown in Section 4.2. A network or
network slice supporting a mix of flows both requiring and not network slice supporting a mix of flows both requiring and not
requiring IP mobility support will need to distinguish these flows. requiring IP mobility support will need to distinguish these flows.
skipping to change at page 5, line 31 skipping to change at page 5, line 31
base specification [RFC6275], the Proxy Mobile IPv6 (PMIPv6) base specification [RFC6275], the Proxy Mobile IPv6 (PMIPv6)
specification [RFC5213], the "Mobility Related Terminologies" specification [RFC5213], the "Mobility Related Terminologies"
[RFC3753], and the DMM current practices and gap analysis [RFC7429]. [RFC3753], and the DMM current practices and gap analysis [RFC7429].
These include terms such as mobile node (MN), correspondent node These include terms such as mobile node (MN), correspondent node
(CN), home agent (HA), home address (HoA), care-of-address (CoA), (CN), home agent (HA), home address (HoA), care-of-address (CoA),
local mobility anchor (LMA), and mobile access gateway (MAG). local mobility anchor (LMA), and mobile access gateway (MAG).
In addition, this document uses the following terms: In addition, this document uses the following terms:
Home network of an application session or a home address: the Home network of an application session or a home address: the
network that has allocated the HoA used for the session identifier network that has assigned the HoA used as the session identifier
by the application running in an MN. The MN may be running by the application running in an MN. The MN may be running
multiple application sessions, and each of these sessions can have multiple application sessions, and each of these sessions can have
a different home network. a different home network.
IP prefix/address anchoring: An IP prefix, i.e., Home Network Prefix IP prefix/address anchoring: An IP prefix, i.e., Home Network Prefix
(HNP), or address, i.e., HoA, allocated to an MN is topologically (HNP), or address, i.e., HoA, assigned for use by an MN is
anchored to an anchor node when the anchor node is able to topologically anchored to an anchor node when the anchor node is
advertise a connected route into the routing infrastructure for able to advertise a connected route into the routing
the allocated IP prefix. infrastructure for the assigned IP prefix.
Location Management (LM) function: managing and keeping track of the Location Management (LM) function: managing and keeping track of the
internetwork location of an MN. The location information may be a internetwork location of an MN. The location information may be a
binding of the advertised IP address/prefix, e.g., HoA or HNP, to binding of the advertised IP address/prefix, e.g., HoA or HNP, to
the IP routing address of the MN or of a node that can forward the IP routing address of the MN or of a node that can forward
packets destined to the MN. 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) carrying 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 IP prefix include the mobile network prefix (MNP), which is the aggregate IP
delegated to the MR. The MNP is allocated to the MNNs in the prefix delegated to the MR to assign IP prefixes for use by the
mobile network. MNNs in the mobile network.
LM is a control plane function. LM is a control plane function.
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). (LMc) and a Location Management server (LMs).
Optionally, there may be a Location Management proxy (LMp) between Optionally, there may be a Location Management proxy (LMp) between
LMc and LMs. LMc and LMs.
With separation of control plane and data plane, the LM function With separation of control plane and data plane, the LM function
is in the control plane. It may be a logical function at the is in the control plane. It may be a logical function at the
control plane node, control plane anchor, or mobility controller. control plane node, control plane anchor, or mobility controller.
It may be distributed or centralized. It may be distributed or centralized.
Forwarding Management (FM) function: packet interception and Forwarding Management (FM) function: packet interception and
forwarding to/from the IP address/prefix assigned to the MN, based forwarding to/from the IP address/prefix assigned for use by the
on the internetwork location information, either to the MN, based on the internetwork location information, either to the
destination or to some other network element that knows how to destination or to some other network element that knows how to
forward the packets to their destination. forward the packets to their destination.
This function may be used to achieve traffic indirection. With This function may be used to achieve traffic indirection. With
separation of control plane and data plane, the FM function may separation of control plane and data plane, the FM function may
split into a FM function in the data plane (FM-DP) and a FM split into a FM function in the data plane (FM-DP) and a FM
function in the control plane (FM-CP). function in the control plane (FM-CP).
FM-DP may be distributed with distributed mobility management. It FM-DP may be distributed with distributed mobility management. It
may be a function in a data plane anchor or data plane node. may be a function in a data plane anchor or data plane node.
skipping to change at page 7, line 29 skipping to change at page 7, line 29
The configurations also differ depending on the desired mobility The configurations also differ depending on the desired mobility
supports: network-based mobility support for a flat network in supports: network-based mobility support for a flat network in
Section 3.1.1, network-based mobility support for a hierarchical Section 3.1.1, network-based mobility support for a hierarchical
network in Section 3.1.2, host-based mobility support in network in Section 3.1.2, host-based mobility support in
Section 3.1.3, and NEtwork MObility (NEMO) based support in Section 3.1.3, and NEtwork MObility (NEMO) based support in
Section 3.1.4. Section 3.1.4.
3.1.1. Network-based Mobility Support for a Flat Network 3.1.1. Network-based Mobility Support for a Flat Network
Figure 1 shows two different configurations of network-based mobility Figure 1 shows two different configurations of network-based
management for a flat network. distributed mobility management for a flat network.
The features common to both Figures 1(a) and 1(b) are:
dmm:1 There are multiple instances of DPA, each with an FM-DP
function.
dmm:2 The control plane may either be distributed (not shown) or
centralized. The CPA may co-locate with DPA or may separate.
When the CPA, each with an FM-CP function, is co-located with
the distributed DPA there will be multiple instances of the
co-located CPA and DPA (not shown).
dmm:3 An IP prefix/address IP1, which is anchored to the DPA with
the IP prefix/address IPa1, is assigned for use by AN MN. The
MN uses IP1 to communicate with a CN not shown in the figure.
The flow of this communication session is shown as flow(IP1,
...), meaning it uses IP1 and other parameters.
(a) (b) (a) (b)
+-----+ +-----+
|LMs | |LMs |
+-----+ +-----+
+------------+ +------------+ +------------+ +------------+
|CPA: | |CPA: | |CPA: | |CPA: |
|FM-CP, LM | |FM-CP, LMc | |FM-CP, LM | |FM-CP, LMc |
+------------+ +------------+ +------------+ +------------+
+------------+ +------------+ +------------+ +------------+ +------------+ +------------+ +------------+ +------------+
|DPA(IPa1): | |DPA(IPa2): | |DPA(IPa1): | |DPA(IPa2): | |DPA(IPa1): | |DPA(IPa2): | |DPA(IPa1): | |DPA(IPa2): |
|anchors IP1 | |anchors IP2 | ... |anchors IP1 | |anchors IP2 | ... |anchors IP1 | |anchors IP2 | ... |anchors IP1 | |anchors IP2 | ...
|FM-DP | |FM-DP | |FM-DP | |FM-DP | |FM-DP | |FM-DP | |FM-DP | |FM-DP |
+------------+ +------------+ +------------+ +------------+ +------------+ +------------+ +------------+ +------------+
skipping to change at page 8, line 29 skipping to change at page 8, line 28
+------------+ +------------+ +------------+ +------------+
|MN(IP1) | |MN(IP1) | |MN(IP1) | |MN(IP1) |
|flow(IP1,..)| |flow(IP1,..)| |flow(IP1,..)| |flow(IP1,..)|
+------------+ +------------+ +------------+ +------------+
Figure 1. Configurations of network-based mobility management for a Figure 1. Configurations of network-based mobility management for a
flat network (a) FM-CP and LM at CPA, FM-DP at DPA; (b) Separate LMs, flat network (a) FM-CP and LM at CPA, FM-DP at DPA; (b) Separate LMs,
FM-CP and LMc at CPA, FM-DP at DPA. FM-CP and LMc at CPA, FM-DP at DPA.
Figure 1 also shows a distributed mobility anchoring environment with In Figure 1(a), LM is at the CPA. Then LM may be distributed or
multiple instances of the DPA. centralized according to whether the CPA is distributed (not shown)
or centralized.
There is an FM-DP function at each of the distributed DPA.
The control plane may either be distributed (not shown) or
centralized. When the CPA is co-located with the distributed DPA
there will be multiple instances of the co-located CPA and DPA (not
shown).
There is an FM-CP function at the CPA.
An MN is allocated an IP prefix/address IP1 which is anchored to the
DPA with the IP prefix/address IPa1. The MN uses IP1 to communicate
with a CN not shown in the figure. The flow of this communication
session is shown as flow(IP1, ...) which uses IP1 and other
parameters.
In Figure 1(a), LM and FM-CP are co-located at the CPA.
Then LM may be distributed or centralized according to whether the
CPA is distributed (not shown) or centralized.
Figure 1(b) differs from Figure 1(a) in that the LM function is split Figure 1(b) differs from Figure 1(a) in that the LM function is split
into a server LMs and a client LMc. into a separate server LMs and a client LMc at the CPA. Then, the
LMs may be centralized whereas the LMc may be distributed or
LMc and FM-CP are co-located at the CPA.
The LMs may be centralized whereas the LMc may be distributed or
centralized according to whether the CPA is distributed (not shown) centralized according to whether the CPA is distributed (not shown)
or centralized. or centralized.
3.1.2. Network-based Mobility Support for a Hierarchical Network 3.1.2. Network-based Mobility Support for a Hierarchical Network
Figure 2 shows two different configurations of network-based mobility Figure 2 shows two different configurations of network-based mobility
management for a hierarchical network. management for a hierarchical network.
(a) (a)
+------------+ +------------+
skipping to change at page 10, line 38 skipping to change at page 10, line 37
+------------+ +------------+ +------------+ +------------+
|MN(IP1) | |MN(IP2) | |MN(IP1) | |MN(IP2) |
|flow(IP1,..)| |flow(IP2,..)| |flow(IP1,..)| |flow(IP2,..)|
+------------+ +------------+ +------------+ +------------+
Figure 2(b). Configurations of network-based mobility management for Figure 2(b). Configurations of network-based mobility management for
a hierarchical network with separate LMs, FM-CP and LMp at CPA, FM-DP a hierarchical network with separate LMs, FM-CP and LMp at CPA, FM-DP
at DPA; FM-CP and LMc at CPN, FM-DP at DPN. at DPA; FM-CP and LMc at CPN, FM-DP at DPN.
Figures 2 also shows a distributed mobility anchoring environment In addition to the dmm feature already described in Figure 1,
with multiple instances of the DPA. Figure 2 shows that there may be multiple instances of DPN, each with
an FM-DP function, for each DPA in the hierarchy. Also when the CPN,
In the hierarchy, there may be multiple DPNs for each DPA. each with an FM-CP function, is co-located with the distributed DPN
there will be multiple instances of the co-located CPN and DPN (not
There is FM-DP at each of the distributed DPA and at each of the shown).
distributed DPN.
The control plane may either be distributed (not shown) or
centralized.
When the CPA is co-located with the distributed DPA there will be
multiple instances of the co-located CPA and DPA (not shown).
When the CPN is co-located with the distributed DPN there will be
multiple instances of the co-located CPN and DPN (not shown).
There is FM-CP function at the CPA and at the CPN.
MN is allocated an IP prefix/address IP1 which is anchored to the DPA
with the IP prefix/address IPa1. It is using IP1 to communicate with
a correspondent node (CN) not shown in the figure. The flow of this
communication session is shown as flow(IP1, ...) which uses IP1 and
other parameters.
In Figure 2(a), LMs and FM-CP are at the CPA. In addition, there are
FM-CP and LMc at the CPN.
LMs may be distributed or centralized according to whether the CPA is In Figure 2(a), LMs is at the CPA and LMc is at the CPN. Then, LMs
distributed or centralized. The CPA may co-locate with DPA or may may be distributed or centralized according to whether the CPA is
separate. distributed or centralized.
Figure 2(b) differs from Figure 2(a) in that the LMs is separated Figure 2(b) differs from Figure 2(a) in that the LMs is separated
out, and a proxy LMp is added between the LMs and LMc. out, and a proxy LMp at the CPA is added between the seaparate LMs
and LMc at the CPN. Then, LMs may be centralized whereas the LMp may
LMp and FM-CP are co-located at the CPA. be distributed or centralized according to whether the CPA is
distributed or centralized.
FM-CP and LMc are co-located at the CPN.
The LMs may be centralized whereas the LMp may be distributed or
centralized according to whether the CPA is distributed or
centralized.
3.1.3. Host-based Mobility Support 3.1.3. Host-based Mobility Support
Host-based variants of the mobility function configurations from Host-based variants of the mobility function configurations from
Figures 2(a) and 2(b) are respectively shown in Figures 3(a) and 3(b) Figures 2(a) and 2(b) are respectively shown in Figures 3(a) and 3(b)
where the role to perform mobility functions by CPN and DPN are now where the role to perform mobility functions by CPN and DPN are now
taken by the MN. The MN then needs to possess the mobility functions taken by the MN. The MN then needs to possess the mobility functions
FM and LMc. FM and LMc.
(a) (b) (a) (b)
skipping to change at page 12, line 32 skipping to change at page 11, line 39
|flow(IP1,..)| |flow(IP1,..)| |flow(IP1,..)| |flow(IP1,..)|
|FM, LMc | |FM, LMc | |FM, LMc | |FM, LMc |
+------------+ +------------+ +------------+ +------------+
Figure 3. Configurations of host-based mobility management (a) FM-CP Figure 3. Configurations of host-based mobility management (a) FM-CP
and LMs at CPA, FM-DP at DPA, FM and LMc at MN; (b) Separate LMs, FM- and LMs at CPA, FM-DP at DPA, FM and LMc at MN; (b) Separate LMs, FM-
CP and LMp at CPA, FM-DP at DPA, FM and LMc at MN. CP and LMp at CPA, FM-DP at DPA, FM and LMc at MN.
Figure 3 shows 2 configurations of host-based mobility management Figure 3 shows 2 configurations of host-based mobility management
with multiple instances of DPA for a distributed mobility anchoring with multiple instances of DPA for a distributed mobility anchoring
environment. environment. Figures 3(a) and 3(b) can be obtained by simply
collapsing CPN, DPN and MN from the respective Figures 2(a) and 2(b)
There is an FM-DP function at each of the distributed DPA. into the MN in Figure 3 which now possesses the mobility functions FM
and LMc that were performed previously by the CPN and the DPN.
The control plane may either be distributed (not shown) or
centralized.
When the CPA is co-located with the distributed DPA there will be
multiple instances of the co-located CPA and DPA (not shown).
There is an FM-CP function at the CPA.
The MN possesses the mobility functions such as FM and LMc.
The MN is allocated an IP prefix/address IP1 which is anchored to the
DPA with the IP prefix/address IPa1. It is using IP1 to communicate
with a CN not shown in the figure. The flow of this communication
session is shown as flow(IP1, ...) which uses IP1 and other
parameters.
In Figure 3(a), LMs and FM-CP are co-located at the CPA.
The LMs may be distributed or centralized according to whether the
CPA is distributed (not shown) or centralized.
Figure 3(b) differs from Figure 3(a) in that the LMs is separated out
and the proxy LMp is added between the LMs and LMc.
LMp and FM-CP are co-located at the CPA.
The LMs may be centralized whereas the LMp may be distributed or
centralized according to whether the CPA is distributed (not shown)
or centralized.
3.1.4. NEtwork MObility (NEMO) Basic Support 3.1.4. NEtwork MObility (NEMO) Basic Support
Figure 4 shows two configurations of NEMO basic support for a mobile Figure 4 shows two configurations of NEMO basic support for a mobile
router. router.
(a) (b) (a) (b)
+-----+ +-----+
|LMs | |LMs |
+-----+ +-----+
skipping to change at page 14, line 39 skipping to change at page 12, line 38
|MNN(IPn1) | |MNN(IPn1) | |MNN(IPn1) | |MNN(IPn1) |
|flow(IPn1,.)| |flow(IPn1,.)| |flow(IPn1,.)| |flow(IPn1,.)|
+------------+ +------------+ +------------+ +------------+
Figure 4. Configurations of NEMO basic support for a MR. (a) FM-CP Figure 4. Configurations of NEMO basic support for a MR. (a) FM-CP
and LMs at CPA, FM-DP at DPA, FM and LMc at MR; (b) Separate LMs, FM- and LMs at CPA, FM-DP at DPA, FM and LMc at MR; (b) Separate LMs, FM-
CP and LMp at CPA, FM-DP at DPA, FM and LMc at MR. CP and LMp at CPA, FM-DP at DPA, FM and LMc at MR.
Figure 4 shows 2 configurations of host-based mobility management for Figure 4 shows 2 configurations of host-based mobility management for
a MR with multiple instances of DPA for a distributed mobility a MR with multiple instances of DPA for a distributed mobility
anchoring environment. anchoring environment. Figures 4(a) and 4(b) can be obtained by
simply changing the MN from the respective Figures 3(a) and 3(b) into
There is an FM-DP function at each of the distributed DPA. the MR carrying a mobile network consisting of mobile network nodes
(MNNs) in Figure 4.
The control plane may either be distributed (not shown) or
centralized.
When the CPA is co-located with the distributed DPA there will be
multiple instances of the co-located CPA and DPA (not shown).
There is FM-CP function at the CPA.
The MR possesses the mobility functions FM and LMc.
MR is allocated an IP prefix/address IP1 which is anchored to the DPA
with the IP prefix/address IPa1.
A mobile network node (MNN) in the mobile network is allocated an IP
prefix/address IPn1 which is anchored to the MR with the IP prefix/
address IP1.
The MNN is using IPn1 to communicate with a correspondent node (CN)
not shown in the figure. The flow of this communication session is
shown as flow(IPn1, ...) which uses IPn1 and other parameters.
In Figure 4(a), LMs and FM-CP are co-located at the CPA.
The LMs may be distributed or centralized according to whether the
CPA is distributed (not shown) or centralized.
Figure 4(b) differs from Figure 4(a) in that the LMs is separated out
and the proxy LMp is added between the LMs and LMc.
LMp and FM-CP are co-located at the CPA. An IP prefix/address IPn1 anchored to the MR is assigned for use by
the MNN in the mobile network. The MNN uses IPn1 to communicate with
a correspondent node (CN) not shown in the figure. The flow of this
communication session is shown as flow(IPn1, ...), meaning it uses
IPn1 and other parameters.
The LMs may be centralized whereas the LMp may be distributed or To enable the MR to anchor and to assign the IP prefix IPn1, the DPA
centralized according to whether the CPA is distributed (not shown) delegates the prefix using DHCPv6-PD to the MR.
or centralized.
3.2. Operations and Parameters 3.2. Operations and Parameters
The operations of distributed mobility anchoring are defined in order The operations of distributed mobility anchoring are defined in order
that they may work together in expected manners to produce a that they might work together to produce a distributed mobility
distributed mobility solution. The needed information is passed as solution. The needed information is passed as mobility message
mobility message parameters, which must be protected in terms of parameters, which must be protected in terms of integrity. Some
integrity. Some parameters may require a means to support privacy of parameters may require a means to support privacy of an MN or MR.
an MN or MR.
The mobility needs in 5G Wireless and beyond are diverse. Therefore The mobility needs in 5G Wireless and beyond are diverse. Therefore
operations needed to enable different distributed mobility solutions operations needed to enable different distributed mobility solutions
in different distributed mobility anchoring configurations are in different distributed mobility anchoring configurations are
extensive as illustrated below. It is however not necessary for extensive as illustrated below. It is however not necessary for
every distributed mobility solution to exhibit all the operations every distributed mobility solution to exhibit all the operations
listed in this section. A given distributed mobility solution may listed in this section. A given distributed mobility solution may
exhibit only those operations needed. exhibit only those operations needed.
3.2.1. Location Management 3.2.1. Location Management
skipping to change at page 18, line 40 skipping to change at page 16, line 10
LM-svr:3 LMs may reply to a peer LMs about location information for LM-svr:3 LMs may reply to a peer LMs about location information for
a prefix of MN. a prefix of MN.
Parameters: Parameters:
- IP prefix of MN: integrity support required and privacy - IP prefix of MN: integrity support required and privacy
support may be required, support may be required,
- IP address of FM-DP/DPA/DPN to forward the packets of the - IP address of FM-DP/DPA/DPN to forward the packets of the
flow: integrity support required. flow: integrity support required.
The parameters indicated above are only the minimal. In a specific The list above only gives the minimal set of the required parameters.
mobility protocol, additional parameters should be added as needed. In a specific mobility protocol, additional parameters should be
Examples of these additional parameters are those passed in the added as needed. Examples of these additional parameters are those
mobility options of the mobility header for MIPv6 [RFC6275] and for passed in the mobility options of the mobility header for MIPv6
PMIPv6 [RFC5213]. [RFC6275] and for PMIPv6 [RFC5213].
3.2.2. Forwarding Management 3.2.2. Forwarding Management
Forwarding management configurations: Forwarding management configurations:
FM-cfg: As shown in Section 3.1: FM-cfg: As shown in Section 3.1:
FM-CP may be implemented at CPA, CPN, MN depending on the FM-CP may be implemented at CPA, CPN, MN depending on the
configuration chosen. configuration chosen.
skipping to change at page 21, line 5 skipping to change at page 18, line 23
changes to the forwarding table and indirection such as changes to the forwarding table and indirection such as
tunneling, rewriting packet header, or NAT. tunneling, rewriting packet header, or NAT.
Note: An emphasis in this document in distributed mobility Note: An emphasis in this document in distributed mobility
anchoring is to explain the use of multiple anchors to anchoring is to explain the use of multiple anchors to
avoid unnecessarily long route which may be encountered in avoid unnecessarily long route which may be encountered in
centralized mobility anchoring. It is therefore not the centralized mobility anchoring. It is therefore not the
emphasis of this document on which particular mechanism to emphasis of this document on which particular mechanism to
choose from. choose from.
FM-path-tbl:4 With forwarding table updates, changes to the FM-path-tbl:4 The objective of forwarding table updates is to change
forwarding table are needed at each of the affected the forwarding path so that the packets in the flow
forwarding switches in order to change the forwarding will be forwarded from the CN to the new AR instead of
path of the packets for the flow from that originally the home network anchor or previous AR. Each of the
between the CN and the home network anchor or previous affected forwarding switches will need appropriate
AR to that between the CN and the new AR. changes to its forwarding table.
Specifically, such forwarding table updates may Specifically, such forwarding table updates may
include: (1) addition of forwarding table entries include: (1) addition of forwarding table entries
needed to forward the packets destined to the MN to needed to forward the packets destined to the MN to
the new AR; (2) deletion of forwarding table entries the new AR; (2) deletion of forwarding table entries
to forward the packets destined to the MN to the home to forward the packets destined to the MN to the home
network anchor or to the previous AR. network anchor or to the previous AR.
FM-path-tbl:5 Forwarding table updates may be triggered using FM-path-tbl:5 Forwarding table updates may be triggered using
DHCPv6-PD prefix delegation to change the role of IP DHCPv6-PD prefix delegation to change the role of IP
skipping to change at page 26, line 46 skipping to change at page 24, line 19
provided by default. The LM and FM functions in the different provided by default. The LM and FM functions in the different
configurations shown in Section 3.1 are then utilized only when configurations shown in Section 3.1 are then utilized only when
needed. needed.
A straightforward choice of mobility anchoring is for a flow to use A straightforward choice of mobility anchoring is for a flow to use
the IP prefix of the network to which the MN is attached when the the IP prefix of the network to which the MN is attached when the
flow is initiated [I-D.seite-dmm-dma]. flow is initiated [I-D.seite-dmm-dma].
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 an
MN attaches to a network (Net1) or moves to a new network (Net2), it MN attaches to a network (Net1) or moves to a new network (Net2), an
is allocated an IP prefix from the attached network. In addition to IP prefix from the attached network is assigned to the MN's
configuring new link-local addresses, the MN configures from this interface. In addition to configuring new link-local addresses, the
prefix an IP address which is typically a dynamic IP address. It MN configures from this prefix an IP address which is typically a
then uses this IP address when a flow is initiated. Packets to the dynamic IP address. It then uses this IP address when a flow is
MN in this flow are simply forwarded according to the forwarding initiated. Packets to the MN in this flow are simply forwarded
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
different access networks. The network may advertise these prefixes different access networks. The network may advertise these prefixes
with cost options [I-D.mccann-dmm-prefixcost] so that the mobile node with cost options [I-D.mccann-dmm-prefixcost] so that the mobile node
may choose the one with the least cost. In addition, these IP may choose the one with the least cost. In addition, these IP
prefixes/addresses may be of different types regarding whether prefixes/addresses may be of different types regarding whether
mobility support is needed [I-D.ietf-dmm-ondemand-mobility]. A flow mobility support is needed [I-D.ietf-dmm-ondemand-mobility]. A flow
will need to choose the appropriate one according to whether it needs will need to choose the appropriate one according to whether it needs
IP mobility support. IP mobility support.
skipping to change at page 27, line 49 skipping to change at page 25, line 31
Figure 5. Changing to the new IP prefix/address. MN running a flow Figure 5. Changing to the new IP prefix/address. MN running a flow
using IP1 in a network Net1 changes to running a flow using IP2 in using IP1 in a network Net1 changes to running a flow using IP2 in
Net2. Net2.
When there is no need to provide IP mobility to a flow, the flow may When there is no need to provide IP mobility to a flow, the flow may
use a new IP address acquired from a new network as the MN moves to use a new IP address acquired from a new network as the MN moves to
the new network. the new network.
Regardless of whether IP mobility is needed, if the flow has Regardless of whether IP mobility is needed, if the flow has
terminated before the MN moves to a new network, the flow may terminated before the MN moves to a new network, the flow may
subsequently restart using the new IP address allocated from the new subsequently restart using the new IP address assigned from the new
network. network.
When IP session continuity is needed, even if a flow is ongoing as When IP session continuity is needed, even if a flow is ongoing as
the MN moves, it may still be desirable for the flow to change to the MN moves, it may still be desirable for the flow to change to
using the new IP prefix configured in the new network. The flow may using the new IP prefix configured in the new network. The flow may
then close and then restart using a new IP address configured in the then close and then restart using a new IP address configured in the
new network. Such a change in the IP address of the flow may be new network. Such a change in the IP address of the flow may be
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.
skipping to change at page 28, line 29 skipping to change at page 26, line 12
An example call flow is outlined in Figure 6. An example call flow is outlined in Figure 6.
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)---| | |
| | | | | | | |
Allocated prefix IP1 | | | Assigned prefix IP1 | | |
IP1 address configuration | | IP1 address configuration | |
| | | | | | | |
|<-Flow(IP1,IPcn,...)-+--------------------------------------------->| |<-Flow(IP1,IPcn,...)-+--------------------------------------------->|
| | | | | | | |
|MN detaches from AR1 | | | |MN detaches from AR1 | | |
|MN attaches to AR2 | | | |MN attaches to AR2 | | |
| | | | | | | |
|--RS------------------------------>| | |--RS------------------------------>| |
| | | | | | | |
|<--------------RA(IP2)-------------| | |<--------------RA(IP2)-------------| |
| | | | | | | |
Allocated prefix IP2 | | | Assigned prefix IP2 | | |
IP2 address configuration | | IP2 address configuration | |
| | | | | | | |
|<-new Flow(IP2,IPcn,...)-----------+------------------------------->| |<-new Flow(IP2,IPcn,...)-----------+------------------------------->|
| | | | | | | |
Figure 6. Re-starting a flow to use the IP prefix allocated from the Figure 6. Re-starting a flow to use the IP prefix assigned from the
network at which the MN is attached. network at which the MN is attached.
4.1.1. Guidelines for IPv6 Nodes: Changing to New IP Prefix/Address 4.1.1. Guidelines for IPv6 Nodes: Changing to New IP Prefix/Address
A network or network slice may not need IP mobility support. For A network or network slice may not need IP mobility support. For
example, a network slice for stationary sensors only will never example, a network slice for stationary sensors only will never
encounter mobility. encounter mobility.
The standard functions in IPv6 already include dropping the old IPv6 The standard functions in IPv6 already include dropping the old IPv6
prefix/address and acquiring new IPv6 prefix/address when the node prefix/address and acquiring new IPv6 prefix/address when the node
skipping to change at page 30, line 27 skipping to change at page 28, line 11
is need of IP mobility support for a flow that does not. When the is need of IP mobility support for a flow that does not. When the
flow needs IP mobility support, the list of guidelines will continue flow needs IP mobility support, the list of guidelines will continue
in Section 4.2.1. in Section 4.2.1.
4.2. Need of IP Mobility 4.2. Need of IP Mobility
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. The mobility support may be provided by IP Section 3.1 are utilized. The mobility support may be provided by IP
prefix anchor switching to the new network to be described in prefix anchor switching to the new network to be described in
Section 5 or by using other mobility management methods Section 5 or by using other mobility management methods
([Paper-Distributed.Mobility.PMIP] and ([Paper-Distributed.Mobility], [Paper-Distributed.Mobility.PMIP] and
[Paper-Distributed.Mobility.Review]). Then the flow may continue to [Paper-Distributed.Mobility.Review]). Then the flow may continue to
use the IP prefix from the prior network of attachment. Yet some use the IP prefix from the prior network of attachment. Yet some
time later, the user application for the flow may be closed. If the time later, the user application for the flow may be closed. If the
application is started again, the new flow may not need to use the application is started again, the new flow may not need to use the
prior network's IP address to avoid having to invoke IP mobility prior network's IP address to avoid having to invoke IP mobility
support. This may be the case where a dynamic IP prefix/address support. This may be the case where a dynamic IP prefix/address
rather than a permanent one is used. The flow may then use the new rather than a permanent one is used. The flow may then use the new
IP prefix in the network where the flow is being initiated. Routing IP prefix in the network where the flow is being initiated. Routing
is again kept simpler without employing IP mobility and will remain is again kept simpler without employing IP mobility and will remain
so as long as the MN which is now in the new network has not moved so as long as the MN which is now in the new network has not moved
skipping to change at page 31, line 12 skipping to change at page 29, line 12
An example call flow in this case is outlined in Figure 7. An example call flow in this case is outlined in Figure 7.
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)---| | |
| | | | | | | |
Allocated prefix IP1 | | | Assigned prefix IP1 | | |
IP1 address configuration | | IP1 address configuration | |
| | | | | | | |
|<-Flow(IP1,IPcn,...)-+--------------------------------------------->| |<-Flow(IP1,IPcn,...)-+--------------------------------------------->|
| | | | | | | |
|MN detach from AR1 | | | |MN detach from AR1 | | |
|MN attach to AR2 | | | |MN attach to AR2 | | |
| | | | | | | |
|--RS------------------------------>| | |--RS------------------------------>| |
IP mobility support such as that described in next sub-section IP mobility support such as that described in next sub-section
|<--------------RA(IP2,IP1)---------| | |<--------------RA(IP2,IP1)---------| |
| | | | | | | |
|<-Flow(IP1,IPcn,...)---------------+------------------------------->| |<-Flow(IP1,IPcn,...)---------------+------------------------------->|
| | | | | | | |
Allocated 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 7. A flow continues to use the IP prefix from its home Figure 7. A flow continues to use the IP prefix from its home
network after MN has moved to a new network. network after MN has moved to a new network.
skipping to change at page 32, line 5 skipping to change at page 30, line 5
follows: follows:
GL-cfg:2 Multiple instances of DPAs (at access routers) which are GL-cfg:2 Multiple instances of DPAs (at access routers) which are
providing IP prefix to the MNs are needed to provide providing IP prefix to the MNs are needed to provide
distributed mobility anchoring in an appropriate distributed mobility anchoring in an appropriate
configuration such as those described in Figure 1 configuration such as those described in Figure 1
(Section 3.1.1) for network-based distributed mobility or (Section 3.1.1) for network-based distributed mobility or
in Figure 3 (Section 3.1.3) for host-based distributed in Figure 3 (Section 3.1.3) for host-based distributed
mobility. mobility.
At the appropriate IPv6 nodes (CPA, DPA, CPN, DPN) the The appropriate IPv6 nodes (CPA, DPA, CPN, DPN) have to
mobility functions LM and FM as described respectively in implement the mobility functions LM and FM as described
LM-cfg and FM-cfg in Section 3.2 according to the respectively in LM-cfg and FM-cfg in Section 3.2 according
configuration chosen have to be implemented. to the configuration chosen.
The guidelines of distributed mobility for the IPv6 nodes in a The guidelines of distributed mobility for the IPv6 nodes in a
network or network slice supporting a mix of flows both requiring and network or network slice supporting a mix of flows both requiring and
not requiring distributed mobility support had begun with those given not requiring distributed mobility support had begun with those given
as GL-mix in Section 4.1.1 and continue as follows: as GL-mix in Section 4.1.1 and continue as follows:
GL-mix:5 The distributed anchors may need to message with each GL-mix:5 The distributed anchors may need to message with each
other. When such messaging is needed, the anchors may need other. When such messaging is needed, the anchors may need
to discover each other as described in the FM operations to discover each other as described in the FM operations
and mobility message parameters (FM-find) in Section 3.2.2. and mobility message parameters (FM-find) in Section 3.2.2.
skipping to change at page 34, line 50 skipping to change at page 32, line 50
The configuration guideline for a flat network or network slice The configuration guideline for a flat network or network slice
supporting a mix of flows both requiring and not requiring IP supporting a mix of flows both requiring and not requiring IP
mobility support is: mobility support is:
GL-cfg:3 Multiple instances of DPAs (at access routers) which are GL-cfg:3 Multiple instances of DPAs (at access routers) which are
providing IP prefix to the MNs are needed to provide providing IP prefix to the MNs are needed to provide
distributed mobility anchoring according to Figure 1(a) or distributed mobility anchoring according to Figure 1(a) or
Figure 1(b) in Section 3.1 for a flat network. Figure 1(b) in Section 3.1 for a flat network.
At the appropriate IPv6 nodes (CPA, DPA) the mobility The appropriate IPv6 nodes (CPA, DPA) have to implement the
functions LM and FM as described respectively in LM-cfg:1 mobility functions LM and FM as described respectively in
or LM-cfg:2 and FM-cfg:1 in Section 3.2 have to be LM-cfg:1 or LM-cfg:2 and FM-cfg:1 in Section 3.2.
implemented.
The guidelines (GL-mix) in Section 4.1.1 and in Section 4.2.1 for the The guidelines (GL-mix) in Section 4.1.1 and in Section 4.2.1 for the
IPv6 nodes for a network or network slice supporting a mix of flows IPv6 nodes for a network or network slice supporting a mix of flows
both requiring and not requiring IP mobility support apply here. In both requiring and not requiring IP mobility support apply here. In
addition, the following are required. addition, the following are required.
GL-switch:1 The location management provides information about which GL-switch:1 The location management provides information about which
IP prefix from an AR in the original network is being IP prefix from an AR in the original network is being
used by a flow in which AR in a new network. Such used by a flow in which AR in a new network. Such
information needs to be deleted or updated when such information needs to be deleted or updated when such
skipping to change at page 37, line 29 skipping to change at page 35, line 5
+...............+ +---------------+ +...............+ +---------------+
.MN(IP1) . MN moves |MN(IP2,IP1) | .MN(IP1) . MN moves |MN(IP2,IP1) |
.flow(IP1,...) . =======> |flow(IP1,...) | .flow(IP1,...) . =======> |flow(IP1,...) |
+...............+ +---------------+ +...............+ +---------------+
Figure 9. IP prefix/address anchor switching to the new network with Figure 9. IP prefix/address anchor switching to the new network with
the LM and the FM-CP in a centralized control plane whereas the FM- the LM and the FM-CP in a centralized control plane whereas the FM-
DPs are distributed. DPs are distributed.
The example call flow in Figure 10 shows that MN is allocated IP1 The example call flow in Figure 10 shows that IP1 is assigned to MN
when it attaches to the AR1 A flow running in MN and needing IP when the MN attaches to the AR1 A flow running in MN and needing IP
mobility may continue to use the previous IP prefix by moving the mobility may continue to use the previous IP prefix by moving the
anchoring of the IP prefix to the new network. Yet a new flow to be anchoring of the IP prefix to the new network. Yet a new flow to be
initiated in the new network may simply use a new IP prefix allocated initiated in the new network may simply use a new IP prefix assigned
from the new network. from the new network.
MN AR1 AR2 DHCPv6 Servers CN MN AR1 AR2 DHCPv6 Servers 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)---| | | |
| | | Allocate MN:IP1 | | | | Assign MN:IP1 |
IP addr config | | | | IP addr config | | | |
| | | | | | | | | |
|<-Flow(IP1,IPcn,...)-+--------------------------------------------->| |<-Flow(IP1,IPcn,...)-+--------------------------------------------->|
| | | | | | | | | |
|MN detach from AR1 | | | | |MN detach from AR1 | | | |
|MN attach to AR2 | | | | |MN attach to AR2 | | | |
| | | | | | | | | |
|--RS------------------------------>| | | |--RS------------------------------>| | |
| | | | | | | | | |
| |------DHCPv6 release-------------->| | | |------DHCPv6 release-------------->| |
| | | | | | | | | |
| | |--DHCPv6 PD request->| | | | |--DHCPv6 PD request->| |
| | |<-DHCPv6 PD reply--->| | | | |<-DHCPv6 PD reply--->| |
| | | | | | | | | |
| forwarding table updates | | | forwarding table updates | |
| | | | | | | | | |
|<--------------RA(IP2,IP1)---------| | | |<--------------RA(IP2,IP1)---------| | |
| | | Allocate MN:IP2 | | | | Assign MN:IP2 |
IP addr config | | | | IP addr config | | | |
| | | | | | | | | |
|<-Flow(IP1,IPcn,...)---------------+------------------------------->| |<-Flow(IP1,IPcn,...)---------------+------------------------------->|
| | | | | | | | | |
| Flow(IP1,IPcn,...) terminates | | | | Flow(IP1,IPcn,...) terminates | | |
| | | | | | | | | |
| | DHCPv6-PD timeout | | | | DHCPv6-PD timeout | |
| | | | | | | | | |
| forwarding table updates | | | forwarding table updates | |
| | | | | | | | | |
| | | | | | | | | |
|<-new Flow(IP2,IPcn,...)-----------+------------------------------->| |<-new Flow(IP2,IPcn,...)-----------+------------------------------->|
| | | | | | | | | |
Figure 10. DMM solution. MN with flow using IP1 in Net1 continues Figure 10. DMM solution. MN with flow using IP1 in Net1 continues
to run the flow using IP1 as it moves to Net2. to run the flow using IP1 as it moves to Net2.
As the MN moves from AR1 to AR2, the AR1 as a DHCPv6 client may send As the MN moves from AR1 to AR2, the AR1 as a DHCPv6 client may send
a DHCPv6 release message to release the IP1. It is now necessary for a DHCPv6 release message to release the IP1. It is now necessary for
AR2 to learn the IP prefix of the MN from the previous network so AR2 to learn the IP prefix of the MN from the previous network so
that it will be possible for Net2 to allocate both the previous that it will be possible for Net2 to assign both the previous network
network prefix and the new network prefix. The network may learn the prefix and the new network prefix. The network may learn the
previous prefix in different methods. For example, the MN may previous prefix in different methods. For example, the MN may
provide its previous network prefix information by including it to provide its previous network prefix information by including it to
the RS message [I-D.jhlee-dmm-dnpp]. the RS message [I-D.jhlee-dmm-dnpp].
Knowing that MN is using IP1, the AR2 sends to a DHCPv6 server a Knowing that MN is using IP1, the AR2 sends to a DHCPv6 server a
DHCPv6-PD request to move the IP1 to AR2. The server sends to AR2 a DHCPv6-PD request to move the IP1 to AR2. The server sends to AR2 a
DHCPv6-PD reply to move the IP1. Then forwarding tables updates will DHCPv6-PD reply to move the IP1. Then forwarding tables updates will
take place here. take place here.
In addition, the MN also needs a new IP in the new network. The AR2 In addition, the MN also needs a new IP in the new network. The AR2
may now send RA to the MN with prefix information that includes IP1 may now send RA to the MN with prefix information that includes IP1
and IP2. The MN may then continue to use IP1. In addition, the MN and IP2. The MN may then continue to use IP1. In addition, the
is allocated the prefix IP2 with which it may configure its IP prefix IP2 is assigned to the MN which may configure the IP addresses
addresses. Now for flows using IP1, packets destined to IP1 will be of its interface. Now for flows using IP1, packets destined to IP1
forwarded to the MN via AR2. will be forwarded to the MN via AR2.
As such flows have terminated and DHCPv6-PD has timed out, IP1 goes As such flows have terminated and DHCPv6-PD has timed out, IP1 goes
back to Net1. MN will then be left with IP2 only, which it will use back to Net1. MN will then be left with IP2 only, which it will use
when it now starts a new flow. when it now starts a new flow.
5.2.1. Additional Guidelines for IPv6 Nodes: Switching Anchor with 5.2.1. Additional Guidelines for IPv6 Nodes: Switching Anchor with
Centralized CP Centralized CP
The configuration guideline for a flat network or network slice with The configuration guideline for a flat network or network slice with
centralized control plane and supporting a mix of flows both centralized control plane and supporting a mix of flows both
requiring and not requiring IP mobility support is: requiring and not requiring IP mobility support is:
GL-cfg:4 Multiple instances of DPAs (at access routers) which are GL-cfg:4 Multiple instances of DPAs (at access routers) which are
providing IP prefix to the MNs are needed to provide providing IP prefix to the MNs are needed to provide
distributed mobility anchoring according to Figure 1(a) or distributed mobility anchoring according to Figure 1(a) or
Figure 1(b) in Section 3.1 with centralized control plane Figure 1(b) in Section 3.1 with centralized control plane
for a flat network. for a flat network.
At the appropriate IPv6 nodes (CPA, DPA) the mobility At the appropriate IPv6 nodes (CPA, DPA) have to implement
functions LM and FM as described respectively in LM-cfg:1 the mobility functions LM and FM as described respectively
or LM-cfg:2 and FM-cfg:1 in Section 3.2 have to be in LM-cfg:1 or LM-cfg:2 and FM-cfg:1 in Section 3.2.
implemented.
The guidelines (GL-mix) in Section 4.1.1 and in Section 4.2.1 for the The guidelines (GL-mix) in Section 4.1.1 and in Section 4.2.1 for the
IPv6 nodes for a network or network slice supporting a mix of flows IPv6 nodes for a network or network slice supporting a mix of flows
both requiring and not requiring IP mobility support apply here. The both requiring and not requiring IP mobility support apply here. The
guidelines (GL-mix) in Section 5.1.1 for moving anchoring for a flat guidelines (GL-mix) in Section 5.1.1 for moving anchoring for a flat
network also apply here. In addition, the following are required. network also apply here. In addition, the following are required.
GL-switch:5 It was already mentioned that the anchor operations to GL-switch:5 It was already mentioned that the anchor operations to
properly forward the packets for a flow as described in properly forward the packets for a flow as described in
the FM operations and mobility message parameters in FM- the FM operations and mobility message parameters in FM-
skipping to change at page 41, line 5 skipping to change at page 38, line 10
distributed mobility management will be deferred to Section 5.4. distributed mobility management will be deferred to Section 5.4.
In this distributed mobility configuration, a mobility event In this distributed mobility configuration, a mobility event
involving change of FW only but not of AR as shown in Figure 11 may involving change of FW only but not of AR as shown in Figure 11 may
still belong to centralized mobility management and may be supported still belong to centralized mobility management and may be supported
using PMIPv6. This configuration of network-based mobility is also using PMIPv6. This configuration of network-based mobility is also
applicable to host-based mobility with the modification for the MN applicable to host-based mobility with the modification for the MN
directly taking the role of DPN and CPN, and the corresponding directly taking the role of DPN and CPN, and the corresponding
centralized mobility event may be supported using MIPv6. centralized mobility event may be supported using MIPv6.
In Figure 11, the IP prefix allocated to the MN is anchored at the In Figure 11, the IP prefix assigned to the MN is anchored at the
access router (AR) supporting indirection to the old FW to which the access router (AR) supporting indirection to the old FW to which the
MN was originally attached as well as to the new FW to which the MN MN was originally attached as well as to the new FW to which the MN
has moved. has moved.
The realization of LM may be the binding between the IP prefix/ The realization of LM may be the binding between the IP prefix/
address of the flow used by the MN and the IP address of the DPN to address of the flow used by the MN and the IP address of the DPN to
which MN has moved. The implementation of FM to enable change of FW which MN has moved. The implementation of FM to enable change of FW
without changing AR may be accomplished using tunneling between the without changing AR may be accomplished using tunneling between the
AR and the FW as described in [I-D.korhonen-dmm-local-prefix] and in AR and the FW as described in [I-D.korhonen-dmm-local-prefix] and in
[I-D.templin-aerolink] or using some other L2 mobility mechanism. [I-D.templin-aerolink] or using some other L2 mobility mechanism.
Net1 Net2 Net1 Net2
+----------------------------------------------------------------------+ +----------------------------------------------------------------------+
| CPA,CPN: | | CPA,CPN: LM:IP1 at IPn2 |
| LM:IP1 at IPn2 | | FM-CP |
| FM-CP |
+----------------------------------------------------------------------+ +----------------------------------------------------------------------+
+---------------+ +---------------+
|AR1 | |AR1 |
+---------------+ +---------------+
|DPA(IPa1): | |DPA(IPa1): |
|anchors IP1 | |anchors IP1 |
|FM-DP | |FM-DP |
+---------------+ +---------------+
skipping to change at page 41, line 45 skipping to change at page 38, line 49
|DPN(IPn1): | -------> |DPN(IPn2): | |DPN(IPn1): | -------> |DPN(IPn2): |
|FM-DP | |FM-DP | |FM-DP | |FM-DP |
+---------------+ +---------------+ +---------------+ +---------------+
+...............+ +---------------+ +...............+ +---------------+
.MN(IP1) . MN moves |MN(IP2) | .MN(IP1) . MN moves |MN(IP2) |
.flow(IP1,...) . =======> |flow(IP1,...) | .flow(IP1,...) . =======> |flow(IP1,...) |
+...............+ +---------------+ +...............+ +---------------+
Figure 11. Mobility without involving change of IP anchoring in a Figure 11. Mobility without involving change of IP anchoring in a
network in which the IP prefix allocated to the MN is anchored at an network in which the IP prefix assigned to the MN is anchored at an
AR which is hierarchically above multiple FWs to which the MN may AR which is hierarchically above multiple FWs to which the MN may
connect. connect.
5.3.1. Additional Guidelines for IPv6 Nodes: Hierarchical Network with 5.3.1. Additional Guidelines for IPv6 Nodes: Hierarchical Network with
No Anchor Relocation No Anchor Relocation
The configuration guideline for a hierarchical network or network The configuration guideline for a hierarchical network or network
slice with centralized control plane and supporting a mix of flows slice with centralized control plane and supporting a mix of flows
both requiring and not requiring IP mobility support is: both requiring and not requiring IP mobility support is:
GL-cfg:5 Multiple instances of DPAs (at access routers) which are GL-cfg:5 Multiple instances of DPAs (at access routers) which are
providing IP prefix to the MNs are needed to provide providing IP prefix to the MNs are needed to provide
distributed mobility anchoring according to Figure 2(a) or distributed mobility anchoring according to Figure 2(a) or
Figure 2(b)in Section 3.1.2 with centralized control plane Figure 2(b)in Section 3.1.2 with centralized control plane
for a hierarchical network. for a hierarchical network.
At the appropriate IPv6 nodes (CPA, DPA) the mobility The appropriate IPv6 nodes (CPA, DPA) have to implement the
functions LM and FM as described respectively in LM-cfg:3 mobility functions LM and FM as described respectively in
or LM-cfg:4 and FM-cfg:2 in Section 3.2 have to be LM-cfg:3 or LM-cfg:4 and FM-cfg:2 in Section 3.2.
implemented.
Even when the mobility event does not involve change of anchor, it is Even when the mobility event does not involve change of anchor, it is
still necessary to distinguish whether a flow needs IP mobility still necessary to distinguish whether a flow needs IP mobility
support. support.
The GL-mix guidelines in Section 4.1.1 and in Section 4.2.1 for the The GL-mix guidelines in Section 4.1.1 and in Section 4.2.1 for the
IPv6 nodes for a network or network slice supporting a mix of flows IPv6 nodes for a network or network slice supporting a mix of flows
both requiring and not requiring IP mobility support apply here. In both requiring and not requiring IP mobility support apply here. In
addition, the following are required. addition, the following are required.
skipping to change at page 44, line 7 skipping to change at page 40, line 12
supports forwarding to the DPN at each of a number of forwarding supports forwarding to the DPN at each of a number of forwarding
switches (FWs). switches (FWs).
A distributed mobility event in this configuration involves change A distributed mobility event in this configuration involves change
from a previous DPN which is hierarchically under the previous DPA to from a previous DPN which is hierarchically under the previous DPA to
a new DPN which is hierarchically under a new DPA. Such an event a new DPN which is hierarchically under a new DPA. Such an event
involving change of both DPA and DPN is shown in Figure 12. involving change of both DPA and DPN is shown in Figure 12.
Net1 Net2 Net1 Net2
+----------------------------------------------------------------------+ +----------------------------------------------------------------------+
| CPA,CPN,Aggregate Router: | | CPA,CPN,Aggregate Router: LM:IP1 at IPn2 at IPa2 |
| LM:IP1 at IPn2 at IPa2 | | FM-CP |
| FM-CP |
+----------------------------------------------------------------------+ +----------------------------------------------------------------------+
+-----------------+ +-----------------+
|Aggregate Router | |Aggregate Router |
+-----------------+ +-----------------+
|FM-DP | |FM-DP |
+-----------------+ +-----------------+
+---------------+ +---------------+ +---------------+ +---------------+
|AR1 | |AR2 | |AR1 | |AR2 |
skipping to change at page 44, line 39 skipping to change at page 40, line 43
|DPN(IPn1): | -------> |DPN(IPn2): | |DPN(IPn1): | -------> |DPN(IPn2): |
|FM-DP | |FM-DP | |FM-DP | |FM-DP |
+---------------+ +---------------+ +---------------+ +---------------+
+...............+ +---------------+ +...............+ +---------------+
.MN(IP1) . MN moves |MN(IP2,IP1) | .MN(IP1) . MN moves |MN(IP2,IP1) |
.flow(IP1,...) . =======> |flow(IP1,...) | .flow(IP1,...) . =======> |flow(IP1,...) |
+...............+ +---------------+ +...............+ +---------------+
Figure 12. Mobility involving change of IP anchoring in a network Figure 12. Mobility involving change of IP anchoring in a network
with hierarchy in which the IP prefix allocated to the MN is anchored with hierarchy in which the IP prefix assigned to the MN is anchored
at an Edge Router supporting multiple access routers to which the MN at an Edge Router supporting multiple access routers to which the MN
may connect. may connect.
This deployment case involves both a change of anchor from AR1 to AR2 This deployment case involves both a change of anchor from AR1 to AR2
and a network hierarchy AR-FW. It can be realized by a combination and a network hierarchy AR-FW. It can be realized by a combination
of relocating the IP prefix/address anchoring from AR1 to AR2 with of relocating the IP prefix/address anchoring from AR1 to AR2 with
the mechanism as described in Section 5.2 and then forwarding the the mechanism as described in Section 5.2 and then forwarding the
packets with network hierarchy AR-FW as described in Section 5.3. packets with network hierarchy AR-FW as described in Section 5.3.
To change the anchoring of IP1, AR1 acting as a DHCPv6-PD client may To change the anchoring of IP1, AR1 acting as a DHCPv6-PD client may
skipping to change at page 45, line 35 skipping to change at page 41, line 35
the new DPN as described in Section 5.3.1 apply as well. the new DPN as described in Section 5.3.1 apply as well.
5.5. Network Mobility 5.5. Network Mobility
The configuration for network mobility has been shown in Figures 4(a) The configuration for network mobility has been shown in Figures 4(a)
and 4(b) in Section 3.1.4. Again, with centralized control plane, and 4(b) in Section 3.1.4. Again, with centralized control plane,
CPA, with the associated LM and FM-CP are all co-located. There are CPA, with the associated LM and FM-CP are all co-located. There are
multiple DPAs (each with FM-DP) in the data plane in distributed multiple DPAs (each with FM-DP) in the data plane in distributed
mobility anchoring. The MR possesses the mobility functions FM and mobility anchoring. The MR possesses the mobility functions FM and
LMc. The IP prefix IPn1 is delegated to the MR, to which an MNN is LMc. The IP prefix IPn1 is delegated to the MR, to which an MNN is
attached and is allocated with an IP address from IPn1. attached and has an IP address from IPn1 assigned to its interface.
Figure 13 shows a distributed mobility event in a hierarchical Figure 13 shows a distributed mobility event in a hierarchical
network with a centralized control plane involving a change of network with a centralized control plane involving a change of
attachment of the MR from a previous DPA to a new DPA while the MNN attachment of the MR from a previous DPA to a new DPA while the MNN
is attached to the MR and therefore moves with the MR. is attached to the MR and therefore moves with the MR.
Net1 Net2 Net1 Net2
+----------------------------------------------------------------------+ +----------------------------------------------------------------------+
| CPA,Aggregate Router: | | CPA,Aggregate Router: LM:IP1 at IPa2; IPn1 at IP1 |
| LM:IP1 at IPa2; IPn1 at IP1 | | FM-CP, LM |
| FM-CP, LM |
+----------------------------------------------------------------------+ +----------------------------------------------------------------------+
+-----------------+ +-----------------+
|Aggregate Router | |Aggregate Router |
+-----------------+ +-----------------+
|FM-DP | |FM-DP |
+-----------------+ +-----------------+
+---------------+ +---------------+ +---------------+ +---------------+
|AR1 | |AR2 | |AR1 | |AR2 |
skipping to change at page 47, line 17 skipping to change at page 43, line 15
5.5.1. Additional Guidelines for IPv6 Nodes: Network mobility 5.5.1. Additional Guidelines for IPv6 Nodes: Network mobility
The configuration guideline for a network or network slice with The configuration guideline for a network or network slice with
centralized control plane to provide network mobility is: centralized control plane to provide network mobility is:
GL-cfg:6 Multiple instances of DPAs (at access routers) which are GL-cfg:6 Multiple instances of DPAs (at access routers) which are
providing IP prefix of the MRs are needed to provide providing IP prefix of the MRs are needed to provide
distributed mobility anchoring according to Figure 4(a) or distributed mobility anchoring according to Figure 4(a) or
Figure 4(b) in Section 3.1. Figure 4(b) in Section 3.1.
At the appropriate IPv6 nodes (CPA, DPA) the mobility The appropriate IPv6 nodes (CPA, DPA) have to implement the
functions LM and FM as described respectively in LM-cfg:3 mobility functions LM and FM as described respectively in
or LM-cfg:4 and FM-cfg:4 in Section 3.2 have to be LM-cfg:3 or LM-cfg:4 and FM-cfg:4 in Section 3.2.
implemented.
The GL-mix guidelines in Section 4.1.1 and in Section 4.2.1 for the The GL-mix guidelines in Section 4.1.1 and in Section 4.2.1 for the
IPv6 nodes for a network or network slice supporting a mix of flows IPv6 nodes for a network or network slice supporting a mix of flows
both requiring and not requiring IP mobility support apply here. both requiring and not requiring IP mobility support apply here.
Here, because the MN is a MR, the following guideline is added: Here, because the MN is a MR, the following guideline is added:
GL-mix:11 There are no flows requiring network mobility support when GL-mix:11 There are no flows requiring network mobility support when
there are no MNN attaching to the MR. Here there are also there are no MNN attaching to the MR. Here there are also
no MNN using a prefix delegated to the MR. Therefore the no MNN using a prefix delegated to the MR. Therefore the
skipping to change at page 49, line 9 skipping to change at page 45, line 4
Section 3.2. Here the mobility message parameters used in DMM must Section 3.2. Here the mobility message parameters used in DMM must
be protected, and some parameters require means to support MN and MR be protected, and some parameters require means to support MN and MR
privacy. The security considerations are also described in the privacy. The security considerations are also described in the
guidelines for IPv6 nodes in various subsections in Section 4, and guidelines for IPv6 nodes in various subsections in Section 4, and
Section 5. Section 5.
The IP address anchoring of an IP prefix is moved from one network to The IP address anchoring of an IP prefix is moved from one network to
another network to support IP mobility Section 5.1. As is considered another network to support IP mobility Section 5.1. As is considered
in the guidelines for IPv6 nodes in Section 5.1.1, the security in the guidelines for IPv6 nodes in Section 5.1.1, the security
management function needs to enable the use in the new network of management function needs to enable the use in the new network of
attachment the IP prefix allocated from another network. Yet it must attachment the IP prefix assigned from another network. Yet it must
do so without compromising on the needed security to prevent the do so without compromising on the needed security to prevent the
possible misuse of an IP prefix belonging to another network. possible misuse of an IP prefix belonging to another network.
In network mobility, the MNN using an IP prefix allocated to it from In network mobility, the MNN using an IP prefix assigned to it from
the MR when the MR was in a prior network moves with the MR to a new the MR when the MR was in a prior network moves with the MR to a new
network Section 5.5. As is considered in the guidelines for IPv6 network Section 5.5. As is considered in the guidelines for IPv6
nodes in Section 5.5.1 to support IP mobility for an ongoing flow, nodes in Section 5.5.1 to support IP mobility for an ongoing flow,
the security management function needs to enable the continued use of the security management function needs to enable the continued use of
this IP prefix by the MNN with MR in the new network of attachment. this IP prefix by the MNN with MR in the new network of attachment.
Yet it must do so without compromising on the needed security to Yet it must do so without compromising on the needed security to
prevent the possible misuse of an IP prefix belonging to another prevent the possible misuse of an IP prefix belonging to another
network. network.
7. IANA Considerations 7. IANA Considerations
skipping to change at page 49, line 39 skipping to change at page 45, line 34
This document has benefited from other work on mobility solutions This document has benefited from other work on mobility solutions
using BGP update, on mobility support in SDN network, on providing using BGP update, on mobility support in SDN network, on providing
mobility support only when needed, and on mobility support in mobility support only when needed, and on mobility support in
enterprise network. These works have been referenced. While some of enterprise network. These works have been referenced. While some of
these authors have taken the work to jointly write this document, these authors have taken the work to jointly write this document,
others have contributed at least indirectly by writing these drafts. others have contributed at least indirectly by writing these drafts.
The latter include Philippe Bertin, Dapeng Liu, Satoru Matushima, The latter include Philippe Bertin, Dapeng Liu, Satoru Matushima,
Peter McCann, Pierrick Seite, Jouni Korhonen, and Sri Gundavelli. Peter McCann, Pierrick Seite, Jouni Korhonen, 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 has generously ChunShan Xiong, and Dapeng Liu. Dirk von Hugo, Byju Pularikkal,
provided careful review with helpful corrections and suggestions. Pierrick Seite have generously provided careful review with helpful
corrections and suggestions.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.geng-netslices-architecture]
67, 4., Bryant, S., and J. Dong, "Network Slicing
Architecture", draft-geng-netslices-architecture-00 (work
in progress), March 2017.
[I-D.ietf-dmm-deployment-models] [I-D.ietf-dmm-deployment-models]
Gundavelli, S. and S. Jeon, "DMM Deployment Models and Gundavelli, S. and S. Jeon, "DMM Deployment Models and
Architectural Considerations", draft-ietf-dmm-deployment- Architectural Considerations", draft-ietf-dmm-deployment-
models-01 (work in progress), February 2017. models-01 (work in progress), February 2017.
[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-07 Configuration (FPC) in DMM", draft-ietf-dmm-fpc-cpdp-07
(work in progress), March 2017. (work in progress), March 2017.
skipping to change at page 51, line 28 skipping to change at page 47, line 28
[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
RFC 5213, DOI 10.17487/RFC5213, August 2008, RFC 5213, DOI 10.17487/RFC5213, August 2008,
<http://www.rfc-editor.org/info/rfc5213>. <http://www.rfc-editor.org/info/rfc5213>.
[RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
2011, <http://www.rfc-editor.org/info/rfc6275>. 2011, <http://www.rfc-editor.org/info/rfc6275>.
[RFC6459] Korhonen, J., Ed., Soininen, J., Patil, B., Savolainen,
T., Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation
Partnership Project (3GPP) Evolved Packet System (EPS)",
RFC 6459, DOI 10.17487/RFC6459, January 2012,
<http://www.rfc-editor.org/info/rfc6459>.
[RFC7077] Krishnan, S., Gundavelli, S., Liebsch, M., Yokota, H., and [RFC7077] Krishnan, S., Gundavelli, S., Liebsch, M., Yokota, H., and
J. Korhonen, "Update Notifications for Proxy Mobile IPv6", J. Korhonen, "Update Notifications for Proxy Mobile IPv6",
RFC 7077, DOI 10.17487/RFC7077, November 2013, RFC 7077, DOI 10.17487/RFC7077, November 2013,
<http://www.rfc-editor.org/info/rfc7077>. <http://www.rfc-editor.org/info/rfc7077>.
[RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J.
Korhonen, "Requirements for Distributed Mobility Korhonen, "Requirements for Distributed Mobility
Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, Management", RFC 7333, DOI 10.17487/RFC7333, August 2014,
<http://www.rfc-editor.org/info/rfc7333>. <http://www.rfc-editor.org/info/rfc7333>.
 End of changes. 70 change blocks. 
284 lines changed or deleted 200 lines changed or added

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