draft-ietf-dmm-deployment-models-02.txt		draft-ietf-dmm-deployment-models-03.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: March 2, 2018 Sungkyunkwan University		Expires: May 16, 2018 Sungkyunkwan University
	August 29, 2017		November 12, 2017
	DMM Deployment Models and Architectural Considerations		DMM Deployment Models and Architectural Considerations
	draft-ietf-dmm-deployment-models-02.txt		draft-ietf-dmm-deployment-models-03.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.
	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 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 March 2, 2018.		This Internet-Draft will expire on May 16, 2018.
	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		(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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3		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 (H-CPA): . . . . . . . . . 5
	3.2.2. Home Data-Plane Anchor (H-DPA): . . . . . . . . . . . 6		3.2.2. Home Data-Plane Anchor (H-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 Function Mapping to other Architectures . . . . . 6		3.2.5. DMM Functions Mapping to Other Architectures . . . . 6
	4. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 7		4. Deployment Models . . . . . . . . . . . . . . . . . . . . . . 7
	4.1. Model-1: Split Home Anchor Mode . . . . . . . . . . . . . 7		4.1. Model-1: Split Home Anchor Mode . . . . . . . . . . . . . 7
	4.2. Model-2: Seperated Control and User Plane Mode . . . . . . 8		4.2. Model-2: Separated Control and User Plane Mode . . . . . 8
	4.3. Model-3: Centralized Control Plane Mode . . . . . . . . . 9		4.3. Model-3: Centralized Control Plane Mode . . . . . . . . . 9
	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. 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
	One of the key aspects of the Distributed Mobility Management (DMM)		One of the key aspects of the Distributed Mobility Management (DMM)
	architecture is the separation of control plane (CP) and data plane		architecture is the separation of control plane (CP) and data plane
	(DP) functions of a network element. While data plane elements		(DP) functions of a network element. While data plane elements
	continue to reside on customized networking hardware, the control		continue to reside on customized networking hardware, the control
	plane resides as a software element in the cloud. This is usually		plane resides as a software element in the cloud. This is usually
	referred to as CP-DP separation and is the basis for the IETF's DMM		referred to as CP-DP separation and is the basis for the IETF's DMM
	Architecture. This approach of centralized control plane and		Architecture. This approach of centralized control plane and
	skipping to change at page 3, line 32 ¶		skipping to change at page 3, line 16 ¶
	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], [RFC7429],		[RFC6275], [RFC5213], [RFC5844], [RFC7333], [RFC7665], [RFC7429],
	[I-D.ietf-sfc-nsh] and [I-D.ietf-dmm-fpc-cpdp]. Additionally, this		[I-D.ietf-sfc-nsh] and [I-D.ietf-dmm-fpc-cpdp]. Additionally, this
	document uses the following terms:		document uses the following terms:
	Home Control-Plane Anchor (H-CPA)		Home Control-Plane Anchor (H-CPA)
	The Home-CPA function hosts the mobile node's mobility session.		The Home-CPA function hosts the mobile node (MN)'s mobility
	There can be more than one mobility session for a mobile node [MN]		session. There can be more than one mobility session for a mobile
	and those sessions may be anchored on the same or different Home-		node and those sessions may be anchored on the same or different
	CPA's. The home-CPA will interface with the home-dpa for managing		Home-CPA's. The home-CPA will interface with the home-dpa for
	the forwarding state.		managing the forwarding state.
	Home Data Plane Anchor (Home-DPA)		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 on a		address/prefix(es). The Home-DPA is chosen by the Home-CPA 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.
	Access Control Plane Node (Access-CPN)		Access Control Plane Node (Access-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)
	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.
	skipping to change at page 4, line 14 ¶		skipping to change at page 3, line 47 ¶
	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)
	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)
			The Routing Controller is a centralized control entity, which is
			able to instruct the forwarding behavior for mobility management
			in Home-DPA and Access-DPN.
			Mobility Controller (MC)
			The Mobility Controller is a function entity, which is able to
			manage the orchestration of Home-CPA and Access-CPN functions.
	3. DMM Architectural Overview		3. DMM Architectural Overview
	Following are the key goals of the Distributed Mobility Management		Following are the key goals of the Distributed Mobility Management
	architecture.		architecture.
	1. Separation of control and data Plane		1. Separation of control and data Plane
	2. Aggregation of control plane for elastic scaling		2. Aggregation of control plane for elastic scaling
	3. Distribution of the data plane for efficient network usage		3. Distribution of the data plane for efficient network usage
	skipping to change at page 4, line 41 ¶		skipping to change at page 4, line 37 ¶
	7. Relocation of anchor functions for efficient network usage		7. Relocation of anchor functions for efficient network usage
	3.1. DMM Service Primitives		3.1. DMM Service Primitives
	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 identifies the service primitives that each of the DMM		below table as shown in Fig. 1 identifies the service primitives that
	function SHOULD support. The marking "X" indicates the service		each of the DMM function SHOULD support. The marking "X" indicates
	primitive on that row needs to be supported by the identified DMM		the service primitive on that row needs to be supported by the
	function on the corresponding column; for example, the IP address		identified DMM function on the corresponding column; for example, the
	management must be supported by Home-CPA function.		IP address management must be supported by Home-CPA function. The
			NSH Classifier denotes the SFC entity that performs the
			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 Detect | | | X | X | | |
	skipping to change at page 5, line 37 ¶		skipping to change at page 5, line 37 ¶
	Figure 1: Mapping of DMM functions		Figure 1: Mapping 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 (H-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 homd-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
	skipping to change at page 6, line 47 ¶		skipping to change at page 6, line 47 ¶
	The Access-DPN function is hosted on the first-hop router where the		The Access-DPN function is hosted on the first-hop router where the
	mobile node is attached. This function is not hosted on a layer-2		mobile node is attached. This function is not hosted on a layer-2
	bridging device such as a eNode(B) or Access Point.		bridging device such as a eNode(B) or Access Point.
	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 Function 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|		| FUNCTION | PMIPv6 | MIPv6 | IPsec | 3GPP | Broadband|
	+===========+==========+==========+==========+==========+==========+		+===========+==========+==========+==========+=============+==========+
	| Home-CPA | LMA-CPA | HA-CPA | IKE-CPA | PGW-CPA | BNG-CPA |		| Home-CPA | LMA-CPA | HA-CPA | IKE-CPA | PGW-CPA/MME | BNG-CPA |
	+-----------+----------+----------+----------+----------+----------+		+-----------+----------+----------+----------+-------------+----------+
	| Home-DPA | LMA-DPA | HA-DPA | IKE-DPA | PGW-DPA | BNG-DPA |		| Home-DPA | LMA-DPA | HA-DPA | IKE-DPA | PGW-DPA | BNG-DPA |
	+-----------+----------+----------+----------+----------+----------+		+-----------+----------+----------+----------+-------------+----------+
	|Access-CPN | MAG-CPN | - | - | SGW-CPN | RG-CPN |		|Access-CPN | MAG-CPN | - | - | SGW-CPN | RG-CPN |
	+-----------+----------+----------+----------+----------+----------+		+-----------+----------+----------+----------+-------------+----------+
	|Access-DPN | MAG-DPN | - | - | SGW-DPN | RG-DPN |		|Access-DPN | MAG-DPN | - | - | SGW-DPN | RG-DPN |
	+-----------+----------+----------+----------+----------+----------+		+-----------+----------+----------+----------+-------------+----------+
	Figure 2: Mapping of DMM functions		Figure 2: Mapping of DMM functions
	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
	skipping to change at page 8, line 30 ¶		skipping to change at page 8, line 30 ¶
	| Legacy |. . . . . . . . . . . . .| Home-DPA |		| Legacy |. . . . . . . . . . . . .| Home-DPA |
	+============+ UP {Tunnel/Route} +============+		+============+ UP {Tunnel/Route} +============+
	.		.
	.		.
	+--+		+--+
	|MN|		|MN|
	+--+		+--+
	Figure 3: Split Home Anchor Mode		Figure 3: Split Home Anchor Mode
	4.2. Model-2: Seperated Control and User Plane Mode		4.2. Model-2: Separated Control and User Plane Mode
	In this model, the control and the data plane functions on both the		In this model, the control and the data plane functions on both the
	home anchor and the access node are seperated and deployed on		home anchor and the access node are seperated and deployed on
	different nodes. The control plane function of the Home anchor is		different nodes. The control plane function of the Home anchor is
	handled by the Home-CPA and where as the data plane function is		handled by the Home-CPA whereas the data plane function is handled by
	handled by the Home-DPA. The control plane function of the access		the Home-DPA. The control plane function of the access node is
	node is handled by the Access-CPN and where as the data plane		handled by the Access-CPN and where as the data plane function is
	function is handled by the Access-DPN.		handled by the Access-DPN.
	The FPC interface defined in [I-D.ietf-dmm-fpc-cpdp] allows the		The FPC interface defined in [I-D.ietf-dmm-fpc-cpdp] allows the
	control plane functions of the home and access nodes to interact with		control plane functions of the home and access nodes to interact with
	the respective data plane functions for the subscriber's forwarding		the respective data plane functions for the subscriber's forwarding
	state management.		state management.
	+============+		+============+
	| Policy |		| Policy |
	. . . . . . .| Function |. . . . . . .		. . . . . . .| Function |. . . . . . .
	. +============+ .		. +============+ .
	skipping to change at page 9, line 26 ¶		skipping to change at page 9, line 26 ¶
	. .		. .
	. FPC . FPC		. FPC . FPC
	. .		. .
	. .		. .
	. .		. .
	+============+ +============+		+============+ +============+
	| Access-DPN |. . . . . . . . . . . | Home-DPA |		| Access-DPN |. . . . . . . . . . . | Home-DPA |
	+============+ UP {Tunnel/Route} +============+		+============+ UP {Tunnel/Route} +============+
	.		.
	.		.
	[MN]		+--+
			|MN|
			+--+
	Figure 4: Seperated Control and User Plane Mode		Figure 4: Seperated Control and User Plane Mode
	4.3. Model-3: Centralized Control Plane Mode		4.3. Model-3: Centralized Control Plane Mode
	In this model, the control-plane functions of the home and the access		In this model, the control-plane functions of the home and the access
	nodes are collapsed. This is a flat architecture with no signaling		nodes are collapsed. This is a flat architecture with no signaling
	protocol between the access node and home anchors. The interface		protocol between the access node and home anchors. The interface
	between the Home-CPA and the Access-DPN is internal to the system.		between the Home-CPA and the Access-DPN is internal to the system.
	skipping to change at page 10, line 20 ¶		skipping to change at page 10, line 20 ¶
	. .		. .
	. .		. .
	FPC . . FPC		FPC . . FPC
	. .		. .
	. .		. .
	+============+ +============+		+============+ +============+
	| Access-DPN |. . . . . . . . . .| Home-DPA |		| Access-DPN |. . . . . . . . . .| Home-DPA |
	+============+ UP {Tunnel/Route} +============+		+============+ UP {Tunnel/Route} +============+
	.		.
	.		.
	[MN]		+--+
			|MN|
			+--+
	Figure 5: Centralized Control Plane Mode		Figure 5: Centralized Control Plane Mode
	4.4. Model-4: Data Plane Abstraction Mode		4.4. Model-4: Data Plane Abstraction Mode
	In this model, the data plane network is completely abstracted from		In this model, the data plane network is completely abstracted from
	the control plane. There is a new network element, Routing		the control plane. There is a new network element, Routing
	Controller which abstracts the entire data plane network and offers		Controller which abstracts the entire data plane network and offers
	data plane services to the control plane functions. The control		data plane services to the control plane functions. The control
	plane functions, Home-CPA and the Access-CPN interface with the		plane functions, Home-CPA and the Access-CPN interface with the
	skipping to change at page 11, line 33 ¶		skipping to change at page 11, line 33 ¶
	. .		. .
	. . BGP/Others		. . BGP/Others
	. .		. .
	. .		. .
	. .		. .
	+============+ +============+		+============+ +============+
	| 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. 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
	+ - - - - - - - - - - - - - - - - - - - - - - - - - - -+		+ - - - - - - - - - - - - - - - - - - - - - - - - - - -+
	| +----------+ +----------+ +----------+ |		| +----------+ +----------+ +----------+ |
	skipping to change at page 14, line 11 ¶		skipping to change at page 14, line 10 ¶
	draft-sijeon-dmm-deployment-models, draft-liu-dmm-deployment-scenario		draft-sijeon-dmm-deployment-models, draft-liu-dmm-deployment-scenario
	and others. The work teams would like to thank the authors of these		and others. The work teams would like to thank the authors of these
	documents and additionally the discussions in DMM Working group that		documents and additionally the discussions in DMM Working group that
	helped shape this document.		helped shape this document.
	9. References		9. References
	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, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119,
	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
	[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-09
	(work in progress), March 2017.		(work in progress), October 2017.
	[I-D.ietf-sfc-nsh]		[I-D.ietf-sfc-nsh]
	Quinn, P., Elzur, U., and C. Pignataro, "Network Service		Quinn, P., Elzur, U., and C. Pignataro, "Network Service
	Header (NSH)", draft-ietf-sfc-nsh-19 (work in progress),		Header (NSH)", draft-ietf-sfc-nsh-28 (work in progress),
	August 2017.		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>.
	[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,		Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July
	July 2011, <https://www.rfc-editor.org/info/rfc6275>.		2011, <https://www.rfc-editor.org/info/rfc6275>.
	[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,
	<https://www.rfc-editor.org/info/rfc7333>.		<https://www.rfc-editor.org/info/rfc7333>.
	[RFC7429] Liu, D., Ed., Zuniga, JC., Ed., Seite, P., Chan, H., and		[RFC7429] Liu, D., Ed., Zuniga, JC., Ed., Seite, P., Chan, H., and
	CJ. Bernardos, "Distributed Mobility Management: Current		CJ. Bernardos, "Distributed Mobility Management: Current
	Practices and Gap Analysis", RFC 7429, DOI 10.17487/		Practices and Gap Analysis", RFC 7429,
	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
			Chaining (SFC) Architecture", RFC 7665,
			DOI 10.17487/RFC7665, October 2015,
			<https://www.rfc-editor.org/info/rfc7665>.
	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.
	75 lines changed or deleted		100 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/