--- 1/draft-ietf-mboned-maccnt-req-00.txt 2007-11-06 23:47:39.000000000 +0100 +++ 2/draft-ietf-mboned-maccnt-req-01.txt 2007-11-06 23:47:39.000000000 +0100 @@ -1,56 +1,54 @@ Tsunemasa Hayashi, NTT Internet Draft Haixiang He, Nortel - Document:draft-ietf-mboned-maccnt-req-00.txt Hiroaki Satou, NTT - Expires: October 15, 2005 Hiroshi Ohta, NTT + Document:draft-ietf-mboned-maccnt-req-01.txt Hiroaki Satou, NTT + Expires: April 15, 2006 Hiroshi Ohta, NTT Susheela Vaidya, Cisco Systems - April 15, 2005 + October 12, 2005 Accounting, Authentication and Authorization Issues in Well Managed IP Multicasting Services - + Status of this Memo - This document is an Internet-Draft and is subject to all provisions - of section 3 of RFC 3667. 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 become aware will be disclosed, in accordance with - RFC 3668. + 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. 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." 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 October 15, 2005 + This Internet-Draft will expire on April 15, 2006. Copyright Notice Copyright (C) The Internet Society (2005) - Abstract + Abstract This Internet Draft (I-D) describes problems in the area of accounting and access control for multicasting. General requirements for accounting capabilities including quality-of- service (QoS) related issues are listed. This I-D assumes that these capabilities can be realized by functions implemented at edges of a network based on IGMP or MLD. By such functions, information obtained from edge routers would be logged in a dedicated database. Finally, cases for Content Delivery Services (CDS) are described as application examples which could benefit from multicasting accounting and access control capabilities as @@ -60,32 +58,32 @@ Table of contents Copyright Notice.................................................1 1. Introduction..................................................3 2. Definitions and Abbreviations.................................4 2.1 Definitions..................................................4 2.2 Abbreviations................................................4 3. Problem statement.............................................5 3.1 Accounting issues...........................................5 3.2 Relationship with secure multicasting (MSEC)................6 - 4. Functional general requirements for well managed IP - multicasting..................................................6 + 4. Functional general requirements for well managed IP multicasting + .................................................................6 5. Application example and its specific requirements............10 - 5.1 IP Multicast-based Content Delivery Service (CDS): CP and - NSP are different entities (companies)......................10 + 5.1 IP Multicast-based Content Delivery Service (CDS): CP and NSP + are different entities (companies)..............................10 5.1.1 Network model for Multicast Content Delivery Service......10 5.1.2 Content Delivery Service Requirements.....................12 5.1.2.1 Accounting Requirements.................................12 5.1.2.2 Authorization Requirements..............................13 5.1.2.3 Authentication Requirements.............................13 - 5.2 IP Multicast-based Content Delivery Service (CDS): CP and - NSP are the same entities (companies).......................14 + 5.2 IP Multicast-based Content Delivery Service (CDS): CP and NSP + are the same entities (companies)...............................14 6. IANA considerations..........................................15 7. Security considerations......................................15 8. Conclusion...................................................15 Normative References............................................16 Full Copyright Statement........................................17 Intellectual Property...........................................17 Acknowledgement.................................................17 1. Introduction The intention of this Internet Draft (I-D) is to initiate a @@ -473,21 +471,21 @@ +----------\--+ +------|------+ +--/----------+ \ | / \ | / <- network/network \ | / interface +------------- \ ------ | ------ / ----+ | \ | / | | NSP +-+-----+-----+-+ | | | Provider Edge | | | +-------+-------+ | +-----------------+ | | |---| Information | - | \ | | | server | + | | | | server | | +--+------+---+ | +-----------------+ | | User Edge | | | +--+---+---+--+ | | / | \ | +------------- / --- | --- \ ----------+ / | \ / | \ <- user/network interface / | \ +---------++ +-----+----+ ++---------+ |client #a | |client #b | |client #c | @@ -504,44 +502,44 @@ different contracts. One is the contract between the NSP and the end user which permits the user to access the basic network resources of the NSP. Another contract is between the CP and end user to permit the user to subscribe multicast content. Because the CP and NSP are different entities, and the NSP generally does not allow a CP to control (operate) the network resources of the NSP, user authorization needs to be done by the CP and NSP independently. Since there is no direct connection to the user/network interface, the CP cannot control the user/network interface. An end user may want to move to another place, or may want to change her/his device - (client) anytime without interrupting her/his receiving services. + (client) anytime without interrupting her/his reception of services. As such, IP Multicast network should support portability capabilities. 5.1.2 Content Delivery Service Requirements To have a successful business providing multicast, there are some specific requirements for the IP Multicast-based Content Delivery Service. 5.1.2.1 Accounting Requirements Since the CP and NSP are different business entities, they need to - share the profit. Such a profit sharing business relationship + share the revenue. Such a revenue sharing business relationship requires accurate and near real-time accounting information about the end user clients' activity on accessing the content services. The accounting information should be per content/usage-base to enable varied billing and charging methods. The user accessing particular content is represented by the user's activities of joining or leaving the corresponding multicast group/channel ( or ). In multicast networks, only NSPs can - collect group joining or leaving activities through their last-hop - multicast access edge devices in real-time. The NSPs can transfer + collect group joining or leaving activities in real-time through + their last-hop multicast access edge devices. The NSPs can transfer the accounting information to related CPs for them to generate end user billing information. The normal AAA technology can be used to transfer the accounting information. To match the accounting information with a particular end-user client, the end-user client has to be authenticated. Usually the account information of an end-user client for content access is maintained by the CP. An end user client may have different user accounts for different CPs. The account is usually in the format of (username, password) so an end user client can access the content @@ -707,21 +705,21 @@ 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 Internet Society (2004). + Copyright (C) The Internet Society (2005). 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. 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 AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT