draft-ietf-mboned-maccnt-req-00.txt   draft-ietf-mboned-maccnt-req-01.txt 
Tsunemasa Hayashi, NTT Tsunemasa Hayashi, NTT
Internet Draft Haixiang He, Nortel Internet Draft Haixiang He, Nortel
Document:draft-ietf-mboned-maccnt-req-00.txt Hiroaki Satou, NTT Document:draft-ietf-mboned-maccnt-req-01.txt Hiroaki Satou, NTT
Expires: October 15, 2005 Hiroshi Ohta, NTT Expires: April 15, 2006 Hiroshi Ohta, NTT
Susheela Vaidya, Cisco Systems Susheela Vaidya, Cisco Systems
April 15, 2005 October 12, 2005
Accounting, Authentication and Authorization Issues in Well Managed Accounting, Authentication and Authorization Issues in Well Managed
IP Multicasting Services IP Multicasting Services
<draft-ietf-mboned-maccnt-req-00.txt> <draft-ietf-mboned-maccnt-req-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as 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-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work 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 October 15, 2005 This Internet-Draft will expire on April 15, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005) Copyright (C) The Internet Society (2005)
Abstract
Abstract
This Internet Draft (I-D) describes problems in the area of This Internet Draft (I-D) describes problems in the area of
accounting and access control for multicasting. General accounting and access control for multicasting. General
requirements for accounting capabilities including quality-of- requirements for accounting capabilities including quality-of-
service (QoS) related issues are listed. This I-D assumes that service (QoS) related issues are listed. This I-D assumes that
these capabilities can be realized by functions implemented at these capabilities can be realized by functions implemented at
edges of a network based on IGMP or MLD. By such functions, edges of a network based on IGMP or MLD. By such functions,
information obtained from edge routers would be logged in a information obtained from edge routers would be logged in a
dedicated database. Finally, cases for Content Delivery Services dedicated database. Finally, cases for Content Delivery Services
(CDS) are described as application examples which could benefit (CDS) are described as application examples which could benefit
from multicasting accounting and access control capabilities as from multicasting accounting and access control capabilities as
skipping to change at page 2, line 29 skipping to change at page 2, line 27
Table of contents Table of contents
Copyright Notice.................................................1 Copyright Notice.................................................1
1. Introduction..................................................3 1. Introduction..................................................3
2. Definitions and Abbreviations.................................4 2. Definitions and Abbreviations.................................4
2.1 Definitions..................................................4 2.1 Definitions..................................................4
2.2 Abbreviations................................................4 2.2 Abbreviations................................................4
3. Problem statement.............................................5 3. Problem statement.............................................5
3.1 Accounting issues...........................................5 3.1 Accounting issues...........................................5
3.2 Relationship with secure multicasting (MSEC)................6 3.2 Relationship with secure multicasting (MSEC)................6
4. Functional general requirements for well managed IP 4. Functional general requirements for well managed IP multicasting
multicasting..................................................6 .................................................................6
5. Application example and its specific requirements............10 5. Application example and its specific requirements............10
5.1 IP Multicast-based Content Delivery Service (CDS): CP and 5.1 IP Multicast-based Content Delivery Service (CDS): CP and NSP
NSP are different entities (companies)......................10 are different entities (companies)..............................10
5.1.1 Network model for Multicast Content Delivery Service......10 5.1.1 Network model for Multicast Content Delivery Service......10
5.1.2 Content Delivery Service Requirements.....................12 5.1.2 Content Delivery Service Requirements.....................12
5.1.2.1 Accounting Requirements.................................12 5.1.2.1 Accounting Requirements.................................12
5.1.2.2 Authorization Requirements..............................13 5.1.2.2 Authorization Requirements..............................13
5.1.2.3 Authentication Requirements.............................13 5.1.2.3 Authentication Requirements.............................13
5.2 IP Multicast-based Content Delivery Service (CDS): CP and 5.2 IP Multicast-based Content Delivery Service (CDS): CP and NSP
NSP are the same entities (companies).......................14 are the same entities (companies)...............................14
6. IANA considerations..........................................15 6. IANA considerations..........................................15
7. Security considerations......................................15 7. Security considerations......................................15
8. Conclusion...................................................15 8. Conclusion...................................................15
Normative References............................................16 Normative References............................................16
Full Copyright Statement........................................17 Full Copyright Statement........................................17
Intellectual Property...........................................17 Intellectual Property...........................................17
Acknowledgement.................................................17 Acknowledgement.................................................17
1. Introduction 1. Introduction
The intention of this Internet Draft (I-D) is to initiate a The intention of this Internet Draft (I-D) is to initiate a
skipping to change at page 11, line 31 skipping to change at page 11, line 31
+----------\--+ +------|------+ +--/----------+ +----------\--+ +------|------+ +--/----------+
\ | / \ | /
\ | / <- network/network \ | / <- network/network
\ | / interface \ | / interface
+------------- \ ------ | ------ / ----+ +------------- \ ------ | ------ / ----+
| \ | / | | \ | / |
| NSP +-+-----+-----+-+ | | NSP +-+-----+-----+-+ |
| | Provider Edge | | | | Provider Edge | |
| +-------+-------+ | +-----------------+ | +-------+-------+ | +-----------------+
| | |---| Information | | | |---| Information |
| \ | | | server | | | | | server |
| +--+------+---+ | +-----------------+ | +--+------+---+ | +-----------------+
| | User Edge | | | | User Edge | |
| +--+---+---+--+ | | +--+---+---+--+ |
| / | \ | | / | \ |
+------------- / --- | --- \ ----------+ +------------- / --- | --- \ ----------+
/ | \ / | \
/ | \ <- user/network interface / | \ <- user/network interface
/ | \ / | \
+---------++ +-----+----+ ++---------+ +---------++ +-----+----+ ++---------+
|client #a | |client #b | |client #c | |client #a | |client #b | |client #c |
skipping to change at page 12, line 14 skipping to change at page 12, line 14
different contracts. One is the contract between the NSP and the different contracts. One is the contract between the NSP and the
end user which permits the user to access the basic network end user which permits the user to access the basic network
resources of the NSP. Another contract is between the CP and end resources of the NSP. Another contract is between the CP and end
user to permit the user to subscribe multicast content. Because the user to permit the user to subscribe multicast content. Because the
CP and NSP are different entities, and the NSP generally does not CP and NSP are different entities, and the NSP generally does not
allow a CP to control (operate) the network resources of the NSP, allow a CP to control (operate) the network resources of the NSP,
user authorization needs to be done by the CP and NSP independently. user authorization needs to be done by the CP and NSP independently.
Since there is no direct connection to the user/network interface, Since there is no direct connection to the user/network interface,
the CP cannot control the user/network interface. An end user may 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 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 As such, IP Multicast network should support portability
capabilities. capabilities.
5.1.2 Content Delivery Service Requirements 5.1.2 Content Delivery Service Requirements
To have a successful business providing multicast, there are some To have a successful business providing multicast, there are some
specific requirements for the IP Multicast-based Content Delivery specific requirements for the IP Multicast-based Content Delivery
Service. Service.
5.1.2.1 Accounting Requirements 5.1.2.1 Accounting Requirements
Since the CP and NSP are different business entities, they need to 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 requires accurate and near real-time accounting information about
the end user clients' activity on accessing the content services. the end user clients' activity on accessing the content services.
The accounting information should be per content/usage-base to The accounting information should be per content/usage-base to
enable varied billing and charging methods. enable varied billing and charging methods.
The user accessing particular content is represented by the user's The user accessing particular content is represented by the user's
activities of joining or leaving the corresponding multicast activities of joining or leaving the corresponding multicast
group/channel (<g> or <s,g>). In multicast networks, only NSPs can group/channel (<g> or <s,g>). In multicast networks, only NSPs can
collect group joining or leaving activities through their last-hop collect group joining or leaving activities in real-time through
multicast access edge devices in real-time. The NSPs can transfer their last-hop multicast access edge devices. The NSPs can transfer
the accounting information to related CPs for them to generate end the accounting information to related CPs for them to generate end
user billing information. The normal AAA technology can be used to user billing information. The normal AAA technology can be used to
transfer the accounting information. transfer the accounting information.
To match the accounting information with a particular end-user To match the accounting information with a particular end-user
client, the end-user client has to be authenticated. Usually the client, the end-user client has to be authenticated. Usually the
account information of an end-user client for content access is account information of an end-user client for content access is
maintained by the CP. An end user client may have different user maintained by the CP. An end user client may have different user
accounts for different CPs. The account is usually in the format of accounts for different CPs. The account is usually in the format of
(username, password) so an end user client can access the content (username, password) so an end user client can access the content
skipping to change at page 17, line 6 skipping to change at page 17, line 6
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 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 This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
 End of changes. 15 change blocks. 
24 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/