--- 1/draft-ietf-mboned-maccnt-req-06.txt 2009-01-14 20:12:05.000000000 +0100 +++ 2/draft-ietf-mboned-maccnt-req-07.txt 2009-01-14 20:12:05.000000000 +0100 @@ -1,74 +1,84 @@ Tsunemasa Hayashi, NTT 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 - 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 Provider(s) and Network Service Provider(s) + maccnt-req-07.txt> Status of this Memo - By submitting this Internet-Draft, each author represents that - any applicable patent or other IPR claims of which he or she is - 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. + This Internet-Draft is submitted to IETF in full conformance with + the provisions of BCP 78 and BCP 79. - Internet-Drafts are working documents of the Internet - Engineering Task Force (IETF), its areas, and its working groups. - Note that other groups may also distribute working documents as - Internet-Drafts. + Internet-Drafts are working documents of the Internet Engineering + Task Force (IETF), its areas, and its working groups. Note that + other groups may also distribute working documents as Internet- + Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other - documents at any time. It is inappropriate to use Internet- - Drafts as reference material or to cite them other than as "work - in progress." + documents at any time. It is inappropriate to use Internet-Drafts + as reference material or to cite them other than as "work in + progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at 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 This memo presents requirements in the area of accounting and - access control for IP multicasting. The scope of the requirements - is limited to cases that Authentication, Accounting and - Authorization (AAA) functions are coordinated between Content - Provider(s) and Network Service Provider(s). General requirements - for accounting and admission control capabilities including - quality-of-service (QoS) related issues are listed. This memo - assumes that these capabilities can be realized by functions - implemented at edges of a network based on IGMP or MLD. Finally, - cases for Content Delivery Services (CDS) are described as - application examples which could benefit from multicasting - accounting and access control capabilities as described in this - memo. + access control for IP multicasting. The scope of the + requirements is limited to cases that Authentication, + Accounting and Authorization (AAA) functions are coordinated + between Content Provider(s) and Network Service Provider(s). + General requirements for accounting and admission control + capabilities including quality-of-service (QoS) related issues + are listed. This memo assumes that these capabilities can be + realized by functions implemented at edges of a network based + on IGMP or MLD. Finally, cases for Content Delivery Services + (CDS) are described as application examples which could benefit + from multicasting accounting and access control capabilities as + described in this memo. This memo defines requirements related to AAA issues for multi- entity provider models in which the network service provider and content provider cooperate to provide CDS and various related AAA functions for purposes such as protecting and accounting for the access to content and network resources. The requirements are generally not relevant to cases in which there is not a reason to share AAA functions between separate entities. Table of Contents - Copyright Notice.................................................1 1. Introduction..................................................3 2. Definitions and Abbreviations.................................5 2.1 Definitions..................................................5 2.2 Abbreviations................................................6 3. Problem Statement.............................................6 3.1 Accounting Issues...........................................6 3.2 Relationship with Secure Multicasting (MSEC)................8 3.3 Regarding Access Media and User Separation..................8 4. General AAA-related Functional Requirements for IP Multicasting .................................................................9 @@ -82,24 +92,20 @@ 5.1.2.3 Authentication Requirements.............................19 5.2 IP Multicast-based Content Delivery Service (CDS): CP and NSP are the same entities (companies)...............................19 6. Acknowledgments..............................................21 7. IANA Considerations..........................................21 8. Security Considerations......................................21 9. Privacy considerations.......................................21 10. Conclusion..................................................21 Normative References............................................22 Authors' Addresses..............................................23 - Full Copyright Statement........................................24 - Intellectual Property...........................................24 - Expiration......................................................25 - Acknowledgement.................................................25 1. Introduction This memo presents general functional requirements related to accounting, access control and admission control issues in IP multicasting networks. A multicast network which fulfills all of these requirements is called a "fully AAA and QoS enabled" IP multicasting network here. Fulfillment of all or some of the requirements will make possible more robust management of IP multicasting networks. @@ -812,58 +818,10 @@ NTT Network Service Systems Laboratories 3-9-11 Midoricho, Musashino-shi, Tokyo, 180-8585 Japan Phone: +81 422 59 3617 Email: ohta.hiroshi@lab.ntt.co.jp Susheela Vaidya Cisco Systems, Inc. 170 W. Tasman Drive San Jose, CA 95134 Phone: +1 408 525 1952 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.