draft-ietf-mboned-maccnt-req-06.txt		draft-ietf-mboned-maccnt-req-07.txt
	Tsunemasa Hayashi, NTT		Tsunemasa Hayashi, NTT
	Internet Draft Haixiang He, Nortel		Internet Draft Haixiang He, Nortel
	Document:draft-ietf-mboned-maccnt-req-06.txt Hiroaki Satou, NTT		Document:draft-ietf-mboned-maccnt-req-07.txt Hiroaki Satou, NTT
	Intended Status: Informational Hiroshi Ohta, NTT		Intended Status: Informational Hiroshi Ohta, NTT
	Expires: December 22, 2008 Susheela Vaidya, Cisco Systems		Expires: July 16, 2009 Susheela Vaidya, Cisco Systems
	June 20, 2008		January 12, 2009
	Requirements for Multicast AAA coordinated between Content		Requirements for Multicast AAA coordinated between Content
	Provider(s) and Network Service Provider(s) <draft-ietf-mboned-		Provider(s) and Network Service Provider(s) <draft-ietf-mboned-
	maccnt-req-06.txt>		maccnt-req-07.txt>
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that		This Internet-Draft is submitted to IETF in full conformance with
	any applicable patent or other IPR claims of which he or she is		the provisions of BCP 78 and BCP 79.
	aware have been or will be disclosed, and any of which he or she
	becomes aware will be disclosed, in accordance with Section 6 of
	BCP 79.
	Internet-Drafts are working documents of the Internet		Internet-Drafts are working documents of the Internet Engineering
	Engineering Task Force (IETF), its areas, and its working groups.		Task Force (IETF), its areas, and its working groups. Note that
	Note that other groups may also distribute working documents as		other groups may also distribute working documents as Internet-
	Internet-Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six
	months and may be updated, replaced, or obsoleted by other		months and may be updated, replaced, or obsoleted by other
	documents at any time. It is inappropriate to use Internet-		documents at any time. It is inappropriate to use Internet-Drafts
	Drafts as reference material or to cite them other than as "work		as reference material or to cite them other than as "work in
	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/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 July 16, 2009.
			Copyright Notice
			Copyright (c) 2009 IETF Trust and the persons identified as the
			document authors. All rights reserved.
			This document is subject to BCP 78 and the IETF Trust's Legal
			Provisions Relating to IETF Documents
			(http://trustee.ietf.org/license-info) in effect on the date of
			publication of this document. Please review these documents
			carefully, as they describe your rights and restrictions with
			respect to this document.
	Abstract		Abstract
	This memo presents requirements in the area of accounting and		This memo presents requirements in the area of accounting and
	access control for IP multicasting. The scope of the requirements		access control for IP multicasting. The scope of the
	is limited to cases that Authentication, Accounting and		requirements is limited to cases that Authentication,
	Authorization (AAA) functions are coordinated between Content		Accounting and Authorization (AAA) functions are coordinated
	Provider(s) and Network Service Provider(s). General requirements		between Content Provider(s) and Network Service Provider(s).
	for accounting and admission control capabilities including		General requirements for accounting and admission control
	quality-of-service (QoS) related issues are listed. This memo		capabilities including quality-of-service (QoS) related issues
	assumes that these capabilities can be realized by functions		are listed. This memo assumes that these capabilities can be
	implemented at edges of a network based on IGMP or MLD. Finally,		realized by functions implemented at edges of a network based
	cases for Content Delivery Services (CDS) are described as		on IGMP or MLD. Finally, cases for Content Delivery Services
	application examples which could benefit from multicasting		(CDS) are described as application examples which could benefit
	accounting and access control capabilities as described in this		from multicasting accounting and access control capabilities as
	memo.		described in this memo.
	This memo defines requirements related to AAA issues for multi-		This memo defines requirements related to AAA issues for multi-
	entity provider models in which the network service provider and		entity provider models in which the network service provider and
	content provider cooperate to provide CDS and various related AAA		content provider cooperate to provide CDS and various related AAA
	functions for purposes such as protecting and accounting for the		functions for purposes such as protecting and accounting for the
	access to content and network resources. The requirements are		access to content and network resources. The requirements are
	generally not relevant to cases in which there is not a reason to		generally not relevant to cases in which there is not a reason to
	share AAA functions between separate entities.		share AAA functions between separate entities.
	Table of Contents		Table of Contents
	Copyright Notice.................................................1
	1. Introduction..................................................3		1. Introduction..................................................3
	2. Definitions and Abbreviations.................................5		2. Definitions and Abbreviations.................................5
	2.1 Definitions..................................................5		2.1 Definitions..................................................5
	2.2 Abbreviations................................................6		2.2 Abbreviations................................................6
	3. Problem Statement.............................................6		3. Problem Statement.............................................6
	3.1 Accounting Issues...........................................6		3.1 Accounting Issues...........................................6
	3.2 Relationship with Secure Multicasting (MSEC)................8		3.2 Relationship with Secure Multicasting (MSEC)................8
	3.3 Regarding Access Media and User Separation..................8		3.3 Regarding Access Media and User Separation..................8
	4. General AAA-related Functional Requirements for IP Multicasting		4. General AAA-related Functional Requirements for IP Multicasting
	.................................................................9		.................................................................9
	skipping to change at page 3, line 35		skipping to change at page 3, line 34
	5.1.2.3 Authentication Requirements.............................19		5.1.2.3 Authentication Requirements.............................19
	5.2 IP Multicast-based Content Delivery Service (CDS): CP and NSP		5.2 IP Multicast-based Content Delivery Service (CDS): CP and NSP
	are the same entities (companies)...............................19		are the same entities (companies)...............................19
	6. Acknowledgments..............................................21		6. Acknowledgments..............................................21
	7. IANA Considerations..........................................21		7. IANA Considerations..........................................21
	8. Security Considerations......................................21		8. Security Considerations......................................21
	9. Privacy considerations.......................................21		9. Privacy considerations.......................................21
	10. Conclusion..................................................21		10. Conclusion..................................................21
	Normative References............................................22		Normative References............................................22
	Authors' Addresses..............................................23		Authors' Addresses..............................................23
	Full Copyright Statement........................................24
	Intellectual Property...........................................24
	Expiration......................................................25
	Acknowledgement.................................................25
	1. Introduction		1. Introduction
	This memo presents general functional requirements related to		This memo presents general functional requirements related to
	accounting, access control and admission control issues in IP		accounting, access control and admission control issues in IP
	multicasting networks. A multicast network which fulfills all of		multicasting networks. A multicast network which fulfills all of
	these requirements is called a "fully AAA and QoS enabled" IP		these requirements is called a "fully AAA and QoS enabled" IP
	multicasting network here. Fulfillment of all or some of the		multicasting network here. Fulfillment of all or some of the
	requirements will make possible more robust management of IP		requirements will make possible more robust management of IP
	multicasting networks.		multicasting networks.
	skipping to change at page 24, line 4		skipping to change at line 828
	NTT Network Service Systems Laboratories		NTT Network Service Systems Laboratories
	3-9-11 Midoricho, Musashino-shi, Tokyo, 180-8585 Japan		3-9-11 Midoricho, Musashino-shi, Tokyo, 180-8585 Japan
	Phone: +81 422 59 3617		Phone: +81 422 59 3617
	Email: ohta.hiroshi@lab.ntt.co.jp		Email: ohta.hiroshi@lab.ntt.co.jp
	Susheela Vaidya		Susheela Vaidya
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 W. Tasman Drive San Jose, CA 95134		170 W. Tasman Drive San Jose, CA 95134
	Phone: +1 408 525 1952		Phone: +1 408 525 1952
	Email: svaidya@cisco.com		Email: svaidya@cisco.com
	Full Copyright Statement
	Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and
	restrictions contained in BCP 78, and except as set forth
	therein, the authors retain all their rights.
	Disclaimer
	This document and the information contained herein are provided
	on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
	REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY,
	THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM
	ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
	ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
	INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
	OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property
	The IETF takes no position regarding the validity or scope of
	any Intellectual Property Rights or other rights that might be
	claimed to pertain to the implementation or use of the
	technology described in this document or the extent to which
	any license under such rights might or might not be available;
	nor does it represent that it has made any independent effort
	to identify any such rights. Information on the procedures with
	respect to rights in RFC documents can be found in BCP 78 and
	BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any
	assurances of licenses to be made available, or the result of an
	attempt made to obtain a general license or permission for the
	use of such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR
	repository at http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention
	any copyrights, patents or patent applications, or other
	proprietary rights that may cover technology that may be
	required to implement this standard. Please address the
	information to the IETF at ietf-ipr@ietf.org.
	Acknowledgement
	Funding for the RFC Editor function is currently provided by the
	Internet Society.
End of changes. 12 change blocks.
	33 lines changed or deleted		39 lines changed or added
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/