draft-ietf-dmm-deployment-models-03.txt   draft-ietf-dmm-deployment-models-04.txt 
DMM WG S. Gundavelli DMM WG S. Gundavelli
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational S. Jeon Intended status: Informational S. Jeon
Expires: May 16, 2018 Sungkyunkwan University Expires: November 17, 2018 Sungkyunkwan University
November 12, 2017 May 16, 2018
DMM Deployment Models and Architectural Considerations DMM Deployment Models and Architectural Considerations
draft-ietf-dmm-deployment-models-03.txt draft-ietf-dmm-deployment-models-04.txt
Abstract Abstract
This document identifies the deployment models for Distributed This document identifies the deployment models for Distributed
Mobility Management architecture. Mobility Management architecture.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 16, 2018. This Internet-Draft will expire on November 17, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3
2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. DMM Architectural Overview . . . . . . . . . . . . . . . . . 4 3. DMM Architectural Overview . . . . . . . . . . . . . . . . . 4
3.1. DMM Service Primitives . . . . . . . . . . . . . . . . . 4 3.1. DMM Service Primitives . . . . . . . . . . . . . . . . . 4
3.2. DMM Functions and Interfaces . . . . . . . . . . . . . . 5 3.2. DMM Functions and Interfaces . . . . . . . . . . . . . . 5
3.2.1. Home Control-Plane Anchor (H-CPA): . . . . . . . . . 5 3.2.1. Home Control-Plane Anchor (Home-CPA): . . . . . . . . 5
3.2.2. Home Data-Plane Anchor (H-DPA): . . . . . . . . . . . 6 3.2.2. Home Data-Plane Anchor (Home-DPA): . . . . . . . . . 6
3.2.3. Access Control Plane Node (Access-CPN) . . . . . . . 6 3.2.3. Access Control Plane Node (Access-CPN) . . . . . . . 6
3.2.4. Access Data Plane Node (Access-DPN) . . . . . . . . . 6 3.2.4. Access Data Plane Node (Access-DPN) . . . . . . . . . 6
3.2.5. DMM Functions Mapping to Other Architectures . . . . 6 3.2.5. DMM Functions Mapping to Other Architectures . . . . 6
4. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 7 4. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Model-1: Split Home Anchor Mode . . . . . . . . . . . . . 7 4.1. Model-1: Split Home Anchor Mode . . . . . . . . . . . . . 8
4.2. Model-2: Separated Control and User Plane Mode . . . . . 8 4.2. Model-2: Separated Control and User Plane Mode . . . . . 9
4.3. Model-3: Centralized Control Plane Mode . . . . . . . . . 9 4.3. Model-3: Centralized Control Plane Mode . . . . . . . . . 10
4.4. Model-4: Data Plane Abstraction Mode . . . . . . . . . . 10 4.4. Model-4: Data Plane Abstraction Mode . . . . . . . . . . 10
4.5. On-Demand Control Plane Orchestration Mode . . . . . . . 11 4.5. Model-5: On-Demand Control Plane Orchestration Mode . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. Work Team . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Work Team . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Overview 1. Overview
skipping to change at page 3, line 17 skipping to change at page 3, line 17
2.1. Conventions 2.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2.2. Terminology 2.2. Terminology
All the mobility related terms are to interpreted as defined in All the mobility related terms are to interpreted as defined in
[RFC6275], [RFC5213], [RFC5844], [RFC7333], [RFC7665], [RFC7429], [RFC6275], [RFC5213], [RFC5844], [RFC7333], [RFC7665], [RFC7429],
[I-D.ietf-sfc-nsh] and [I-D.ietf-dmm-fpc-cpdp]. Additionally, this [RFC8300] and [I-D.ietf-dmm-fpc-cpdp]. Additionally, this document
document uses the following terms: uses the following terms:
Home Control-Plane Anchor (H-CPA) Home Control-Plane Anchor (Home-CPA or H-CPA)
The Home-CPA function hosts the mobile node (MN)'s mobility The Home-CPA function hosts the mobile node (MN)'s mobility
session. There can be more than one mobility session for a mobile session. There can be more than one mobility session for a mobile
node and those sessions may be anchored on the same or different node and those sessions may be anchored on the same or different
Home-CPA's. The home-CPA will interface with the home-dpa for Home-CPA's. The home-CPA will interface with the home-DPA for
managing the forwarding state. managing the forwarding state.
Home Data Plane Anchor (Home-DPA) Home Data Plane Anchor (Home-DPA or H-DPA)
The Home-DPA is the topological anchor for the mobile node's IP The Home-DPA is the topological anchor for the MN's IP address/
address/prefix(es). The Home-DPA is chosen by the Home-CPA on a prefix(es). The Home-DPA is chosen by the Home-CPA on a session-
session-basis. The Home-DPA is in the forwarding path for all the basis. The Home-DPA is in the forwarding path for all the mobile
mobile node's IP traffic. node's IP traffic.
Access Control Plane Node (Access-CPN) Access Control Plane Node (Access-CPN or A-CPN)
The Access-CPN is responsible for interfacing with the mobile The Access-CPN is responsible for interfacing with the mobile
node's Home-CPA and with the Access-DPN. The Access-CPN has a node's Home-CPA and with the Access-DPN. The Access-CPN has a
protocol interface to the Home-CPA. protocol interface to the Home-CPA.
Access Data Plane Node (Access-DPN) Access Data Plane Node (Access-DPN or A-DPN)
The Access-DPN function is hosted on the first-hop router where The Access-DPN function is hosted on the first-hop router where
the mobile node is attached. This function is not hosted on a the mobile node is attached. This function is not hosted on a
layer-2 bridging device such as a eNode(B) or Access Point. layer-2 bridging device such as a eNode(B) or Access Point.
Routing Controller (RC) Routing Controller (RC)
The Routing Controller is a centralized control entity, which is The Routing Controller is a centralized control entity, which is
able to instruct the forwarding behavior for mobility management able to instruct the forwarding behavior for mobility management
in Home-DPA and Access-DPN. in Home-DPA and Access-DPN.
skipping to change at page 4, line 41 skipping to change at page 4, line 41
The functions in the DMM architecture support a set of service The functions in the DMM architecture support a set of service
primitives. Each of these service primitives identifies a specific primitives. Each of these service primitives identifies a specific
service capability with the exact service definition. The functions service capability with the exact service definition. The functions
in the DMM architecture are required to support a specific set of in the DMM architecture are required to support a specific set of
service primitives that are mandatory for that service function. Not service primitives that are mandatory for that service function. Not
all service primitives are applicable to all DMM functions. The all service primitives are applicable to all DMM functions. The
below table as shown in Fig. 1 identifies the service primitives that below table as shown in Fig. 1 identifies the service primitives that
each of the DMM function SHOULD support. The marking "X" indicates each of the DMM function SHOULD support. The marking "X" indicates
the service primitive on that row needs to be supported by the the service primitive on that row needs to be supported by the
identified DMM function on the corresponding column; for example, the identified DMM function on the corresponding column; for example, the
IP address management must be supported by Home-CPA function. The IP address management MUST be supported by Home-CPA function. The
NSH Classifier denotes the SFC entity that performs the NSH Classifier denotes the SFC entity that performs the
classification of a service flow, defined in [RFC7665]. classification of a service flow, defined in [RFC7665].
+=================+=======+=======+=======+=======+=======+=======+ +=================+=======+=======+=======+=======+=======+=======+
| Service | H-CPA | H-DPA | A-CPN | A-DPN | MC | RC | | Service | H-CPA | H-DPA | A-CPN | A-DPN | MC | RC |
| Primitive | | | | | | | | Primitive | | | | | | |
+=================+=======+=======+=======+=======+=======+=======+ +=================+=======+=======+=======+=======+=======+=======+
| IP Management | X | | | | X | | | IP Management | X | | | | X | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| IP Anchoring | | X | | | | | | IP Anchoring | | X | | | | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| MN Detect | | | X | X | | | | MN Detection | | | X | X | | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| Routing | | X | | X | | | | Routing | | X | | X | | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| Tunneling | | X | | X | | | | Tunneling | | X | | X | | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| QoS Enforcement | | X | | X | | | | QoS Enforcement | | X | | X | | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| FPC Client | X | | X | | X | | | FPC Client | X | | X | | X | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| FPC Agent | | X | | X | | X | | FPC Agent | | X | | X | | X |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
| NSH Classifier | | X | | X | | | | NSH Classifier | | X | | X | | |
+-----------------+-------+-------+-------+-------+-------+-------+ +-----------------+-------+-------+-------+-------+-------+-------+
Figure 1: Mapping of DMM functions Figure 1: Role or capability of DMM functions
3.2. DMM Functions and Interfaces 3.2. DMM Functions and Interfaces
3.2.1. Home Control-Plane Anchor (H-CPA): 3.2.1. Home Control-Plane Anchor (Home-CPA):
The Home-CPA function hosts the mobile node's mobility session. The Home-CPA function hosts the mobile node's mobility session.
There can be more than one mobility session for a mobile node and There can be more than one mobility session for a mobile node and
those sessions may be anchored on the same or different Home-CPA's. those sessions may be anchored on the same or different Home-CPA's.
The home-CPA will interface with the home-dpa for managing the The home-CPA will interface with the home-dpa for managing the
forwarding state. forwarding state.
There can be more than one Home-CPA serving the same mobile node at a There can be more than one Home-CPA serving the same mobile node at a
given point of time, each hosting a different control plane session. given point of time, each hosting a different control plane session.
The Home-CPA is responsible for life cycle management of the session, The Home-CPA is responsible for life cycle management of the session,
interfacing with the policy infrastructure, policy control and interfacing with the policy infrastructure, policy control and
interfacing with the Home-DPA functions. interfacing with the Home-DPA functions.
The Home-CPA function typically stays on the same node. In some The Home-CPA function typically stays on the same node. In some
special use-cases (Ex: Geo-Redundancy), the session may be migrated special use-cases (Ex: Geo-Redundancy), the session may be migrated
to a different node and with the new node assuming the Home-CPA role to a different node and with the new node assuming the Home-CPA role
for that session. for that session.
3.2.2. Home Data-Plane Anchor (H-DPA): 3.2.2. Home Data-Plane Anchor (Home-DPA):
The Home-DPA is the topological anchor for the mobile node's IP The Home-DPA is the topological anchor for the mobile node's IP
address/prefix(es). The Home-DPA is chosen by the Home-CPA/MC on a address/prefix(es). The Home-DPA is chosen by the Home-CPA/MC on a
session-basis. The Home-DPA is in the forwarding path for all the session-basis. The Home-DPA is in the forwarding path for all the
mobile node's IP traffic. mobile node's IP traffic.
As the mobile node roams in the mobile network, the mobile node's As the mobile node roams in the mobile network, the mobile node's
access-DPN may change, however, the Home-DPA does not change, unless access-DPN may change, however, the Home-DPA does not change, unless
the session is migrated to a new node. the session is migrated to a new node.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
The Access-DPA will have a protocol interface to the Access-CPA. The Access-DPA will have a protocol interface to the Access-CPA.
The Access-DPN and the Home-DPA functions may be collocated on the The Access-DPN and the Home-DPA functions may be collocated on the
same node. same node.
3.2.5. DMM Functions Mapping to Other Architectures 3.2.5. DMM Functions Mapping to Other Architectures
Following table identifies the potential mapping of DMM functions to Following table identifies the potential mapping of DMM functions to
protocol functions in other system architectures. protocol functions in other system architectures.
+===========+==========+==========+==========+=============+==========+ +=======+=========+========+=========+=============+==========+=======+
| FUNCTION | PMIPv6 | MIPv6 | IPsec | 3GPP | Broadband| | Func. | PMIPv6 | MIPv6 | IPsec | 3GPP-SAE | BBF | 5GC |
+===========+==========+==========+==========+=============+==========+ +=======+=========+========+=========+=============+==========+=======+
| Home-CPA | LMA-CPA | HA-CPA | IKE-CPA | PGW-CPA/MME | BNG-CPA | | H-CPA | LMA-CPA | HA-CPA | IKE-CPA | PGW-CPA/MME | BNG-CPA |AMF/SMF|
+-----------+----------+----------+----------+-------------+----------+ +-------+---------+--------+---------+-------------+----------+-------+
| Home-DPA | LMA-DPA | HA-DPA | IKE-DPA | PGW-DPA | BNG-DPA | | H-DPA | LMA-DPA | HA-DPA | IKE-DPA | PGW-DPA | BNG-DPA | UPF |
+-----------+----------+----------+----------+-------------+----------+ +-------+---------+--------+---------+-------------+----------+-------+
|Access-CPN | MAG-CPN | - | - | SGW-CPN | RG-CPN | | A-CPN | MAG-CPN | - | - | SGW-CPN | RG-CPN | SMF |
+-----------+----------+----------+----------+-------------+----------+ +-------+---------+--------+---------+-------------+----------+-------+
|Access-DPN | MAG-DPN | - | - | SGW-DPN | RG-DPN | | A-DPN | MAG-DPN | - | - | SGW-DPN | RG-DPN | UPF |
+-----------+----------+----------+----------+-------------+----------+ +-------+---------+--------+---------+-------------+----------+-------+
Figure 2: Mapping of DMM functions Figure 2: Mapping of DMM functions in other system architectures
Mapping from the DMM functions to network components in PMIPv6,
MIPv6, IPsec, Broadband Forum (BBF) can be given straight-forward.
In the 3GPP System Architecture Evolution (SAE), H-CPA functionality
is charged by PGW-CPA and Mobility Management Entity (MME), as MME is
the key control-plane node involving in such as location management,
handoff management, selection of SGW/PGW as well as authorization of
UEs. But PGW-CPA is in charge of tunnel control based on UE's
subscription and policy between SGW and PGW. The rest of the 3GPP
SAE network components are as given in Fig. 2.
The 3GPP Release 15 introduces the Service-Based Architecture (SBA)
for 5G networks. The 3GPP 5G architecture can be represented by
reference point or service-based interfaces [_3GPP.23.501]. Allowing
the service-based interface provides greater flexibility for updates
and extensions of the 5G control plane system by operator's need or
request. The architecture introduces various kinds of network
functions granularized in the CP/DP separation concept. In Fig. 2,
Access and Mobility Management Function (AMF), Session Management
Function (SMF), and User Plane Function (UPF) are picked up among all
the network functions introduced in the 5G SBA for mapping to the DMM
functions.
AMF and SMF take major roles for mobility management in control
plane. AMF manages access control and mobility and includes network
slice selection functionality. SMF manages sessions based on UE's
subscription and network policy and is in charge of IP address
allocation management. UPF is the data plane node, which works for
data packet handling based on forwarding policy regulated by control
plane nodes such as AMF and SMF, etc.
4. Deployment Models 4. Deployment Models
This section identifies the key deployment models for the DMM This section identifies the key deployment models for the DMM
architecture. architecture.
4.1. Model-1: Split Home Anchor Mode 4.1. Model-1: Split Home Anchor Mode
In this model, the control and the data plane functions of the home In this model, the control and the data plane functions of the home
anchor are separated and deployed on different nodes. The control anchor are separated and deployed on different nodes. The control
skipping to change at page 11, line 39 skipping to change at page 11, line 39
| Access-DPN |. . . . . . . . . .| Home-DPA | | Access-DPN |. . . . . . . . . .| Home-DPA |
+============+ UP {Tunnel/Route} +============+ +============+ UP {Tunnel/Route} +============+
. .
. .
+--+ +--+
|MN| |MN|
+--+ +--+
Figure 6: Data Plane Abstraction Mode Figure 6: Data Plane Abstraction Mode
4.5. On-Demand Control Plane Orchestration Mode 4.5. Model-5: On-Demand Control Plane Orchestration Mode
In this model, there is a new function Mobility Controller which In this model, there is a new function Mobility Controller which
manages the orchestration of Access-CPN and Home-CPA functions. The manages the orchestration of Access-CPN and Home-CPA functions. The
Mobility Controller allocates the Home-CPA and Access-DPN Mobility Controller allocates the Home-CPA and Access-DPN
+ - - - - - - - - - - - - - - - - - - - - - - - - - - -+ + - - - - - - - - - - - - - - - - - - - - - - - - - - -+
| +----------+ +----------+ +----------+ | | +----------+ +----------+ +----------+ |
|Access-CPN| |Access-CPN| |Access-CPN| |Access-CPN| |Access-CPN| |Access-CPN|
| +----------+ +----------+ +----------+ | | +----------+ +----------+ +----------+ |
| +----------+ +----------+ +----------+ | | +----------+ +----------+ +----------+ |
| Home-CPA | | Home-CPA | | Home-CPA | | Home-CPA | | Home-CPA | | Home-CPA |
| +----------+ +----------+ +----------+ | | +----------+ +----------+ +----------+ |
+ - - - - - - - - - - - - - - - - - - - - - - - - - - -+ + - - - - - - - - - - - - - - - - - - - - - - - - - - -+
. . . .
. . . .
. . . .
. +============+ +============+ . +============+ +============+
. | Mobility | | Policy | . | Mobility | | Policy |
. | Controller |-----| Function | . | Controller |-----| Function |
. +============+ +============+ . +============+ +============+
. .
. .
. .
. +============+ . +============+
. . . . . .| Routing | . . . . . .| Routing |
| Controller | | Controller |
+============+ +============+
. .
skipping to change at page 14, line 16 skipping to change at page 14, line 16
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
9.2. Informative References 9.2. Informative References
[_3GPP.23.501]
3GPP, "System Architecture for the 5G System", 3GPP
TS 23.501 15.0.0, December 2018,
<http://www.3gpp.org/ftp/Specs/html-info/23501.htm>.
[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-09 Configuration (FPC) in DMM", draft-ietf-dmm-fpc-cpdp-10
(work in progress), October 2017. (work in progress), March 2018.
[I-D.ietf-sfc-nsh]
Quinn, P., Elzur, U., and C. Pignataro, "Network Service
Header (NSH)", draft-ietf-sfc-nsh-28 (work in progress),
November 2017.
[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,
<https://www.rfc-editor.org/info/rfc5213>. <https://www.rfc-editor.org/info/rfc5213>.
[RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010, Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010,
<https://www.rfc-editor.org/info/rfc5844>. <https://www.rfc-editor.org/info/rfc5844>.
skipping to change at page 15, line 10 skipping to change at page 15, line 10
CJ. Bernardos, "Distributed Mobility Management: Current CJ. Bernardos, "Distributed Mobility Management: Current
Practices and Gap Analysis", RFC 7429, Practices and Gap Analysis", RFC 7429,
DOI 10.17487/RFC7429, January 2015, DOI 10.17487/RFC7429, January 2015,
<https://www.rfc-editor.org/info/rfc7429>. <https://www.rfc-editor.org/info/rfc7429>.
[RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function [RFC7665] Halpern, J., Ed. and C. Pignataro, Ed., "Service Function
Chaining (SFC) Architecture", RFC 7665, Chaining (SFC) Architecture", RFC 7665,
DOI 10.17487/RFC7665, October 2015, DOI 10.17487/RFC7665, October 2015,
<https://www.rfc-editor.org/info/rfc7665>. <https://www.rfc-editor.org/info/rfc7665>.
[RFC8300] Quinn, P., Ed., Elzur, U., Ed., and C. Pignataro, Ed.,
"Network Service Header (NSH)", RFC 8300,
DOI 10.17487/RFC8300, January 2018,
<https://www.rfc-editor.org/info/rfc8300>.
Authors' Addresses Authors' Addresses
Sri Gundavelli Sri Gundavelli
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: sgundave@cisco.com Email: sgundave@cisco.com
 End of changes. 26 change blocks. 
49 lines changed or deleted 84 lines changed or added

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