draft-ietf-dmm-lma-controlled-mag-params-01.txt		draft-ietf-dmm-lma-controlled-mag-params-02.txt
	DMM WG D. Patki		DMM WG D. Patki
	Internet-Draft S. Gundavelli		Internet-Draft S. Gundavelli
	Intended status: Standards Track Cisco		Intended status: Standards Track Cisco
	Expires: October 15, 2016 J. Lee		Expires: January 2, 2017 J. Lee
	Sangmyung University		Sangmyung University
	Q. Fu		Q. Fu
	China Mobile		China Mobile
	L. Bertz		L. Bertz
	Sprint		Sprint
	April 13, 2016		July 1, 2016
	LMA Controlled MAG Session Parameters		LMA Controlled MAG Session Parameters
	draft-ietf-dmm-lma-controlled-mag-params-01.txt		draft-ietf-dmm-lma-controlled-mag-params-02.txt
	Abstract		Abstract
	This specification defines a new extension, LMA-Controlled-MAG-		This specification defines a new extension, LMA-Controlled-MAG-
	Session-Params to Proxy Mobile IPv6. This option can be used by the		Session-Params to Proxy Mobile IPv6. This option can be used by the
	LMA in PMIPv6 signaling for notifying the MAG to conform to various		LMA in PMIPv6 signaling for notifying the MAG to conform to various
	parameters contained in this extension.		parameters contained in this extension.
	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 http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on October 15, 2016.		This Internet-Draft will expire on January 2, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 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. Protocol Extension . . . . . . . . . . . . . . . . . . . . . . 3		3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . 3
	3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . . 4		3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 4
	3.1.1. Binding Re-registration Control Sub-Option . . . . . . 5		3.1.1. Binding Re-registration Control Sub-Option . . . . . 5
	3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . . 6		3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 5
	4. Protocol Configuration Variables . . . . . . . . . . . . . . . 6		4. Protocol Configuration Variables . . . . . . . . . . . . . . 6
	4.1. Local Mobility Anchor - Configuration Variables . . . . . 7		4.1. Local Mobility Anchor - Configuration Variables . . . . . 6
	5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8		5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8
	5.1. Local Mobility Anchor Considerations . . . . . . . . . . . 9		5.1. Local Mobility Anchor Considerations . . . . . . . . . . 9
	5.2. Mobile Access Gateway Considerations . . . . . . . . . . . 10		5.2. Mobile Access Gateway Considerations . . . . . . . . . . 9
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 11		7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 11		8.1. Normative References . . . . . . . . . . . . . . . . . . 10
	8.2. Informative References . . . . . . . . . . . . . . . . . . 11		8.2. Informative References . . . . . . . . . . . . . . . . . 11
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
	1. Introduction		1. Introduction
	A large PMIPv6 deployment, such as residential deployment, can have		A large PMIPv6 deployment, such as residential deployment, can have
	tens of thousands of MAGs spread across geographical locations.		tens of thousands of MAGs spread across geographical locations.
	While it can be operationally challenging to manage such a large		While it can be operationally challenging to manage such a large
	number of MAGs, it can also be very difficult to ensure configuration		number of MAGs, it can also be very difficult to ensure configuration
	consistency across all the MAGs if they are not centrally managed.		consistency across all the MAGs if they are not centrally managed.
	Configuring aggresive values of parameters such as re-registration		Configuring aggressive values of parameters such as re-registration
	timeout and heartbeat interval can potentially create considerable		timeout and heartbeat interval can potentially create considerable
	signaling load on the LMA. This document provides a new option to		signaling load on the LMA. This document provides a new option to
	enable the LMA to control various parameters on the MAG such as the		enable the LMA to control various parameters on the MAG such as the
	re-registration frequency [RFC5213] and heartbeat frequency		re-registration frequency [RFC5213] and heartbeat frequency
	[RFC5847]. With this option, the configuration of these tunable		[RFC5847]. With this option, the configuration of these tunable
	parameters done centrally on the LMA enables Service Providers to		parameters done centrally on the LMA enables Service Providers to
	have better control on the behavior of the MAGs with deterministic		have better control on the behavior of the MAGs with deterministic
	singaling load on the LMA.		singaling load on the LMA.
	2. Conventions and Terminology		2. Conventions and Terminology
	skipping to change at page 7, line 51 ¶		skipping to change at page 7, line 33 ¶
	per binding, per peering MAG, per cluster of MAGs or any other custom		per binding, per peering MAG, per cluster of MAGs or any other custom
	grouping. Regardless of the granularity of this configuration, the		grouping. Regardless of the granularity of this configuration, the
	local mobility anchor should be able to determine the value of these		local mobility anchor should be able to determine the value of these
	variables on an individual binding basis by way of configuration		variables on an individual binding basis by way of configuration
	hierarchy.		hierarchy.
	LCMPReregistrationStartTime		LCMPReregistrationStartTime
	This variable is used to set the minimum time interval in number		This variable is used to set the minimum time interval in number
	of seconds before the expiry of the PMIPv6 binding lifetime when		of seconds before the expiry of the PMIPv6 binding lifetime when
	the registration refresh process SHOULD be activated.		the registration refresh process SHOULD be activated. The default
			value is 10 units, where each unit is 4 seconds.
	LCMPInitialRetransmissionTime		LCMPInitialRetransmissionTime
	This variable is used to set the minimum delay in seconds before		This variable is used to set the minimum delay in seconds before
	the first PBU retransmission of the exponential back-off process.		the first PBU retransmission of the exponential back-off process.
	This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in		This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in
	Section 6.9.4 of [RFC5213].		Section 6.9.4 of [RFC5213]. The default value is 1 second.
	LCMPMaximumRetransmissionTime		LCMPMaximumRetransmissionTime
	This variable is used to set the maximum delay in seconds before		This variable is used to set the maximum delay in seconds before
	the last PBU retransmission message of the exponential back-off		the last PBU retransmission message of the exponential back-off
	process. This variable is same as MAX_BINDACK_TIMEOUT mentioned		process. This variable is same as MAX_BINDACK_TIMEOUT mentioned
	in Section 6.9.4 of [RFC5213].		in Section 6.9.4 of [RFC5213]. The default value is 32 seconds.
	LCMPHeartbeatInterval		LCMPHeartbeatInterval
	This variable is used to set the time delay in seconds after a		This variable is used to set the time delay in seconds after a
	successful heartbeat exchange (request followed by response) when		successful heartbeat exchange (request followed by response) when
	the next heartbeat exchange can be triggered. The default value		the next heartbeat exchange can be triggered. The default value
	is 60 seconds. It SHOULD NOT be set to less than 30 seconds or		is 60 seconds. It SHOULD NOT be set to less than 30 seconds or
	more than 3600 seconds. The value of this variable MAY be derived		more than 3600 seconds. The value of this variable MAY be derived
	from the variable HEARTBEAT_INTERVAL defined in Section 5 of		from the variable HEARTBEAT_INTERVAL defined in Section 5 of
	[RFC5847] if defined on the local mobility anchor.		[RFC5847] if defined on the local mobility anchor.
	LCMPHeartbeatRetransmissionDelay		LCMPHeartbeatRetransmissionDelay
	skipping to change at page 10, line 14 ¶		skipping to change at page 9, line 43 ¶
	5.2. Mobile Access Gateway Considerations		5.2. Mobile Access Gateway Considerations
	o On Receiving Proxy Binding Acknowledge message [RFC5213] from the		o On Receiving Proxy Binding Acknowledge message [RFC5213] from the
	local mobility anchor with LMA Controlled MAG Parameters mobility		local mobility anchor with LMA Controlled MAG Parameters mobility
	option, the mobile access gateway MUST overwrite the binding re-		option, the mobile access gateway MUST overwrite the binding re-
	registration related timer parameters with the parameters received		registration related timer parameters with the parameters received
	in Binding Re-registration Control Sub-Option, if present in the		in Binding Re-registration Control Sub-Option, if present in the
	LMA Controlled MAG Parameters mobility option. Similarly, the		LMA Controlled MAG Parameters mobility option. Similarly, the
	mobile access gateway MUST overwrite the heartbeat related timer		mobile access gateway MUST overwrite the heartbeat related timer
	parameters with the parameters reveived in Heartbeat Control Sub-		parameters with the parameters received in Heartbeat Control Sub-
	Option, if present in the LMA Controlled MAG Parameters mobility		Option, if present in the LMA Controlled MAG Parameters mobility
	option.		option.
	o If any of the parameters in the Binding Re-registration Control		o If any of the parameters in the Binding Re-registration Control
	Sub-Option is ZERO, then the sub-option MUST be ignored and an		Sub-Option is ZERO, then the sub-option MUST be ignored and an
	error message SHOULD be logged.		error message SHOULD be logged.
	o If any of the parameters in the Heartbeat Control Sub-Option		o If any of the parameters in the Heartbeat Control Sub-Option
	except HB-Retransmission-Delay is ZERO, then the sub-option MUST		except HB-Retransmission-Delay is ZERO, then the sub-option MUST
	be ignored and error message SHOULD be logged.		be ignored and error message SHOULD be logged.
	skipping to change at page 11, line 19 ¶		skipping to change at page 10, line 50 ¶
	specification is for use in Proxy Binding Acknowledgement message.		specification is for use in Proxy Binding Acknowledgement message.
	This option is carried like any other mobility header option as		This option is carried like any other mobility header option as
	specified in [RFC6275] and does not require any special security		specified in [RFC6275] and does not require any special security
	considerations.		considerations.
	8. References		8. References
	8.1. Normative References		8.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,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
	[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,		[RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
	Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",		Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
	RFC 5213, DOI 10.17487/RFC5213, August 2008,		RFC 5213, DOI 10.17487/RFC5213, August 2008,
	<http://www.rfc-editor.org/info/rfc5213>.		<http://www.rfc-editor.org/info/rfc5213>.
	[RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N.,		[RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N.,
	Krishnan, S., and J. Laganier, "Heartbeat Mechanism for		Krishnan, S., and J. Laganier, "Heartbeat Mechanism for
	Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847,		Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June
	June 2010, <http://www.rfc-editor.org/info/rfc5847>.		2010, <http://www.rfc-editor.org/info/rfc5847>.
	[RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen,		[RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen,
	J., and J. Kaippallimalil, "Extensions to the Proxy Mobile		J., and J. Kaippallimalil, "Extensions to the Proxy Mobile
	IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563,		IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563,
	DOI 10.17487/RFC7563, June 2015,		DOI 10.17487/RFC7563, June 2015,
	<http://www.rfc-editor.org/info/rfc7563>.		<http://www.rfc-editor.org/info/rfc7563>.
	8.2. Informative References		8.2. Informative References
	[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6		[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
	(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,		(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
	December 1998, <http://www.rfc-editor.org/info/rfc2460>.		December 1998, <http://www.rfc-editor.org/info/rfc2460>.
	[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, <http://www.rfc-editor.org/info/rfc6275>.		2011, <http://www.rfc-editor.org/info/rfc6275>.
	Authors' Addresses		Authors' Addresses
	Dhananjay Patki		Dhananjay Patki
	Cisco		Cisco
	Cessna Business Park SEZ, Kadubeesanahalli		Cessna Business Park SEZ, Kadubeesanahalli
	Bangalore, Karnataka 560087		Bangalore, Karnataka 560087
	India		India
	Email: dhpatki@cisco.com		Email: dhpatki@cisco.com
End of changes. 15 change blocks.
	36 lines changed or deleted		36 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/