draft-ietf-ancp-pon-01.txt		draft-ietf-ancp-pon-02.txt
	Network Working Group Nabil Bitar(ed.)		Network Working Group Nabil Bitar(ed.)
	Verizon		Verizon
	Internet Draft		Internet Draft
	Intended Status: Informational Sanjay Wadhwa (ed.)		Intended Status: Informational Sanjay Wadhwa (ed.)
	Alcatel-Lucent		Alcatel-Lucent
	Expires: January 11, 2012		Expires: June 16, 2012
	Thomas Haag		Thomas Haag
	Deutsche Telekom		Deutsche Telekom
	Hongyu Li		Hongyu Li
	HuaweiTechnologies		HuaweiTechnologies
	July 11, 2011		January 16, 2012
	Applicability of Access Node Control Mechanism to		Applicability of Access Node Control Mechanism to
	PON based Broadband Networks		PON based Broadband Networks
	draft-ietf-ancp-pon-01.txt		draft-ietf-ancp-pon-02.txt
	Abstract		Abstract
	The purpose of this document is to provide applicability of the		The purpose of this document is to provide applicability of the
	Access Node Control Mechanism, as described in [ANCP-FRAMEWORK],		Access Node Control Mechanism, as described in [RFC5851],
	to PON based broadband access. The need for an Access Node Control		to PON based broadband access. The need for an Access Node Control
	Mechanism between a Network Access Server (NAS) and an Access Node		Mechanism between a Network Access Server (NAS) and an Access Node
	Complex (a combination of Optical Line Termination (OLT) and		Complex (a combination of Optical Line Termination (OLT) and
	Optical Network Termination (ONT) elements) is described in a		Optical Network Termination (ONT) elements) is described in a
	multi-service reference architecture in order to perform QoS-		multi-service reference architecture in order to perform QoS-
	related, service-related and Subscriber-related operations. The		related, service-related and Subscriber-related operations. The
	Access Node Control Mechanism is also extended for interaction		Access Node Control Mechanism is also extended for interaction
	between components of the Access Node Complex (OLT and ONT). The		between components of the Access Node Complex (OLT and ONT). The
	Access Node Control mechanism will ensure that the transmission of		Access Node Control mechanism will ensure that the transmission of
	information between the NAS and Access Node Complex (ANX) and		information between the NAS and Access Node Complex (ANX) and
	skipping to change at page 2, line 13		skipping to change at page 2, line 13
	documents at any time. It is inappropriate to use Internet-Drafts		documents at any time. It is inappropriate to use Internet-Drafts
	as reference material or to cite them other than as "work in		as reference material or to cite them other than as "work in
	progress."		progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/1id-abstracts.html.		http://www.ietf.org/1id-abstracts.html.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on January 11, 2012.		This Internet-Draft will expire on June 16-02, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2012 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		carefully, as they describe your rights and restrictions with
	respect to this document. Code Components extracted from this		respect to this document. Code Components extracted from this
	document must include Simplified BSD License text as described in		document must include Simplified BSD License text as described in
	Section 4.e of the Trust Legal Provisions and are provided without		Section 4.e of the Trust Legal Provisions and are provided without
	skipping to change at page 4, line 47		skipping to change at page 4, line 47
	multicast on the Access Node (AN) complex composed of the Optical		multicast on the Access Node (AN) complex composed of the Optical
	Network Terminal (ONT) or Unit (ONU) and Optical Line Terminal (OLT),		Network Terminal (ONT) or Unit (ONU) and Optical Line Terminal (OLT),
	as applicable. This is as opposed to Digital Subscriber Line (DSL)		as applicable. This is as opposed to Digital Subscriber Line (DSL)
	deployments where multicast is enabled on the DSL Access Multiplexer		deployments where multicast is enabled on the DSL Access Multiplexer
	(DSLAM) only. The focus in this document will be on the ANCP		(DSLAM) only. The focus in this document will be on the ANCP
	requirements needed for coordinated admission control of unicast and		requirements needed for coordinated admission control of unicast and
	multicast video in FTTP/B/C PON environments between the AN complex		multicast video in FTTP/B/C PON environments between the AN complex
	(ANX) and the NAS, specifically focusing on bandwidth dedicated for		(ANX) and the NAS, specifically focusing on bandwidth dedicated for
	multicast and shared bandwidth between multicast and unicast.		multicast and shared bandwidth between multicast and unicast.
	[ANCP-FRAMEWORK] provides the framework and requirements for		[RFC5851] provides the framework and requirements for
	coordinated admission control between a NAS and an AN with special		coordinated admission control between a NAS and an AN with special
	focus on DSL deployments. This document extends that framework and		focus on DSL deployments. This document extends that framework and
	the related requirements to explicitly address PON deployments.		the related requirements to explicitly address PON deployments.
	3. Terminology		3. Terminology
	- PON (Passive Optical Network): a point-to-multipoint fiber to the		- PON (Passive Optical Network): a point-to-multipoint fiber to the
	premises network architecture in which unpowered splitters are used		premises network architecture in which unpowered splitters are used
	to enable the splitting of an optical signal from a central office on		to enable the splitting of an optical signal from a central office on
	a single optical fiber to multiple premises. Up to 32-128 may be		a single optical fiber to multiple premises. Up to 32-128 may be
	skipping to change at page 7, line 12		skipping to change at page 7, line 12
	ONT with multiple Ethernet ports, each connected to a living unit.		ONT with multiple Ethernet ports, each connected to a living unit.
	Thus, the ONT must not only be able to receive a multicast frame, but		Thus, the ONT must not only be able to receive a multicast frame, but
	must also be able to forward that frame only to the Ethernet port		must also be able to forward that frame only to the Ethernet port
	with receivers for the corresponding channel.		with receivers for the corresponding channel.
	In order to implement triple-play service delivery with necessary		In order to implement triple-play service delivery with necessary
	"quality-of-experience", including end-to-end bandwidth optimized		"quality-of-experience", including end-to-end bandwidth optimized
	multicast video delivery, there needs to be tight coordination		multicast video delivery, there needs to be tight coordination
	between the NAS and the ANX. This interaction needs to be near real-		between the NAS and the ANX. This interaction needs to be near real-
	time as services are requested via application or network level		time as services are requested via application or network level
	signaling by broadband subscribers. ANCP as defined in [ANCP-		signaling by broadband subscribers. ANCP as defined in [RFC5851]
	FRAMEWORK] for DSL based networks is very suitable to realize a		for DSL based networks is very suitable to realize a
	control protocol (with transactional exchange capabilities), between		control protocol (with transactional exchange capabilities), between
	PON enabled ANX and the NAS, and also between the components		PON enabled ANX and the NAS, and also between the components
	comprising the ANX i.e. between OLT and the ONT. Typical use cases		comprising the ANX i.e. between OLT and the ONT. Typical use cases
	for ANCP in PON environment include the following:		for ANCP in PON environment include the following:
	- Access topology discovery		- Access topology discovery
	- Access Loop Configuration		- Access Loop Configuration
	- Multicast		- Multicast
	skipping to change at page 16, line 13		skipping to change at page 16, line 13
	based on a non-subscriber request.		based on a non-subscriber request.
	Where network-based channel conditional access is desired, there are		Where network-based channel conditional access is desired, there are
	two approaches. It can be done on the NAS along with bandwidth based		two approaches. It can be done on the NAS along with bandwidth based
	admission control. The NAS can control the replication state on the		admission control. The NAS can control the replication state on the
	ANX based on the outcome of access and bandwidth based admission		ANX based on the outcome of access and bandwidth based admission
	control. This is covered a later section. The other approach is to		control. This is covered a later section. The other approach is to
	provision the necessary conditional access information on the ANX		provision the necessary conditional access information on the ANX
	(ONT/ONU and/or OLT) so the ANX can perform the conditional access		(ONT/ONU and/or OLT) so the ANX can perform the conditional access
	decisions autonomously. For these cases, the NAS can use ANCP to		decisions autonomously. For these cases, the NAS can use ANCP to
	provision black and white lists as defined in [ANCP-FRAMEWORK], on		provision black and white lists as defined in [RFC5851], on
	the ANX so that the ANX can decide locally to honor a join or not. It		the ANX so that the ANX can decide locally to honor a join or not. It
	should be noted that in the PON case, the ANX is composed of the		should be noted that in the PON case, the ANX is composed of the
	ONT/ONU and OLT. Thus, this information can be programmed on the		ONT/ONU and OLT. Thus, this information can be programmed on the
	ONT/ONU and/or OLT. Programming this information on the ONT/ONU		ONT/ONU and/or OLT. Programming this information on the ONT/ONU
	prevents illegitimate joins from propagating further into the		prevents illegitimate joins from propagating further into the
	network. A third approach, outside of the scope, may be to program		network. A third approach, outside of the scope, may be to program
	the HGW with the access list.		the HGW with the access list.
	A White list associated with an Access Port identifies the multicast		A White list associated with an Access Port identifies the multicast
	channels that are allowed to be replicated to that port. A Black		channels that are allowed to be replicated to that port. A Black
	list associated with an Access Port identifies the multicast channels		list associated with an Access Port identifies the multicast channels
	skipping to change at page 28, line 6		skipping to change at page 28, line 6
	flow to a particular Access Port or user starts and stops. Multicast		flow to a particular Access Port or user starts and stops. Multicast
	accounting can be addressed in two ways:		accounting can be addressed in two ways:
	- ANX keeps track of when replication starts or stops, and reports		- ANX keeps track of when replication starts or stops, and reports
	this information to the NAS for further processing. In this case,		this information to the NAS for further processing. In this case,
	ANCP can be used to send the information from the ANX to the NAS.		ANCP can be used to send the information from the ANX to the NAS.
	This can be done with the Information Report message. The NAS can		This can be done with the Information Report message. The NAS can
	then generate the appropriate time and/or volume accounting		then generate the appropriate time and/or volume accounting
	information per Access Loop and per multicast flow, to be sent to the		information per Access Loop and per multicast flow, to be sent to the
	accounting system. The ANCP requirements to support this approach are		accounting system. The ANCP requirements to support this approach are
	specified in [ANCP-FRAMEWORK. If the replication function is		specified in [RFC5851]. If the replication function is
	distributed between the OLT and ONT/ONU, a query from the NAS will		distributed between the OLT and ONT/ONU, a query from the NAS will
	result in OLT generating a query to the ONT/ONU.		result in OLT generating a query to the ONT/ONU.
	- ANX keeps track of when replication starts or stops, and		- ANX keeps track of when replication starts or stops, and
	generates the time and/or volume based accounting information per		generates the time and/or volume based accounting information per
	Access Loop and per multicast flow, before sending it to a central		Access Loop and per multicast flow, before sending it to a central
	accounting system for logging. Since ANX communicates with this		accounting system for logging. Since ANX communicates with this
	accounting system directly, the approach does not require the use of		accounting system directly, the approach does not require the use of
	ANCP. It is therefore beyond the scope of this document;		ANCP. It is therefore beyond the scope of this document;
	skipping to change at page 31, line 22		skipping to change at page 31, line 22
	Parameters of UNI (subscriber interface to HGW/CPE) of ONU/ONT can		Parameters of UNI (subscriber interface to HGW/CPE) of ONU/ONT can
	also be configured via ANCP. When the ONU/ONT supports ANCP,		also be configured via ANCP. When the ONU/ONT supports ANCP,
	parameters of the UNI on ONU/ONT are sent to the ONU/ONT via ANCP. If		parameters of the UNI on ONU/ONT are sent to the ONU/ONT via ANCP. If
	the ONU/ONT does not support ANCP, but only OMCI, parameters have to		the ONU/ONT does not support ANCP, but only OMCI, parameters have to
	be sent from the NAS to the OLT via ANCP first. Then, the OLT		be sent from the NAS to the OLT via ANCP first. Then, the OLT
	translates such configuration into OMCI and sends it to the ONU/ONT.		translates such configuration into OMCI and sends it to the ONU/ONT.
	9 Security Considerations		9 Security Considerations
	[ANCP-SECURITY] lists the ANCP related security threats that could be		[RFC5713] lists the ANCP related security threats that could be
	encountered on the Access Node and the NAS. It develops a threat		encountered on the Access Node and the NAS. It develops a threat
	model for ANCP security, and lists the security functions that are		model for ANCP security, and lists the security functions that are
	required at the ANCP level.		required at the ANCP level.
	With Multicast handling as described in this document, ANCP protocol		With Multicast handling as described in this document, ANCP protocol
	activity between the ANX and the NAS is triggered by join/leave		activity between the ANX and the NAS is triggered by join/leave
	requests coming from the end-user equipment. This could potentially		requests coming from the end-user equipment. This could potentially
	be used for denial of service attack against the ANX and/or the NAS.		be used for denial of service attack against the ANX and/or the NAS.
	To mitigate this risk, the NAS and ANX MAY implement control plane		To mitigate this risk, the NAS and ANX MAY implement control plane
	protection mechanisms such as limiting the number of multicast flows		protection mechanisms such as limiting the number of multicast flows
	a given user can simultaneously join, or limiting the maximum rate of		a given user can simultaneously join, or limiting the maximum rate of
	join/leave from a given user.		join/leave from a given user.
	Protection against invalid or unsubscribed flows can be deployed via		Protection against invalid or unsubscribed flows can be deployed via
	provisioning black lists as close to the subscriber as possible (e.g.		provisioning black lists as close to the subscriber as possible (e.g.
	in the ONT).		in the ONT).
	10 Differences in ANCP applicability between DSL and PON		10 Differences in ANCP applicability between DSL and PON
	As it currently stands, both ANCP framework [ANCP-FRAMEWORK] and		As it currently stands, both ANCP framework [RFC5851] and
	protocol [ANCP-PROTOCOL] are defined in context of DSL access. Due to		protocol [RFC6320] are defined in context of DSL access. Due to
	inherent differences between PON and DSL access technologies, ANCP		inherent differences between PON and DSL access technologies, ANCP
	needs a few extensions for supporting the use-cases outlined in this		needs a few extensions for supporting the use-cases outlined in this
	document for PON based access. These specific differences and		document for PON based access. These specific differences and
	extensions are outlined below.		extensions are outlined below.
	- In PON, the access-node functionality is split between OLT and ONT.		- In PON, the access-node functionality is split between OLT and ONT.
	Therefore, ANCP interaction between NAS and AN translates to		Therefore, ANCP interaction between NAS and AN translates to
	transactions between NAS and OLT and between OLT and ONT. The		transactions between NAS and OLT and between OLT and ONT. The
	processing of ANCP messages (e.g. for multicast replication control)		processing of ANCP messages (e.g. for multicast replication control)
	on the OLT can trigger generation of ANCP messages from OLT to ONT.		on the OLT can trigger generation of ANCP messages from OLT to ONT.
	skipping to change at page 34, line 21		skipping to change at page 34, line 21
	[RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation		[RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation
	over ATM Adaptation Layer 5", RFC 2684, September 1999.		over ATM Adaptation Layer 5", RFC 2684, September 1999.
	14.2. Informative References		14.2. Informative References
	[RFC2881] Mitton, D. and M. Beadles, "Network Access Server		[RFC2881] Mitton, D. and M. Beadles, "Network Access Server
	Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, Jul		Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, Jul
	2000.		2000.
	[ANCP-FRAMEWORK] Ooghe, S., et al., "Framework and Requirements		[RFC5851] Ooghe, S., et al., "Framework and Requirements
	for Access Node Control Mechanism in Broadband Networks", RFC 5851,		for Access Node Control Mechanism in Broadband Networks", RFC 5851,
	May 2010.		May 2010.
	[G.983.1] ITU-T recommendation G.983.1, Broadband optical access		[G.983.1] ITU-T recommendation G.983.1, Broadband optical access
	systems based on Passive Optical Networks (PON).		systems based on Passive Optical Networks (PON).
	[G.984.1] ITU-T recommendation G.984.1 Gigabit-capable Passive		[G.984.1] ITU-T recommendation G.984.1 Gigabit-capable Passive
	Optical Networks (G-PON): General characteristics		Optical Networks (G-PON): General characteristics
	[TR-101] Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL		[TR-101] Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL
	Aggregation", DSL Forum TR-101, May 2006.		Aggregation", DSL Forum TR-101, May 2006.
	[ANCP-SECURITY] Moustafa, H., Tschofenig, H., and S. De Cnodder,		[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder,
	"Security Threats and Security Requirements for the Access Node		"Security Threats and Security Requirements for the Access Node
	Control Protocol (ANCP)", RFC 5713, January 2010.		Control Protocol (ANCP)", RFC 5713, January 2010.
	[OMCI] ITU-T recommendation G.984.4 GPON ONT Management and Control		[OMCI] ITU-T recommendation G.984.4 GPON ONT Management and Control
	Interface (OMCI) Specifications.		Interface (OMCI) Specifications.
	[ANCP-PROTOCOL] Wadhwa, S et al, "Protocol for Access Node Control		[RFC6320] Taylor, T., et al, "Protocol for Access Node Control
	Mechanism in Broadband Networks", draft-ietf-ancp-protocol-17.txt,		Mechanism in Broadband Networks", RFC 6320, October 2011.
	April 2011, work in progress.
	Authors' Addresses		Authors' Addresses
	Nabil Bitar		Nabil Bitar
	Verizon		Verizon
	60 Sylvan Road		60 Sylvan Road
	Waltham, MA 02451		Waltham, MA 02451
	Email: nabil.n.bitar@verizon.com		Email: nabil.n.bitar@verizon.com
	Sanjay Wadhwa		Sanjay Wadhwa
	Alcatel-Lucent		Alcatel-Lucent
End of changes. 15 change blocks.
	19 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/