Re: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-req-08.txt
"ALTOM, MARK W (ATTLABS)" <ma697r@att.com> Sat, 13 February 2010 12:37 UTC
Return-Path: <ma697r@att.com>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D445F3A79B3 for <mboned@core3.amsl.com>; Sat, 13 Feb 2010 04:37:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIDOmiLtVPyp for <mboned@core3.amsl.com>; Sat, 13 Feb 2010 04:37:11 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 15F1628C11C for <mboned@ietf.org>; Sat, 13 Feb 2010 04:37:10 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: ma697r@att.com
X-Msg-Ref: server-9.tower-161.messagelabs.com!1266064711!20200189!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 24939 invoked from network); 13 Feb 2010 12:38:32 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-9.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Feb 2010 12:38:32 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o1DCcNJC020204 for <mboned@ietf.org>; Sat, 13 Feb 2010 07:38:23 -0500
Received: from misout7msgusr7c.ugd.att.com (misout7msgusr7c.ugd.att.com [144.155.43.105]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o1DCcLpa020199 for <mboned@ietf.org>; Sat, 13 Feb 2010 07:38:22 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 13 Feb 2010 07:38:29 -0500
Message-ID: <3580159D7E3D824780C0B52AFC6D32E403264823@misout7msgusr7c.ugd.att.com>
In-Reply-To: <3580159D7E3D824780C0B52AFC6D32E403264821@misout7msgusr7c.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-req-08.txt
Thread-Index: Acl2dlM1zT++qkk2SrKiLLbT51DlaE1upg2QAB4T5tA=
References: <20090114183001.5681F3A6A15@core3.amsl.com> <3580159D7E3D824780C0B52AFC6D32E403264821@misout7msgusr7c.ugd.att.com>
From: "ALTOM, MARK W (ATTLABS)" <ma697r@att.com>
To: mboned@ietf.org
Subject: Re: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-req-08.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Feb 2010 12:37:13 -0000
The following are our comments on "Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s)(draft-ietf-mboned-maccnt-req-08)" 1. A requirement should be added that the AAA mechanisms that are specified should be applicable to AMT multicast as well as end-to-end native multicast. http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-09 2. How do you "unauthorize" an end user after the end user has been authenticated and authorized to join a multicast stream? For example: * An end-user may only be authorized to join a multicast stream for a specific amount of time. How do you drop a user from the stream when the user has "timed out?" * An end-user may be authorized to access only a certain amount of content. How do you drop a user from the stream when the user has exceeded the specified amount of content? This suggests that at a minimum, the elements to authorization should include: * Stream (S,G or *,G) * Time * Bandwidth or amount of content 3. Are there any mechanisms for re-authentication and re-authorization? 4. Section 3 is titled "Current Business Models," but only 2 business models are described: * A single entity model where CP (Content Provider) and NSP (Network Service Provider) are the same entity * Multiple entity model without direct content-based billing However, these are not the only current business models. Maybe a better title for section 3 is "Common Business Models." 5. Section 4 describes a proposed model with direct billing of the end user. However, the proposed AAA mechanisms would also be applicable to scenarios where the CP or NSP wants to restrict access, but does not necessarily require direct billing of the end user (for example support for closed user groups). Please let us know if you have questions or if you need additional details. Thanks, Mark Altom Andy Huang Tom Imburgia Pat McCrink Han Nguyen Doug Nortz AT&T Labs (Contact Mark Altom: ma697r@att.com; +1 732 420 9073) -----Original Message----- From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Wednesday, January 14, 2009 1:30 PM To: i-d-announce@ietf.org Cc: mboned@ietf.org Subject: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-req-07.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the MBONE Deployment Working Group of the IETF. Title : Requirements for Multicast AAA coordinated between Content Provider(s) and Network Service Provider(s) Author(s) : H. Ohta, H. Satou, S. Vaidya, T. Hayashi, H. He Filename : draft-ietf-mboned-maccnt-req-07.txt Pages : 23 Date : 2009-1-12 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. 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mboned-maccnt-req-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
- [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-req-… Internet-Drafts
- Re: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-… ALTOM, MARK W (ATTLABS)
- Re: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-… Hiroaki Sato
- Re: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-… ALTOM, MARK W (ATTLABS)
- Re: [MBONED] I-D ACTION:draft-ietf-mboned-maccnt-… Hiroaki Sato