draft-ietf-mboned-multiaaa-framework-11.txt		draft-ietf-mboned-multiaaa-framework-12.txt
	mboned H. Satou,		mboned H. Satou,
	Internet-Draft H. Ohta,		Internet-Draft H. Ohta,
	Intended status: Informational T. Hayashi,		Intended status: Informational T. Hayashi,
	Expires: September 6, 2010 NTT		Expires: February 25, 2011 NTT
	C. Jacquenet		C. Jacquenet
	France Telecom		France Telecom
	H. He		H. He
	Nortel		Nortel
	March 5, 2010		August 24, 2010
	AAA and Admission Control Framework for Multicasting		AAA and Admission Control Framework for Multicasting
	draft-ietf-mboned-multiaaa-framework-11		draft-ietf-mboned-multiaaa-framework-12
	Abstract		Abstract
	IP multicast-based services, such as TV broadcasting or		IP multicast-based services, such as TV broadcasting or
	videoconferencing raise the issue of making sure that potential		videoconferencing raise the issue of making sure that potential
	customers are fully entitled to access the corresponding contents.		customers are fully entitled to access the corresponding contents.
	There is indeed a need for service and content providers to identify		There is indeed a need for service and content providers to identify
	users (if not authenticate, especially within the context of		users (if not authenticate, especially within the context of
	enforcing electronic payment schemes) and to retrieve statistical		enforcing electronic payment schemes) and to retrieve statistical
	information for accounting purposes, as far as content and network		information for accounting purposes, as far as content and network
	usage are concerned. This memo describes the framework for		usage are concerned. This memo describes the framework for
	specifying the Authentication, Authorization and Accounting (AAA)		specifying the Authorization, Authentication and Accounting (AAA)
	capabilities that could be activated within the context of the		capabilities that could be activated within the context of the
	deployment and the operation of IP multicast-based services. This		deployment and the operation of IP multicast-based services. This
	framework addresses the requirements presented in "Requirements for		framework addresses the requirements presented in "Requirements for
	Accounting, Authentication and Authorization in Well Managed IP		Accounting, Authentication and Authorization in Well Managed IP
	Multicasting Services" [I-D.ietf-mboned-maccnt-req]. The memo		Multicasting Services" [I-D.ietf-mboned-maccnt-req]. The memo
	provides a basic AAA enabled model as well as an extended fully		provides a basic AAA enabled model as well as an extended fully
	enabled model with resource and admission control coordination.		enabled model with resource and admission control coordination.
	Status of this Memo		Status of this Memo
	skipping to change at page 2, line 16		skipping to change at page 2, line 16
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	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 September 6, 2010.		This Internet-Draft will expire on February 25, 2011.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Purpose and Background . . . . . . . . . . . . . . . . . . 3		1.1. Purpose and Background . . . . . . . . . . . . . . . . . . 3
	2. Definitions and Abbreviations . . . . . . . . . . . . . . . . 4		2. Definitions and Abbreviations . . . . . . . . . . . . . . . . 4
	2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4		2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4
	2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5		2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
	3. Common use models and network architecture implications . . . 6		3. Common use models and network architecture implications . . . 6
	4. Framework and Roles of Entities . . . . . . . . . . . . . . . 7		4. Framework and Roles of Entities . . . . . . . . . . . . . . . 7
	skipping to change at page 8, line 21		skipping to change at page 8, line 21
	The content may be associated with (or managed by) a specific CP. In		The content may be associated with (or managed by) a specific CP. In
	this case, when the user selects content, the CP is automatically		this case, when the user selects content, the CP is automatically
	selected.		selected.
	Requests for multicast sent by the user to a selected NSP should		Requests for multicast sent by the user to a selected NSP should
	include enough information not only for authentication by the CP but		include enough information not only for authentication by the CP but
	also for CP selection and admission control by the NSP.		also for CP selection and admission control by the NSP.
	When an NSP receives a request for multicast from a user, the NSP		When an NSP receives a request for multicast from a user, the NSP
	requests the appropriate CP to make sure that the user is entitled to		requests the appropriate CP to make sure that the user is entitled to
	access the corresponding content as the NSP is responsible for		access the corresponding content As the NSP is responsible for
	managing its network resources, the NSP may perform admission		managing its network resources, the NSP may perform admission
	control.The NSP will allow access to the multicast service, depending		control.The NSP will allow access to the multicast service, depending
	on both the response sent by the CP and the availability of resources		on both the response sent by the CP and the availability of resources
	operated by the NSP. That is, the NSP will forward multicast traffic		operated by the NSP. That is, the NSP will forward multicast traffic
	towards the user only when the NSP has 1) made sure the user is		towards the user only when the NSP has 1) made sure the user is
	entitled to access the network resources operated by the NSP, 2)		entitled to access the network resources operated by the NSP, 2)
	received a confirmation from the CP that the user is entitled to		received a confirmation from the CP that the user is entitled to
	access the content and (possibly) 3) determined that the network		access the content and (possibly) 3) determined that the network
	resources (e.g. bandwidth) are sufficient to deliver the multicast		resources (e.g. bandwidth) are sufficient to deliver the multicast
	traffic to the user with the relevant level of quality. When neither		traffic to the user with the relevant level of quality. When neither
	skipping to change at page 20, line 22		skipping to change at page 20, line 22
	meet the requirements. Further work should be done to specify the		meet the requirements. Further work should be done to specify the
	interfaces between the user and NSP, NAS and mAAA, mAAA and MACF and		interfaces between the user and NSP, NAS and mAAA, mAAA and MACF and
	NSP-mAAA and CP-AAA (presented in 5.2.)		NSP-mAAA and CP-AAA (presented in 5.2.)
	10. Normative References		10. Normative References
	[I-D.ietf-ancp-framework]		[I-D.ietf-ancp-framework]
	Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.		Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S.
	Wadhwa, "Framework and Requirements for an Access Node		Wadhwa, "Framework and Requirements for an Access Node
	Control Mechanism in Broadband Multi-Service Networks",		Control Mechanism in Broadband Multi-Service Networks",
	draft-ietf-ancp-framework-11 (work in progress),		draft-ietf-ancp-framework-12 (work in progress),
	July 2009.		July 2009.
	[I-D.ietf-mboned-maccnt-req]		[I-D.ietf-mboned-maccnt-req]
	Hayashi, T., He, H., Satou, H., Ohta, H., and S. Vaidya,		Hayashi, T., He, H., Satou, H., Ohta, H., and S. Vaidya,
	"Requirements for Multicast AAA coordinated between		"Requirements for Multicast AAA coordinated between
	Content Provider(s) and Network Service Provider(s)",		Content Provider(s) and Network Service Provider(s)",
	draft-ietf-mboned-maccnt-req-08 (work in progress),		draft-ietf-mboned-maccnt-req-08 (work in progress),
	July 2009.		July 2009.
	Authors' Addresses		Authors' Addresses
End of changes. 7 change blocks.
	7 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/