--- 1/draft-ietf-dmm-distributed-mobility-anchoring-04.txt 2017-05-09 21:13:10.422265252 -0700 +++ 2/draft-ietf-dmm-distributed-mobility-anchoring-05.txt 2017-05-09 21:13:10.526267733 -0700 @@ -1,40 +1,40 @@ DMM H. Chan, Ed. Internet-Draft X. Wei Intended status: Informational Huawei Technologies -Expires: October 13, 2017 J. Lee +Expires: November 10, 2017 J. Lee Sangmyung University S. Jeon Sungkyunkwan University A. Petrescu CEA, LIST F. Templin Boeing Research and Technology - April 11, 2017 + May 9, 2017 Distributed Mobility Anchoring - draft-ietf-dmm-distributed-mobility-anchoring-04 + draft-ietf-dmm-distributed-mobility-anchoring-05 Abstract This document defines distributed mobility anchoring in terms of the different configurations, operations and parameters of mobility functions to provide different IP mobility support for the diverse mobility needs in 5G Wireless and beyond. A network or network slice may be configured with distributed mobility anchoring functions according to the needs of mobility support. In the distributed mobility anchoring environment, multiple anchors are available for 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 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 anchoring of the prior IP prefix may be moved to the new network. The mobility functions and their operations and parameters are general for different configurations. The mobility signaling may be 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 a host-based solution. The mobile node may be a host, but may also be a router carrying a network requiring network mobility support. Status of This Memo @@ -45,21 +45,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -70,115 +70,114 @@ described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5 3. Distributed Mobility Anchoring . . . . . . . . . . . . . . . 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.2. Network-based Mobility Support for a Hierarchical - Network . . . . . . . . . . . . . . . . . . . . . . . 9 + Network . . . . . . . . . . . . . . . . . . . . . . . 8 3.1.3. Host-based Mobility Support . . . . . . . . . . . . . 11 - 3.1.4. NEtwork MObility (NEMO) Basic Support . . . . . . . . 13 - 3.2. Operations and Parameters . . . . . . . . . . . . . . . . 15 - 3.2.1. Location Management . . . . . . . . . . . . . . . . . 16 - 3.2.2. Forwarding Management . . . . . . . . . . . . . . . . 18 + 3.1.4. NEtwork MObility (NEMO) Basic Support . . . . . . . . 11 + 3.2. Operations and Parameters . . . . . . . . . . . . . . . . 13 + 3.2.1. Location Management . . . . . . . . . . . . . . . . . 13 + 3.2.2. Forwarding Management . . . . . . . . . . . . . . . . 16 4. IP Mobility Handling in Distributed Anchoring Environments - - Mobility Support Only When Needed . . . . . . . . . . . . . . 26 - 4.1. No Need of IP Mobility: Changing to New IP Prefix/Address 27 + Mobility Support Only When Needed . . . . . . . . . . . . . . 24 + 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 - Prefix/Address . . . . . . . . . . . . . . . . . . . 29 - 4.2. Need of IP Mobility . . . . . . . . . . . . . . . . . . . 30 - 4.2.1. Guidelines for IPv6 Nodes: Need of IP Mobility . . . 31 + Prefix/Address . . . . . . . . . . . . . . . . . . . 26 + 4.2. Need of IP Mobility . . . . . . . . . . . . . . . . . . . 28 + 4.2.1. Guidelines for IPv6 Nodes: Need of IP Mobility . . . 29 5. IP Mobility Handling in Distributed Mobility Anchoring - Environments - Anchor Switching to the New Network . . . . . 33 - 5.1. IP Prefix/Address Anchor Switching for Flat Network . . . 33 + Environments - Anchor Switching to the New Network . . . . . 31 + 5.1. IP Prefix/Address Anchor Switching for Flat Network . . . 31 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 - Centralized Control Plane . . . . . . . . . . . . . . . . 36 + Centralized Control Plane . . . . . . . . . . . . . . . . 34 5.2.1. Additional Guidelines for IPv6 Nodes: Switching - Anchor with Centralized CP . . . . . . . . . . . . . 39 - 5.3. Hierarchical Network . . . . . . . . . . . . . . . . . . 40 + Anchor with Centralized CP . . . . . . . . . . . . . 36 + 5.3. Hierarchical Network . . . . . . . . . . . . . . . . . . 37 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 - Network . . . . . . . . . . . . . . . . . . . . . . . . . 42 + Network . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.4.1. Additional Guidelines for IPv6 Nodes: Switching - Anchor with Hierarchical Network . . . . . . . . . . 45 - 5.5. Network Mobility . . . . . . . . . . . . . . . . . . . . 45 + Anchor with Hierarchical Network . . . . . . . . . . 41 + 5.5. Network Mobility . . . . . . . . . . . . . . . . . . . . 41 5.5.1. Additional Guidelines for IPv6 Nodes: Network - mobility . . . . . . . . . . . . . . . . . . . . . . 47 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 48 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 - 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 49 - 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 - 9.1. Normative References . . . . . . . . . . . . . . . . . . 49 - 9.2. Informative References . . . . . . . . . . . . . . . . . 51 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 52 + mobility . . . . . . . . . . . . . . . . . . . . . . 43 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 44 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 + 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 45 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 45 + 9.1. Normative References . . . . . . . . . . . . . . . . . . 45 + 9.2. Informative References . . . . . . . . . . . . . . . . . 48 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48 1. Introduction A key requirement in distributed mobility management [RFC7333] is to enable traffic to avoid traversing a single mobility anchor far from - an optimal route. Distributed mobility management solutions do not - rely on a centrally deployed mobility anchor in the data plane - [Paper-Distributed.Mobility]. As such, the traffic of a flow SHOULD - be able to change from traversing one mobility anchor to traversing - another mobility anchor as a mobile node (MN) moves, or when changing + an optimal route. The traffic of a flow SHOULD then 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 switching, thus avoiding non-optimal routes. Companion distributed mobility management documents are already addressing the architecture and deployment [I-D.ietf-dmm-deployment-models], source address selection [I-D.ietf-dmm-ondemand-mobility], and control-plane data-plane signaling [I-D.ietf-dmm-fpc-cpdp]. Yet in 5G Wireless and beyond, the mobility requirements are diverse, and IP mobility support is no longer by default with a one-size-fit-all solution. In different - networks or network slices, different kinds of mobility support are - possible depending on the needs. It may not always be obvious on how - to best configure and use only the needed mobility functions to - provide the specific mobility support. This draft defines different - configurations, functional operations and parameters for distributed - mobility anchoring and explains how to use them to make the route - changes to avoid unnecessarily long routes. + networks or network slices [I-D.geng-netslices-architecture], + different kinds of mobility support are possible depending on the + needs. It may not always be obvious on how to best configure and use + only the needed mobility functions to provide the specific mobility + support. This draft defines different configurations, functional + operations and parameters for distributed mobility anchoring and + explains how to use them to make the route changes to avoid + unnecessarily long routes. Distributed mobility anchoring employs multiple anchors in the data plane. In general, control plane functions may be separate from data plane functions and be centralized but may also be co-located with the data plane functions at the distributed anchors. Different configurations of distributed mobility anchoring are described in Section 3.1. For instance, the configurations for network-based mobility support in a flat network, for network-based mobility support in a hierarchical network, for host-based mobility support, and for NEtwork MObility (NEMO) basic support are described 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 mobility anchoring are presented in Section 3.2. For instance, location management is described in Section 3.2.1, forwarding management is described in Section 3.2.2. - An MN attached to an access router of a network or network slice may - be allocated an IP prefix which is anchored to that router. It may - then use an IP address configured from this prefix as the source IP - address to run a flow with its correspondent node (CN). When there - are multiple mobility anchors, an address selection for a given flow - is first required before the flow is initiated. Using an anchor in - an MN's network of attachment has the advantage that the packets can - simply be forwarded according to the forwarding table. Although the - anchor is in the MN's network of attachment when the flow was - initiated, the MN may later move to another network, so that the IP - address no longer belongs to the current network of attachment of the - MN. + As an MN attaches to an access router and establishes a link between + them, a /64 IPv6 prefix anchored to the router may be assigned to the + link for exclusive use by the MN [RFC6459]. The MN may then + configure a global IPv6 address from this prefix and use it as the + source IP address in a flow to communicate with with its + correspondent node (CN). When there are multiple mobility anchors, + an address selection for a given flow is first required before the + flow is initiated. Using an anchor in an MN's network of attachment + has the advantage that the packets can simply be forwarded according + to the forwarding table. However, after the flow has been initiated, + the MN may later move to another network, so that the IP address no + longer belongs to the current network of attachment of the MN. 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 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 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, mobility support is needed as shown in Section 4.2. A network or network slice supporting a mix of flows both requiring and not requiring IP mobility support will need to distinguish these flows. @@ -213,61 +212,61 @@ base specification [RFC6275], the Proxy Mobile IPv6 (PMIPv6) specification [RFC5213], the "Mobility Related Terminologies" [RFC3753], and the DMM current practices and gap analysis [RFC7429]. These include terms such as mobile node (MN), correspondent node (CN), home agent (HA), home address (HoA), care-of-address (CoA), local mobility anchor (LMA), and mobile access gateway (MAG). In addition, this document uses the following terms: 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 multiple application sessions, and each of these sessions can have a different home network. IP prefix/address anchoring: An IP prefix, i.e., Home Network Prefix - (HNP), or address, i.e., HoA, allocated to an MN is topologically - anchored to an anchor node when the anchor node is able to - advertise a connected route into the routing infrastructure for - the allocated IP prefix. + (HNP), or address, i.e., HoA, assigned for use by an MN is + topologically anchored to an anchor node when the anchor node is + able to advertise a connected route into the routing + infrastructure for the assigned IP prefix. Location Management (LM) function: managing and keeping track of the internetwork location of an MN. The location information may be a 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 packets destined to the MN. When the MN is a mobile router (MR) carrying a mobile network of mobile network nodes (MNN), the location information will also - include the mobile network prefix (MNP), which is the IP prefix - delegated to the MR. The MNP is allocated to the MNNs in the - mobile network. + include the mobile network prefix (MNP), which is the aggregate IP + prefix delegated to the MR to assign IP prefixes for use by the + MNNs in the mobile network. LM is a control plane function. In a client-server protocol model, location query and update messages may be exchanged between a Location Management client (LMc) and a Location Management server (LMs). Optionally, there may be a Location Management proxy (LMp) between LMc and LMs. With separation of control plane and data plane, the LM function is in the control plane. It may be a logical function at the control plane node, control plane anchor, or mobility controller. It may be distributed or centralized. Forwarding Management (FM) function: packet interception and - forwarding to/from the IP address/prefix assigned to the MN, based - on the internetwork location information, either to the + forwarding to/from the IP address/prefix assigned for use by the + MN, based on the internetwork location information, either to the destination or to some other network element that knows how to forward the packets to their destination. This function may be used to achieve traffic indirection. With 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 function in the control plane (FM-CP). FM-DP may be distributed with distributed mobility management. It may be a function in a data plane anchor or data plane node. @@ -300,28 +299,44 @@ The configurations also differ depending on the desired mobility supports: network-based mobility support for a flat network in Section 3.1.1, network-based mobility support for a hierarchical 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.4. 3.1.1. Network-based Mobility Support for a Flat Network - Figure 1 shows two different configurations of network-based mobility - management for a flat network. + Figure 1 shows two different configurations of network-based + 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) +-----+ |LMs | +-----+ - +------------+ +------------+ |CPA: | |CPA: | |FM-CP, LM | |FM-CP, LMc | +------------+ +------------+ +------------+ +------------+ +------------+ +------------+ |DPA(IPa1): | |DPA(IPa2): | |DPA(IPa1): | |DPA(IPa2): | |anchors IP1 | |anchors IP2 | ... |anchors IP1 | |anchors IP2 | ... |FM-DP | |FM-DP | |FM-DP | |FM-DP | +------------+ +------------+ +------------+ +------------+ @@ -327,49 +342,27 @@ +------------+ +------------+ |MN(IP1) | |MN(IP1) | |flow(IP1,..)| |flow(IP1,..)| +------------+ +------------+ 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, FM-CP and LMc at CPA, FM-DP at DPA. - Figure 1 also shows a distributed mobility anchoring environment with - multiple instances of the DPA. - - 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. + In Figure 1(a), LM is 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 - into a server LMs and a client LMc. - - LMc and FM-CP are co-located at the CPA. - - The LMs may be centralized whereas the LMc may be distributed or + 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 centralized according to whether the CPA is distributed (not shown) or centralized. 3.1.2. Network-based Mobility Support for a Hierarchical Network Figure 2 shows two different configurations of network-based mobility management for a hierarchical network. (a) +------------+ @@ -426,62 +418,36 @@ +------------+ +------------+ |MN(IP1) | |MN(IP2) | |flow(IP1,..)| |flow(IP2,..)| +------------+ +------------+ Figure 2(b). Configurations of network-based mobility management for 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. - Figures 2 also shows a distributed mobility anchoring environment - with multiple instances of the DPA. - - In the hierarchy, there may be multiple DPNs for each DPA. - - There is FM-DP at each of the distributed DPA and at each of the - 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. + In addition to the dmm feature already described in Figure 1, + 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, + 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 + shown). - LMs may be distributed or centralized according to whether the CPA is - distributed or centralized. The CPA may co-locate with DPA or may - separate. + In Figure 2(a), LMs is at the CPA and LMc is at the CPN. Then, LMs + may be distributed or centralized according to whether the CPA is + distributed or centralized. 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. - - LMp and FM-CP are co-located at the CPA. - - 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. + 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 + be distributed or centralized according to whether the CPA is + distributed or centralized. 3.1.3. Host-based Mobility Support 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) 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 FM and LMc. (a) (b) @@ -504,53 +469,24 @@ |flow(IP1,..)| |flow(IP1,..)| |FM, LMc | |FM, LMc | +------------+ +------------+ 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- CP and LMp at CPA, FM-DP at DPA, FM and LMc at MN. Figure 3 shows 2 configurations of host-based mobility management with multiple instances of DPA for a distributed mobility anchoring - environment. - - 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. - - 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. + 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) + 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. 3.1.4. NEtwork MObility (NEMO) Basic Support Figure 4 shows two configurations of NEMO basic support for a mobile router. (a) (b) +-----+ |LMs | +-----+ @@ -577,67 +512,41 @@ |MNN(IPn1) | |MNN(IPn1) | |flow(IPn1,.)| |flow(IPn1,.)| +------------+ +------------+ 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- 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 a MR with multiple instances of DPA for a distributed mobility - anchoring environment. - - 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 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. + 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 + the MR carrying a mobile network consisting of mobile network nodes + (MNNs) in Figure 4. - 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 - centralized according to whether the CPA is distributed (not shown) - or centralized. + To enable the MR to anchor and to assign the IP prefix IPn1, the DPA + delegates the prefix using DHCPv6-PD to the MR. 3.2. Operations and Parameters The operations of distributed mobility anchoring are defined in order - that they may work together in expected manners to produce a - distributed mobility solution. The needed information is passed as - mobility message parameters, which must be protected in terms of - integrity. Some parameters may require a means to support privacy of - an MN or MR. + that they might work together to produce a distributed mobility + solution. The needed information is passed as mobility message + parameters, which must be protected in terms of integrity. Some + parameters may require a means to support privacy of an MN or MR. The mobility needs in 5G Wireless and beyond are diverse. Therefore operations needed to enable different distributed mobility solutions in different distributed mobility anchoring configurations are extensive as illustrated below. It is however not necessary for every distributed mobility solution to exhibit all the operations listed in this section. A given distributed mobility solution may exhibit only those operations needed. 3.2.1. Location Management @@ -765,25 +673,25 @@ LM-svr:3 LMs may reply to a peer LMs about location information for a prefix of MN. Parameters: - IP prefix of MN: integrity support required and privacy support may be required, - IP address of FM-DP/DPA/DPN to forward the packets of the flow: integrity support required. - The parameters indicated above are only the minimal. In a specific - mobility protocol, additional parameters should be added as needed. - Examples of these additional parameters are those passed in the - mobility options of the mobility header for MIPv6 [RFC6275] and for - PMIPv6 [RFC5213]. + The list above only gives the minimal set of the required parameters. + In a specific mobility protocol, additional parameters should be + added as needed. Examples of these additional parameters are those + passed in the mobility options of the mobility header for MIPv6 + [RFC6275] and for PMIPv6 [RFC5213]. 3.2.2. Forwarding Management Forwarding management configurations: FM-cfg: As shown in Section 3.1: FM-CP may be implemented at CPA, CPN, MN depending on the configuration chosen. @@ -871,26 +779,26 @@ changes to the forwarding table and indirection such as tunneling, rewriting packet header, or NAT. Note: An emphasis in this document in distributed mobility anchoring is to explain the use of multiple anchors to avoid unnecessarily long route which may be encountered in centralized mobility anchoring. It is therefore not the emphasis of this document on which particular mechanism to choose from. - FM-path-tbl:4 With forwarding table updates, changes to the - forwarding table are needed at each of the affected - forwarding switches in order to change the forwarding - path of the packets for the flow from that originally - between the CN and the home network anchor or previous - AR to that between the CN and the new AR. + FM-path-tbl:4 The objective of forwarding table updates is to change + the forwarding path so that the packets in the flow + will be forwarded from the CN to the new AR instead of + the home network anchor or previous AR. Each of the + affected forwarding switches will need appropriate + changes to its forwarding table. Specifically, such forwarding table updates may include: (1) addition of forwarding table entries needed to forward the packets destined to the MN to the new AR; (2) deletion of forwarding table entries to forward the packets destined to the MN to the home network anchor or to the previous AR. FM-path-tbl:5 Forwarding table updates may be triggered using DHCPv6-PD prefix delegation to change the role of IP @@ -1140,27 +1048,27 @@ provided by default. The LM and FM functions in the different configurations shown in Section 3.1 are then utilized only when needed. 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 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 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 - is allocated an IP prefix from the attached network. In addition to - configuring new link-local addresses, the 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 initiated. Packets to the - MN in this flow are simply forwarded according to the forwarding - table. + 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 + interface. In addition to configuring new link-local addresses, the + 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 + initiated. Packets to the MN in this flow are simply forwarded + according to the forwarding table. 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 different access networks. The network may advertise these prefixes 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 prefixes/addresses may be of different types regarding whether mobility support is needed [I-D.ietf-dmm-ondemand-mobility]. A flow will need to choose the appropriate one according to whether it needs IP mobility support. @@ -1190,21 +1098,21 @@ 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 Net2. 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 the new network. Regardless of whether IP mobility is needed, if the flow has 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. 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 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 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 scope of this document. @@ -1217,39 +1125,39 @@ An example call flow is outlined in Figure 6. MN AR1 AR2 CN |MN attaches to AR1: | | | |acquire MN-ID and profile | | |--RS---------------->| | | | | | | |<----------RA(IP1)---| | | | | | | -Allocated prefix IP1 | | | +Assigned prefix IP1 | | | IP1 address configuration | | | | | | |<-Flow(IP1,IPcn,...)-+--------------------------------------------->| | | | | |MN detaches from AR1 | | | |MN attaches to AR2 | | | | | | | |--RS------------------------------>| | | | | | |<--------------RA(IP2)-------------| | | | | | -Allocated prefix IP2 | | | +Assigned prefix IP2 | | | IP2 address configuration | | | | | | |<-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. 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 example, a network slice for stationary sensors only will never encounter mobility. The standard functions in IPv6 already include dropping the old IPv6 prefix/address and acquiring new IPv6 prefix/address when the node @@ -1308,21 +1216,21 @@ 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 in Section 4.2.1. 4.2. Need of IP Mobility 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 prefix anchor switching to the new network to be described in 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 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 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 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 IP prefix in the network where the flow is 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 network has not moved @@ -1330,36 +1238,35 @@ An example call flow in this case is outlined in Figure 7. MN AR1 AR2 CN |MN attaches to AR1: | | | |acquire MN-ID and profile | | |--RS---------------->| | | | | | | |<----------RA(IP1)---| | | | | | | -Allocated prefix IP1 | | | +Assigned prefix IP1 | | | IP1 address configuration | | | | | | |<-Flow(IP1,IPcn,...)-+--------------------------------------------->| | | | | |MN detach from AR1 | | | |MN attach to AR2 | | | | | | | |--RS------------------------------>| | - IP mobility support such as that described in next sub-section |<--------------RA(IP2,IP1)---------| | | | | | |<-Flow(IP1,IPcn,...)---------------+------------------------------->| | | | | -Allocated prefix IP2 | | | +Assigned prefix IP2 | | | IP2 address configuration | | | | | | Flow(IP1,IPcn) terminates | | | | | | |<-new Flow(IP2,IPcn,...)-----------+------------------------------->| | | | | Figure 7. A flow continues to use the IP prefix from its home network after MN has moved to a new network. @@ -1371,24 +1278,24 @@ follows: GL-cfg:2 Multiple instances of DPAs (at access routers) which are providing IP prefix to the MNs are needed to provide distributed mobility anchoring in an appropriate configuration such as those described in Figure 1 (Section 3.1.1) for network-based distributed mobility or in Figure 3 (Section 3.1.3) for host-based distributed mobility. - At the appropriate IPv6 nodes (CPA, DPA, CPN, DPN) the - mobility functions LM and FM as described respectively in - LM-cfg and FM-cfg in Section 3.2 according to the - configuration chosen have to be implemented. + The appropriate IPv6 nodes (CPA, DPA, CPN, DPN) have to + implement the mobility functions LM and FM as described + respectively in LM-cfg and FM-cfg in Section 3.2 according + to the configuration chosen. The guidelines of distributed mobility for the IPv6 nodes in a network or network slice supporting a mix of flows both requiring and not requiring distributed mobility support had begun with those given as GL-mix in Section 4.1.1 and continue as follows: GL-mix:5 The distributed anchors may need to message with each other. When such messaging is needed, the anchors may need to discover each other as described in the FM operations and mobility message parameters (FM-find) in Section 3.2.2. @@ -1492,24 +1399,23 @@ The configuration guideline for a flat network or network slice supporting a mix of flows both requiring and not requiring IP mobility support is: GL-cfg:3 Multiple instances of DPAs (at access routers) which are providing IP prefix to the MNs are needed to provide distributed mobility anchoring according to Figure 1(a) or Figure 1(b) in Section 3.1 for a flat network. - At the appropriate IPv6 nodes (CPA, DPA) the mobility - functions LM and FM as described respectively in LM-cfg:1 - or LM-cfg:2 and FM-cfg:1 in Section 3.2 have to be - implemented. + The appropriate IPv6 nodes (CPA, DPA) have to implement the + mobility functions LM and FM as described respectively in + LM-cfg:1 or LM-cfg:2 and FM-cfg:1 in Section 3.2. 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 both requiring and not requiring IP mobility support apply here. In addition, the following are required. GL-switch:1 The location management provides information about which IP prefix from an AR in the original network is being used by a flow in which AR in a new network. Such information needs to be deleted or updated when such @@ -1592,110 +1498,109 @@ +...............+ +---------------+ .MN(IP1) . MN moves |MN(IP2,IP1) | .flow(IP1,...) . =======> |flow(IP1,...) | +...............+ +---------------+ 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- DPs are distributed. - The example call flow in Figure 10 shows that MN is allocated IP1 - when it attaches to the AR1 A flow running in MN and needing IP + The example call flow in Figure 10 shows that IP1 is assigned to MN + 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 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. MN AR1 AR2 DHCPv6 Servers CN |MN attaches to AR1: | | | | |acquire MN-ID and profile | | | |--RS---------------->| | | | |<----------RA(IP1)---| | | | - | | | Allocate MN:IP1 | + | | | Assign MN:IP1 | IP addr config | | | | | | | | | |<-Flow(IP1,IPcn,...)-+--------------------------------------------->| | | | | | |MN detach from AR1 | | | | |MN attach to AR2 | | | | | | | | | |--RS------------------------------>| | | | | | | | | |------DHCPv6 release-------------->| | | | | | | | | |--DHCPv6 PD request->| | | | |<-DHCPv6 PD reply--->| | | | | | | | forwarding table updates | | | | | | | |<--------------RA(IP2,IP1)---------| | | - | | | Allocate MN:IP2 | + | | | Assign MN:IP2 | IP addr config | | | | | | | | | |<-Flow(IP1,IPcn,...)---------------+------------------------------->| | | | | | | Flow(IP1,IPcn,...) terminates | | | | | | | | | | DHCPv6-PD timeout | | | | | | | | forwarding table updates | | | | | | | | | | | | |<-new Flow(IP2,IPcn,...)-----------+------------------------------->| | | | | | Figure 10. DMM solution. MN with flow using IP1 in Net1 continues 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 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 - that it will be possible for Net2 to allocate both the previous - network prefix and the new network prefix. The network may learn the + that it will be possible for Net2 to assign both the previous network + prefix and the new network prefix. The network may learn the previous prefix in different methods. For example, the MN may provide its previous network prefix information by including it to the RS message [I-D.jhlee-dmm-dnpp]. 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 reply to move the IP1. Then forwarding tables updates will take place here. 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 - and IP2. The MN may then continue to use IP1. In addition, the MN - is allocated the prefix IP2 with which it may configure its IP - addresses. Now for flows using IP1, packets destined to IP1 will be - forwarded to the MN via AR2. + and IP2. The MN may then continue to use IP1. In addition, the + prefix IP2 is assigned to the MN which may configure the IP addresses + of its interface. Now for flows using IP1, packets destined to IP1 + will be forwarded to the MN via AR2. 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 when it now starts a new flow. 5.2.1. Additional Guidelines for IPv6 Nodes: Switching Anchor with Centralized CP The configuration guideline for a flat network or network slice with centralized control plane and supporting a mix of flows both requiring and not requiring IP mobility support is: GL-cfg:4 Multiple instances of DPAs (at access routers) which are providing IP prefix to the MNs are needed to provide distributed mobility anchoring according to Figure 1(a) or Figure 1(b) in Section 3.1 with centralized control plane for a flat network. - At the appropriate IPv6 nodes (CPA, DPA) the mobility - functions LM and FM as described respectively in LM-cfg:1 - or LM-cfg:2 and FM-cfg:1 in Section 3.2 have to be - implemented. + At the appropriate IPv6 nodes (CPA, DPA) have to implement + the mobility functions LM and FM as described respectively + in LM-cfg:1 or LM-cfg:2 and FM-cfg:1 in Section 3.2. 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 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 network also apply here. In addition, the following are required. GL-switch:5 It was already mentioned that the anchor operations to properly forward the packets for a flow as described in the FM operations and mobility message parameters in FM- @@ -1741,36 +1646,35 @@ distributed mobility management will be deferred to Section 5.4. In this distributed mobility configuration, a mobility event 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 using PMIPv6. This configuration of network-based mobility is also applicable to host-based mobility with the modification for the MN directly taking the role of DPN and CPN, and the corresponding 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 MN was originally attached as well as to the new FW to which the MN has moved. 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 which MN has moved. The implementation of FM to enable change of FW 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 [I-D.templin-aerolink] or using some other L2 mobility mechanism. Net1 Net2 +----------------------------------------------------------------------+ -| CPA,CPN: | -| LM:IP1 at IPn2 | +| CPA,CPN: LM:IP1 at IPn2 | | FM-CP | +----------------------------------------------------------------------+ +---------------+ |AR1 | +---------------+ |DPA(IPa1): | |anchors IP1 | |FM-DP | +---------------+ @@ -1781,41 +1685,40 @@ |DPN(IPn1): | -------> |DPN(IPn2): | |FM-DP | |FM-DP | +---------------+ +---------------+ +...............+ +---------------+ .MN(IP1) . MN moves |MN(IP2) | .flow(IP1,...) . =======> |flow(IP1,...) | +...............+ +---------------+ 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 connect. 5.3.1. Additional Guidelines for IPv6 Nodes: Hierarchical Network with No Anchor Relocation The configuration guideline for a hierarchical network or network slice with centralized control plane and supporting a mix of flows both requiring and not requiring IP mobility support is: GL-cfg:5 Multiple instances of DPAs (at access routers) which are providing IP prefix to the MNs are needed to provide distributed mobility anchoring according to Figure 2(a) or Figure 2(b)in Section 3.1.2 with centralized control plane for a hierarchical network. - At the appropriate IPv6 nodes (CPA, DPA) the mobility - functions LM and FM as described respectively in LM-cfg:3 - or LM-cfg:4 and FM-cfg:2 in Section 3.2 have to be - implemented. + The appropriate IPv6 nodes (CPA, DPA) have to implement the + mobility functions LM and FM as described respectively in + LM-cfg:3 or LM-cfg:4 and FM-cfg:2 in Section 3.2. Even when the mobility event does not involve change of anchor, it is still necessary to distinguish whether a flow needs IP mobility support. 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 both requiring and not requiring IP mobility support apply here. In addition, the following are required. @@ -1841,22 +1744,21 @@ supports forwarding to the DPN at each of a number of forwarding switches (FWs). A distributed mobility event in this configuration involves change 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 involving change of both DPA and DPN is shown in Figure 12. Net1 Net2 +----------------------------------------------------------------------+ -| CPA,CPN,Aggregate Router: | -| LM:IP1 at IPn2 at IPa2 | +| CPA,CPN,Aggregate Router: LM:IP1 at IPn2 at IPa2 | | FM-CP | +----------------------------------------------------------------------+ +-----------------+ |Aggregate Router | +-----------------+ |FM-DP | +-----------------+ +---------------+ +---------------+ @@ -1873,21 +1775,21 @@ |DPN(IPn1): | -------> |DPN(IPn2): | |FM-DP | |FM-DP | +---------------+ +---------------+ +...............+ +---------------+ .MN(IP1) . MN moves |MN(IP2,IP1) | .flow(IP1,...) . =======> |flow(IP1,...) | +...............+ +---------------+ 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 may connect. 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 of relocating the IP prefix/address anchoring from AR1 to AR2 with the mechanism as described in Section 5.2 and then forwarding the 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 @@ -1913,31 +1815,30 @@ the new DPN as described in Section 5.3.1 apply as well. 5.5. Network Mobility 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, 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 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 - 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 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 is attached to the MR and therefore moves with the MR. Net1 Net2 +----------------------------------------------------------------------+ -| CPA,Aggregate Router: | -| LM:IP1 at IPa2; IPn1 at IP1 | +| CPA,Aggregate Router: LM:IP1 at IPa2; IPn1 at IP1 | | FM-CP, LM | +----------------------------------------------------------------------+ +-----------------+ |Aggregate Router | +-----------------+ |FM-DP | +-----------------+ +---------------+ +---------------+ @@ -1976,24 +1877,23 @@ 5.5.1. Additional Guidelines for IPv6 Nodes: Network mobility The configuration guideline for a network or network slice with centralized control plane to provide network mobility is: GL-cfg:6 Multiple instances of DPAs (at access routers) which are providing IP prefix of the MRs are needed to provide distributed mobility anchoring according to Figure 4(a) or Figure 4(b) in Section 3.1. - At the appropriate IPv6 nodes (CPA, DPA) the mobility - functions LM and FM as described respectively in LM-cfg:3 - or LM-cfg:4 and FM-cfg:4 in Section 3.2 have to be - implemented. + The appropriate IPv6 nodes (CPA, DPA) have to implement the + mobility functions LM and FM as described respectively in + LM-cfg:3 or LM-cfg:4 and FM-cfg:4 in Section 3.2. 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 both requiring and not requiring IP mobility support apply here. Here, because the MN is a MR, the following guideline is added: GL-mix:11 There are no flows requiring network mobility support when there are no MNN attaching to the MR. Here there are also no MNN using a prefix delegated to the MR. Therefore the @@ -2062,25 +1962,25 @@ Section 3.2. Here the mobility message parameters used in DMM must be protected, and some parameters require means to support MN and MR privacy. The security considerations are also described in the guidelines for IPv6 nodes in various subsections in Section 4, and Section 5. 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 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 - 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 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 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, 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. Yet it must do so without compromising on the needed security to prevent the possible misuse of an IP prefix belonging to another network. 7. IANA Considerations @@ -2092,27 +1992,33 @@ This document has benefited from other work on mobility solutions using BGP update, on mobility support in SDN network, on providing mobility support only when needed, and on mobility support in enterprise network. These works have been referenced. While some of these authors have taken the work to jointly write this document, others have contributed at least indirectly by writing these drafts. The latter include Philippe Bertin, Dapeng Liu, Satoru Matushima, Peter McCann, Pierrick Seite, Jouni Korhonen, and Sri Gundavelli. Valuable comments have been received from John Kaippallimalil, - ChunShan Xiong, and Dapeng Liu. Dirk von Hugo has generously - provided careful review with helpful corrections and suggestions. + ChunShan Xiong, and Dapeng Liu. Dirk von Hugo, Byju Pularikkal, + Pierrick Seite have generously provided careful review with helpful + corrections and suggestions. 9. 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] Gundavelli, S. and S. Jeon, "DMM Deployment Models and Architectural Considerations", draft-ietf-dmm-deployment- models-01 (work in progress), February 2017. [I-D.ietf-dmm-fpc-cpdp] Matsushima, S., Bertz, L., Liebsch, M., Gundavelli, S., Moses, D., and C. Perkins, "Protocol for Forwarding Policy Configuration (FPC) in DMM", draft-ietf-dmm-fpc-cpdp-07 (work in progress), March 2017. @@ -2175,20 +2081,26 @@ [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", RFC 5213, DOI 10.17487/RFC5213, August 2008, . [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 2011, . + [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, + . + [RFC7077] Krishnan, S., Gundavelli, S., Liebsch, M., Yokota, H., and J. Korhonen, "Update Notifications for Proxy Mobile IPv6", RFC 7077, DOI 10.17487/RFC7077, November 2013, . [RFC7333] Chan, H., Ed., Liu, D., Seite, P., Yokota, H., and J. Korhonen, "Requirements for Distributed Mobility Management", RFC 7333, DOI 10.17487/RFC7333, August 2014, .