Re: [MBONED] I-D Action:draft-ietf-mboned-multiaaa-framework-10.txt

"ALTOM, MARK W (ATTLABS)" <ma697r@att.com> Sat, 13 February 2010 12:38 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 0BF2A3A79B5 for <mboned@core3.amsl.com>; Sat, 13 Feb 2010 04:38:24 -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=[AWL=0.000, 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 9bnXTJ9zfl02 for <mboned@core3.amsl.com>; Sat, 13 Feb 2010 04:38:22 -0800 (PST)
Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id CFE333A79B4 for <mboned@ietf.org>; Sat, 13 Feb 2010 04:38:22 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: ma697r@att.com
X-Msg-Ref: server-6.tower-161.messagelabs.com!1266064783!25372478!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 20514 invoked from network); 13 Feb 2010 12:39:44 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-6.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Feb 2010 12:39:44 -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 o1DCdZYx020512 for <mboned@ietf.org>; Sat, 13 Feb 2010 07:39:35 -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 o1DCdVpd020490 for <mboned@ietf.org>; Sat, 13 Feb 2010 07:39:31 -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:39:39 -0500
Message-ID: <3580159D7E3D824780C0B52AFC6D32E403264824@misout7msgusr7c.ugd.att.com>
In-Reply-To: <3580159D7E3D824780C0B52AFC6D32E40326481F@misout7msgusr7c.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MBONED] I-D Action:draft-ietf-mboned-multiaaa-framework-10.txt
Thread-Index: AcoVigO2774ytY81Rp+Ga8iHIVcVxSWpXUmwAB6BWwA=
References: <20090805044502.1510F3A6DA3@core3.amsl.com> <4A791383.9040503@lab.ntt.co.jp> <3580159D7E3D824780C0B52AFC6D32E40326481F@misout7msgusr7c.ugd.att.com>
From: "ALTOM, MARK W (ATTLABS)" <ma697r@att.com>
To: Hiroaki Sato <satou.hiroaki@lab.ntt.co.jp>, mboned@ietf.org
Subject: Re: [MBONED] I-D Action:draft-ietf-mboned-multiaaa-framework-10.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:38:24 -0000

Hiroaki,
Here a few notes that we had on AAA and Admission Control Framework for
Multicasting (draft-ietf-mboned-multiaaa-framework-10).

1.  Is there a mechanism to prevent the sharing of authorization (e.g.,
sharing an S,G among end users)?

2.  Section 4.1.1 states that "...NSP will forward multicast traffic
towards the user only when the NSP has 1) made sure the user is entitled
to access the network resources operated by the NSP, 2) received a
confirmation from the CP that the user is entitled to access the content
and (possibly) 3) determined that the network resources (e.g.,
bandwidth) are sufficient to deliver the multicast traffic to the user
with the relevant level of quality."  When the third condition is not
satisfied and an end-user is prevented from joining the multicast
stream, should the CP be notified as part of accounting?

3.  The heading to Section 4.1.3 is incorrect.  It should be "A single
CP is connected to multiple NSPs."

4.  On page 19, the reference in the text to Figure 3 should be to
Figure 4.  The text should read:  "In the fully enabled model (Figure 4)
resource management and admission control is provided by MACF (Multicast
Admission Control Function)."

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 Hiroaki Sato
Sent: Wednesday, August 05, 2009 1:07 AM
To: mboned@ietf.org
Subject: Re: [MBONED] I-D
Action:draft-ietf-mboned-multiaaa-framework-10.txt

Marshall and all,

I submitted the muliticast AAA framework draft.
As I said at IETF75, we just extend the expire date and the cotent is
not changed.
We'd like chairs to check it again as Marshall told at the mboned
meeting.

Thank you
Hiroaki

> 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           : AAA and Admission Control Framework for
Multicasting
> 	Author(s)       : T. Hayashi, et al.
> 	Filename        : draft-ietf-mboned-multiaaa-framework-10.txt
> 	Pages           : 22
> 	Date            : 2009-08-04
> 
> IP multicast-based services, such as TV broadcasting or
> videoconferencing raise the issue of making sure that potential
> customers are fully entitled to access the corresponding contents.
> There is indeed a need for service and content providers to identify
> users (if not authenticate, especially within the context of
> enforcing electronic payment schemes) and to retrieve statistical
> information for accounting purposes, as far as content and network
> usage are concerned.  This memo describes the framework for
> specifying the Authorization, Authentication and Accounting (AAA)
> capabilities that could be activated within the context of the
> deployment and the operation of IP multicast-based services.  This
> framework addresses the requirements presented in "Requirements for
> Accounting, Authentication and Authorization in Well Managed IP
> Multicasting Services" [I-D.ietf-mboned-maccnt-req].  The memo
> provides a basic AAA enabled model as well as an extended fully
> enabled model with resource and admission control coordination.
> 
> A URL for this Internet-Draft is:
>
http://www.ietf.org/internet-drafts/draft-ietf-mboned-multiaaa-framework
-10.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 mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


-- 
************************************
NTT Network Service Systems Lab.
Hiroaki Sato
TEL:0422-59-3141 (+81-422-59-3141)
FAX:0422-59-3167 (+81-422-59-3167)
************************************

_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned