< draft-ietf-ancp-mc-extensions-10.txt		draft-ietf-ancp-mc-extensions-11.txt >
	ANCP F. Le Faucheur		ANCP F. Le Faucheur
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track R. Maglione		Intended status: Standards Track R. Maglione
	Expires: February 23, 2014 Cisco Systems		Expires: May 18, 2014 Cisco Systems
	T. Taylor		T. Taylor
	Huawei		Huawei
	August 22, 2013		November 14, 2013
	Multicast Control Extensions for ANCP		Multicast Control Extensions for ANCP
	draft-ietf-ancp-mc-extensions-10.txt		draft-ietf-ancp-mc-extensions-11.txt
	Abstract		Abstract
	This document specifies the extensions to the Access Node Control		This document specifies the extensions to the Access Node Control
	Protocol required for support of the multicast use cases defined in		Protocol required for support of the multicast use cases defined in
	the Access Node Control Protocol framework document and one		the Access Node Control Protocol framework document and one
	additional use case described in this document. These use cases are		additional use case described in this document. These use cases are
	organized into the following ANCP capabilities:		organized into the following ANCP capabilities:
	o NAS-initiated multicast replication;		o NAS-initiated multicast replication;
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	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 February 23, 2014.		This Internet-Draft will expire on May 18, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 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.
	This document may contain material from IETF Documents or IETF
	Contributions published or made publicly available before November
	10, 2008. The person(s) controlling the copyright in some of this
	material may not have granted the IETF Trust the right to allow
	modifications of such material outside the IETF Standards Process.
	Without obtaining an adequate license from the person(s) controlling
	the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may
	not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other
	than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6		3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6
	3.1. NAS Initiated Multicast Replication Control Use Case . . 7		3.1. NAS Initiated Multicast Replication Control Use Case . . 7
	3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7		3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7
	3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7		3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7
	3.2. Conditional Access and Admission Control Use Case . . . . 8		3.2. Conditional Access and Admission Control Use Case . . . . 8
	3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8		3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8
	skipping to change at page 3, line 7 ¶		skipping to change at page 2, line 43 ¶
	3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9		3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9
	3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9		3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9
	3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10		3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10
	3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10		3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10
	3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10		3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10
	4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11		4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11
	4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11		4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11
	4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12		4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12
	4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13		4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13
	4.2. Port Management Message . . . . . . . . . . . . . . . . . 14		4.2. Port Management Message . . . . . . . . . . . . . . . . . 14
	4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15		4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 14
	4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15		4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15
	4.3. Multicast Replication Control Message . . . . . . . . . . 16		4.3. Multicast Replication Control Message . . . . . . . . . . 15
	4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19		4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19
	4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 20		4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 19
	4.4. Multicast Admission Control Message . . . . . . . . . . . 22		4.4. Multicast Admission Control Message . . . . . . . . . . . 22
	4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23		4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23
	4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24		4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 23
	4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25		4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25
	4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25		4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25
	4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26		4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26
	4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29		4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29
	4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30		4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 29
	4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30		4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30
	4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31		4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31
	4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31		4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31
	4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31		4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31
	4.8. Delegated Bandwidth Query Response Message . . . . . . . 32		4.8. Delegated Bandwidth Query Response Message . . . . . . . 32
	4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32		4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32
	4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32		4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32
	4.9. Multicast Flow Query Request and Response Messages . . . 33		4.9. Multicast Flow Query Request and Response Messages . . . 33
	4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34		4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 33
	4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34		4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34
	4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36		4.10. Committed Bandwidth Report Message . . . . . . . . . . . 35
	4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36		4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36
	4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36		4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36
	5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37		5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 36
	5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37		5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 36
	5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38		5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 37
	5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39		5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 38
	5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41		5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 40
	5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42		5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 41
	5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42		5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42
	5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43		5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 42
	5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43		5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43
	5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 44		5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 43
	5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44		5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44
	5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45		5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45
	5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46		5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46
	5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 47		5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 46
	6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47		6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47
	6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48		6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48
	6.1.1. Protocol Requirements For NAS-Initiated Replication . 48		6.1.1. Protocol Requirements For NAS-Initiated Replication . 48
	6.1.2. Protocol Requirements For Committed Multicast		6.1.2. Protocol Requirements For Committed Multicast
	Bandwidth Reporting . . . . . . . . . . . . . . . . . 49		Bandwidth Reporting . . . . . . . . . . . . . . . . . 49
	6.1.3. Protocol Requirements For Conditional Access With		6.1.3. Protocol Requirements For Conditional Access With
	White and Black Lists . . . . . . . . . . . . . . . . 50		White and Black Lists . . . . . . . . . . . . . . . . 49
	6.1.4. Protocol Requirements For Conditional Access With		6.1.4. Protocol Requirements For Conditional Access With
	Grey Lists . . . . . . . . . . . . . . . . . . . . . 50		Grey Lists . . . . . . . . . . . . . . . . . . . . . 50
	6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52		6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 51
	6.2. Capability-Specific Procedures for Providing Multicast		6.2. Capability-Specific Procedures for Providing Multicast
	Service . . . . . . . . . . . . . . . . . . . . . . . . . 52		Service . . . . . . . . . . . . . . . . . . . . . . . . . 52
	6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52		6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52
	6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53		6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53
	6.2.3. Procedures For Conditional Access With Black and		6.2.3. Procedures For Conditional Access With Black and
	White Lists . . . . . . . . . . . . . . . . . . . . . 54		White Lists . . . . . . . . . . . . . . . . . . . . . 54
	6.2.4. Procedures For Conditional Access With Grey Lists . . 56		6.2.4. Procedures For Conditional Access With Grey Lists . . 55
	6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57		6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57
	6.3. Combinations of Multicast Capabilities . . . . . . . . . 58		6.3. Combinations of Multicast Capabilities . . . . . . . . . 58
	6.3.1. Combination of Conditional Access With White and		6.3.1. Combination of Conditional Access With White and
	Black Lists and Conditional Access With Grey Lists . 58		Black Lists and Conditional Access With Grey Lists . 58
	6.3.2. Combination of Conditional Access With Delegated		6.3.2. Combination of Conditional Access With Delegated
	Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60		Bandwidth . . . . . . . . . . . . . . . . . . . . . . 59
	6.3.3. Combination of NAS-Initiated Replication with Other		6.3.3. Combination of NAS-Initiated Replication with Other
	Capabilities . . . . . . . . . . . . . . . . . . . . 60		Capabilities . . . . . . . . . . . . . . . . . . . . 59
	6.3.4. Combinations of Committed Bandwidth Reporting with		6.3.4. Combinations of Committed Bandwidth Reporting with
	Other Multicast Capabilities . . . . . . . . . . . . 61		Other Multicast Capabilities . . . . . . . . . . . . 60
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 61		7. Security Considerations . . . . . . . . . . . . . . . . . . . 60
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 64		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 63
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 64		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 63
	10.1. Normative References . . . . . . . . . . . . . . . . . . 64		10.1. Normative References . . . . . . . . . . . . . . . . . . 63
	10.2. Informative References . . . . . . . . . . . . . . . . . 64		10.2. Informative References . . . . . . . . . . . . . . . . . 64
	Appendix A. Example of Messages and Message Flows . . . . . . . 65		Appendix A. Example of Messages and Message Flows . . . . . . . 64
	A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 66		A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 65
	A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70		A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70
	A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75		A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75
	A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79		A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79
	A.5. Handling Of Requests To Join and Leave the On-Line Game . 80		A.5. Handling Of Requests To Join and Leave the On-Line Game . 79
	A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 82		A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 81
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 85		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84
	1. Introduction		1. Introduction
	[RFC5851] defines a framework and requirements for an Access Node		[RFC5851] defines a framework and requirements for an Access Node
	control mechanism between a Network Access Server (NAS) and an Access		control mechanism between a Network Access Server (NAS) and an Access
	Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a		Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a
	multi-service reference architecture in order to perform QoS-related,		multi-service reference architecture in order to perform QoS-related,
	service-related and subscriber-related operations. [RFC6320]		service-related and subscriber-related operations. [RFC6320]
	specifies a protocol for Access Node Control in broadband networks in		specifies a protocol for Access Node Control in broadband networks in
	line with this framework.		line with this framework.
	skipping to change at page 5, line 18 ¶		skipping to change at page 5, line 4 ¶
	However, it does not support the multicast use cases defined in		However, it does not support the multicast use cases defined in
	[RFC5851]. The present document specifies the extensions to the		[RFC5851]. The present document specifies the extensions to the
	Access Node Control Protocol required for support of these multicast		Access Node Control Protocol required for support of these multicast
	use cases. In addition, it supports the Committed Bandwidth		use cases. In addition, it supports the Committed Bandwidth
	Reporting use case, described below. In terms of the ANCP protocol,		Reporting use case, described below. In terms of the ANCP protocol,
	these use cases are organized into five capabilities:		these use cases are organized into five capabilities:
	o NAS-initiated multicast replication;		o NAS-initiated multicast replication;
	o conditional access with white and black lists;		o conditional access with white and black lists;
	o conditional access with grey lists;		o conditional access with grey lists;
	o bandwidth delegation;		o bandwidth delegation;
	o committed bandwidth reporting.		o committed bandwidth reporting.
	NAS-initiated multicast replication assumes that multicast "join" and		NAS-initiated multicast replication assumes that multicast "join" and
	"leave" requests are terminated on the NAS, or that the NAS receives		"leave" requests are terminated on the NAS, or that the NAS receives
	requests to establish multicast sessions through other means (e.g.,		requests to establish multicast sessions through other means (e.g.,
	application-level signalling). The NAS sends commands to the AN to		application-level signalling). The NAS sends commands to the AN to
	start or stop replication of specific multicast flows on specific		start or stop replication of specific multicast flows on specific
	subscriber ports. This use case is described briefly in the next-to-		subscriber ports. This use case is described briefly in the next-to-
	last paragraph of Section 3.4 of [RFC5851].		last paragraph of Section 3.4 of [RFC5851].
	Conditional access is described in Sections 3.4.1 and 3.4.2.3 of		Conditional access is described in Section 3.4.1 and Section 3.4.2.3
	[RFC5851], with the latter section particularly applicable to		of [RFC5851], with the latter section particularly applicable to
	operation with white and black lists only. In case of "conditional		operation with white and black lists only. In case of "conditional
	access with white and black lists", multicast join and leave requests		access with white and black lists", multicast join and leave requests
	are terminated at the AN and accepted or ignored in accordance with		are terminated at the AN and accepted or ignored in accordance with
	the direction provided by white and black lists respectively. The		the direction provided by white and black lists respectively. The
	white and black lists are provisioned per port at startup time and		white and black lists are provisioned per port at startup time and
	may be modified thereafter. The NAS may enable admission control of		may be modified thereafter. The NAS may enable admission control of
	white-listed flows by appropriate provisioning.		white-listed flows by appropriate provisioning.
	Conditional access with grey lists is similar to conditional access		Conditional access with grey lists is similar to conditional access
	with white lists, except that before accepting any request matching a		with white lists, except that before accepting any request matching a
	skipping to change at page 24, line 45 ¶		skipping to change at page 24, line 33 ¶
	* MUST contain the directive as accepted by the NAS. The NAS MAY		* MUST contain the directive as accepted by the NAS. The NAS MAY
	modify the Accounting field if flow accounting is required.		modify the Accounting field if flow accounting is required.
	o if the directive in the Multicast Admission Control message is "1		o if the directive in the Multicast Admission Control message is "1
	- Add", is processed correctly but not accepted by the NAS (i.e.,		- Add", is processed correctly but not accepted by the NAS (i.e.,
	it does not pass the admission control or conditional access		it does not pass the admission control or conditional access
	check), the NAS MAY generate a Multicast Replication Control		check), the NAS MAY generate a Multicast Replication Control
	message in response to the Multicast Admission Control message.		message in response to the Multicast Admission Control message.
	This optional message can be used by the AN to maintain statistics		This optional message can be used by the AN to maintain statistics
	about admission control rejections.		about admission control rejections. When used in this situation,
			the Multicast Replication Control message:
	In the future, the AN may be able to notify the subscriber that
	the request was rejected (e.g., using
	[I-D.morin-mboned-igmpmld-error-feedback]).
	When used in this situation, the Multicast Replication Control
	message:
	* MUST contain a Result set to 0x0;		* MUST contain a Result set to 0x0;
	* MUST contain a Transaction ID with a unique value, as described		* MUST contain a Transaction ID with a unique value, as described
	in Section 3.6.1.6 of [RFC6320];		in Section 3.6.1.6 of [RFC6320];
	* MUST contain the directive rejected by the NAS (i.e., Target		* MUST contain the directive rejected by the NAS (i.e., Target
	TLV and Command TLV) but with a Command Code set to "4 -		TLV and Command TLV) but with a Command Code set to "4 -
	Admission Control Reject", "5 - Conditional Access Reject", or		Admission Control Reject", "5 - Conditional Access Reject", or
	"6 - Admission Control and Conditional Access Reject" as		"6 - Admission Control and Conditional Access Reject" as
	skipping to change at page 64, line 23 ¶		skipping to change at page 63, line 38 ¶
	that formed the base of the Multicast Flow Reporting solution.		that formed the base of the Multicast Flow Reporting solution.
	Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided		Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided
	substantial contributions on the solution for the NAS initiated		substantial contributions on the solution for the NAS initiated
	multicast control use case. Kristian Poscic provided the committed		multicast control use case. Kristian Poscic provided the committed
	bandwidth reporting use case.		bandwidth reporting use case.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/		[PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim-
	EUI48.html", 2010.		parameters.xhtml", 2005.
	[IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
	EUI64.html", 2010.
	[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, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast		[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
	Listener Discovery (MLD) for IPv6", RFC 2710, October		Listener Discovery (MLD) for IPv6", RFC 2710, October
	1999.		1999.
	[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.		[RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
	Thyagarajan, "Internet Group Management Protocol, Version		Thyagarajan, "Internet Group Management Protocol, Version
	skipping to change at page 64, line 49 ¶		skipping to change at page 64, line 14 ¶
	[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery		[RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery
	Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.		Version 2 (MLDv2) for IPv6", RFC 3810, June 2004.
	[RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T.		[RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T.
	Taylor, "Protocol for Access Node Control Mechanism in		Taylor, "Protocol for Access Node Control Mechanism in
	Broadband Networks", RFC 6320, October 2011.		Broadband Networks", RFC 6320, October 2011.
	10.2. Informative References		10.2. Informative References
	[I-D.morin-mboned-igmpmld-error-feedback]		[IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
	Morin, T. and B. Haberman, "IGMP/MLD Error Feedback",		EUI48.html", 2010.
	draft-morin-mboned-igmpmld-error-feedback-02 (work in
	progress), November 2008.
	[PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim-
	parameters.xhtml", 2005.
	[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,		[IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/
	"Protocol Independent Multicast - Sparse Mode (PIM-SM):		EUI64.html", 2010.
	Protocol Specification (Revised)", RFC 4601, August 2006.
	[RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol		[RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
	Independent Multicast (PIM) Join Attribute Format", RFC		Independent Multicast (PIM) Join Attribute Format", RFC
	5384, November 2008.		5384, November 2008.
	[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security		[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security
	Threats and Security Requirements for the Access Node		Threats and Security Requirements for the Access Node
	Control Protocol (ANCP)", RFC 5713, January 2010.		Control Protocol (ANCP)", RFC 5713, January 2010.
	[RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.		[RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.
	skipping to change at page 68, line 40 ¶		skipping to change at page 67, line 43 ¶
	NAS.		NAS.
	As soon as the AN port comes up, the AN sends an ANCP PORT_UP message		As soon as the AN port comes up, the AN sends an ANCP PORT_UP message
	to the NAS specifying the Access Loop Circuit ID. The NAS replies		to the NAS specifying the Access Loop Circuit ID. The NAS replies
	with an ANCP Port Management message that, together with the other		with an ANCP Port Management message that, together with the other
	parameters, includes the multicast service profile name to be		parameters, includes the multicast service profile name to be
	associated to that port along with the initial amount of delegated		associated to that port along with the initial amount of delegated
	bandwidth. The corresponding message flow is illustrated in Figure		bandwidth. The corresponding message flow is illustrated in Figure
	21.		21.
	+----------+ +---------+ +-----+ +-----+		+----------+ +---------+ +-----+ +-----+
	|Subscriber| | Home | | AN | | NAS |		|Subscriber| | Home | | AN | | NAS |
	+----------+ | Gateway | +-----+ +-----+		+----------+ | Gateway | +-----+ +-----+
	| +---------+ | |		| +---------+ | |
	| | | |		| | | |
	| | | |		| | | |
	| | DSL Synch. | |		| | DSL Synch. | |
	| |--------------------->| |		| |---------------->| |
	| | |(M1)PORT_UP(Port ID) |		| | |(M1)PORT_UP(Port ID) |
	| | |-------------------->|		| | |-------------------->|
	| | | (*)		| | | (*)
	| | |(M2) PORT_MNGT |		| | |(M2) PORT_MNGT |
	| | | (Port ID, |		| | | (Port ID, |
	| | |Mcast S Profile Name,|		| | |Mcast S Profile Name,|
	| | |Bandwidth Allocation)|		| | |Bandwidth Allocation)|
	| | |<--------------------|		| | |<--------------------|
	(*) The NAS may optionally seek direction from an external		(*) The NAS may optionally seek direction from an external
	Autorization/Policy Server		Autorization/Policy Server
	Figure 21: Configuring an AN Port With Multicast Service Profile ID		Figure 21: Configuring an AN Port With Multicast Service Profile ID
	and Delegated Bandwidth Amount		and Delegated Bandwidth Amount
	The Port Management message will typically contain other TLVs but our		The Port Management message will typically contain other TLVs but our
	example (Figure 22) just shows the Target, Multicast-Service-Profile-		example (Figure 22) just shows the Target, Multicast-Service-Profile-
	Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the		Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the
	skipping to change at page 81, line 24 ¶		skipping to change at page 81, line 6 ¶
	Figure 32: NAS-Initiated Flows For On-Line Gaming		Figure 32: NAS-Initiated Flows For On-Line Gaming
	Multicast Replication Control message (M1) in Figure 33 looks like		Multicast Replication Control message (M1) in Figure 33 looks like
	the message in Figure 25 with two exceptions. The first is that the		the message in Figure 25 with two exceptions. The first is that the
	NAS has the option to set the Result field to AckAll (0x02) if it		NAS has the option to set the Result field to AckAll (0x02) if it
	needs positive reassurance that the flow has been enabled. This was		needs positive reassurance that the flow has been enabled. This was
	not done here to save having to depict a response differing only in		not done here to save having to depict a response differing only in
	the Result field. The larger difference in this example is that the		the Result field. The larger difference in this example is that the
	flow description in the Multicast-Flow embedded TLV is that of an ASM		flow description in the Multicast-Flow embedded TLV is that of an ASM
	multicast group (Flow Type = 0x01) with IPv4 (0x01) group address		multicast group (Flow Type = 0x01) with IPv4 (0x01) group address
	233.252.1.100.		233.252.0.100.
	1 2 3		1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type (0x880C) | Length = 44 |		| Type (0x880C) | Length = 44 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Version | Msg Type=144 | 0x1 | Result Code = 0x000 |		| Version | Msg Type=144 | 0x1 | Result Code = 0x000 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Partition ID | Transaction Identifier |		| Partition ID | Transaction Identifier |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 81, line 51 ¶		skipping to change at page 81, line 33 ¶
	| Access Loop Circuit ID |		| Access Loop Circuit ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Command TLV Type = 0x11 | TLV Length = 16 |		| Command TLV Type = 0x11 | TLV Length = 16 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 |		| Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 |		|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 |		|Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Multicast Group Address = 233.252.1.100 |		| Multicast Group Address = 233.252.0.100 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
	Figure 33: Enabling The Subscriber To Join An On-Line Game		Figure 33: Enabling The Subscriber To Join An On-Line Game
	Message M2 terminating the flow when the subscriber leaves the game		Message M2 terminating the flow when the subscriber leaves the game
	looks the same as the message in Figure 33 with two exceptions: the		looks the same as the message in Figure 33 with two exceptions: the
	Command Code becomes Delete (2), and Accounting is set to 0 to turn		Command Code becomes Delete (2), and Accounting is set to 0 to turn
	off flow accounting. Of course, the Transaction Identifier values		off flow accounting. Of course, the Transaction Identifier values
	will differ between the two messages.		will differ between the two messages.
	skipping to change at page 83, line 41 ¶		skipping to change at page 83, line 22 ¶
	| |		| |
	~ Access Loop Circuit ID (port11) ~		~ Access Loop Circuit ID (port11) ~
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 35: Multicast Flow Query Request Message For Per-Port		Figure 35: Multicast Flow Query Request Message For Per-Port
	Multicast Flow Reporting		Multicast Flow Reporting
	The Multicast Flow Query Response message (M2) is illustrated in		The Multicast Flow Query Response message (M2) is illustrated in
	Figure 36. It indicates that there is one active multicast flow		Figure 36. It indicates that there is one active multicast flow
	[(192.0.2.1, 233.252.2.4)] on port 10, no active multicast flow on		[(192.0.2.1, 233.252.0.4)] on port 10, no active multicast flow on
	port 20 and two active multicast flows [(192.0.2.1, 233.252.2.4) and		port 20 and two active multicast flows [(192.0.2.1, 233.252.0.4) and
	(192.0.2.2, 233.252.2.10)] on port 11.		(192.0.2.2, 233.252.0.10)] on port 11.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type (0x880C) | Length |		| Type (0x880C) | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Version | Msg Type = 149|Rslt=3 | Result Code = 0 |		| Version | Msg Type = 149|Rslt=3 | Result Code = 0 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Partition ID | Transaction Identifier |		| Partition ID | Transaction Identifier |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 84, line 20 ¶		skipping to change at page 83, line 49 ¶
	| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |		| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Access Loop Circuit ID (port10) ~		~ Access Loop Circuit ID (port10) ~
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |		|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |		|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Multicast Group Address = 233.252.2.4 |		| Multicast Group Address = 233.252.0.4 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Unicast Source Address = 192.0.2.1 |		| Unicast Source Address = 192.0.2.1 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
	| Type = 0x1000 (Target) | Target TLV Length |		| Type = 0x1000 (Target) | Target TLV Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |		| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Access Loop Circuit ID (port20) ~		~ Access Loop Circuit ID (port20) ~
	| |		| |
	skipping to change at page 84, line 44 ¶		skipping to change at page 84, line 25 ¶
	| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |		| Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	~ Access Loop Circuit ID (port11) ~		~ Access Loop Circuit ID (port11) ~
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |		|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |		|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Multicast Group Address = 233.252.2.4 |		| Multicast Group Address = 233.252.0.4 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Unicast Source Address = 192.0.2.1 |		| Unicast Source Address = 192.0.2.1 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
	|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |		|Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |		|Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Multicast Group Address: 233.252.2.10 |		| Multicast Group Address: 233.252.0.10 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Unicast Source Address = 192.0.2.2 |		| Unicast Source Address = 192.0.2.2 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+
	Figure 36: Multicast Flow Query Response message For Per-Port		Figure 36: Multicast Flow Query Response message For Per-Port
	Multicast Flow Reporting		Multicast Flow Reporting
	Authors' Addresses		Authors' Addresses
	Francois Le Faucheur		Francois Le Faucheur
End of changes. 38 change blocks.
	99 lines changed or deleted		70 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/