From ancp-bounces@ietf.org  Tue Oct  7 04:15:04 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93B7D3A6B5C;
	Tue,  7 Oct 2008 04:15:04 -0700 (PDT)
X-Original-To: ancp@ietf.org
Delivered-To: ancp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id D26823A6B4C; Tue,  7 Oct 2008 04:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081007111501.D26823A6B4C@core3.amsl.com>
Date: Tue,  7 Oct 2008 04:15:01 -0700 (PDT)
Cc: ancp@ietf.org
Subject: [ANCP] I-D Action:draft-ietf-ancp-security-threats-06.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Access Node Control Protocol Working Group of the IETF.


	Title           : Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)
	Author(s)       : H. Moustafa, et al.
	Filename        : draft-ietf-ancp-security-threats-06.txt
	Pages           : 16
	Date            : 2008-10-07

The Access Node Control Protocol (ANCP) aims to communicate QoS-
related, service-related and subscriber-related configurations and
operations between a Network Access Server (NAS) and an Access Node
(e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)).  The
main goal of this protocol is to allow the NAS to configure, manage
and control access equipments including the ability for the access
nodes to report information to the NAS.
The present document investigates security threats that all ANCP
nodes could encounter.  This document develops a threat model for
ANCP security aiming to decide which security functions are required.
Based on this, security requirements regarding the Access Node
Control Protocol are defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ancp-security-threats-06.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.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-ancp-security-threats-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-10-07040602.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--NextPart--


From ancp-bounces@ietf.org  Tue Oct  7 09:23:06 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A8883A689C;
	Tue,  7 Oct 2008 09:23:06 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FB113A67D4
	for <ancp@core3.amsl.com>; Tue,  7 Oct 2008 09:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 gJDiSM8kxUdF for <ancp@core3.amsl.com>;
	Tue,  7 Oct 2008 09:23:04 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id CE8033A67A2
	for <ancp@ietf.org>; Tue,  7 Oct 2008 09:23:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,373,1220227200"; d="scan'208,217";a="21892297"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 07 Oct 2008 16:23:39 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m97GNd0M027959
	for <ancp@ietf.org>; Tue, 7 Oct 2008 18:23:39 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m97GNdoS023561
	for <ancp@ietf.org>; Tue, 7 Oct 2008 16:23:39 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 18:23:39 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 7 Oct 2008 18:23:31 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405CBEFAD@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF73 - ANCP slots
Thread-Index: AckomQlsobMXdQetQY6cKA3jSRr1sQ==
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 07 Oct 2008 16:23:39.0833 (UTC)
	FILETIME=[0EB09290:01C92899]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1889; t=1223396619;
	x=1224260619; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20IETF73=20-=20ANCP=20slots |Sender:=20;
	bh=TqnRlcSMO2vjIJUEMsxedoKQItKtQzPKmcWAk1++Wkk=;
	b=L+YkBceS6Lu7088QJYRALSwK6m5qYK94yte7ssUB/WQB7b2Om6MF+ZnD7a
	MyUZZVfo0RTN3p9VmNeNFqHgg86bQ0gm1RDi+amMg/i1SF9kz96TUNgBeGYA
	B+o2UBJ4oP;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: [ANCP] IETF73 - ANCP slots
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0251982469=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0251982469==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92899.0E97E262"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92899.0E97E262
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Folks,=20
We have asked for an ANCP WG slot at the upcoming IETF73 meeting.=20
Please let me know if you would like a slot to present during the WG
meeting.
As usual, please send a brief summary of the topic, a pointer to the
draft (if any), and how much time you would like.=20
Regards,=20
Woj & Matthew=20


------_=_NextPart_001_01C92899.0E97E262
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>IETF73 - ANCP slots</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">Hi =
Folks,</FONT><FONT FACE=3D"Times New Roman"> </FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">We have asked for =
an ANCP WG slot at the upcoming IETF73 meeting.</FONT> </SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">Please let me =
know if you would like a slot to present during the WG =
meeting.</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">As usual, please =
send a brief summary of the topic, a pointer to the draft (if any), and =
how much time you would like.</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 =
FACE=3D"Arial">Regards,</FONT><FONT FACE=3D"Times New Roman"> =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D2 FACE=3D"Arial">Woj &amp; =
Matthew</FONT><FONT FACE=3D"Times New Roman"> </FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C92899.0E97E262--

--===============0251982469==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0251982469==--


From ancp-bounces@ietf.org  Tue Oct 14 05:49:09 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62F3C28C15C;
	Tue, 14 Oct 2008 05:49:09 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C7823A6BCC
	for <ancp@core3.amsl.com>; Tue, 14 Oct 2008 05:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aaYNMud1mAkh for <ancp@core3.amsl.com>;
	Tue, 14 Oct 2008 05:49:07 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 6370D3A6ABA
	for <ancp@ietf.org>; Tue, 14 Oct 2008 05:49:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,409,1220227200"; d="scan'208";a="48886210"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 14 Oct 2008 12:49:33 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9ECnXRf031132; 
	Tue, 14 Oct 2008 05:49:33 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9ECnX5R022988;
	Tue, 14 Oct 2008 12:49:33 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 05:49:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 05:49:32 -0700
Message-ID: <48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal for changing messages names in Multicast Control
	Extensions 
Thread-Index: Ackt8mzi+Xqn9f4HQkKdSP4M+mBKigACEQhg
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
From: "Philippe Champagne (pchamp)" <pchamp@cisco.com>
To: "Maglione Roberta" <roberta.maglione@telecomitalia.it>,
	"DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Sanjay Wadhwa" <swadhwa@juniper.net>
X-OriginalArrivalTime: 14 Oct 2008 12:49:33.0271 (UTC)
	FILETIME=[4E6F0670:01C92DFB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1951; t=1223988573;
	x=1224852573; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pchamp@cisco.com;
	z=From:=20=22Philippe=20Champagne=20(pchamp)=22=20<pchamp@ci
	sco.com>
	|Subject:=20RE=3A=20Proposal=20for=20changing=20messages=20
	names=20in=20Multicast=20Control=20Extensions=20 |Sender:=20;
	bh=S/CLeZZDM4SoWviJYQNwcH49/QFsfH2hEX0PXvsEBuE=;
	b=hrs4t4zgN8wBVsPm3Or8VTNypMoViSFSZGcWI4y/V7HXSqqKFmxTD9NMrZ
	MWGs3JrsCHQq278uFMll7chd8x187941Q+SBsTervDOMGrzV9EwENX+JDTZV
	eVdHLft770;
Authentication-Results: sj-dkim-4; header.From=pchamp@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


I'm ok with those renaming.

Do you mean that when the ANCP client ask authorization for a Join, its
request is a Multicast Replication Control Message and the reply from
the server is the same or different:____  While if the server is sending
a directive to the ANCP client to have a port join a multicast, do you
mean this is also called Multicast Replication Control Message?




>-----Original Message-----
>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it] 
>Sent: Tuesday, October 14, 2008 7:46 AM
>To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; 
>Wojciech Dec (wdec); 'Sanjay Wadhwa'
>Subject: Proposal for changing messages names in Multicast 
>Control Extensions 
>
>
>Hello,
>        I'm currently merging draft-ancp-mc-extensions with 
>draft-ietf-ancp-protocol, and I am thinking it could be useful 
>to simplify the terminology in terms of multicast message names.
>In particular I'd like to rename:
>- Multicast Replication Control Request Message in just 
>Multicast Replication Control Message
>- Multicast Status Response Message and in Multicast Status Message
>
>This change would allow re-using the same message type for 
>different purposes/use cases if needed in future, without 
>affecting current scenario.
>
>Please let me know what's your opinion on this proposal.
>
>Thanks and best regards,
>
>Roberta
>
>
>CONFIDENTIALITY NOTICE
>
>This message and its attachments are addressed solely to the 
>persons above and may contain confidential information. If you 
>have received the message in error, be informed that any use 
>of the content hereof is prohibited. Please return it 
>immediately to the sender and delete the message. Should you 
>have any questions, please contact us by replying to 
>webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 14 06:21:36 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 53B0628C1AD;
	Tue, 14 Oct 2008 06:21:36 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95FCA28C1AD
	for <ancp@core3.amsl.com>; Tue, 14 Oct 2008 06:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 zy99waCKgFta for <ancp@core3.amsl.com>;
	Tue, 14 Oct 2008 06:21:33 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it
	(grfedg701rm001.telecomitalia.it [217.169.121.20])
	by core3.amsl.com (Postfix) with ESMTP id 7F4273A6BA6
	for <ancp@ietf.org>; Tue, 14 Oct 2008 06:21:33 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by
	GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP
	Server (TLS) id 8.1.291.1; Tue, 14 Oct 2008 15:23:54 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by
	grfhub703rm001.griffon.local ([10.19.3.10]) with mapi; Tue, 14 Oct 2008
	15:21:55 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "'Philippe Champagne (pchamp)'" <pchamp@cisco.com>, DE CNODDER Stefaan
	<stefaan.de_cnodder@alcatel-lucent.be>, "Wojciech Dec (wdec)"
	<wdec@cisco.com>, Sanjay Wadhwa <swadhwa@juniper.net>
Date: Tue, 14 Oct 2008 15:21:54 +0200
Thread-Topic: Proposal for changing messages names in Multicast Control
	Extensions 
Thread-Index: Ackt8mzi+Xqn9f4HQkKdSP4M+mBKigACEQhgAAD3xcA=
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
 Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hi Phil,
        please see inline.

Regards,
Roberta

-----Original Message-----
From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
Sent: Tuesday, October 14, 2008 2:50 PM
To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay Wadhwa
Cc: ancp@ietf.org
Subject: RE: Proposal for changing messages names in Multicast Control Extensions


> I'm ok with those renaming.
[RM] Great

> Do you mean that when the ANCP client ask authorization for a Join, its
> request is a Multicast Replication Control Message and the reply from
> the server is the same or different:____

[RM] not exactly, what I meant is slightly different:  when an ANCP client asks for authorization to Join a multicast flow, it uses an ANCP message (not defined yet), while when the server replies to the authorization message sent by the client it could use a Multicast Replication Control Message

> While if the server is sending
> a directive to the ANCP client to have a port join a multicast, do you
> mean this is also called Multicast Replication Control Message?

[RM] yes this is current scenario where the server uses a Multicast Replication Control Message to send a directive to the ANCP client to have a port join or leave a multicast flow.
Does it make sense?

Thanks,
Roberta




>-----Original Message-----
>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>Sent: Tuesday, October 14, 2008 7:46 AM
>To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan';
>Wojciech Dec (wdec); 'Sanjay Wadhwa'
>Subject: Proposal for changing messages names in Multicast
>Control Extensions
>
>
>Hello,
>        I'm currently merging draft-ancp-mc-extensions with
>draft-ietf-ancp-protocol, and I am thinking it could be useful
>to simplify the terminology in terms of multicast message names.
>In particular I'd like to rename:
>- Multicast Replication Control Request Message in just
>Multicast Replication Control Message
>- Multicast Status Response Message and in Multicast Status Message
>
>This change would allow re-using the same message type for
>different purposes/use cases if needed in future, without
>affecting current scenario.
>
>Please let me know what's your opinion on this proposal.
>
>Thanks and best regards,
>
>Roberta
>
>
>CONFIDENTIALITY NOTICE
>
>This message and its attachments are addressed solely to the
>persons above and may contain confidential information. If you
>have received the message in error, be informed that any use
>of the content hereof is prohibited. Please return it
>immediately to the sender and delete the message. Should you
>have any questions, please contact us by replying to
>webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
>


CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 14 06:33:29 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B3443A6BF0;
	Tue, 14 Oct 2008 06:33:29 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2AE73A69C0
	for <ancp@core3.amsl.com>; Tue, 14 Oct 2008 06:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 q5ymw7ZI55FV for <ancp@core3.amsl.com>;
	Tue, 14 Oct 2008 06:33:19 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 124563A6BF0
	for <ancp@ietf.org>; Tue, 14 Oct 2008 06:33:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,409,1220227200"; d="scan'208";a="48901400"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 14 Oct 2008 13:32:56 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9EDWu4O018794; 
	Tue, 14 Oct 2008 06:32:56 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9EDWu6T006291;
	Tue, 14 Oct 2008 13:32:56 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 06:32:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 06:32:54 -0700
Message-ID: <48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal for changing messages names in Multicast Control
	Extensions 
Thread-Index: Ackt8mzi+Xqn9f4HQkKdSP4M+mBKigACEQhgAAD3xcAAAGcMAA==
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
From: "Philippe Champagne (pchamp)" <pchamp@cisco.com>
To: "Maglione Roberta" <roberta.maglione@telecomitalia.it>,
	"DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Sanjay Wadhwa" <swadhwa@juniper.net>
X-OriginalArrivalTime: 14 Oct 2008 13:32:56.0224 (UTC)
	FILETIME=[5DEA2200:01C92E01]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4308; t=1223991176;
	x=1224855176; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pchamp@cisco.com;
	z=From:=20=22Philippe=20Champagne=20(pchamp)=22=20<pchamp@ci
	sco.com>
	|Subject:=20RE=3A=20Proposal=20for=20changing=20messages=20
	names=20in=20Multicast=20Control=20Extensions=20 |Sender:=20;
	bh=Btl/TAEVgThlc9nhxOlYmB6OQmVF1pe2/5cNbbRZ1Vs=;
	b=kQVOrULKNOYECofFX/6GteAFe+mYExEGF+zk5KO5HNy/4kmSCxTrn06Mby
	QKH2P1IAGp6s4KVRqHihbygI/ePEzFQpqT2GiEkPrVKcxT+bAE9iKAsPPA2e
	MQLU4+wU2/;
Authentication-Results: sj-dkim-4; header.From=pchamp@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


Ok, just wanted to make sure what you meant.

So, this means a Multicast Replication Control Message would be used
both as a reply to an authorization as well as a directive.  I tend to
agree with this, although, we might review that case when we define the
authorization message and if the reply from the server would carry
roughly the same information as the directive. I would assume it would.



>-----Original Message-----
>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it] 
>Sent: Tuesday, October 14, 2008 9:22 AM
>To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech 
>Dec (wdec); Sanjay Wadhwa
>Cc: ancp@ietf.org
>Subject: RE: Proposal for changing messages names in Multicast 
>Control Extensions 
>
>Hi Phil,
>        please see inline.
>
>Regards,
>Roberta
>
>-----Original Message-----
>From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>Sent: Tuesday, October 14, 2008 2:50 PM
>To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); 
>Sanjay Wadhwa
>Cc: ancp@ietf.org
>Subject: RE: Proposal for changing messages names in Multicast 
>Control Extensions
>
>
>> I'm ok with those renaming.
>[RM] Great
>
>> Do you mean that when the ANCP client ask authorization for a Join, 
>> its request is a Multicast Replication Control Message and the reply 
>> from the server is the same or different:____
>
>[RM] not exactly, what I meant is slightly different:  when an 
>ANCP client asks for authorization to Join a multicast flow, 
>it uses an ANCP message (not defined yet), while when the 
>server replies to the authorization message sent by the client 
>it could use a Multicast Replication Control Message
>
>> While if the server is sending
>> a directive to the ANCP client to have a port join a 
>multicast, do you 
>> mean this is also called Multicast Replication Control Message?
>
>[RM] yes this is current scenario where the server uses a 
>Multicast Replication Control Message to send a directive to 
>the ANCP client to have a port join or leave a multicast flow.
>Does it make sense?
>
>Thanks,
>Roberta
>
>
>
>
>>-----Original Message-----
>>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>Sent: Tuesday, October 14, 2008 7:46 AM
>>To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec 
>>(wdec); 'Sanjay Wadhwa'
>>Subject: Proposal for changing messages names in Multicast Control 
>>Extensions
>>
>>
>>Hello,
>>        I'm currently merging draft-ancp-mc-extensions with 
>>draft-ietf-ancp-protocol, and I am thinking it could be useful to 
>>simplify the terminology in terms of multicast message names.
>>In particular I'd like to rename:
>>- Multicast Replication Control Request Message in just Multicast 
>>Replication Control Message
>>- Multicast Status Response Message and in Multicast Status Message
>>
>>This change would allow re-using the same message type for different 
>>purposes/use cases if needed in future, without affecting current 
>>scenario.
>>
>>Please let me know what's your opinion on this proposal.
>>
>>Thanks and best regards,
>>
>>Roberta
>>
>>
>>CONFIDENTIALITY NOTICE
>>
>>This message and its attachments are addressed solely to the persons 
>>above and may contain confidential information. If you have received 
>>the message in error, be informed that any use of the content 
>hereof is 
>>prohibited. Please return it immediately to the sender and delete the 
>>message. Should you have any questions, please contact us by replying 
>>to webmaster@telecomitalia.it.
>>
>>        Thank you
>>
>>                                        www.telecomitalia.it
>>
>
>
>CONFIDENTIALITY NOTICE
>
>This message and its attachments are addressed solely to the 
>persons above and may contain confidential information. If you 
>have received the message in error, be informed that any use 
>of the content hereof is prohibited. Please return it 
>immediately to the sender and delete the message. Should you 
>have any questions, please contact us by replying to 
>webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 14 06:50:23 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E02828C17C;
	Tue, 14 Oct 2008 06:50:23 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77BAC28C17C
	for <ancp@core3.amsl.com>; Tue, 14 Oct 2008 06:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 DxF-HHP6TK7L for <ancp@core3.amsl.com>;
	Tue, 14 Oct 2008 06:50:17 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id 5C3BE28C1A4
	for <ancp@ietf.org>; Tue, 14 Oct 2008 06:50:17 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9EDogJB004212; 
	Tue, 14 Oct 2008 15:50:44 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 14 Oct 2008 15:50:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 15:50:40 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E025E89B4@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal for changing messages names in Multicast Control
	Extensions 
Thread-Index: Ackt8mzi+Xqn9f4HQkKdSP4M+mBKigACEQhgAACK9lA=
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Maglione Roberta" <roberta.maglione@telecomitalia.it>
X-OriginalArrivalTime: 14 Oct 2008 13:50:42.0664 (UTC)
	FILETIME=[D98FF680:01C92E03]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


Roberta,

I am fine with the renaming as well.

What do you mean with this:

>This change would allow re-using the same message type for 
>different purposes/use cases if needed in future, without 
>affecting current scenario.

Are you talking about re-using both message types for something else in
the future, or are you only referring to the multicast status response
message?  Could you give an example of this future use?  

regards,
Stefaan

-----Original Message-----
From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com] 
Sent: dinsdag 14 oktober 2008 14:50
To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
Wadhwa
Cc: ancp@ietf.org
Subject: RE: Proposal for changing messages names in Multicast Control
Extensions 


I'm ok with those renaming.

Do you mean that when the ANCP client ask authorization for a Join, its
request is a Multicast Replication Control Message and the reply from
the server is the same or different:____  While if the server is sending
a directive to the ANCP client to have a port join a multicast, do you
mean this is also called Multicast Replication Control Message?




>-----Original Message-----
>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>Sent: Tuesday, October 14, 2008 7:46 AM
>To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec 
>(wdec); 'Sanjay Wadhwa'
>Subject: Proposal for changing messages names in Multicast Control 
>Extensions
>
>
>Hello,
>        I'm currently merging draft-ancp-mc-extensions with 
>draft-ietf-ancp-protocol, and I am thinking it could be useful 
>to simplify the terminology in terms of multicast message names.
>In particular I'd like to rename:
>- Multicast Replication Control Request Message in just 
>Multicast Replication Control Message
>- Multicast Status Response Message and in Multicast Status Message
>
>This change would allow re-using the same message type for 
>different purposes/use cases if needed in future, without 
>affecting current scenario.
>
>Please let me know what's your opinion on this proposal.
>
>Thanks and best regards,
>
>Roberta
>
>
>CONFIDENTIALITY NOTICE
>
>This message and its attachments are addressed solely to the 
>persons above and may contain confidential information. If you 
>have received the message in error, be informed that any use 
>of the content hereof is prohibited. Please return it 
>immediately to the sender and delete the message. Should you 
>have any questions, please contact us by replying to 
>webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 14 06:59:50 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B727228C1DB;
	Tue, 14 Oct 2008 06:59:50 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 94E8A28C1DB
	for <ancp@core3.amsl.com>; Tue, 14 Oct 2008 06:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 j3-GLsbsFNaG for <ancp@core3.amsl.com>;
	Tue, 14 Oct 2008 06:59:45 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it
	(grfedg701rm001.telecomitalia.it [217.169.121.20])
	by core3.amsl.com (Postfix) with ESMTP id 51B6528C1D6
	for <ancp@ietf.org>; Tue, 14 Oct 2008 06:59:45 -0700 (PDT)
Received: from GRFHUB706RM001.griffon.local (10.19.3.71) by
	GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP
	Server (TLS) id 8.1.291.1; Tue, 14 Oct 2008 16:01:49 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by
	GRFHUB706RM001.griffon.local ([10.19.9.239]) with mapi; Tue, 14 Oct 2008
	15:59:50 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'DE CNODDER Stefaan' <stefaan.de_cnodder@alcatel-lucent.be>
Date: Tue, 14 Oct 2008 15:59:50 +0200
Thread-Topic: Proposal for changing messages names in Multicast Control
	Extensions 
Thread-Index: Ackt8mzi+Xqn9f4HQkKdSP4M+mBKigACEQhgAACK9lAAAfDAcA==
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A20129491FF8@GRFMBX702RM001.griffon.local>
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E025E89B4@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E025E89B4@FRVELSMBS22.ad2.ad.alcatel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
 Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hi Stefaan,
        please see inline.
Regards,
Roberta

-----Original Message-----
From: DE CNODDER Stefaan [mailto:stefaan.de_cnodder@alcatel-lucent.be]
Sent: Tuesday, October 14, 2008 3:51 PM
To: Maglione Roberta
Cc: ancp@ietf.org
Subject: RE: Proposal for changing messages names in Multicast Control Extensions


Roberta,

I am fine with the renaming as well.

[RM] great

What do you mean with this:

>This change would allow re-using the same message type for
>different purposes/use cases if needed in future, without
>affecting current scenario.

Are you talking about re-using both message types for something else in
the future, or are you only referring to the multicast status response
message?  Could you give an example of this future use?

[RM] I was thinking more about reusing Multicast Replication Control Message in the following scenario:
when an ANCP client asks for authorization to Join a multicast flow, it uses an ANCP message (not defined yet), while when the server replies to the authorization message sent by the client it could use a Multicast Replication Control Message


-----Original Message-----
From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
Sent: dinsdag 14 oktober 2008 14:50
To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
Wadhwa
Cc: ancp@ietf.org
Subject: RE: Proposal for changing messages names in Multicast Control
Extensions


I'm ok with those renaming.

Do you mean that when the ANCP client ask authorization for a Join, its
request is a Multicast Replication Control Message and the reply from
the server is the same or different:____  While if the server is sending
a directive to the ANCP client to have a port join a multicast, do you
mean this is also called Multicast Replication Control Message?




>-----Original Message-----
>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>Sent: Tuesday, October 14, 2008 7:46 AM
>To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec
>(wdec); 'Sanjay Wadhwa'
>Subject: Proposal for changing messages names in Multicast Control
>Extensions
>
>
>Hello,
>        I'm currently merging draft-ancp-mc-extensions with
>draft-ietf-ancp-protocol, and I am thinking it could be useful
>to simplify the terminology in terms of multicast message names.
>In particular I'd like to rename:
>- Multicast Replication Control Request Message in just
>Multicast Replication Control Message
>- Multicast Status Response Message and in Multicast Status Message
>
>This change would allow re-using the same message type for
>different purposes/use cases if needed in future, without
>affecting current scenario.
>
>Please let me know what's your opinion on this proposal.
>
>Thanks and best regards,
>
>Roberta
>
>
>CONFIDENTIALITY NOTICE
>
>This message and its attachments are addressed solely to the
>persons above and may contain confidential information. If you
>have received the message in error, be informed that any use
>of the content hereof is prohibited. Please return it
>immediately to the sender and delete the message. Should you
>have any questions, please contact us by replying to
>webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
>


CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 14 07:01:21 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E37683A6BF0;
	Tue, 14 Oct 2008 07:01:21 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7439E3A6BE6
	for <ancp@core3.amsl.com>; Tue, 14 Oct 2008 07:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8hzrXeIsh6bJ for <ancp@core3.amsl.com>;
	Tue, 14 Oct 2008 07:01:19 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 0C0A53A6BDA
	for <ancp@ietf.org>; Tue, 14 Oct 2008 07:01:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,409,1220227200"; d="scan'208";a="22579740"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 14 Oct 2008 14:01:37 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9EE1bjM010798; 
	Tue, 14 Oct 2008 16:01:37 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9EE1bn8025729;
	Tue, 14 Oct 2008 14:01:37 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 16:01:37 +0200
Received: from [144.254.203.147] ([144.254.203.147]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 16:01:36 +0200
Message-Id: <8F6F7C4E-B7F7-4F0E-94D1-271B7A4425FD@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: DE CNODDER Stefaan <stefaan.de_cnodder@alcatel-lucent.be>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E025E89B4@FRVELSMBS22.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 14 Oct 2008 16:01:35 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E025E89B4@FRVELSMBS22.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 14 Oct 2008 14:01:36.0910 (UTC)
	FILETIME=[5F85FAE0:01C92E05]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3258; t=1223992897;
	x=1224856897; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=KOFzqpdQTHlziZQ0ROOoZm5hgwDxNEJc49dHUofRgQs=;
	b=IAzT/W1R+40XgDjt744lgOoG9XwMJGdjE22r8lOwp3CNGuHOAa3KppKNPA
	G2bUOwO8PMwtglgNov8kcfgqkv89rEgtSxjuS3lL1V7ehcWn6l7Sxp9bh8F8
	uz5lJ/zeNg;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Roberta and all,
I support these name changes.

Stefaan,
One example is (re)using the Multicast Replication Control message as  
a "response" to a multicast admission request from AN (eg when AN  
receives an IGMP Join).

Francois

On 14 Oct 2008, at 15:50, DE CNODDER Stefaan wrote:

>
> Roberta,
>
> I am fine with the renaming as well.
>
> What do you mean with this:
>
>> This change would allow re-using the same message type for
>> different purposes/use cases if needed in future, without
>> affecting current scenario.
>
> Are you talking about re-using both message types for something else  
> in
> the future, or are you only referring to the multicast status response
> message?  Could you give an example of this future use?
>
> regards,
> Stefaan
>
> -----Original Message-----
> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
> Sent: dinsdag 14 oktober 2008 14:50
> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
> Wadhwa
> Cc: ancp@ietf.org
> Subject: RE: Proposal for changing messages names in Multicast Control
> Extensions
>
>
> I'm ok with those renaming.
>
> Do you mean that when the ANCP client ask authorization for a Join,  
> its
> request is a Multicast Replication Control Message and the reply from
> the server is the same or different:____  While if the server is  
> sending
> a directive to the ANCP client to have a port join a multicast, do you
> mean this is also called Multicast Replication Control Message?
>
>
>
>
>> -----Original Message-----
>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>> Sent: Tuesday, October 14, 2008 7:46 AM
>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec
>> (wdec); 'Sanjay Wadhwa'
>> Subject: Proposal for changing messages names in Multicast Control
>> Extensions
>>
>>
>> Hello,
>>       I'm currently merging draft-ancp-mc-extensions with
>> draft-ietf-ancp-protocol, and I am thinking it could be useful
>> to simplify the terminology in terms of multicast message names.
>> In particular I'd like to rename:
>> - Multicast Replication Control Request Message in just
>> Multicast Replication Control Message
>> - Multicast Status Response Message and in Multicast Status Message
>>
>> This change would allow re-using the same message type for
>> different purposes/use cases if needed in future, without
>> affecting current scenario.
>>
>> Please let me know what's your opinion on this proposal.
>>
>> Thanks and best regards,
>>
>> Roberta
>>
>>
>> CONFIDENTIALITY NOTICE
>>
>> This message and its attachments are addressed solely to the
>> persons above and may contain confidential information. If you
>> have received the message in error, be informed that any use
>> of the content hereof is prohibited. Please return it
>> immediately to the sender and delete the message. Should you
>> have any questions, please contact us by replying to
>> webmaster@telecomitalia.it.
>>
>>       Thank you
>>
>>                                       www.telecomitalia.it
>>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Wed Oct 15 05:08:49 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 63F353A6974;
	Wed, 15 Oct 2008 05:08:49 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4D003A6974
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 05:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 Uh4aIkf9o1GQ for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 05:08:42 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5])
	by core3.amsl.com (Postfix) with ESMTP id CED643A694F
	for <ancp@ietf.org>; Wed, 15 Oct 2008 05:08:41 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9FC9QtO001151
	for <ancp@ietf.org>; Wed, 15 Oct 2008 14:09:38 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Wed, 15 Oct 2008 14:09:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 14:09:30 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal for changing messages names in Multicast Control
	Extensions 
Thread-Index: Ackt8mzi+Xqn9f4HQkKdSP4M+mBKigACEQhgAAD3xcAAAGcMAAAvc2gw
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 15 Oct 2008 12:09:31.0151 (UTC)
	FILETIME=[E11259F0:01C92EBE]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


If a message can be used as both a request and a reply, is the defitions
of the Transaction Identifier still accurate?  Currently the draft says:

- trans id in request is linearly incrementing, and is per message type
- trans id in response is copied from request

If the same message type can be both request and response, then how will
the trans id behave?  Should the receiver first try to find out whether
it is a request or a response, and then process it accordingly?  Or how
should it then work?

regards,
Stefaan


-----Original Message-----
From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com] 
Sent: dinsdag 14 oktober 2008 15:33
To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
Wadhwa
Cc: ancp@ietf.org
Subject: RE: Proposal for changing messages names in Multicast Control
Extensions 


Ok, just wanted to make sure what you meant.

So, this means a Multicast Replication Control Message would be used
both as a reply to an authorization as well as a directive.  I tend to
agree with this, although, we might review that case when we define the
authorization message and if the reply from the server would carry
roughly the same information as the directive. I would assume it would.



>-----Original Message-----
>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>Sent: Tuesday, October 14, 2008 9:22 AM
>To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec 
>(wdec); Sanjay Wadhwa
>Cc: ancp@ietf.org
>Subject: RE: Proposal for changing messages names in Multicast Control 
>Extensions
>
>Hi Phil,
>        please see inline.
>
>Regards,
>Roberta
>
>-----Original Message-----
>From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>Sent: Tuesday, October 14, 2008 2:50 PM
>To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay 
>Wadhwa
>Cc: ancp@ietf.org
>Subject: RE: Proposal for changing messages names in Multicast Control 
>Extensions
>
>
>> I'm ok with those renaming.
>[RM] Great
>
>> Do you mean that when the ANCP client ask authorization for a Join, 
>> its request is a Multicast Replication Control Message and the reply 
>> from the server is the same or different:____
>
>[RM] not exactly, what I meant is slightly different:  when an ANCP 
>client asks for authorization to Join a multicast flow, it uses an ANCP

>message (not defined yet), while when the server replies to the 
>authorization message sent by the client it could use a Multicast 
>Replication Control Message
>
>> While if the server is sending
>> a directive to the ANCP client to have a port join a
>multicast, do you
>> mean this is also called Multicast Replication Control Message?
>
>[RM] yes this is current scenario where the server uses a Multicast 
>Replication Control Message to send a directive to the ANCP client to 
>have a port join or leave a multicast flow.
>Does it make sense?
>
>Thanks,
>Roberta
>
>
>
>
>>-----Original Message-----
>>From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>Sent: Tuesday, October 14, 2008 7:46 AM
>>To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec 
>>(wdec); 'Sanjay Wadhwa'
>>Subject: Proposal for changing messages names in Multicast Control 
>>Extensions
>>
>>
>>Hello,
>>        I'm currently merging draft-ancp-mc-extensions with 
>>draft-ietf-ancp-protocol, and I am thinking it could be useful to 
>>simplify the terminology in terms of multicast message names.
>>In particular I'd like to rename:
>>- Multicast Replication Control Request Message in just Multicast 
>>Replication Control Message
>>- Multicast Status Response Message and in Multicast Status Message
>>
>>This change would allow re-using the same message type for different 
>>purposes/use cases if needed in future, without affecting current 
>>scenario.
>>
>>Please let me know what's your opinion on this proposal.
>>
>>Thanks and best regards,
>>
>>Roberta
>>
>>
>>CONFIDENTIALITY NOTICE
>>
>>This message and its attachments are addressed solely to the persons 
>>above and may contain confidential information. If you have received 
>>the message in error, be informed that any use of the content
>hereof is
>>prohibited. Please return it immediately to the sender and delete the 
>>message. Should you have any questions, please contact us by replying 
>>to webmaster@telecomitalia.it.
>>
>>        Thank you
>>
>>                                        www.telecomitalia.it
>>
>
>
>CONFIDENTIALITY NOTICE
>
>This message and its attachments are addressed solely to the persons 
>above and may contain confidential information. If you have received 
>the message in error, be informed that any use of the content hereof is

>prohibited. Please return it immediately to the sender and delete the 
>message. Should you have any questions, please contact us by replying 
>to webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Wed Oct 15 06:19:09 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BEC0A3A692F;
	Wed, 15 Oct 2008 06:19:09 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EEF63A692F
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 06:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 GexcW6OW3AA0 for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 06:19:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 216993A67F7
	for <ancp@ietf.org>; Wed, 15 Oct 2008 06:19:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,415,1220227200"; d="scan'208";a="22700872"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 15 Oct 2008 13:19:17 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9FDJHtt001070; 
	Wed, 15 Oct 2008 15:19:17 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9FDJHOn001524;
	Wed, 15 Oct 2008 13:19:17 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 15:19:17 +0200
Received: from [144.254.203.147] ([144.254.203.147]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 15:19:17 +0200
Message-Id: <494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: DE CNODDER Stefaan <stefaan.de_cnodder@alcatel-lucent.be>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 15:19:14 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 15 Oct 2008 13:19:17.0175 (UTC)
	FILETIME=[A022EC70:01C92EC8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5905; t=1224076757;
	x=1224940757; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=CMs/dF3aZpWPxt4mIha8XSV/+vEPZia86TwIC4ykl98=;
	b=Ds1w4/oL+7B8cK6lc4CNzDFX59yv+qndf7gytqY5+yEUHi8LuQzDkG/Pxi
	ho9AWOvoJSkRku/7Bx1G+jN12It0FawOSzKt3o99xOcjtKcoJSJvrvw9dPTq
	iP8rR+9kPd;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


On 15 Oct 2008, at 14:09, DE CNODDER Stefaan wrote:

>
> If a message can be used as both a request and a reply, is the  
> defitions
> of the Transaction Identifier still accurate?  Currently the draft  
> says:
>
> - trans id in request is linearly incrementing, and is per message  
> type
> - trans id in response is copied from request
>
> If the same message type can be both request and response, then how  
> will
> the trans id behave?  Should the receiver first try to find out  
> whether
> it is a request or a response, and then process it accordingly?  Or  
> how
> should it then work?

One option would be for the sender to look at the Result field:
	* if it is set to Success/Failure, then this message is a "response"  
to an earlier request (and its Transaction ID echoed the one of the  
request)
	* if it is set to Ack/Nack, then this messages is a request (and the  
transaction ID was generated by remote end)

>
>
> regards,
> Stefaan
>
>
> -----Original Message-----
> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
> Sent: dinsdag 14 oktober 2008 15:33
> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
> Wadhwa
> Cc: ancp@ietf.org
> Subject: RE: Proposal for changing messages names in Multicast Control
> Extensions
>
>
> Ok, just wanted to make sure what you meant.
>
> So, this means a Multicast Replication Control Message would be used
> both as a reply to an authorization as well as a directive.  I tend to
> agree with this, although, we might review that case when we define  
> the
> authorization message and if the reply from the server would carry
> roughly the same information as the directive. I would assume it  
> would.
>
>
>
>> -----Original Message-----
>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>> Sent: Tuesday, October 14, 2008 9:22 AM
>> To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec
>> (wdec); Sanjay Wadhwa
>> Cc: ancp@ietf.org
>> Subject: RE: Proposal for changing messages names in Multicast  
>> Control
>> Extensions
>>
>> Hi Phil,
>>       please see inline.
>>
>> Regards,
>> Roberta
>>
>> -----Original Message-----
>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>> Sent: Tuesday, October 14, 2008 2:50 PM
>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
>> Wadhwa
>> Cc: ancp@ietf.org
>> Subject: RE: Proposal for changing messages names in Multicast  
>> Control
>> Extensions
>>
>>
>>> I'm ok with those renaming.
>> [RM] Great
>>
>>> Do you mean that when the ANCP client ask authorization for a Join,
>>> its request is a Multicast Replication Control Message and the reply
>>> from the server is the same or different:____
>>
>> [RM] not exactly, what I meant is slightly different:  when an ANCP
>> client asks for authorization to Join a multicast flow, it uses an  
>> ANCP
>
>> message (not defined yet), while when the server replies to the
>> authorization message sent by the client it could use a Multicast
>> Replication Control Message
>>
>>> While if the server is sending
>>> a directive to the ANCP client to have a port join a
>> multicast, do you
>>> mean this is also called Multicast Replication Control Message?
>>
>> [RM] yes this is current scenario where the server uses a Multicast
>> Replication Control Message to send a directive to the ANCP client to
>> have a port join or leave a multicast flow.
>> Does it make sense?
>>
>> Thanks,
>> Roberta
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>> Sent: Tuesday, October 14, 2008 7:46 AM
>>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec
>>> (wdec); 'Sanjay Wadhwa'
>>> Subject: Proposal for changing messages names in Multicast Control
>>> Extensions
>>>
>>>
>>> Hello,
>>>       I'm currently merging draft-ancp-mc-extensions with
>>> draft-ietf-ancp-protocol, and I am thinking it could be useful to
>>> simplify the terminology in terms of multicast message names.
>>> In particular I'd like to rename:
>>> - Multicast Replication Control Request Message in just Multicast
>>> Replication Control Message
>>> - Multicast Status Response Message and in Multicast Status Message
>>>
>>> This change would allow re-using the same message type for different
>>> purposes/use cases if needed in future, without affecting current
>>> scenario.
>>>
>>> Please let me know what's your opinion on this proposal.
>>>
>>> Thanks and best regards,
>>>
>>> Roberta
>>>
>>>
>>> CONFIDENTIALITY NOTICE
>>>
>>> This message and its attachments are addressed solely to the persons
>>> above and may contain confidential information. If you have received
>>> the message in error, be informed that any use of the content
>> hereof is
>>> prohibited. Please return it immediately to the sender and delete  
>>> the
>>> message. Should you have any questions, please contact us by  
>>> replying
>>> to webmaster@telecomitalia.it.
>>>
>>>       Thank you
>>>
>>>                                       www.telecomitalia.it
>>>
>>
>>
>> CONFIDENTIALITY NOTICE
>>
>> This message and its attachments are addressed solely to the persons
>> above and may contain confidential information. If you have received
>> the message in error, be informed that any use of the content  
>> hereof is
>
>> prohibited. Please return it immediately to the sender and delete the
>> message. Should you have any questions, please contact us by replying
>> to webmaster@telecomitalia.it.
>>
>>       Thank you
>>
>>                                       www.telecomitalia.it
>>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Wed Oct 15 06:22:53 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 319E628C205;
	Wed, 15 Oct 2008 06:22:53 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9E86B28C205
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 06:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 2G2bwo6khNgx for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 06:22:51 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id A44A928C1F4
	for <ancp@ietf.org>; Wed, 15 Oct 2008 06:22:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,415,1220227200"; d="scan'208";a="22701471"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 15 Oct 2008 13:23:10 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9FDNAJB030328; 
	Wed, 15 Oct 2008 15:23:10 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9FDNAKg002961;
	Wed, 15 Oct 2008 13:23:10 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 15:23:10 +0200
Received: from [144.254.203.147] ([144.254.203.147]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 15:23:10 +0200
Message-Id: <74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
In-Reply-To: <494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 15:23:07 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 15 Oct 2008 13:23:10.0028 (UTC)
	FILETIME=[2AED78C0:01C92EC9]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6632; t=1224076990;
	x=1224940990; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=WRgCjHGHNDp38//8sZAI1D1SPbJxL911TAtkl5A/Pq4=;
	b=G93F0Nv9AKTQ85jIDwSBv1K+8uOR5k7vbEVjERNdUJPPtMoeBodUbLBIyY
	8zdhYd6nPcJtgwVlgHAjQ/XioRhMOMue4KyEKG9RoR45u5HIWqvSZ9hETY64
	mJMZvEkAnU;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


On 15 Oct 2008, at 15:19, Francois Le Faucheur IMAP wrote:

>
> On 15 Oct 2008, at 14:09, DE CNODDER Stefaan wrote:
>
>>
>> If a message can be used as both a request and a reply, is the  
>> defitions
>> of the Transaction Identifier still accurate?  Currently the draft  
>> says:
>>
>> - trans id in request is linearly incrementing, and is per message  
>> type
>> - trans id in response is copied from request
>>
>> If the same message type can be both request and response, then how  
>> will
>> the trans id behave?  Should the receiver first try to find out  
>> whether
>> it is a request or a response, and then process it accordingly?  Or  
>> how
>> should it then work?
>

Oops, there was a typo in earlier message. This should read:
One option would be for the receiver to look at the Result field:
	* if it is set to Success/Failure, then this message is a "response"  
to an earlier request (and its Transaction ID echoed the one of the  
request)
	* if it is set to Ack/Nack, then this messages is a "request" (and  
the transaction ID was generated by remote end)

> One option would be for the sender to look at the Result field:
> 	* if it is set to Success/Failure, then this message is a  
> "response" to an earlier request (and its Transaction ID echoed the  
> one of the request)
> 	* if it is set to Ack/Nack, then this messages is a request (and  
> the transaction ID was generated by remote end)
>
>>
>>
>> regards,
>> Stefaan
>>
>>
>> -----Original Message-----
>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>> Sent: dinsdag 14 oktober 2008 15:33
>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); Sanjay
>> Wadhwa
>> Cc: ancp@ietf.org
>> Subject: RE: Proposal for changing messages names in Multicast  
>> Control
>> Extensions
>>
>>
>> Ok, just wanted to make sure what you meant.
>>
>> So, this means a Multicast Replication Control Message would be used
>> both as a reply to an authorization as well as a directive.  I tend  
>> to
>> agree with this, although, we might review that case when we define  
>> the
>> authorization message and if the reply from the server would carry
>> roughly the same information as the directive. I would assume it  
>> would.
>>
>>
>>
>>> -----Original Message-----
>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>> Sent: Tuesday, October 14, 2008 9:22 AM
>>> To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec
>>> (wdec); Sanjay Wadhwa
>>> Cc: ancp@ietf.org
>>> Subject: RE: Proposal for changing messages names in Multicast  
>>> Control
>>> Extensions
>>>
>>> Hi Phil,
>>>      please see inline.
>>>
>>> Regards,
>>> Roberta
>>>
>>> -----Original Message-----
>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>> Sent: Tuesday, October 14, 2008 2:50 PM
>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>> Sanjay
>>> Wadhwa
>>> Cc: ancp@ietf.org
>>> Subject: RE: Proposal for changing messages names in Multicast  
>>> Control
>>> Extensions
>>>
>>>
>>>> I'm ok with those renaming.
>>> [RM] Great
>>>
>>>> Do you mean that when the ANCP client ask authorization for a Join,
>>>> its request is a Multicast Replication Control Message and the  
>>>> reply
>>>> from the server is the same or different:____
>>>
>>> [RM] not exactly, what I meant is slightly different:  when an ANCP
>>> client asks for authorization to Join a multicast flow, it uses an  
>>> ANCP
>>
>>> message (not defined yet), while when the server replies to the
>>> authorization message sent by the client it could use a Multicast
>>> Replication Control Message
>>>
>>>> While if the server is sending
>>>> a directive to the ANCP client to have a port join a
>>> multicast, do you
>>>> mean this is also called Multicast Replication Control Message?
>>>
>>> [RM] yes this is current scenario where the server uses a Multicast
>>> Replication Control Message to send a directive to the ANCP client  
>>> to
>>> have a port join or leave a multicast flow.
>>> Does it make sense?
>>>
>>> Thanks,
>>> Roberta
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>> Sent: Tuesday, October 14, 2008 7:46 AM
>>>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech Dec
>>>> (wdec); 'Sanjay Wadhwa'
>>>> Subject: Proposal for changing messages names in Multicast Control
>>>> Extensions
>>>>
>>>>
>>>> Hello,
>>>>      I'm currently merging draft-ancp-mc-extensions with
>>>> draft-ietf-ancp-protocol, and I am thinking it could be useful to
>>>> simplify the terminology in terms of multicast message names.
>>>> In particular I'd like to rename:
>>>> - Multicast Replication Control Request Message in just Multicast
>>>> Replication Control Message
>>>> - Multicast Status Response Message and in Multicast Status Message
>>>>
>>>> This change would allow re-using the same message type for  
>>>> different
>>>> purposes/use cases if needed in future, without affecting current
>>>> scenario.
>>>>
>>>> Please let me know what's your opinion on this proposal.
>>>>
>>>> Thanks and best regards,
>>>>
>>>> Roberta
>>>>
>>>>
>>>> CONFIDENTIALITY NOTICE
>>>>
>>>> This message and its attachments are addressed solely to the  
>>>> persons
>>>> above and may contain confidential information. If you have  
>>>> received
>>>> the message in error, be informed that any use of the content
>>> hereof is
>>>> prohibited. Please return it immediately to the sender and delete  
>>>> the
>>>> message. Should you have any questions, please contact us by  
>>>> replying
>>>> to webmaster@telecomitalia.it.
>>>>
>>>>      Thank you
>>>>
>>>>                                      www.telecomitalia.it
>>>>
>>>
>>>
>>> CONFIDENTIALITY NOTICE
>>>
>>> This message and its attachments are addressed solely to the persons
>>> above and may contain confidential information. If you have received
>>> the message in error, be informed that any use of the content  
>>> hereof is
>>
>>> prohibited. Please return it immediately to the sender and delete  
>>> the
>>> message. Should you have any questions, please contact us by  
>>> replying
>>> to webmaster@telecomitalia.it.
>>>
>>>      Thank you
>>>
>>>                                      www.telecomitalia.it
>>>
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Wed Oct 15 07:26:25 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEC803A6B81;
	Wed, 15 Oct 2008 07:26:25 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A0D23A6B81
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 07:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 66sVp-7dMbPu for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 07:26:23 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 185B73A6963
	for <ancp@ietf.org>; Wed, 15 Oct 2008 07:26:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,416,1220227200"; d="scan'208,217";a="22712144"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 15 Oct 2008 14:26:38 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9FEQcqg027825; 
	Wed, 15 Oct 2008 16:26:38 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9FEQcGi029285;
	Wed, 15 Oct 2008 14:26:38 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 16:26:38 +0200
Received: from [144.254.203.147] ([144.254.203.147]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 16:26:37 +0200
Message-Id: <DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
In-Reply-To: <74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 16:26:34 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 15 Oct 2008 14:26:37.0868 (UTC)
	FILETIME=[0893BEC0:01C92ED2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=35045; t=1224080798;
	x=1224944798; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=cc6yxNmV9q4nFjrq7HQK1C+0Let6quAsTM1PRUtEUig=;
	b=HXwp2RzJImwSJngwXmWxTfpc5W1ecTOPmzwiEpSdcNKL1G6cV1tZ2RKf6S
	fQdHBzZrUIFoPsrKLAidFWy46k4l2JTOh3Ia/RkKGZd6AuIbNMUDTPfTYqFe
	isVcuUiVS0;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1142235047=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============1142235047==
Content-Type: multipart/alternative; boundary=Apple-Mail-2-960459111


--Apple-Mail-2-960459111
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

>>>
>>>
>>> If a message can be used as both a request and a reply, is the  
>>> defitions
>>> of the Transaction Identifier still accurate?  Currently the draft  
>>> says:
>>>
>>> - trans id in request is linearly incrementing, and is per message  
>>> type
>>> - trans id in response is copied from request
>>>
>>> If the same message type can be both request and response, then  
>>> how will
>>> the trans id behave?  Should the receiver first try to find out  
>>> whether
>>> it is a request or a response, and then process it accordingly?   
>>> Or how
>>> should it then work?
>>
>
> Oops, there was a typo in earlier message. This should read:
> One option would be for the receiver to look at the Result field:
> 	* if it is set to Success/Failure, then this message is a  
> "response" to an earlier request (and its Transaction ID echoed the  
> one of the request)
> 	* if it is set to Ack/Nack, then this messages is a "request" (and  
> the transaction ID was generated by remote end)

Note also that the AN may not even care that much whether it is a  
response or a spontaneous request, because the two are idempotent.

Francois


>
>
>> One option would be for the sender to look at the Result field:
>> 	* if it is set to Success/Failure, then this message is a  
>> "response" to an earlier request (and its Transaction ID echoed the  
>> one of the request)
>> 	* if it is set to Ack/Nack, then this messages is a request (and  
>> the transaction ID was generated by remote end)
>>
>>>
>>>
>>> regards,
>>> Stefaan
>>>
>>>
>>> -----Original Message-----
>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>> Sent: dinsdag 14 oktober 2008 15:33
>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>> Sanjay
>>> Wadhwa
>>> Cc: ancp@ietf.org
>>> Subject: RE: Proposal for changing messages names in Multicast  
>>> Control
>>> Extensions
>>>
>>>
>>> Ok, just wanted to make sure what you meant.
>>>
>>> So, this means a Multicast Replication Control Message would be used
>>> both as a reply to an authorization as well as a directive.  I  
>>> tend to
>>> agree with this, although, we might review that case when we  
>>> define the
>>> authorization message and if the reply from the server would carry
>>> roughly the same information as the directive. I would assume it  
>>> would.
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>> Sent: Tuesday, October 14, 2008 9:22 AM
>>>> To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec
>>>> (wdec); Sanjay Wadhwa
>>>> Cc: ancp@ietf.org
>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>> Control
>>>> Extensions
>>>>
>>>> Hi Phil,
>>>>     please see inline.
>>>>
>>>> Regards,
>>>> Roberta
>>>>
>>>> -----Original Message-----
>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>> Sent: Tuesday, October 14, 2008 2:50 PM
>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>> Sanjay
>>>> Wadhwa
>>>> Cc: ancp@ietf.org
>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>> Control
>>>> Extensions
>>>>
>>>>
>>>>> I'm ok with those renaming.
>>>> [RM] Great
>>>>
>>>>> Do you mean that when the ANCP client ask authorization for a  
>>>>> Join,
>>>>> its request is a Multicast Replication Control Message and the  
>>>>> reply
>>>>> from the server is the same or different:____
>>>>
>>>> [RM] not exactly, what I meant is slightly different:  when an ANCP
>>>> client asks for authorization to Join a multicast flow, it uses  
>>>> an ANCP
>>>
>>>> message (not defined yet), while when the server replies to the
>>>> authorization message sent by the client it could use a Multicast
>>>> Replication Control Message
>>>>
>>>>> While if the server is sending
>>>>> a directive to the ANCP client to have a port join a
>>>> multicast, do you
>>>>> mean this is also called Multicast Replication Control Message?
>>>>
>>>> [RM] yes this is current scenario where the server uses a Multicast
>>>> Replication Control Message to send a directive to the ANCP  
>>>> client to
>>>> have a port join or leave a multicast flow.
>>>> Does it make sense?
>>>>
>>>> Thanks,
>>>> Roberta
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>>> Sent: Tuesday, October 14, 2008 7:46 AM
>>>>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech  
>>>>> Dec
>>>>> (wdec); 'Sanjay Wadhwa'
>>>>> Subject: Proposal for changing messages names in Multicast Control
>>>>> Extensions
>>>>>
>>>>>
>>>>> Hello,
>>>>>     I'm currently merging draft-ancp-mc-extensions with
>>>>> draft-ietf-ancp-protocol, and I am thinking it could be useful to
>>>>> simplify the terminology in terms of multicast message names.
>>>>> In particular I'd like to rename:
>>>>> - Multicast Replication Control Request Message in just Multicast
>>>>> Replication Control Message
>>>>> - Multicast Status Response Message and in Multicast Status  
>>>>> Message
>>>>>
>>>>> This change would allow re-using the same message type for  
>>>>> different
>>>>> purposes/use cases if needed in future, without affecting current
>>>>> scenario.
>>>>>
>>>>> Please let me know what's your opinion on this proposal.
>>>>>
>>>>> Thanks and best regards,
>>>>>
>>>>> Roberta
>>>>>
>>>>>
>>>>> CONFIDENTIALITY NOTICE
>>>>>
>>>>> This message and its attachments are addressed solely to the  
>>>>> persons
>>>>> above and may contain confidential information. If you have  
>>>>> received
>>>>> the message in error, be informed that any use of the content
>>>> hereof is
>>>>> prohibited. Please return it immediately to the sender and  
>>>>> delete the
>>>>> message. Should you have any questions, please contact us by  
>>>>> replying
>>>>> to webmaster@telecomitalia.it.
>>>>>
>>>>>     Thank you
>>>>>
>>>>>                                     www.telecomitalia.it
>>>>>
>>>>
>>>>
>>>> CONFIDENTIALITY NOTICE
>>>>
>>>> This message and its attachments are addressed solely to the  
>>>> persons
>>>> above and may contain confidential information. If you have  
>>>> received
>>>> the message in error, be informed that any use of the content  
>>>> hereof is
>>>
>>>> prohibited. Please return it immediately to the sender and delete  
>>>> the
>>>> message. Should you have any questions, please contact us by  
>>>> replying
>>>> to webmaster@telecomitalia.it.
>>>>
>>>>     Thank you
>>>>
>>>>                                     www.telecomitalia.it
>>>>
>>> _______________________________________________
>>> ANCP mailing list
>>> ANCP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ancp
>>
>


--Apple-Mail-2-960459111
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite"><blockquote =
type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#006312"><br></font><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">If a message can be used as both =
a request and a reply, is the =
defitions<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">of the Transaction Identifier =
still accurate? &nbsp;Currently the draft =
says:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">- trans id in request is =
linearly incrementing, and is per message =
type<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">- trans id in response is copied from =
request<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">If the same message type can be =
both request and response, then how =
will<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">the trans id behave? &nbsp;Should the receiver first try =
to find out whether<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">it is a request or a response, =
and then process it accordingly? &nbsp;Or =
how<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">should it then =
work?<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>Oops, there was a typo in earlier =
message. This should read:<br>One option would be for the receiver to =
look at the Result field:<br><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* if it is set to =
Success/Failure, then this message is a "response" to an earlier request =
(and its Transaction ID echoed the one of the request)<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* if it =
is set to Ack/Nack, then this messages is a "request" (and the =
transaction ID was generated by remote =
end)</div></blockquote><div><br></div><div>Note also that the AN may not =
even care that much whether it is a response or a spontaneous request, =
because the two are =
idempotent.</div><div><br></div><div>Francois</div><div><br></div><br><blo=
ckquote type=3D"cite"><div><br><br><blockquote type=3D"cite">One option =
would be for the sender to look at the Result =
field:<br></blockquote><blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* if it =
is set to Success/Failure, then this message is a "response" to an =
earlier request (and its Transaction ID echoed the one of the =
request)<br></blockquote><blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* if it =
is set to Ack/Nack, then this messages is a request (and the transaction =
ID was generated by remote end)<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">regards,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Stefaan<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: Philippe Champagne =
(pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">Sent:=
 dinsdag 14 oktober 2008 15:33<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan; Wojciech Dec (wdec); =
Sanjay<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite">Subject: RE: =
Proposal for changing messages names in Multicast =
Control<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">Extensions<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Ok, just wanted to make sure =
what you meant.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">So, this means a Multicast =
Replication Control Message would be =
used<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">both as a reply to an authorization as well as a =
directive. &nbsp;I tend to<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">agree with this, although, we =
might review that case when we define =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">authorization message and if the reply from the server =
would carry<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">roughly the same information as =
the directive. I would assume it =
would.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">From: =
Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Sent: =
Tuesday, October 14, 2008 9:22 =
AM<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">To: =
Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech =
Dec<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">(wdec); =
Sanjay Wadhwa<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Subject: RE: Proposal for =
changing messages names in Multicast =
Control<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote><blockq=
uote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Hi =
Phil,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;please see =
inline.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Regards,<br></blockquote></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">From: =
Philippe Champagne (pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Sent: Tuesday, October 14, 2008 =
2:50 PM<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">To: =
Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec); =
Sanjay<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Cc: =
<a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Subject: RE: Proposal for =
changing messages names in Multicast =
Control<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote><blockq=
uote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">I'm ok with those =
renaming.<br></blockquote></blockquote></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">[RM] =
Great<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Do you mean that when the ANCP =
client ask authorization for a =
Join,<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">its request is a Multicast =
Replication Control Message and the =
reply<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">from the server is the same or =
different:____<br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">[RM] =
not exactly, what I meant is slightly different: &nbsp;when an =
ANCP<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">client =
asks for authorization to Join a multicast flow, it uses an =
ANCP<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">message =
(not defined yet), while when the server replies to =
the<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">authorization message sent by the client it could use a =
Multicast<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Replication Control =
Message<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">While if the server is =
sending<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">a directive to the ANCP client =
to have a port join =
a<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">multicast, do =
you<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">mean this is also called =
Multicast Replication Control =
Message?<br></blockquote></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">[RM] =
yes this is current scenario where the server uses a =
Multicast<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Replication Control Message to send a directive to the =
ANCP client to<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">have a =
port join or leave a multicast =
flow.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Does =
it make sense?<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Thanks,<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote></blockquote></blockquote></blockquote><block=
quote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">From: Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Sent: Tuesday, October 14, 2008 =
7:46 =
AM<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">To: Philippe Champagne (pchamp); =
'DE CNODDER Stefaan'; Wojciech =
Dec<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">(wdec); 'Sanjay =
Wadhwa'<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Subject: Proposal for changing =
messages names in Multicast =
Control<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote></block=
quote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Hello,<br></blockquote></blockquote></blockquote></blockquot=
e><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"> &nbsp;&nbsp;&nbsp;&nbsp;I'm =
currently merging draft-ancp-mc-extensions =
with<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">draft-ietf-ancp-protocol, and I =
am thinking it could be useful =
to<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">simplify the terminology in =
terms of multicast message =
names.<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">In particular I'd like to =
rename:<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">- Multicast Replication Control =
Request Message in just =
Multicast<br></blockquote></blockquote></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Replication Control =
Message<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">- Multicast Status Response =
Message and in Multicast Status =
Message<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">This change would allow re-using =
the same message type for =
different<br></blockquote></blockquote></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">purposes/use cases if needed in =
future, without affecting =
current<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">scenario.<br></blockquote></blockquote></blockquote></blockq=
uote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Please let me know what's your =
opinion on this =
proposal.<br></blockquote></blockquote></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Thanks and best =
regards,<br></blockquote></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">CONFIDENTIALITY =
NOTICE<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">This message and its attachments =
are addressed solely to the =
persons<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">above and may contain =
confidential information. If you have =
received<br></blockquote></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">the message in error, be =
informed that any use of the =
content<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">hereof =
is<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">prohibited. Please return it =
immediately to the sender and delete =
the<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">message. Should you have any =
questions, please contact us by =
replying<br></blockquote></blockquote></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"> &nbsp;&nbsp;&nbsp;&nbsp;Thank =
you<br></blockquote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">CONFIDENTIALITY =
NOTICE<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">This =
message and its attachments are addressed solely to the =
persons<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">above =
and may contain confidential information. If you have =
received<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">the =
message in error, be informed that any use of the content hereof =
is<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">prohibited. Please return it immediately to the sender and =
delete the<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">message.=
 Should you have any questions, please contact us by =
replying<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;Thank =
you<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">ANCP =
mailing list<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><br></div></blockquote></div><br></body></h=
tml>=

--Apple-Mail-2-960459111--

--===============1142235047==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1142235047==--


From ancp-bounces@ietf.org  Wed Oct 15 07:36:41 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FD813A68CC;
	Wed, 15 Oct 2008 07:36:41 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A9CC3A68CC
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 07:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001]
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 hdCdEfmfk4Kr for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 07:36:38 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id B21763A67B2
	for <ancp@ietf.org>; Wed, 15 Oct 2008 07:36:37 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9FEaUQi018205; 
	Wed, 15 Oct 2008 16:36:30 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Wed, 15 Oct 2008 16:36:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 16:36:29 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Proposal for changing messages names in Multicast Control
	Extensions
Thread-Index: Acku0g8I5Adm9QUmRUSA+ixtrai78wAAKRTg
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
X-OriginalArrivalTime: 15 Oct 2008 14:36:30.0933 (UTC)
	FILETIME=[6A124850:01C92ED3]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0930166847=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0930166847==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92ED3.697D51F3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92ED3.697D51F3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
Francois,
=20
If it is a request, then the AN just executes the commands.  If it is a
response, then I would think it has to look up the state indexed by
trans id to clean it up, and to execute the join which is in that state.
So yes, it looks to me that both are different.  Also the processing of
the trans id is different because for requests it has to check whether
it is each time incremented by 1, which it does not have to do for
responses.
=20
regards,
Stefaan

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: woensdag 15 oktober 2008 16:27
To: Francois Le Faucheur IMAP
Cc: DE CNODDER Stefaan; ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
Control Extensions



		=09
		=09
		=09

			If a message can be used as both a request and a
reply, is the defitions
		=09

			of the Transaction Identifier still accurate?
Currently the draft says:
		=09


			- trans id in request is linearly incrementing,
and is per message type
		=09

			- trans id in response is copied from request
		=09


			If the same message type can be both request and
response, then how will
		=09

			the trans id behave?  Should the receiver first
try to find out whether
		=09

			it is a request or a response, and then process
it accordingly?  Or how
		=09

			should it then work?
		=09



	Oops, there was a typo in earlier message. This should read:
	One option would be for the receiver to look at the Result
field:
	* if it is set to Success/Failure, then this message is a
"response" to an earlier request (and its Transaction ID echoed the one
of the request)
	* if it is set to Ack/Nack, then this messages is a "request"
(and the transaction ID was generated by remote end)


Note also that the AN may not even care that much whether it is a
response or a spontaneous request, because the two are idempotent.

Francois





		One option would be for the sender to look at the Result
field:
	=09

		* if it is set to Success/Failure, then this message is
a "response" to an earlier request (and its Transaction ID echoed the
one of the request)
	=09

		* if it is set to Ack/Nack, then this messages is a
request (and the transaction ID was generated by remote end)
	=09




			regards,
		=09

			Stefaan
		=09



			-----Original Message-----
		=09

			From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
		=09

			Sent: dinsdag 14 oktober 2008 15:33
		=09

			To: Maglione Roberta; DE CNODDER Stefaan;
Wojciech Dec (wdec); Sanjay
		=09

			Wadhwa
		=09

			Cc: ancp@ietf.org
		=09

			Subject: RE: Proposal for changing messages
names in Multicast Control
		=09

			Extensions
		=09



			Ok, just wanted to make sure what you meant.
		=09


			So, this means a Multicast Replication Control
Message would be used
		=09

			both as a reply to an authorization as well as a
directive.  I tend to
		=09

			agree with this, although, we might review that
case when we define the
		=09

			authorization message and if the reply from the
server would carry
		=09

			roughly the same information as the directive. I
would assume it would.
		=09




				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 9:22 AM
			=09

				To: Philippe Champagne (pchamp); DE
CNODDER Stefaan; Wojciech Dec
			=09

				(wdec); Sanjay Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09


				Hi Phil,
			=09

				    please see inline.
			=09


				Regards,
			=09

				Roberta
			=09


				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: Tuesday, October 14, 2008 2:50 PM
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				I'm ok with those renaming.
			=09

				[RM] Great
			=09


				Do you mean that when the ANCP client
ask authorization for a Join,
			=09

				its request is a Multicast Replication
Control Message and the reply
			=09

				from the server is the same or
different:____
			=09


				[RM] not exactly, what I meant is
slightly different:  when an ANCP
			=09

				client asks for authorization to Join a
multicast flow, it uses an ANCP
			=09


				message (not defined yet), while when
the server replies to the
			=09

				authorization message sent by the client
it could use a Multicast
			=09

				Replication Control Message
			=09


				While if the server is sending
			=09

				a directive to the ANCP client to have a
port join a
			=09

				multicast, do you
			=09

				mean this is also called Multicast
Replication Control Message?
			=09


				[RM] yes this is current scenario where
the server uses a Multicast
			=09

				Replication Control Message to send a
directive to the ANCP client to
			=09

				have a port join or leave a multicast
flow.
			=09

				Does it make sense?
			=09


				Thanks,
			=09

				Roberta
			=09





				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 7:46 AM
			=09

				To: Philippe Champagne (pchamp); 'DE
CNODDER Stefaan'; Wojciech Dec
			=09

				(wdec); 'Sanjay Wadhwa'
			=09

				Subject: Proposal for changing messages
names in Multicast Control
			=09

				Extensions
			=09



				Hello,
			=09

				    I'm currently merging
draft-ancp-mc-extensions with
			=09

				draft-ietf-ancp-protocol, and I am
thinking it could be useful to
			=09

				simplify the terminology in terms of
multicast message names.
			=09

				In particular I'd like to rename:
			=09

				- Multicast Replication Control Request
Message in just Multicast
			=09

				Replication Control Message
			=09

				- Multicast Status Response Message and
in Multicast Status Message
			=09


				This change would allow re-using the
same message type for different
			=09

				purposes/use cases if needed in future,
without affecting current
			=09

				scenario.
			=09


				Please let me know what's your opinion
on this proposal.
			=09


				Thanks and best regards,
			=09


				Roberta
			=09



				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content
			=09

				hereof is
			=09

				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09




				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content hereof is
			=09


				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09


			_______________________________________________
		=09

			ANCP mailing list
		=09

			ANCP@ietf.org
		=09

			https://www.ietf.org/mailman/listinfo/ancp
		=09





------_=_NextPart_001_01C92ED3.697D51F3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just=20
executes the commands.&nbsp; If it is a response, then I would think it =
has to=20
look up the state indexed by trans id to clean it up, and to execute the =
join=20
which is in that state.&nbsp; So yes, it looks to me that both are=20
different.&nbsp; Also the processing of the trans id is =
different&nbsp;because=20
for requests it has to check whether it is each time incremented by 1, =
which it=20
does not have to do for responses.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> woensdag 15 oktober 2008=20
16:27<BR><B>To:</B> Francois Le Faucheur IMAP<BR><B>Cc:</B> DE CNODDER =
Stefaan;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Proposal for changing =
messages names=20
in Multicast Control Extensions<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<BLOCKQUOTE type=3D"cite">
  <DIV>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><FONT class=3DApple-style-span=20
      color=3D#006312><BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">If a message can be used as both a request =
and a=20
      reply, is the defitions<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">of the Transaction Identifier still =
accurate?=20
      &nbsp;Currently the draft says:<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">- trans id in request is linearly =
incrementing,=20
      and is per message type<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">- trans id in response is copied from=20
    request<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">If the same message type can be both =
request and=20
      response, then how will<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">the trans id behave? &nbsp;Should the =
receiver=20
      first try to find out whether<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">it is a request or a response, and then =
process it=20
      accordingly? &nbsp;Or how<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">should it then =
work?<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE><BR>Oops, there was a typo =
in earlier=20
  message. This should read:<BR>One option would be for the receiver to =
look at=20
  the Result field:<BR><SPAN class=3DApple-tab-span=20
  style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Success/Failure, =
then this=20
  message is a "response" to an earlier request (and its Transaction ID =
echoed=20
  the one of the request)<BR><SPAN class=3DApple-tab-span=20
  style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, then =
this messages=20
  is a "request" (and the transaction ID was generated by remote=20
end)</DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Note also that the AN may not even care that much whether it is a =
response=20
or a spontaneous request, because the two are idempotent.</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV>
<DIV><BR></DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV><BR><BR>
  <BLOCKQUOTE type=3D"cite">One option would be for the sender to look =
at the=20
    Result field:<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
    style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Success/Failure, =
then this=20
    message is a "response" to an earlier request (and its Transaction =
ID echoed=20
    the one of the request)<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
    style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, then =
this=20
    messages is a request (and the transaction ID was generated by =
remote=20
    end)<BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">regards,<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Stefaan<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">-----Original=20
  Message-----<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) [<A=20
      =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Sent: dinsdag 14 oktober 2008=20
  15:33<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER Stefaan; =
Wojciech=20
      Dec (wdec); Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Cc: <A=20
      =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages names=20
      in Multicast Control<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">Ok, just wanted to make sure what you=20
    meant.<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">So, this means a Multicast Replication =
Control=20
      Message would be used<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">both as a reply to an authorization as =
well as a=20
      directive. &nbsp;I tend to<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">agree with this, although, we might review =
that=20
      case when we define the<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">authorization message and if the reply =
from the=20
      server would carry<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">roughly the same information as the =
directive. I=20
      would assume it would.<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">-----Original=20
    Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
        =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 9:22=20
      AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); DE =
CNODDER=20
        Stefaan; Wojciech Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">(wdec); Sanjay=20
  Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Cc: <A=20
        =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
        names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Hi =
Phil,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see=20
      inline.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">-----Original=20
    Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) [<A=20
        =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 2:50=20
      PM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
        Wojciech Dec (wdec); =
Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Cc: <A=20
        =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
        names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">I'm ok with those=20
      renaming.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">[RM] =
Great<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Do you mean that when the ANCP client =
ask=20
          authorization for a=20
  Join,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">its request is a Multicast Replication =
Control=20
          Message and the =
reply<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">from the server is the same or=20
          =
different:____<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">[RM] not exactly, what I meant is =
slightly=20
        different: &nbsp;when an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">client asks for authorization to Join a=20
        multicast flow, it uses an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">message (not defined yet), while when =
the server=20
        replies to the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">authorization message sent by the client =
it=20
        could use a Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Replication Control=20
    Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">While if the server is=20
      sending<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">a directive to the ANCP client to have =
a port=20
          join a<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">multicast, do=20
  you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">mean this is also called Multicast =
Replication=20
          Control =
Message?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">[RM] yes this is current scenario where =
the=20
        server uses a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Replication Control Message to send a =
directive=20
        to the ANCP client to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">have a port join or leave a multicast=20
      flow.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Does it make=20
  sense?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Thanks,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">-----Original=20
      =
Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
          =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 7:46=20
        AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); 'DE =
CNODDER=20
          Stefaan'; Wojciech =
Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">(wdec); 'Sanjay=20
      Wadhwa'<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Subject: Proposal for changing =
messages names=20
          in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  =
type=3D"cite">Hello,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm currently =
merging=20
          draft-ancp-mc-extensions=20
  with<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">draft-ietf-ancp-protocol, and I am =
thinking it=20
          could be useful =
to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">simplify the terminology in terms of =
multicast=20
          message =
names.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">In particular I'd like to=20
        rename:<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">- Multicast Replication Control =
Request=20
          Message in just=20
  Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Replication Control=20
      Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">- Multicast Status Response Message =
and in=20
          Multicast Status=20
  Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">This change would allow re-using the =
same=20
          message type for=20
  different<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">purposes/use cases if needed in =
future,=20
          without affecting=20
  current<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  =
type=3D"cite">scenario.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Please let me know what's your opinion =
on this=20
          =
proposal.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Thanks and best=20
      regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQU=
OTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
      NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">This message and its attachments are =
addressed=20
          solely to the =
persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">above and may contain confidential=20
          information. If you have=20
  received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">the message in error, be informed that =
any use=20
          of the =
content<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">hereof =
is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately to=20
          the sender and delete=20
  the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions, please=20
          contact us by =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">to <A=20
          =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
        you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
          =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
          =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
  type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
  NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">This message and its attachments are =
addressed=20
        solely to the persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">above and may contain confidential =
information.=20
        If you have received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">the message in error, be informed that =
any use=20
        of the content hereof =
is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">prohibited. Please return it immediately =
to the=20
        sender and delete the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">message. Should you have any questions, =
please=20
        contact us by =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">to <A=20
        =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
    you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE=20
        =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
        =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE=20
    =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite">ANCP mailing =
list<BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><A=20
      =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
  <BLOCKQUOTE type=3D"cite">
    <BLOCKQUOTE type=3D"cite"><A=20
      =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></BLOCKQUOTE></BLOCKQUOTE>
  <BLOCKQUOTE=20
type=3D"cite"><BR></BLOCKQUOTE><BR></DIV></BLOCKQUOTE></DIV><BR></BODY></=
HTML>

------_=_NextPart_001_01C92ED3.697D51F3--

--===============0930166847==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0930166847==--


From ancp-bounces@ietf.org  Wed Oct 15 08:52:58 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8722328C12D;
	Wed, 15 Oct 2008 08:52:58 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F42028C12D
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 08:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 KMogbs0UDMSP for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 08:52:55 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id AD6533A677C
	for <ancp@ietf.org>; Wed, 15 Oct 2008 08:52:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,417,1220227200"; d="scan'208,217";a="22725597"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 15 Oct 2008 15:53:06 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9FFr6F9023098; 
	Wed, 15 Oct 2008 17:53:06 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9FFr3BE003767;
	Wed, 15 Oct 2008 15:53:06 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 17:53:03 +0200
Received: from [144.254.203.147] ([144.254.203.147]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 17:52:47 +0200
Message-Id: <87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 17:52:44 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 15 Oct 2008 15:52:47.0123 (UTC)
	FILETIME=[11B17630:01C92EDE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=43606; t=1224085986;
	x=1224949986; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=aZ+/eSeFE59rG6WJPZp2etYyvQF435+WQk2PGF15xgM=;
	b=O72vP2VxwQarWfF/hUpHrA6at+QSopP7FFT62MrOrqtX44JAUhMq+IqaOM
	KF4PtOn9+Wusi2dxCISndVFGkToTM9YuIOrA8+Mdjue4m3KAf4qGdRjJCp9x
	eWLpxcNTrs;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1587733014=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============1587733014==
Content-Type: multipart/alternative; boundary=Apple-Mail-4-965629223


--Apple-Mail-4-965629223
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi Stefaan,

On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:

>
> Francois,
>
> If it is a request, then the AN just executes the commands.  If it  
> is a response, then I would think it has to look up the state  
> indexed by trans id to clean it up, and to execute the join which is  
> in that state.

First, just to make sure we don't lose the first point: if the AN  
needs to know whether it is a request or a response, it could do so  
via the Result code.

Now regarding whether AN needs to know, that may be implementation  
dependent.
One model could be as you described above, in which case AN needs to  
know.
Another model could be where the AN operates in a simpler "Fire and  
Forget" mode:
	* AN sends admission request (and AN increments its Transaction ID  
value)
	* AN forgets about it (AN relies on TCP to make sure request reached  
NAS and relies on ANCP behavior to get a response)
	* when AN gets a Multicast Replication message, it just executes. A  
key assumption here is that the multicast replication control message  
contains all the information necessary for execution (eg "add channel  
C to port P")

Makes sense?

Francois


>   So yes, it looks to me that both are different.  Also the  
> processing of the trans id is different because for requests it has  
> to check whether it is each time incremented by 1, which it does not  
> have to do for responses.
>
> regards,
> Stefaan
>
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: woensdag 15 oktober 2008 16:27
> To: Francois Le Faucheur IMAP
> Cc: DE CNODDER Stefaan; ancp@ietf.org
> Subject: Re: [ANCP] Proposal for changing messages names in  
> Multicast Control Extensions
>
>>>>
>>>>
>>>> If a message can be used as both a request and a reply, is the  
>>>> defitions
>>>> of the Transaction Identifier still accurate?  Currently the  
>>>> draft says:
>>>>
>>>> - trans id in request is linearly incrementing, and is per  
>>>> message type
>>>> - trans id in response is copied from request
>>>>
>>>> If the same message type can be both request and response, then  
>>>> how will
>>>> the trans id behave?  Should the receiver first try to find out  
>>>> whether
>>>> it is a request or a response, and then process it accordingly?   
>>>> Or how
>>>> should it then work?
>>>
>>
>> Oops, there was a typo in earlier message. This should read:
>> One option would be for the receiver to look at the Result field:
>> * if it is set to Success/Failure, then this message is a  
>> "response" to an earlier request (and its Transaction ID echoed the  
>> one of the request)
>> * if it is set to Ack/Nack, then this messages is a "request" (and  
>> the transaction ID was generated by remote end)
>
> Note also that the AN may not even care that much whether it is a  
> response or a spontaneous request, because the two are idempotent.
>
> Francois
>
>
>>
>>
>>> One option would be for the sender to look at the Result field:
>>> * if it is set to Success/Failure, then this message is a  
>>> "response" to an earlier request (and its Transaction ID echoed  
>>> the one of the request)
>>> * if it is set to Ack/Nack, then this messages is a request (and  
>>> the transaction ID was generated by remote end)
>>>
>>>>
>>>>
>>>> regards,
>>>> Stefaan
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>> Sent: dinsdag 14 oktober 2008 15:33
>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>> Sanjay
>>>> Wadhwa
>>>> Cc: ancp@ietf.org
>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>> Control
>>>> Extensions
>>>>
>>>>
>>>> Ok, just wanted to make sure what you meant.
>>>>
>>>> So, this means a Multicast Replication Control Message would be  
>>>> used
>>>> both as a reply to an authorization as well as a directive.  I  
>>>> tend to
>>>> agree with this, although, we might review that case when we  
>>>> define the
>>>> authorization message and if the reply from the server would carry
>>>> roughly the same information as the directive. I would assume it  
>>>> would.
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>>> Sent: Tuesday, October 14, 2008 9:22 AM
>>>>> To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec
>>>>> (wdec); Sanjay Wadhwa
>>>>> Cc: ancp@ietf.org
>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>> Control
>>>>> Extensions
>>>>>
>>>>> Hi Phil,
>>>>>     please see inline.
>>>>>
>>>>> Regards,
>>>>> Roberta
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>>> Sent: Tuesday, October 14, 2008 2:50 PM
>>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>>> Sanjay
>>>>> Wadhwa
>>>>> Cc: ancp@ietf.org
>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>> Control
>>>>> Extensions
>>>>>
>>>>>
>>>>>> I'm ok with those renaming.
>>>>> [RM] Great
>>>>>
>>>>>> Do you mean that when the ANCP client ask authorization for a  
>>>>>> Join,
>>>>>> its request is a Multicast Replication Control Message and the  
>>>>>> reply
>>>>>> from the server is the same or different:____
>>>>>
>>>>> [RM] not exactly, what I meant is slightly different:  when an  
>>>>> ANCP
>>>>> client asks for authorization to Join a multicast flow, it uses  
>>>>> an ANCP
>>>>
>>>>> message (not defined yet), while when the server replies to the
>>>>> authorization message sent by the client it could use a Multicast
>>>>> Replication Control Message
>>>>>
>>>>>> While if the server is sending
>>>>>> a directive to the ANCP client to have a port join a
>>>>> multicast, do you
>>>>>> mean this is also called Multicast Replication Control Message?
>>>>>
>>>>> [RM] yes this is current scenario where the server uses a  
>>>>> Multicast
>>>>> Replication Control Message to send a directive to the ANCP  
>>>>> client to
>>>>> have a port join or leave a multicast flow.
>>>>> Does it make sense?
>>>>>
>>>>> Thanks,
>>>>> Roberta
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>>>> Sent: Tuesday, October 14, 2008 7:46 AM
>>>>>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan'; Wojciech  
>>>>>> Dec
>>>>>> (wdec); 'Sanjay Wadhwa'
>>>>>> Subject: Proposal for changing messages names in Multicast  
>>>>>> Control
>>>>>> Extensions
>>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>     I'm currently merging draft-ancp-mc-extensions with
>>>>>> draft-ietf-ancp-protocol, and I am thinking it could be useful to
>>>>>> simplify the terminology in terms of multicast message names.
>>>>>> In particular I'd like to rename:
>>>>>> - Multicast Replication Control Request Message in just Multicast
>>>>>> Replication Control Message
>>>>>> - Multicast Status Response Message and in Multicast Status  
>>>>>> Message
>>>>>>
>>>>>> This change would allow re-using the same message type for  
>>>>>> different
>>>>>> purposes/use cases if needed in future, without affecting current
>>>>>> scenario.
>>>>>>
>>>>>> Please let me know what's your opinion on this proposal.
>>>>>>
>>>>>> Thanks and best regards,
>>>>>>
>>>>>> Roberta
>>>>>>
>>>>>>
>>>>>> CONFIDENTIALITY NOTICE
>>>>>>
>>>>>> This message and its attachments are addressed solely to the  
>>>>>> persons
>>>>>> above and may contain confidential information. If you have  
>>>>>> received
>>>>>> the message in error, be informed that any use of the content
>>>>> hereof is
>>>>>> prohibited. Please return it immediately to the sender and  
>>>>>> delete the
>>>>>> message. Should you have any questions, please contact us by  
>>>>>> replying
>>>>>> to webmaster@telecomitalia.it.
>>>>>>
>>>>>>     Thank you
>>>>>>
>>>>>>                                     www.telecomitalia.it
>>>>>>
>>>>>
>>>>>
>>>>> CONFIDENTIALITY NOTICE
>>>>>
>>>>> This message and its attachments are addressed solely to the  
>>>>> persons
>>>>> above and may contain confidential information. If you have  
>>>>> received
>>>>> the message in error, be informed that any use of the content  
>>>>> hereof is
>>>>
>>>>> prohibited. Please return it immediately to the sender and  
>>>>> delete the
>>>>> message. Should you have any questions, please contact us by  
>>>>> replying
>>>>> to webmaster@telecomitalia.it.
>>>>>
>>>>>     Thank you
>>>>>
>>>>>                                     www.telecomitalia.it
>>>>>
>>>> _______________________________________________
>>>> ANCP mailing list
>>>> ANCP@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ancp
>>>
>>
>


--Apple-Mail-4-965629223
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi =
Stefaan,<div><br><div><div>On 15 Oct 2008, at 16:36, DE CNODDER Stefaan =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"> <div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font>&nbsp;</div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"503243114-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Francois,</font></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just executes the commands.&nbsp; If it is a response, then I =
would think it has to look up the state indexed by trans id to clean it =
up, and to execute the join which is in that =
state.</font></span></div></div></blockquote><div><br></div><div>First, =
just to make sure we don't lose the first point: if the AN needs to know =
whether it is a request or a response, it could do so via the Result =
code.</div><div><br></div><div>Now regarding whether AN needs to know, =
that may be implementation dependent.</div><div>One model could be as =
you described above, in which case AN needs to know.</div><div>Another =
model could be where the AN operates in a simpler "Fire and Forget" =
mode:</div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>* AN sends admission request (and AN increments its Transaction =
ID value)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* AN forgets about it (AN relies =
on TCP to make sure request reached NAS and relies on ANCP behavior to =
get a response)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* when AN gets a Multicast =
Replication message, it just executes. A key assumption here is that the =
multicast replication control message contains all the information =
necessary for execution&nbsp;(eg "add channel C to port =
P")</div><div><br></div><div>Makes =
sense?</div><div><br></div><div>Francois</div><div><br></div><br><blockquo=
te type=3D"cite"><div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space"><div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">&nbsp; So yes, it looks to me that both are =
different.&nbsp; Also the processing of the trans id is =
different&nbsp;because for requests it has to check whether it is each =
time incremented by 1, which it does not have to do for =
responses.</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"503243114-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">regards,</font></span></div> <div dir=3D"ltr"=
 align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Stefaan</font></span></div><br> <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
<hr tabindex=3D"-1"> <font face=3D"Tahoma" size=3D"2"><b>From:</b> =
Francois Le Faucheur IMAP [<a =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</a>] =
<br><b>Sent:</b> woensdag 15 oktober 2008 16:27<br><b>To:</b> Francois =
Le Faucheur IMAP<br><b>Cc:</b> DE CNODDER Stefaan; <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br><b>Subject:</b> Re: =
[ANCP] Proposal for changing messages names in Multicast Control =
Extensions<br></font><br></div> <div></div> <div> <blockquote =
type=3D"cite">  <div>  <blockquote type=3D"cite">    <blockquote =
type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#006312"><br></font><br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">If a message can be used as =
both a request and a       reply, is the =
defitions<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">of the Transaction Identifier still accurate?  =
     &nbsp;Currently the draft says:<br></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote =
type=3D"cite"><br></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">- trans id in request is linearly =
incrementing,       and is per message =
type<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">- trans id in response is copied from     =
request<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite"><br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">If the same message type can =
be both request and       response, then how =
will<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">the trans id behave? &nbsp;Should the receiver =
      first try to find out whether<br></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">it is a request =
or a response, and then process it       accordingly? &nbsp;Or =
how<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">should it then =
work?<br></blockquote></blockquote>  <blockquote =
type=3D"cite"><br></blockquote><br>Oops, there was a typo in earlier   =
message. This should read:<br>One option would be for the receiver to =
look at   the Result field:<br><span class=3D"Apple-tab-span" =
style=3D"WHITE-SPACE: pre"></span>* if it is set to Success/Failure, =
then this   message is a "response" to an earlier request (and its =
Transaction ID echoed   the one of the request)<br><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Ack/Nack, then this messages   is a "request" (and the =
transaction ID was generated by remote end)</div></blockquote> =
<div><br></div> <div>Note also that the AN may not even care that much =
whether it is a response or a spontaneous request, because the two are =
idempotent.</div> <div><br></div> <div>Francois</div> =
<div><br></div><br> <blockquote type=3D"cite">  <div><br><br>  =
<blockquote type=3D"cite">One option would be for the sender to look at =
the     Result field:<br></blockquote>  <blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Success/Failure, then this     message is a "response" to an =
earlier request (and its Transaction ID echoed     the one of the =
request)<br></blockquote>  <blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Ack/Nack, then this     messages is a request (and the =
transaction ID was generated by remote     end)<br></blockquote>  =
<blockquote type=3D"cite"><br></blockquote>  <blockquote type=3D"cite">  =
  <blockquote type=3D"cite"><br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite"><br></blockquote></blockquote>=
  <blockquote type=3D"cite">    <blockquote =
type=3D"cite">regards,<br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote =
type=3D"cite">Stefaan<br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite"><br></blockquote></blockquote>=
  <blockquote type=3D"cite">    <blockquote =
type=3D"cite"><br></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">-----Original   =
Message-----<br></blockquote></blockquote>  <blockquote type=3D"cite">   =
 <blockquote type=3D"cite">From: Philippe Champagne (pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote>  <blockquote type=3D"cite">    <blockquote =
type=3D"cite">Sent: dinsdag 14 oktober 2008   =
15:33<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">To: Maglione Roberta; DE CNODDER Stefaan; =
Wojciech       Dec (wdec); Sanjay<br></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te>  <blockquote type=3D"cite">    <blockquote type=3D"cite">Subject: =
RE: Proposal for changing messages names       in Multicast =
Control<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">Extensions<br></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote =
type=3D"cite"><br></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite"><br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">Ok, just wanted to make sure =
what you     meant.<br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite"><br></blockquote></blockquote>=
  <blockquote type=3D"cite">    <blockquote type=3D"cite">So, this means =
a Multicast Replication Control       Message would be =
used<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">both as a reply to an authorization as well as =
a       directive. &nbsp;I tend to<br></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">agree with this, =
although, we might review that       case when we define =
the<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">authorization message and if the reply from =
the       server would carry<br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">roughly the same information =
as the directive. I       would assume it =
would.<br></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite"><br></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite"><br></blockquote></blockquote>=
  <blockquote type=3D"cite">    <blockquote =
type=3D"cite"><br></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">-----Original=
     Message-----<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">From: Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">Sent: Tuesday, October 14, 2008 9:22       =
AM<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">To: =
Philippe Champagne (pchamp); DE CNODDER         Stefaan; Wojciech =
Dec<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">=
    <blockquote type=3D"cite">      <blockquote type=3D"cite">(wdec); =
Sanjay   Wadhwa<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote>  <blockquote type=3D"cite">    <blockquote type=3D"cite">=
      <blockquote type=3D"cite">Subject: RE: Proposal for changing =
messages         names in Multicast =
Control<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">Hi =
Phil,<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see       =
inline.<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Regards,<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">-----Original     =
Message-----<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">From: Philippe Champagne (pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">Sent: Tuesday, =
October 14, 2008 2:50       =
PM<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">To: =
Maglione Roberta; DE CNODDER Stefaan;         Wojciech Dec (wdec); =
Sanjay<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote>  <blockquote type=3D"cite">    <blockquote type=3D"cite">=
      <blockquote type=3D"cite">Subject: RE: Proposal for changing =
messages         names in Multicast =
Control<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">I'm ok with =
those       =
renaming.<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">[RM] =
Great<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">Do you mean that when =
the ANCP client ask           authorization for a   =
Join,<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">its request =
is a Multicast Replication Control           Message and the =
reply<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">from the =
server is the same or           =
different:____<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">[RM] not exactly, what I meant is slightly     =
    different: &nbsp;when an =
ANCP<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">client asks for authorization to Join a         multicast =
flow, it uses an ANCP<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote =
type=3D"cite"><br></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">message =
(not defined yet), while when the server         replies to =
the<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">=
    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">authorization message sent by the client it         could =
use a Multicast<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Replication Control     =
Message<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">While if the server is   =
    sending<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">a directive =
to the ANCP client to have a port           join =
a<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">multicast, do   =
you<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">=
    <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">mean this is also called Multicast Replication =
          Control =
Message?<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">[RM] yes this is current scenario where the    =
     server uses a Multicast<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">Replication Control Message to send a =
directive         to the ANCP client =
to<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">have a port =
join or leave a multicast       =
flow.<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Does it make   =
sense?<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Thanks,<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">-----Original =
      =
Message-----<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">From: =
Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote></blockquo=
te>  <blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">Sent: =
Tuesday, October 14, 2008 7:46         =
AM<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">To: Philippe Champagne =
(pchamp); 'DE CNODDER           Stefaan'; Wojciech =
Dec<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">(wdec); 'Sanjay       =
Wadhwa'<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">Subject: =
Proposal for changing messages names           in Multicast =
Control<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote></block=
quote>  <blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">Hello,<br></blockquote></blockquote></blockquote></blockquot=
e>  <blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm currently merging           =
draft-ancp-mc-extensions   =
with<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">draft-ietf-ancp-protocol, and I am thinking it           =
could be useful =
to<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">simplify the terminology =
in terms of multicast           message =
names.<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">In =
particular I'd like to         =
rename:<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">- Multicast =
Replication Control Request           Message in just   =
Multicast<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">Replication =
Control       =
Message<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">- Multicast =
Status Response Message and in           Multicast Status   =
Message<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">This change =
would allow re-using the same           message type for   =
different<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">purposes/use =
cases if needed in future,           without affecting   =
current<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">scenario.<br></blockquote></blockquote></blockquote></blockq=
uote>  <blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">Please let =
me know what's your opinion on this           =
proposal.<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">Thanks and =
best       =
regards,<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote></blockquo=
te>  <blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">CONFIDENTIALITY       =
NOTICE<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">This message =
and its attachments are addressed           solely to the =
persons<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">above and =
may contain confidential           information. If you have   =
received<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">the message =
in error, be informed that any use           of the =
content<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">hereof =
is<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">prohibited. Please return it immediately to    =
       the sender and delete   =
the<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">message. Should you have =
any questions, please           contact us by =
replying<br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank         =
you<br></blockquote></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">  =
  <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">CONFIDENTIALITY   =
NOTICE<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">This message and its attachments are addressed         =
solely to the persons<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">above and may contain confidential =
information.         If you have =
received<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">the message in error, be informed that any use         of =
the content hereof is<br></blockquote></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote =
type=3D"cite"><br></blockquote></blockquote>  <blockquote type=3D"cite"> =
   <blockquote type=3D"cite">      <blockquote type=3D"cite">prohibited. =
Please return it immediately to the         sender and delete =
the<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">=
    <blockquote type=3D"cite">      <blockquote type=3D"cite">message. =
Should you have any questions, please         contact us by =
replying<br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">  =
  <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank     =
you<br></blockquote></blockquote></blockquote>  <blockquote type=3D"cite">=
    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote>  <blockquote type=3D"cite">    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>  <blockquote =
type=3D"cite">    <blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote>  <blockquote type=3D"cite">    <blockquote =
type=3D"cite">ANCP mailing list<br></blockquote></blockquote>  =
<blockquote type=3D"cite">    <blockquote type=3D"cite"><a =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br></blockquote></blockquo=
te>  <blockquote type=3D"cite">    <blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><br></blockquote></blockquote>  <blockquote =
type=3D"cite"><br></blockquote><br></div></blockquote></div><br></div></bl=
ockquote></div><br></div></body></html>=

--Apple-Mail-4-965629223--

--===============1587733014==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1587733014==--


From ancp-bounces@ietf.org  Wed Oct 15 09:08:10 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3A8D28C221;
	Wed, 15 Oct 2008 09:08:10 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A0F928C12D
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 09:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001]
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 ZLNoPiwCCTKL for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 09:08:08 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id 57EB63A69A0
	for <ancp@ietf.org>; Wed, 15 Oct 2008 09:08:07 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9FG8Han025712; 
	Wed, 15 Oct 2008 18:08:18 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Wed, 15 Oct 2008 18:08:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 18:08:16 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Proposal for changing messages names in Multicast Control
	Extensions
Thread-Index: Acku3iiQeeF3YCFMRlmGxyfeKRb1yQAANpfA
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
	<87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
X-OriginalArrivalTime: 15 Oct 2008 16:08:17.0679 (UTC)
	FILETIME=[3C5909F0:01C92EE0]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2108493318=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2108493318==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92EE0.3BF9B19E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92EE0.3BF9B19E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
About the "fire and forget".  I like it a lot because of its simplicity
but it has an issue:
=20
1) user sends join matching grey list
2) AN sends admission request to NAS and forgets about it
3) user sends leave, which is not doing anything since the NAS has not
replied yet
4) AN receives possitive answer to join the stream
=20
In this case the multicast flow is replicated to the line although the
user had sent a leave.
=20
First processing the Result field without knowing what the message is
about looks to me like a strange way of processing, but it works.
However, just using a different message type would make it easier
according to me.  No need to repeat all commands or even no need to
repeat the port id, so not much re-use anyhow.
=20
If the "fire and forget" method would work, there is not really a
response, and the current message as defined today is sufficient, but in
the above case I have some doubts.
=20
regards,
Stefaan

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: woensdag 15 oktober 2008 17:53
To: DE CNODDER Stefaan
Cc: Francois Le Faucheur IMAP; ancp@ietf.org; Philippe (pchamp)
Champagne
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
Control Extensions


Hi Stefaan,=20

On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:


	=20
	Francois,
	=20
	If it is a request, then the AN just executes the commands.  If
it is a response, then I would think it has to look up the state indexed
by trans id to clean it up, and to execute the join which is in that
state.


First, just to make sure we don't lose the first point: if the AN needs
to know whether it is a request or a response, it could do so via the
Result code.

Now regarding whether AN needs to know, that may be implementation
dependent.
One model could be as you described above, in which case AN needs to
know.
Another model could be where the AN operates in a simpler "Fire and
Forget" mode:
* AN sends admission request (and AN increments its Transaction ID
value)
* AN forgets about it (AN relies on TCP to make sure request reached NAS
and relies on ANCP behavior to get a response)
* when AN gets a Multicast Replication message, it just executes. A key
assumption here is that the multicast replication control message
contains all the information necessary for execution (eg "add channel C
to port P")

Makes sense?

Francois



	  So yes, it looks to me that both are different.  Also the
processing of the trans id is different because for requests it has to
check whether it is each time incremented by 1, which it does not have
to do for responses.
	=20
	regards,
	Stefaan

________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: woensdag 15 oktober 2008 16:27
	To: Francois Le Faucheur IMAP
	Cc: DE CNODDER Stefaan; ancp@ietf.org
	Subject: Re: [ANCP] Proposal for changing messages names in
Multicast Control Extensions
=09
=09

			=09
			=09
			=09

				If a message can be used as both a
request and a reply, is the defitions
			=09

				of the Transaction Identifier still
accurate?  Currently the draft says:
			=09


				- trans id in request is linearly
incrementing, and is per message type
			=09

				- trans id in response is copied from
request
			=09


				If the same message type can be both
request and response, then how will
			=09

				the trans id behave?  Should the
receiver first try to find out whether
			=09

				it is a request or a response, and then
process it accordingly?  Or how
			=09

				should it then work?
			=09



		Oops, there was a typo in earlier message. This should
read:
		One option would be for the receiver to look at the
Result field:
		* if it is set to Success/Failure, then this message is
a "response" to an earlier request (and its Transaction ID echoed the
one of the request)
		* if it is set to Ack/Nack, then this messages is a
"request" (and the transaction ID was generated by remote end)


	Note also that the AN may not even care that much whether it is
a response or a spontaneous request, because the two are idempotent.

	Francois





			One option would be for the sender to look at
the Result field:
		=09

			* if it is set to Success/Failure, then this
message is a "response" to an earlier request (and its Transaction ID
echoed the one of the request)
		=09

			* if it is set to Ack/Nack, then this messages
is a request (and the transaction ID was generated by remote end)
		=09




				regards,
			=09

				Stefaan
			=09



				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: dinsdag 14 oktober 2008 15:33
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				Ok, just wanted to make sure what you
meant.
			=09


				So, this means a Multicast Replication
Control Message would be used
			=09

				both as a reply to an authorization as
well as a directive.  I tend to
			=09

				agree with this, although, we might
review that case when we define the
			=09

				authorization message and if the reply
from the server would carry
			=09

				roughly the same information as the
directive. I would assume it would.
			=09




				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 9:22 AM
			=09

				To: Philippe Champagne (pchamp); DE
CNODDER Stefaan; Wojciech Dec
			=09

				(wdec); Sanjay Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09


				Hi Phil,
			=09

				    please see inline.
			=09


				Regards,
			=09

				Roberta
			=09


				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: Tuesday, October 14, 2008 2:50 PM
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				I'm ok with those renaming.
			=09

				[RM] Great
			=09


				Do you mean that when the ANCP client
ask authorization for a Join,
			=09

				its request is a Multicast Replication
Control Message and the reply
			=09

				from the server is the same or
different:____
			=09


				[RM] not exactly, what I meant is
slightly different:  when an ANCP
			=09

				client asks for authorization to Join a
multicast flow, it uses an ANCP
			=09


				message (not defined yet), while when
the server replies to the
			=09

				authorization message sent by the client
it could use a Multicast
			=09

				Replication Control Message
			=09


				While if the server is sending
			=09

				a directive to the ANCP client to have a
port join a
			=09

				multicast, do you
			=09

				mean this is also called Multicast
Replication Control Message?
			=09


				[RM] yes this is current scenario where
the server uses a Multicast
			=09

				Replication Control Message to send a
directive to the ANCP client to
			=09

				have a port join or leave a multicast
flow.
			=09

				Does it make sense?
			=09


				Thanks,
			=09

				Roberta
			=09





				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 7:46 AM
			=09

				To: Philippe Champagne (pchamp); 'DE
CNODDER Stefaan'; Wojciech Dec
			=09

				(wdec); 'Sanjay Wadhwa'
			=09

				Subject: Proposal for changing messages
names in Multicast Control
			=09

				Extensions
			=09



				Hello,
			=09

				    I'm currently merging
draft-ancp-mc-extensions with
			=09

				draft-ietf-ancp-protocol, and I am
thinking it could be useful to
			=09

				simplify the terminology in terms of
multicast message names.
			=09

				In particular I'd like to rename:
			=09

				- Multicast Replication Control Request
Message in just Multicast
			=09

				Replication Control Message
			=09

				- Multicast Status Response Message and
in Multicast Status Message
			=09


				This change would allow re-using the
same message type for different
			=09

				purposes/use cases if needed in future,
without affecting current
			=09

				scenario.
			=09


				Please let me know what's your opinion
on this proposal.
			=09


				Thanks and best regards,
			=09


				Roberta
			=09



				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content
			=09

				hereof is
			=09

				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09




				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content hereof is
			=09


				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09


=09
_______________________________________________
			=09

				ANCP mailing list
			=09

				ANCP@ietf.org
			=09

=09
https://www.ietf.org/mailman/listinfo/ancp
			=09






------_=_NextPart_001_01C92EE0.3BF9B19E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>About the "fire and forget".&nbsp; I like it a =
lot because=20
of its simplicity but it has an issue:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>1) user sends join matching grey =
list</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>2) AN sends admission request to NAS and =
forgets about=20
it</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>3) user sends leave, which is not doing =
anything since the=20
NAS has not replied yet</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>4) AN receives possitive answer to join the=20
stream</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In this case the multicast flow is replicated =
to the line=20
although the user had sent a leave.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>First processing the Result field without =
knowing what the=20
message is about looks to me like a strange way of processing, but it=20
works.&nbsp; However, just using a different message type would make it =
easier=20
according to me.&nbsp; No need to repeat all commands or even no need to =
repeat=20
the port id, so not much re-use anyhow.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If the "fire and forget" method would work, =
there is not=20
really a response, and the current message as defined today is =
sufficient, but=20
in the above case I have some doubts.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> woensdag 15 oktober 2008=20
17:53<BR><B>To:</B> DE CNODDER Stefaan<BR><B>Cc:</B> Francois Le =
Faucheur IMAP;=20
ancp@ietf.org; Philippe (pchamp) Champagne<BR><B>Subject:</B> Re: [ANCP] =

Proposal for changing messages names in Multicast Control=20
Extensions<BR></FONT><BR></DIV>
<DIV></DIV>Hi Stefaan,
<DIV><BR>
<DIV>
<DIV>On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just=20
  executes the commands.&nbsp; If it is a response, then I would think =
it has to=20
  look up the state indexed by trans id to clean it up, and to execute =
the join=20
  which is in that state.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>First, just to make sure we don't lose the first point: if the AN =
needs to=20
know whether it is a request or a response, it could do so via the =
Result=20
code.</DIV>
<DIV><BR></DIV>
<DIV>Now regarding whether AN needs to know, that may be implementation=20
dependent.</DIV>
<DIV>One model could be as you described above, in which case AN needs =
to=20
know.</DIV>
<DIV>Another model could be where the AN operates in a simpler "Fire and =
Forget"=20
mode:</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* AN =
sends=20
admission request (and AN increments its Transaction ID value)</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* AN =
forgets=20
about it (AN relies on TCP to make sure request reached NAS and relies =
on ANCP=20
behavior to get a response)</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
when AN gets a=20
Multicast Replication message, it just executes. A key assumption here =
is that=20
the multicast replication control message contains all the information =
necessary=20
for execution&nbsp;(eg "add channel C to port P")</DIV>
<DIV><BR></DIV>
<DIV>Makes sense?</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV>
<DIV><BR></DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp; So yes, it looks to me that both are=20
  different.&nbsp; Also the processing of the trans id is =
different&nbsp;because=20
  for requests it has to check whether it is each time incremented by 1, =
which=20
  it does not have to do for responses.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A=20
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
  <BR><B>Sent:</B> woensdag 15 oktober 2008 16:27<BR><B>To:</B> Francois =
Le=20
  Faucheur IMAP<BR><B>Cc:</B> DE CNODDER Stefaan; <A=20
  href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> Re: =
[ANCP]=20
  Proposal for changing messages names in Multicast Control=20
  Extensions<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><FONT class=3DApple-style-span=20
        color=3D#006312><BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">If a message can be used as both a =
request and a=20
        reply, is the defitions<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">of the Transaction Identifier still =
accurate?=20
        &nbsp;Currently the draft says:<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">- trans id in request is linearly =
incrementing,=20
        and is per message type<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">- trans id in response is copied from=20
      request<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">If the same message type can be both =
request and=20
        response, then how will<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">the trans id behave? &nbsp;Should the =
receiver=20
        first try to find out whether<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">it is a request or a response, and then =
process=20
        it accordingly? &nbsp;Or how<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">should it then =
work?<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE><BR>Oops, there was a =
typo in=20
    earlier message. This should read:<BR>One option would be for the =
receiver=20
    to look at the Result field:<BR><SPAN class=3DApple-tab-span=20
    style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Success/Failure, =
then this=20
    message is a "response" to an earlier request (and its Transaction =
ID echoed=20
    the one of the request)<BR><SPAN class=3DApple-tab-span=20
    style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, then =
this=20
    messages is a "request" (and the transaction ID was generated by =
remote=20
    end)</DIV></BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>Note also that the AN may not even care that much whether it is a =

  response or a spontaneous request, because the two are =
idempotent.</DIV>
  <DIV><BR></DIV>
  <DIV>Francois</DIV>
  <DIV><BR></DIV><BR>
  <BLOCKQUOTE type=3D"cite">
    <DIV><BR><BR>
    <BLOCKQUOTE type=3D"cite">One option would be for the sender to look =
at the=20
      Result field:<BR></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
      style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure, then=20
      this message is a "response" to an earlier request (and its =
Transaction ID=20
      echoed the one of the request)<BR></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
      style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, then =
this=20
      messages is a request (and the transaction ID was generated by =
remote=20
      end)<BR></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">regards,<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Stefaan<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">-----Original=20
    Message-----<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) [<A=20
        =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Sent: dinsdag 14 oktober 2008=20
      15:33<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
        Wojciech Dec (wdec); Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Cc: <A=20
        =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
        names in Multicast Control<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">Ok, just wanted to make sure what you=20
      meant.<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">So, this means a Multicast Replication =
Control=20
        Message would be used<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">both as a reply to an authorization as =
well as a=20
        directive. &nbsp;I tend to<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">agree with this, although, we might =
review that=20
        case when we define the<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">authorization message and if the reply =
from the=20
        server would carry<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">roughly the same information as the =
directive. I=20
        would assume it would.<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">-----Original=20
      Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
          =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 9:22=20
        AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); DE =
CNODDER=20
          Stefaan; Wojciech =
Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">(wdec); Sanjay=20
    Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Cc: <A=20
          =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
          names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Hi =
Phil,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see=20
        inline.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite">Regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">-----Original=20
      Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) [<A=20
          =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 2:50=20
        PM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
          Wojciech Dec (wdec); =
Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Cc: <A=20
          =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
          names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">I'm ok with those=20
        =
renaming.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">[RM]=20
Great<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Do you mean that when the ANCP =
client ask=20
            authorization for a=20
    Join,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">its request is a Multicast =
Replication=20
            Control Message and the=20
    reply<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">from the server is the same or=20
            =
different:____<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">[RM] not exactly, what I meant is =
slightly=20
          different: &nbsp;when an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">client asks for authorization to Join =
a=20
          multicast flow, it uses an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">message (not defined yet), while when =
the=20
          server replies to =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">authorization message sent by the =
client it=20
          could use a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Replication Control=20
      Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">While if the server is=20
        sending<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">a directive to the ANCP client to =
have a=20
            port join =
a<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">multicast, do=20
    you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">mean this is also called Multicast=20
            Replication Control=20
    Message?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">[RM] yes this is current scenario =
where the=20
          server uses a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Replication Control Message to send a=20
          directive to the ANCP client =
to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">have a port join or leave a multicast=20
        flow.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Does it make=20
    sense?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite">Thanks,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">-----Original=20
        =
Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
            =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 7:46 =

          AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); 'DE =
CNODDER=20
            Stefaan'; Wojciech=20
    Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">(wdec); 'Sanjay=20
        Wadhwa'<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Subject: Proposal for changing =
messages=20
            names in Multicast=20
    Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
      =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite">Hello,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm =
currently=20
            merging draft-ancp-mc-extensions=20
      with<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">draft-ietf-ancp-protocol, and I am =
thinking=20
            it could be useful=20
to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">simplify the terminology in terms of =

            multicast message=20
    names.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">In particular I'd like to=20
          =
rename:<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">- Multicast Replication Control =
Request=20
            Message in just=20
    Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Replication Control=20
        Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">- Multicast Status Response Message =
and in=20
            Multicast Status=20
    Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">This change would allow re-using the =
same=20
            message type for=20
    different<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">purposes/use cases if needed in =
future,=20
            without affecting=20
    current<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
      =
type=3D"cite">scenario.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Please let me know what's your =
opinion on=20
            this =
proposal.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Thanks and best=20
        regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQU=
OTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
        NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">This message and its attachments are =

            addressed solely to the=20
    persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">above and may contain confidential=20
            information. If you have=20
      received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">the message in error, be informed =
that any=20
            use of the =
content<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">hereof =
is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately to=20
            the sender and delete=20
    the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions,=20
            please contact us by=20
    replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">to <A=20
            =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
          you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
            =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
            =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
      NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">This message and its attachments are =
addressed=20
          solely to the =
persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">above and may contain confidential=20
          information. If you have =
received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">the message in error, be informed that =
any use=20
          of the content hereof =
is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately to=20
          the sender and delete =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions, please=20
          contact us by =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">to <A=20
          =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
        you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
          =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
          =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE=20
        =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite">ANCP mailing =
list<BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><A=20
        =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
    <BLOCKQUOTE type=3D"cite">
      <BLOCKQUOTE type=3D"cite"><A=20
        =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></BLOCKQUOTE></BLOCKQUOTE>
    <BLOCKQUOTE=20
  =
type=3D"cite"><BR></BLOCKQUOTE><BR></DIV></BLOCKQUOTE></DIV><BR></DIV></B=
LOCKQUOTE></DIV><BR></DIV></BODY></HTML>

------_=_NextPart_001_01C92EE0.3BF9B19E--

--===============2108493318==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============2108493318==--


From ancp-bounces@ietf.org  Wed Oct 15 11:07:45 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E77F3A69A7;
	Wed, 15 Oct 2008 11:07:45 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 330A03A67FA
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 11:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 RAwArkJG4A6i for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 11:07:41 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id B042D3A67EF
	for <ancp@ietf.org>; Wed, 15 Oct 2008 11:07:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,417,1220227200"; d="scan'208,217";a="91400352"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 15 Oct 2008 18:08:10 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9FI8Ab0031952; 
	Wed, 15 Oct 2008 11:08:10 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9FI8AYI023262;
	Wed, 15 Oct 2008 18:08:10 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 11:08:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 11:08:09 -0700
Message-ID: <48214755113BB04F84D958B4F0DE261C069350E2@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Proposal for changing messages names in Multicast Control
	Extensions
Thread-Index: Acku3iiQeeF3YCFMRlmGxyfeKRb1yQAANpfAAAQM6CA=
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
	<87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Philippe Champagne (pchamp)" <pchamp@cisco.com>
To: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>,
	"Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 15 Oct 2008 18:08:10.0636 (UTC)
	FILETIME=[FBAF2CC0:01C92EF0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=58311; t=1224094090;
	x=1224958090; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pchamp@cisco.com;
	z=From:=20=22Philippe=20Champagne=20(pchamp)=22=20<pchamp@ci
	sco.com>
	|Subject:=20RE=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=FcmiRNPkSSP58Kgn4K297e1YFgnVow8oEL+Rsy+3Q3Q=;
	b=sVhkk2QkEojf/wCaKyx2JJ7EJi8SToLWtUIkmq4F39QczZKVXakB1r+JW2
	uG7irIcaDIobfbRmHtGNLDRm7zd+kilTYnPJA5YM2FYaO/DWraDko+yC2mOC
	dgeKQUc93Z;
Authentication-Results: sj-dkim-2; header.From=pchamp@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0837082615=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0837082615==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92EF0.FB75BE05"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92EF0.FB75BE05
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Stefaan
=20
I think it could go this way:
=20
Either the AN also sends the Leave to the NAS - which will be processed
serially by the NAS after the Join, and the NAS therefore will reply for
the leave shortly after. In this case, the AN gets a leave.
or
The AN does not sends the Leave to the NAS but holds it for a specific
time (the time we should expect such join from the server).=20
=20
For the fire and forget, I personally prefer the first option, I mean,
if we have to have the AN holding info, might as well be the whole thing
where it knows also about the JOIN sent shortly before for which it is
awaiting a response.
=20
The question is then, which way to go?  Can we allow "fire and forget"
and "remember the states" to both be used at the discretion of the
implementor of the ANCP client or do we force one way to go. =20
It depends if the ANCP server needs to know about bandwidth usage for
bandwidth requirement decision, in which case, it would need to know
about Leave as well, isn't it?   Can that behavior (bandwith decision)
be configurable, allowing "remember the states" (where Leaves are not
necessarily forwarded) to exist in other deployment model?
=20
=20


________________________________

	From: DE CNODDER Stefaan
[mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
	Sent: Wednesday, October 15, 2008 12:08 PM
	To: Francois Le Faucheur (flefauch)
	Cc: ancp@ietf.org; Philippe Champagne (pchamp)
	Subject: RE: [ANCP] Proposal for changing messages names in
Multicast Control Extensions
=09
=09
	=20
	About the "fire and forget".  I like it a lot because of its
simplicity but it has an issue:
	=20
	1) user sends join matching grey list
	2) AN sends admission request to NAS and forgets about it
	3) user sends leave, which is not doing anything since the NAS
has not replied yet
	4) AN receives possitive answer to join the stream
	=20
	In this case the multicast flow is replicated to the line
although the user had sent a leave.
	=20
	First processing the Result field without knowing what the
message is about looks to me like a strange way of processing, but it
works.  However, just using a different message type would make it
easier according to me.  No need to repeat all commands or even no need
to repeat the port id, so not much re-use anyhow.
	=20
	If the "fire and forget" method would work, there is not really
a response, and the current message as defined today is sufficient, but
in the above case I have some doubts.
	=20
	regards,
	Stefaan

________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: woensdag 15 oktober 2008 17:53
	To: DE CNODDER Stefaan
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org; Philippe (pchamp)
Champagne
	Subject: Re: [ANCP] Proposal for changing messages names in
Multicast Control Extensions
=09
=09
	Hi Stefaan,=20

	On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:


		=20
		Francois,
		=20
		If it is a request, then the AN just executes the
commands.  If it is a response, then I would think it has to look up the
state indexed by trans id to clean it up, and to execute the join which
is in that state.


	First, just to make sure we don't lose the first point: if the
AN needs to know whether it is a request or a response, it could do so
via the Result code.

	Now regarding whether AN needs to know, that may be
implementation dependent.
	One model could be as you described above, in which case AN
needs to know.
	Another model could be where the AN operates in a simpler "Fire
and Forget" mode:
	* AN sends admission request (and AN increments its Transaction
ID value)
	* AN forgets about it (AN relies on TCP to make sure request
reached NAS and relies on ANCP behavior to get a response)
	* when AN gets a Multicast Replication message, it just
executes. A key assumption here is that the multicast replication
control message contains all the information necessary for execution (eg
"add channel C to port P")

	Makes sense?

	Francois



		  So yes, it looks to me that both are different.  Also
the processing of the trans id is different because for requests it has
to check whether it is each time incremented by 1, which it does not
have to do for responses.
		=20
		regards,
		Stefaan

________________________________

		From: Francois Le Faucheur IMAP
[mailto:flefauch@cisco.com]=20
		Sent: woensdag 15 oktober 2008 16:27
		To: Francois Le Faucheur IMAP
		Cc: DE CNODDER Stefaan; ancp@ietf.org
		Subject: Re: [ANCP] Proposal for changing messages names
in Multicast Control Extensions
	=09
	=09

			=09
			=09
			=09

				If a message can be used as both a
request and a reply, is the defitions
			=09

				of the Transaction Identifier still
accurate?  Currently the draft says:
			=09


				- trans id in request is linearly
incrementing, and is per message type
			=09

				- trans id in response is copied from
request
			=09


				If the same message type can be both
request and response, then how will
			=09

				the trans id behave?  Should the
receiver first try to find out whether
			=09

				it is a request or a response, and then
process it accordingly?  Or how
			=09

				should it then work?
			=09



			Oops, there was a typo in earlier message. This
should read:
			One option would be for the receiver to look at
the Result field:
			* if it is set to Success/Failure, then this
message is a "response" to an earlier request (and its Transaction ID
echoed the one of the request)
			* if it is set to Ack/Nack, then this messages
is a "request" (and the transaction ID was generated by remote end)


		Note also that the AN may not even care that much
whether it is a response or a spontaneous request, because the two are
idempotent.

		Francois





				One option would be for the sender to
look at the Result field:
			=09

				* if it is set to Success/Failure, then
this message is a "response" to an earlier request (and its Transaction
ID echoed the one of the request)
			=09

				* if it is set to Ack/Nack, then this
messages is a request (and the transaction ID was generated by remote
end)
			=09




				regards,
			=09

				Stefaan
			=09



				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: dinsdag 14 oktober 2008 15:33
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				Ok, just wanted to make sure what you
meant.
			=09


				So, this means a Multicast Replication
Control Message would be used
			=09

				both as a reply to an authorization as
well as a directive.  I tend to
			=09

				agree with this, although, we might
review that case when we define the
			=09

				authorization message and if the reply
from the server would carry
			=09

				roughly the same information as the
directive. I would assume it would.
			=09




				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 9:22 AM
			=09

				To: Philippe Champagne (pchamp); DE
CNODDER Stefaan; Wojciech Dec
			=09

				(wdec); Sanjay Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09


				Hi Phil,
			=09

				    please see inline.
			=09


				Regards,
			=09

				Roberta
			=09


				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: Tuesday, October 14, 2008 2:50 PM
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				I'm ok with those renaming.
			=09

				[RM] Great
			=09


				Do you mean that when the ANCP client
ask authorization for a Join,
			=09

				its request is a Multicast Replication
Control Message and the reply
			=09

				from the server is the same or
different:____
			=09


				[RM] not exactly, what I meant is
slightly different:  when an ANCP
			=09

				client asks for authorization to Join a
multicast flow, it uses an ANCP
			=09


				message (not defined yet), while when
the server replies to the
			=09

				authorization message sent by the client
it could use a Multicast
			=09

				Replication Control Message
			=09


				While if the server is sending
			=09

				a directive to the ANCP client to have a
port join a
			=09

				multicast, do you
			=09

				mean this is also called Multicast
Replication Control Message?
			=09


				[RM] yes this is current scenario where
the server uses a Multicast
			=09

				Replication Control Message to send a
directive to the ANCP client to
			=09

				have a port join or leave a multicast
flow.
			=09

				Does it make sense?
			=09


				Thanks,
			=09

				Roberta
			=09





				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 7:46 AM
			=09

				To: Philippe Champagne (pchamp); 'DE
CNODDER Stefaan'; Wojciech Dec
			=09

				(wdec); 'Sanjay Wadhwa'
			=09

				Subject: Proposal for changing messages
names in Multicast Control
			=09

				Extensions
			=09



				Hello,
			=09

				    I'm currently merging
draft-ancp-mc-extensions with
			=09

				draft-ietf-ancp-protocol, and I am
thinking it could be useful to
			=09

				simplify the terminology in terms of
multicast message names.
			=09

				In particular I'd like to rename:
			=09

				- Multicast Replication Control Request
Message in just Multicast
			=09

				Replication Control Message
			=09

				- Multicast Status Response Message and
in Multicast Status Message
			=09


				This change would allow re-using the
same message type for different
			=09

				purposes/use cases if needed in future,
without affecting current
			=09

				scenario.
			=09


				Please let me know what's your opinion
on this proposal.
			=09


				Thanks and best regards,
			=09


				Roberta
			=09



				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content
			=09

				hereof is
			=09

				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09




				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content hereof is
			=09


				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09


=09
_______________________________________________
			=09

				ANCP mailing list
			=09

				ANCP@ietf.org
			=09

=09
https://www.ietf.org/mailman/listinfo/ancp
			=09






------_=_NextPart_001_01C92EF0.FB75BE05
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008>Hi Stefaan</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008>I think it could go this =
way:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008>Either the AN also sends the Leave to the NAS =
- which=20
will be processed serially by the NAS after the Join, and the NAS =
therefore will=20
reply for the leave shortly after. In this case, the AN gets a=20
leave.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008>or</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008>The AN does not sends the Leave to the NAS =
but holds it=20
for a specific time (the time we should expect such join from the =
server).=20
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008>For the fire and forget, I personally prefer =
the first=20
option, I mean, if we have to have the AN holding info, might as well be =
the=20
whole thing where&nbsp;it knows also about the =
JOIN&nbsp;sent&nbsp;shortly=20
before for which&nbsp;it is awaiting a response.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D439305517-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The question is then, which way to go?&nbsp; =
Can we allow=20
"fire and forget" and "remember the states" to both be used at the =
discretion of=20
the implementor of the ANCP client or do we force one way to go.&nbsp;=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D439305517-15102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>It depends if the ANCP server needs to know =
about=20
bandwidth&nbsp;usage&nbsp;for bandwidth requirement decision, in which =
case, it=20
would need to know about Leave as well, isn't it?&nbsp;&nbsp; Can that =
behavior=20
(bandwith decision)&nbsp;be configurable, allowing&nbsp;"remember the =
states"=20
(where Leaves are not necessarily&nbsp;forwarded) to exist in other =
deployment=20
model?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> DE CNODDER Stefaan=20
  [mailto:stefaan.de_cnodder@alcatel-lucent.be] <BR><B>Sent:</B> =
Wednesday,=20
  October 15, 2008 12:08 PM<BR><B>To:</B> Francois Le Faucheur=20
  (flefauch)<BR><B>Cc:</B> ancp@ietf.org; Philippe Champagne=20
  (pchamp)<BR><B>Subject:</B> RE: [ANCP] Proposal for changing messages =
names in=20
  Multicast Control Extensions<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>About the "fire and forget".&nbsp; I like it =
a lot=20
  because of its simplicity but it has an issue:</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>1) user sends join matching grey =
list</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>2) AN sends admission request to NAS and =
forgets about=20
  it</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>3) user sends leave, which is not doing =
anything since=20
  the NAS has not replied yet</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>4) AN receives possitive answer to join the=20
  stream</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>In this case the multicast flow is replicated =
to the line=20
  although the user had sent a leave.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>First processing the Result field without =
knowing what=20
  the message is about looks to me like a strange way of processing, but =
it=20
  works.&nbsp; However, just using a different message type would make =
it easier=20
  according to me.&nbsp; No need to repeat all commands or even no need =
to=20
  repeat the port id, so not much re-use anyhow.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>If the "fire and forget" method would work, =
there is not=20
  really a response, and the current message as defined today is =
sufficient, but=20
  in the above case I have some doubts.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
  [mailto:flefauch@cisco.com] <BR><B>Sent:</B> woensdag 15 oktober 2008=20
  17:53<BR><B>To:</B> DE CNODDER Stefaan<BR><B>Cc:</B> Francois Le =
Faucheur=20
  IMAP; ancp@ietf.org; Philippe (pchamp) Champagne<BR><B>Subject:</B> =
Re: [ANCP]=20
  Proposal for changing messages names in Multicast Control=20
  Extensions<BR></FONT><BR></DIV>
  <DIV></DIV>Hi Stefaan,=20
  <DIV><BR>
  <DIV>
  <DIV>On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite">
    <DIV=20
    style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just=20
    executes the commands.&nbsp; If it is a response, then I would think =
it has=20
    to look up the state indexed by trans id to clean it up, and to =
execute the=20
    join which is in that state.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>First, just to make sure we don't lose the first point: if the AN =
needs=20
  to know whether it is a request or a response, it could do so via the =
Result=20
  code.</DIV>
  <DIV><BR></DIV>
  <DIV>Now regarding whether AN needs to know, that may be =
implementation=20
  dependent.</DIV>
  <DIV>One model could be as you described above, in which case AN needs =
to=20
  know.</DIV>
  <DIV>Another model could be where the AN operates in a simpler "Fire =
and=20
  Forget" mode:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
AN sends=20
  admission request (and AN increments its Transaction ID value)</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
AN forgets=20
  about it (AN relies on TCP to make sure request reached NAS and relies =
on ANCP=20
  behavior to get a response)</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
when AN gets=20
  a Multicast Replication message, it just executes. A key assumption =
here is=20
  that the multicast replication control message contains all the =
information=20
  necessary for execution&nbsp;(eg "add channel C to port P")</DIV>
  <DIV><BR></DIV>
  <DIV>Makes sense?</DIV>
  <DIV><BR></DIV>
  <DIV>Francois</DIV>
  <DIV><BR></DIV><BR>
  <BLOCKQUOTE type=3D"cite">
    <DIV=20
    style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>&nbsp; So yes, it looks to me that both are =

    different.&nbsp; Also the processing of the trans id is=20
    different&nbsp;because for requests it has to check whether it is =
each time=20
    incremented by 1, which it does not have to do for=20
    responses.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A=20
    href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
    <BR><B>Sent:</B> woensdag 15 oktober 2008 16:27<BR><B>To:</B> =
Francois Le=20
    Faucheur IMAP<BR><B>Cc:</B> DE CNODDER Stefaan; <A=20
    href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> =
Re: [ANCP]=20
    Proposal for changing messages names in Multicast Control=20
    Extensions<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV>
    <BLOCKQUOTE type=3D"cite">
      <DIV>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><FONT class=3DApple-style-span=20
          color=3D#006312><BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">If a message can be used as both a =
request and=20
          a reply, is the defitions<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">of the Transaction Identifier still =
accurate?=20
          &nbsp;Currently the draft says:<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">- trans id in request is linearly=20
          incrementing, and is per message =
type<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">- trans id in response is copied from=20
          request<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">If the same message type can be both =
request=20
          and response, then how will<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">the trans id behave? &nbsp;Should the =
receiver=20
          first try to find out whether<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">it is a request or a response, and =
then=20
          process it accordingly? &nbsp;Or =
how<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">should it then =
work?<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE><BR>Oops, there was a =
typo in=20
      earlier message. This should read:<BR>One option would be for the =
receiver=20
      to look at the Result field:<BR><SPAN class=3DApple-tab-span=20
      style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure, then=20
      this message is a "response" to an earlier request (and its =
Transaction ID=20
      echoed the one of the request)<BR><SPAN class=3DApple-tab-span=20
      style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, then =
this=20
      messages is a "request" (and the transaction ID was generated by =
remote=20
      end)</DIV></BLOCKQUOTE>
    <DIV><BR></DIV>
    <DIV>Note also that the AN may not even care that much whether it is =
a=20
    response or a spontaneous request, because the two are =
idempotent.</DIV>
    <DIV><BR></DIV>
    <DIV>Francois</DIV>
    <DIV><BR></DIV><BR>
    <BLOCKQUOTE type=3D"cite">
      <DIV><BR><BR>
      <BLOCKQUOTE type=3D"cite">One option would be for the sender to =
look at=20
        the Result field:<BR></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
        style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure, then=20
        this message is a "response" to an earlier request (and its =
Transaction=20
        ID echoed the one of the request)<BR></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
        style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, =
then this=20
        messages is a request (and the transaction ID was generated by =
remote=20
        end)<BR></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">regards,<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Stefaan<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">-----Original=20
      Message-----<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) [<A=20
          =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Sent: dinsdag 14 oktober 2008=20
        15:33<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
          Wojciech Dec (wdec); Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Cc: <A=20
          =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
          names in Multicast Control<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">Ok, just wanted to make sure what you=20
          meant.<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">So, this means a Multicast Replication =
Control=20
          Message would be used<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">both as a reply to an authorization as =
well as=20
          a directive. &nbsp;I tend to<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">agree with this, although, we might =
review=20
          that case when we define the<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">authorization message and if the reply =
from=20
          the server would carry<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">roughly the same information as the =
directive.=20
          I would assume it would.<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">-----Original=20
        Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
            =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 9:22 =

          AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); DE =
CNODDER=20
            Stefaan; Wojciech =
Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">(wdec); Sanjay=20
        Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Cc: <A=20
            =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
            names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
      =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Hi=20
Phil,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see=20
            inline.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
type=3D"cite">Regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">-----Original=20
        Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) =
[<A=20
            =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 2:50 =

          PM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
            Wojciech Dec (wdec); =
Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Cc: <A=20
            =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
            names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
      =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">I'm ok with those=20
          =
renaming.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">[RM]=20
      Great<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Do you mean that when the ANCP =
client ask=20
              authorization for a=20
      Join,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">its request is a Multicast =
Replication=20
              Control Message and the=20
      reply<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">from the server is the same or=20
              =
different:____<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">[RM] not exactly, what I meant is =
slightly=20
            different: &nbsp;when an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">client asks for authorization to =
Join a=20
            multicast flow, it uses an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">message (not defined yet), while =
when the=20
            server replies to =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">authorization message sent by the =
client it=20
            could use a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Replication Control=20
        Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">While if the server is=20
            =
sending<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">a directive to the ANCP client to =
have a=20
              port join =
a<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">multicast, do=20
      you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">mean this is also called Multicast =

              Replication Control=20
      Message?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">[RM] yes this is current scenario =
where the=20
            server uses a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Replication Control Message to send =
a=20
            directive to the ANCP client =
to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">have a port join or leave a =
multicast=20
            flow.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Does it make=20
      sense?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">Thanks,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">-----Original=20
          =
Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
              =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 =
7:46=20
            AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); =
'DE=20
              CNODDER Stefaan'; Wojciech=20
      Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">(wdec); 'Sanjay=20
          =
Wadhwa'<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Subject: Proposal for changing =
messages=20
              names in Multicast=20
      Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite">Hello,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm =
currently=20
              merging draft-ancp-mc-extensions=20
        with<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">draft-ietf-ancp-protocol, and I am =

              thinking it could be useful=20
      to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">simplify the terminology in terms =
of=20
              multicast message=20
      names.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">In particular I'd like to=20
            =
rename:<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">- Multicast Replication Control =
Request=20
              Message in just=20
      Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Replication Control=20
          =
Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">- Multicast Status Response =
Message and in=20
              Multicast Status=20
      Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">This change would allow re-using =
the same=20
              message type for=20
      different<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">purposes/use cases if needed in =
future,=20
              without affecting=20
      current<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        =
type=3D"cite">scenario.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Please let me know what's your =
opinion on=20
              this =
proposal.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Thanks and best=20
          =
regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQU=
OTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
          NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">This message and its attachments =
are=20
              addressed solely to the=20
        persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">above and may contain confidential =

              information. If you have=20
        received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">the message in error, be informed =
that any=20
              use of the =
content<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">hereof=20
      is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately=20
              to the sender and delete=20
      the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions,=20
              please contact us by=20
      replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">to <A=20
              =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
            you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
              =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
              =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
        NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">This message and its attachments are =

            addressed solely to the =
persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">above and may contain confidential=20
            information. If you have=20
      received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">the message in error, be informed =
that any=20
            use of the content hereof =
is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately to=20
            the sender and delete =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions,=20
            please contact us by =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">to <A=20
            =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
          you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
            =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
            =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE=20
          =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite">ANCP mailing =
list<BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><A=20
          =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
      <BLOCKQUOTE type=3D"cite">
        <BLOCKQUOTE type=3D"cite"><A=20
          =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></BLOCKQUOTE></BLOCKQUOTE>
      <BLOCKQUOTE=20
    =
type=3D"cite"><BR></BLOCKQUOTE><BR></DIV></BLOCKQUOTE></DIV><BR></DIV></B=
LOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C92EF0.FB75BE05--

--===============0837082615==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0837082615==--


From ancp-bounces@ietf.org  Wed Oct 15 23:36:57 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56F773A6A63;
	Wed, 15 Oct 2008 23:36:57 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B733A3A6A63
	for <ancp@core3.amsl.com>; Wed, 15 Oct 2008 23:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 d42rET5Fizti for <ancp@core3.amsl.com>;
	Wed, 15 Oct 2008 23:36:54 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id A24E53A68FE
	for <ancp@ietf.org>; Wed, 15 Oct 2008 23:36:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,422,1220227200"; d="scan'208,217";a="22770196"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 16 Oct 2008 06:37:50 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9G6bojR022587; 
	Thu, 16 Oct 2008 08:37:50 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9G6bo2O002481;
	Thu, 16 Oct 2008 06:37:50 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 08:37:50 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 08:37:47 +0200
Message-Id: <43DBB22A-C83C-4DB2-B478-A9693A3F6D0C@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: DE CNODDER Stefaan <stefaan.de_cnodder@alcatel-lucent.be>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 08:37:45 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
	<87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 16 Oct 2008 06:37:47.0832 (UTC)
	FILETIME=[B42EA380:01C92F59]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=52096; t=1224139070;
	x=1225003070; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=seKLpXhmvE04ns2biM99zTxmeXNWkKbkN6Sez9eCTJg=;
	b=WAhoi8ZqwoDAlJ7yckQxB2txAUiVlec7zFHbZkRffreI/f6FdpdTJvL9qP
	3C1Q1Na349gZ26mTsxAHSvBGdX741rkAt7AEuvZI5GRuHEJw9foEOI4UndyV
	/8ytIFUaic;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2013582877=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============2013582877==
Content-Type: multipart/alternative; boundary=Apple-Mail-1-1018730007


--Apple-Mail-1-1018730007
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On 15 Oct 2008, at 18:08, DE CNODDER Stefaan wrote:

>
> About the "fire and forget".  I like it a lot because of its  
> simplicity but it has an issue:
>
> 1) user sends join matching grey list
> 2) AN sends admission request to NAS and forgets about it
> 3) user sends leave,

Then the AN would "Fire and Forget" an ANCP message conveying the  
Leave (whether or not the NAS has already responded to the previous  
admission request).
So I'm not sure the above scenario creates an issue.

The AN is effectively responsible for conveying all the Join/leave  
transitions to the NAS and relies on NAS to process and then instruct  
back the AN to perform the resulting replication add/delete for  
<channels,ports>.

Francois


> which is not doing anything since the NAS has not replied yet
> 4) AN receives possitive answer to join the stream
>
> In this case the multicast flow is replicated to the line although  
> the user had sent a leave.
>
> First processing the Result field without knowing what the message  
> is about looks to me like a strange way of processing, but it  
> works.  However, just using a different message type would make it  
> easier according to me.  No need to repeat all commands or even no  
> need to repeat the port id, so not much re-use anyhow.
>
> If the "fire and forget" method would work, there is not really a  
> response, and the current message as defined today is sufficient,  
> but in the above case I have some doubts.
>
> regards,
> Stefaan
>
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: woensdag 15 oktober 2008 17:53
> To: DE CNODDER Stefaan
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org; Philippe (pchamp)  
> Champagne
> Subject: Re: [ANCP] Proposal for changing messages names in  
> Multicast Control Extensions
>
> Hi Stefaan,
>
> On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:
>
>>
>> Francois,
>>
>> If it is a request, then the AN just executes the commands.  If it  
>> is a response, then I would think it has to look up the state  
>> indexed by trans id to clean it up, and to execute the join which  
>> is in that state.
>
> First, just to make sure we don't lose the first point: if the AN  
> needs to know whether it is a request or a response, it could do so  
> via the Result code.
>
> Now regarding whether AN needs to know, that may be implementation  
> dependent.
> One model could be as you described above, in which case AN needs to  
> know.
> Another model could be where the AN operates in a simpler "Fire and  
> Forget" mode:
> * AN sends admission request (and AN increments its Transaction ID  
> value)
> * AN forgets about it (AN relies on TCP to make sure request reached  
> NAS and relies on ANCP behavior to get a response)
> * when AN gets a Multicast Replication message, it just executes. A  
> key assumption here is that the multicast replication control  
> message contains all the information necessary for execution (eg  
> "add channel C to port P")
>
> Makes sense?
>
> Francois
>
>
>>   So yes, it looks to me that both are different.  Also the  
>> processing of the trans id is different because for requests it has  
>> to check whether it is each time incremented by 1, which it does  
>> not have to do for responses.
>>
>> regards,
>> Stefaan
>>
>> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
>> Sent: woensdag 15 oktober 2008 16:27
>> To: Francois Le Faucheur IMAP
>> Cc: DE CNODDER Stefaan; ancp@ietf.org
>> Subject: Re: [ANCP] Proposal for changing messages names in  
>> Multicast Control Extensions
>>
>>>>>
>>>>>
>>>>> If a message can be used as both a request and a reply, is the  
>>>>> defitions
>>>>> of the Transaction Identifier still accurate?  Currently the  
>>>>> draft says:
>>>>>
>>>>> - trans id in request is linearly incrementing, and is per  
>>>>> message type
>>>>> - trans id in response is copied from request
>>>>>
>>>>> If the same message type can be both request and response, then  
>>>>> how will
>>>>> the trans id behave?  Should the receiver first try to find out  
>>>>> whether
>>>>> it is a request or a response, and then process it accordingly?   
>>>>> Or how
>>>>> should it then work?
>>>>
>>>
>>> Oops, there was a typo in earlier message. This should read:
>>> One option would be for the receiver to look at the Result field:
>>> * if it is set to Success/Failure, then this message is a  
>>> "response" to an earlier request (and its Transaction ID echoed  
>>> the one of the request)
>>> * if it is set to Ack/Nack, then this messages is a "request" (and  
>>> the transaction ID was generated by remote end)
>>
>> Note also that the AN may not even care that much whether it is a  
>> response or a spontaneous request, because the two are idempotent.
>>
>> Francois
>>
>>
>>>
>>>
>>>> One option would be for the sender to look at the Result field:
>>>> * if it is set to Success/Failure, then this message is a  
>>>> "response" to an earlier request (and its Transaction ID echoed  
>>>> the one of the request)
>>>> * if it is set to Ack/Nack, then this messages is a request (and  
>>>> the transaction ID was generated by remote end)
>>>>
>>>>>
>>>>>
>>>>> regards,
>>>>> Stefaan
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>>> Sent: dinsdag 14 oktober 2008 15:33
>>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>>> Sanjay
>>>>> Wadhwa
>>>>> Cc: ancp@ietf.org
>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>> Control
>>>>> Extensions
>>>>>
>>>>>
>>>>> Ok, just wanted to make sure what you meant.
>>>>>
>>>>> So, this means a Multicast Replication Control Message would be  
>>>>> used
>>>>> both as a reply to an authorization as well as a directive.  I  
>>>>> tend to
>>>>> agree with this, although, we might review that case when we  
>>>>> define the
>>>>> authorization message and if the reply from the server would carry
>>>>> roughly the same information as the directive. I would assume it  
>>>>> would.
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>>>> Sent: Tuesday, October 14, 2008 9:22 AM
>>>>>> To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec
>>>>>> (wdec); Sanjay Wadhwa
>>>>>> Cc: ancp@ietf.org
>>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>>> Control
>>>>>> Extensions
>>>>>>
>>>>>> Hi Phil,
>>>>>>     please see inline.
>>>>>>
>>>>>> Regards,
>>>>>> Roberta
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>>>> Sent: Tuesday, October 14, 2008 2:50 PM
>>>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>>>> Sanjay
>>>>>> Wadhwa
>>>>>> Cc: ancp@ietf.org
>>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>>> Control
>>>>>> Extensions
>>>>>>
>>>>>>
>>>>>>> I'm ok with those renaming.
>>>>>> [RM] Great
>>>>>>
>>>>>>> Do you mean that when the ANCP client ask authorization for a  
>>>>>>> Join,
>>>>>>> its request is a Multicast Replication Control Message and the  
>>>>>>> reply
>>>>>>> from the server is the same or different:____
>>>>>>
>>>>>> [RM] not exactly, what I meant is slightly different:  when an  
>>>>>> ANCP
>>>>>> client asks for authorization to Join a multicast flow, it uses  
>>>>>> an ANCP
>>>>>
>>>>>> message (not defined yet), while when the server replies to the
>>>>>> authorization message sent by the client it could use a Multicast
>>>>>> Replication Control Message
>>>>>>
>>>>>>> While if the server is sending
>>>>>>> a directive to the ANCP client to have a port join a
>>>>>> multicast, do you
>>>>>>> mean this is also called Multicast Replication Control Message?
>>>>>>
>>>>>> [RM] yes this is current scenario where the server uses a  
>>>>>> Multicast
>>>>>> Replication Control Message to send a directive to the ANCP  
>>>>>> client to
>>>>>> have a port join or leave a multicast flow.
>>>>>> Does it make sense?
>>>>>>
>>>>>> Thanks,
>>>>>> Roberta
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Maglione Roberta  
>>>>>>> [mailto:roberta.maglione@telecomitalia.it]
>>>>>>> Sent: Tuesday, October 14, 2008 7:46 AM
>>>>>>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan';  
>>>>>>> Wojciech Dec
>>>>>>> (wdec); 'Sanjay Wadhwa'
>>>>>>> Subject: Proposal for changing messages names in Multicast  
>>>>>>> Control
>>>>>>> Extensions
>>>>>>>
>>>>>>>
>>>>>>> Hello,
>>>>>>>     I'm currently merging draft-ancp-mc-extensions with
>>>>>>> draft-ietf-ancp-protocol, and I am thinking it could be useful  
>>>>>>> to
>>>>>>> simplify the terminology in terms of multicast message names.
>>>>>>> In particular I'd like to rename:
>>>>>>> - Multicast Replication Control Request Message in just  
>>>>>>> Multicast
>>>>>>> Replication Control Message
>>>>>>> - Multicast Status Response Message and in Multicast Status  
>>>>>>> Message
>>>>>>>
>>>>>>> This change would allow re-using the same message type for  
>>>>>>> different
>>>>>>> purposes/use cases if needed in future, without affecting  
>>>>>>> current
>>>>>>> scenario.
>>>>>>>
>>>>>>> Please let me know what's your opinion on this proposal.
>>>>>>>
>>>>>>> Thanks and best regards,
>>>>>>>
>>>>>>> Roberta
>>>>>>>
>>>>>>>
>>>>>>> CONFIDENTIALITY NOTICE
>>>>>>>
>>>>>>> This message and its attachments are addressed solely to the  
>>>>>>> persons
>>>>>>> above and may contain confidential information. If you have  
>>>>>>> received
>>>>>>> the message in error, be informed that any use of the content
>>>>>> hereof is
>>>>>>> prohibited. Please return it immediately to the sender and  
>>>>>>> delete the
>>>>>>> message. Should you have any questions, please contact us by  
>>>>>>> replying
>>>>>>> to webmaster@telecomitalia.it.
>>>>>>>
>>>>>>>     Thank you
>>>>>>>
>>>>>>>                                     www.telecomitalia.it
>>>>>>>
>>>>>>
>>>>>>
>>>>>> CONFIDENTIALITY NOTICE
>>>>>>
>>>>>> This message and its attachments are addressed solely to the  
>>>>>> persons
>>>>>> above and may contain confidential information. If you have  
>>>>>> received
>>>>>> the message in error, be informed that any use of the content  
>>>>>> hereof is
>>>>>
>>>>>> prohibited. Please return it immediately to the sender and  
>>>>>> delete the
>>>>>> message. Should you have any questions, please contact us by  
>>>>>> replying
>>>>>> to webmaster@telecomitalia.it.
>>>>>>
>>>>>>     Thank you
>>>>>>
>>>>>>                                     www.telecomitalia.it
>>>>>>
>>>>> _______________________________________________
>>>>> ANCP mailing list
>>>>> ANCP@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ancp
>>>>
>>>
>>
>


--Apple-Mail-1-1018730007
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On 15 Oct 2008, =
at 18:08, DE CNODDER Stefaan wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"> <div =
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font>&nbsp;</div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">About the "fire and forget".&nbsp; I like it a lot because of =
its simplicity but it has an issue:</font></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">1) user sends join matching grey =
list</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">2) AN sends admission request to NAS and forgets about =
it</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">3) user sends leave, =
</font></span></div></div></blockquote><div><br></div><div>Then the AN =
would "Fire and Forget" an ANCP message conveying the Leave (whether or =
not the NAS has already responded to the previous admission =
request).</div><div>So I'm not sure the above scenario creates an =
issue.</div><div><br></div><div>The AN is effectively responsible for =
conveying all the Join/leave transitions to the NAS and relies on NAS to =
process and then instruct back the AN to perform the resulting =
replication add/delete for =
&lt;channels,ports>.</div><div><br></div><div>Francois</div><div><br></div=
><br><blockquote type=3D"cite"><div style=3D"WORD-WRAP: break-word; =
webkit-nbsp-mode: space; webkit-line-break: after-white-space"><div =
dir=3D"ltr" align=3D"left"><span class=3D"935315915-15102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">which is not doing anything =
since the NAS has not replied yet</font></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">4) AN receives possitive answer to join the =
stream</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">In this case the multicast flow is =
replicated to the line although the user had sent a =
leave.</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">First processing the Result field without =
knowing what the message is about looks to me like a strange way of =
processing, but it works.&nbsp; However, just using a different message =
type would make it easier according to me.&nbsp; No need to repeat all =
commands or even no need to repeat the port id, so not much re-use =
anyhow.</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">If the "fire and forget" method would work, =
there is not really a response, and the current message as defined today =
is sufficient, but in the above case I have some =
doubts.</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">regards,</font></span></div> <div dir=3D"ltr"=
 align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Stefaan</font></span></div><br> <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
<hr tabindex=3D"-1"> <font face=3D"Tahoma" size=3D"2"><b>From:</b> =
Francois Le Faucheur IMAP [<a =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</a>] =
<br><b>Sent:</b> woensdag 15 oktober 2008 17:53<br><b>To:</b> DE CNODDER =
Stefaan<br><b>Cc:</b> Francois Le Faucheur IMAP; <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a>; Philippe (pchamp) =
Champagne<br><b>Subject:</b> Re: [ANCP] Proposal for changing messages =
names in Multicast Control Extensions<br></font><br></div> <div></div>Hi =
Stefaan, <div><br> <div> <div>On 15 Oct 2008, at 16:36, DE CNODDER =
Stefaan wrote:</div><br class=3D"Apple-interchange-newline"> <blockquote =
type=3D"cite">  <div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space">  <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font>&nbsp;</div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"503243114-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Francois,</font></span></div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just   executes the commands.&nbsp; If it is a response, then I =
would think it has to   look up the state indexed by trans id to clean =
it up, and to execute the join   which is in that =
state.</font></span></div></div></blockquote> <div><br></div> =
<div>First, just to make sure we don't lose the first point: if the AN =
needs to know whether it is a request or a response, it could do so via =
the Result code.</div> <div><br></div> <div>Now regarding whether AN =
needs to know, that may be implementation dependent.</div> <div>One =
model could be as you described above, in which case AN needs to =
know.</div> <div>Another model could be where the AN operates in a =
simpler "Fire and Forget" mode:</div> <div><span class=3D"Apple-tab-span" =
style=3D"WHITE-SPACE: pre"></span>* AN sends admission request (and AN =
increments its Transaction ID value)</div> <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* AN forgets =
about it (AN relies on TCP to make sure request reached NAS and relies =
on ANCP behavior to get a response)</div> <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* when AN =
gets a Multicast Replication message, it just executes. A key assumption =
here is that the multicast replication control message contains all the =
information necessary for execution&nbsp;(eg "add channel C to port =
P")</div> <div><br></div> <div>Makes sense?</div> <div><br></div> =
<div>Francois</div> <div><br></div><br> <blockquote type=3D"cite">  <div =
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">  <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">&nbsp; So yes, it looks to me that both are =
  different.&nbsp; Also the processing of the trans id is =
different&nbsp;because   for requests it has to check whether it is each =
time incremented by 1, which   it does not have to do for =
responses.</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"503243114-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">regards,</font></span></div>  <div =
dir=3D"ltr" align=3D"left"><span class=3D"503243114-15102008"><font =
face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Stefaan</font></span></div><br>  <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
 <hr tabindex=3D"-1">  <font face=3D"Tahoma" size=3D"2"><b>From:</b> =
Francois Le Faucheur IMAP [<a =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</a>]   =
<br><b>Sent:</b> woensdag 15 oktober 2008 16:27<br><b>To:</b> Francois =
Le   Faucheur IMAP<br><b>Cc:</b> DE CNODDER Stefaan; <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br><b>Subject:</b> Re: =
[ANCP]   Proposal for changing messages names in Multicast Control   =
Extensions<br></font><br></div>  <div></div>  <div>  <blockquote =
type=3D"cite">    <div>    <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#006312"><br></font><br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">If a message =
can be used as both a request and a         reply, is the =
defitions<br></blockquote></blockquote>    <blockquote type=3D"cite">    =
  <blockquote type=3D"cite">of the Transaction Identifier still =
accurate?         &nbsp;Currently the draft =
says:<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">- trans id in request is =
linearly incrementing,         and is per message =
type<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">- trans id in response is copied from       =
request<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite"><br></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">If the same message type =
can be both request and         response, then how =
will<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">the trans id behave? &nbsp;Should the receiver =
        first try to find out whether<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">it is a =
request or a response, and then process         it accordingly? &nbsp;Or =
how<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">should it then =
work?<br></blockquote></blockquote>    <blockquote =
type=3D"cite"><br></blockquote><br>Oops, there was a typo in     earlier =
message. This should read:<br>One option would be for the receiver     =
to look at the Result field:<br><span class=3D"Apple-tab-span" =
style=3D"WHITE-SPACE: pre"></span>* if it is set to Success/Failure, =
then this     message is a "response" to an earlier request (and its =
Transaction ID echoed     the one of the request)<br><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Ack/Nack, then this     messages is a "request" (and the =
transaction ID was generated by remote     end)</div></blockquote>  =
<div><br></div>  <div>Note also that the AN may not even care that much =
whether it is a   response or a spontaneous request, because the two are =
idempotent.</div>  <div><br></div>  <div>Francois</div>  =
<div><br></div><br>  <blockquote type=3D"cite">    <div><br><br>    =
<blockquote type=3D"cite">One option would be for the sender to look at =
the       Result field:<br></blockquote>    <blockquote =
type=3D"cite"><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: =
pre"></span>* if it is set to Success/Failure, then       this message =
is a "response" to an earlier request (and its Transaction ID       =
echoed the one of the request)<br></blockquote>    <blockquote =
type=3D"cite"><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: =
pre"></span>* if it is set to Ack/Nack, then this       messages is a =
request (and the transaction ID was generated by remote       =
end)<br></blockquote>    <blockquote type=3D"cite"><br></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite"><br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite">regards,<br></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote =
type=3D"cite">Stefaan<br></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite"><br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">-----Original  =
   Message-----<br></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">From: Philippe Champagne =
(pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote>    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">Sent: dinsdag 14 oktober 2008       =
15:33<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">To: Maglione Roberta; DE CNODDER Stefaan;      =
   Wojciech Dec (wdec); Sanjay<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te>    <blockquote type=3D"cite">      <blockquote type=3D"cite">Subject: =
RE: Proposal for changing messages         names in Multicast =
Control<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">Extensions<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite"><br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">Ok, just =
wanted to make sure what you       meant.<br></blockquote></blockquote>  =
  <blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite">So, this means a Multicast Replication =
Control         Message would be used<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">both as a =
reply to an authorization as well as a         directive. &nbsp;I tend =
to<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">agree with this, although, we might review =
that         case when we define the<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">authorization =
message and if the reply from the         server would =
carry<br></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">roughly the same information as the directive. =
I         would assume it would.<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite"><br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">-----Original       =
Message-----<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">From: Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">Sent: Tuesday, October 14, 2008 9:22         =
AM<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">To: Philippe Champagne (pchamp); DE CNODDER           =
Stefaan; Wojciech Dec<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">(wdec); Sanjay     =
Wadhwa<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote>    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">Subject: RE: Proposal =
for changing messages           names in Multicast =
Control<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">Hi =
Phil,<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see         =
inline.<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Regards,<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">-----Original       =
Message-----<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">From: Philippe Champagne (pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">Sent: =
Tuesday, October 14, 2008 2:50         =
PM<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">To: Maglione Roberta; DE CNODDER Stefaan;           =
Wojciech Dec (wdec); Sanjay<br></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote>    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">Subject: RE: Proposal =
for changing messages           names in Multicast =
Control<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">I'm ok =
with those         =
renaming.<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">[RM] =
Great<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote type=3D"cite">Do you mean that when =
the ANCP client ask             authorization for a     =
Join,<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">its =
request is a Multicast Replication             Control Message and the   =
  reply<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">from the =
server is the same or             =
different:____<br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">[RM] not exactly, what I meant is slightly     =
      different: &nbsp;when an =
ANCP<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">client asks for authorization to Join a           =
multicast flow, it uses an =
ANCP<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite">        <blockquote type=3D"cite">message =
(not defined yet), while when the           server replies to =
the<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">authorization message sent by the client it           =
could use a Multicast<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">Replication Control       =
Message<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote type=3D"cite">While if the server is =
        sending<br></blockquote></blockquote></blockquote></blockquote>  =
  <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">a =
directive to the ANCP client to have a             port join =
a<br></blockquote></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">multicast, do     =
you<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote type=3D"cite">mean this is also =
called Multicast             Replication Control     =
Message?<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">[RM] yes this is current scenario where the    =
       server uses a =
Multicast<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Replication Control Message to send a           directive =
to the ANCP client to<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">have a port join or leave a multicast         =
flow.<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Does it make     =
sense?<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Thanks,<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">-----Original         =
Message-----<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">From: =
Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote></blockquo=
te>    <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">Sent: =
Tuesday, October 14, 2008 7:46           =
AM<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">To: =
Philippe Champagne (pchamp); 'DE CNODDER             Stefaan'; Wojciech  =
   Dec<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">(wdec); =
'Sanjay         =
Wadhwa'<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">Subject: =
Proposal for changing messages             names in Multicast     =
Control<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote></block=
quote>    <blockquote type=3D"cite">      <blockquote type=3D"cite">     =
   <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">Hello,<br></blockquote></blockquote></blockquote></blockquot=
e>    <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm currently             merging =
draft-ancp-mc-extensions       =
with<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">draft-ietf-ancp-protocol, and I am thinking             it =
could be useful =
to<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">simplify =
the terminology in terms of             multicast message     =
names.<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">In =
particular I'd like to           =
rename:<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">- =
Multicast Replication Control Request             Message in just     =
Multicast<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">Replication =
Control         =
Message<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">- =
Multicast Status Response Message and in             Multicast Status    =
 Message<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">This =
change would allow re-using the same             message type for     =
different<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">purposes/use=
 cases if needed in future,             without affecting     =
current<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">scenario.<br></blockquote></blockquote></blockquote></blockq=
uote>    <blockquote type=3D"cite">      <blockquote type=3D"cite">      =
  <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">Please let =
me know what's your opinion on             this =
proposal.<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">Thanks and =
best         =
regards,<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote></blockquo=
te>    <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">CONFIDENTIALITY         =
NOTICE<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">This =
message and its attachments are             addressed solely to the     =
persons<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">above and =
may contain confidential             information. If you have       =
received<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">the =
message in error, be informed that any             use of the =
content<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">hereof =
is<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote type=3D"cite">prohibited. Please =
return it immediately to             the sender and delete     =
the<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">message. =
Should you have any questions,             please contact us by     =
replying<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank           =
you<br></blockquote></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote></blockquote>    <blockquote type=3D"cite"> =
     <blockquote type=3D"cite">        <blockquote type=3D"cite">        =
  <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
 <blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">CONFIDENTIALITY       =
NOTICE<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">This message and its attachments are addressed           =
solely to the persons<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">above and may contain confidential           =
information. If you have =
received<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">the message in error, be informed that any use           =
of the content hereof is<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote =
type=3D"cite"><br></blockquote></blockquote>    <blockquote type=3D"cite">=
      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">prohibited. Please return it immediately to           the =
sender and delete the<br></blockquote></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">message. Should you have any questions, please =
          contact us by =
replying<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote>    <blockquote type=3D"cite"> =
     <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank         =
you<br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote>    <blockquote type=3D"cite">      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>    <blockquote =
type=3D"cite">      <blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote>    <blockquote type=3D"cite">      <blockquote =
type=3D"cite">ANCP mailing list<br></blockquote></blockquote>    =
<blockquote type=3D"cite">      <blockquote type=3D"cite"><a =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br></blockquote></blockquo=
te>    <blockquote type=3D"cite">      <blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><br></blockquote></blockquote>    <blockquote =
type=3D"cite"><br></blockquote><br></div></blockquote></div><br></div></bl=
ockquote></div><br></div></div></blockquote></div><br></body></html>=

--Apple-Mail-1-1018730007--

--===============2013582877==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============2013582877==--


From ancp-bounces@ietf.org  Thu Oct 16 00:11:25 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 296F83A6A7F;
	Thu, 16 Oct 2008 00:11:25 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 94B4A3A6A7F
	for <ancp@core3.amsl.com>; Thu, 16 Oct 2008 00:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 2BYvKpYm0Tpq for <ancp@core3.amsl.com>;
	Thu, 16 Oct 2008 00:11:21 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 26F763A6952
	for <ancp@ietf.org>; Thu, 16 Oct 2008 00:11:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,422,1220227200"; d="scan'208,217";a="22774052"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 16 Oct 2008 07:11:23 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9G7BNPq032575; 
	Thu, 16 Oct 2008 09:11:23 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9G7BNO3012373;
	Thu, 16 Oct 2008 07:11:23 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 09:11:23 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 09:11:20 +0200
Message-Id: <68005082-BEE6-4215-8F68-509C047EDE28@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Philippe Champagne (pchamp) <pchamp@cisco.com>
In-Reply-To: <48214755113BB04F84D958B4F0DE261C069350E2@xmb-sjc-222.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 09:11:19 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
	<87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
	<48214755113BB04F84D958B4F0DE261C069350E2@xmb-sjc-222.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 16 Oct 2008 07:11:20.0827 (UTC)
	FILETIME=[64054CB0:01C92F5E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=60761; t=1224141083;
	x=1225005083; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=efnhO9dpzsdDXparhHp33qi5jwpXTyNsiiT64/fi0sU=;
	b=gbrt7O69shXWRUbW5fN05StEmFb7is/RbduQGD4sgugw4Xvs4zNoDLcjY+
	X4u1QibbzMpHr76qAsgDwSgJJVkFveFKAsbHoP0zobvKhuHrur+05cCrTbZv
	js4nBH6d5r;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0203618941=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============0203618941==
Content-Type: multipart/alternative; boundary=Apple-Mail-2-1020743513


--Apple-Mail-2-1020743513
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Philippe, Stefaan,

On 15 Oct 2008, at 20:08, Philippe Champagne (pchamp) wrote:

> Hi Stefaan
>
> I think it could go this way:
>
> Either the AN also sends the Leave to the NAS - which will be  
> processed serially by the NAS after the Join, and the NAS therefore  
> will reply for the leave shortly after. In this case, the AN gets a  
> leave.
> or
> The AN does not sends the Leave to the NAS but holds it for a  
> specific time (the time we should expect such join from the server).
>
> For the fire and forget, I personally prefer the first option, I  
> mean, if we have to have the AN holding info, might as well be the  
> whole thing where it knows also about the JOIN sent shortly before  
> for which it is awaiting a response.
>
> The question is then, which way to go?  Can we allow "fire and  
> forget" and "remember the states" to both be used at the discretion  
> of the implementor of the ANCP client or do we force one way to go.
> It depends if the ANCP server needs to know about bandwidth usage  
> for bandwidth requirement decision, in which case, it would need to  
> know about Leave as well, isn't it?   Can that behavior (bandwith  
> decision) be configurable, allowing "remember the states" (where  
> Leaves are not necessarily forwarded) to exist in other deployment  
> model?

I would say that we already have a model to allow the AN to operate  
fairly autonomously (ie Black List & White-List + Bandwidth  
delegation). In that model, the NAS does not need to track all join/ 
leaves and we take advantage of that to have AN handles Join/Leave  
without having to keep NAS aware of all that..

The Admission Control request that we are discussing in the thread is  
associated with the Grey-List Model where the NAS is likely to need to  
track all join/leaves (eg because admission control is performed by  
NAS or Policy Server, perhaps for accounting reason, perhaps for  
conditional access). So to mimimze the number of options, I would  
suggest that in this case of Grey-List operation, we only allow a  
single behavior whereby the AN conveys all the Leave/Join transitions  
to NAS.
Note that the AN may use some liberty in how it does that (eg. it may  
optionally wait a little bit on receipt of a Leave to see if a Join is  
not immediately following to bundle that in a single ANCP request, it  
may decide to remember the state for a while or until it gets a  
response,...) but I would suggest that no matter what the AN should  
always convey all Join/Leave transitions (in this Grey-List Model).

Makes sense?

Francois


>
>
>
> From: DE CNODDER Stefaan [mailto:stefaan.de_cnodder@alcatel-lucent.be]
> Sent: Wednesday, October 15, 2008 12:08 PM
> To: Francois Le Faucheur (flefauch)
> Cc: ancp@ietf.org; Philippe Champagne (pchamp)
> Subject: RE: [ANCP] Proposal for changing messages names in  
> Multicast Control Extensions
>
>
> About the "fire and forget".  I like it a lot because of its  
> simplicity but it has an issue:
>
> 1) user sends join matching grey list
> 2) AN sends admission request to NAS and forgets about it
> 3) user sends leave, which is not doing anything since the NAS has  
> not replied yet
> 4) AN receives possitive answer to join the stream
>
> In this case the multicast flow is replicated to the line although  
> the user had sent a leave.
>
> First processing the Result field without knowing what the message  
> is about looks to me like a strange way of processing, but it  
> works.  However, just using a different message type would make it  
> easier according to me.  No need to repeat all commands or even no  
> need to repeat the port id, so not much re-use anyhow.
>
> If the "fire and forget" method would work, there is not really a  
> response, and the current message as defined today is sufficient,  
> but in the above case I have some doubts.
>
> regards,
> Stefaan
>
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: woensdag 15 oktober 2008 17:53
> To: DE CNODDER Stefaan
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org; Philippe (pchamp)  
> Champagne
> Subject: Re: [ANCP] Proposal for changing messages names in  
> Multicast Control Extensions
>
> Hi Stefaan,
>
> On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:
>
>>
>> Francois,
>>
>> If it is a request, then the AN just executes the commands.  If it  
>> is a response, then I would think it has to look up the state  
>> indexed by trans id to clean it up, and to execute the join which  
>> is in that state.
>
> First, just to make sure we don't lose the first point: if the AN  
> needs to know whether it is a request or a response, it could do so  
> via the Result code.
>
> Now regarding whether AN needs to know, that may be implementation  
> dependent.
> One model could be as you described above, in which case AN needs to  
> know.
> Another model could be where the AN operates in a simpler "Fire and  
> Forget" mode:
> * AN sends admission request (and AN increments its Transaction ID  
> value)
> * AN forgets about it (AN relies on TCP to make sure request reached  
> NAS and relies on ANCP behavior to get a response)
> * when AN gets a Multicast Replication message, it just executes. A  
> key assumption here is that the multicast replication control  
> message contains all the information necessary for execution (eg  
> "add channel C to port P")
>
> Makes sense?
>
> Francois
>
>
>>   So yes, it looks to me that both are different.  Also the  
>> processing of the trans id is different because for requests it has  
>> to check whether it is each time incremented by 1, which it does  
>> not have to do for responses.
>>
>> regards,
>> Stefaan
>>
>> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
>> Sent: woensdag 15 oktober 2008 16:27
>> To: Francois Le Faucheur IMAP
>> Cc: DE CNODDER Stefaan; ancp@ietf.org
>> Subject: Re: [ANCP] Proposal for changing messages names in  
>> Multicast Control Extensions
>>
>>>>>
>>>>>
>>>>> If a message can be used as both a request and a reply, is the  
>>>>> defitions
>>>>> of the Transaction Identifier still accurate?  Currently the  
>>>>> draft says:
>>>>>
>>>>> - trans id in request is linearly incrementing, and is per  
>>>>> message type
>>>>> - trans id in response is copied from request
>>>>>
>>>>> If the same message type can be both request and response, then  
>>>>> how will
>>>>> the trans id behave?  Should the receiver first try to find out  
>>>>> whether
>>>>> it is a request or a response, and then process it accordingly?   
>>>>> Or how
>>>>> should it then work?
>>>>
>>>
>>> Oops, there was a typo in earlier message. This should read:
>>> One option would be for the receiver to look at the Result field:
>>> * if it is set to Success/Failure, then this message is a  
>>> "response" to an earlier request (and its Transaction ID echoed  
>>> the one of the request)
>>> * if it is set to Ack/Nack, then this messages is a "request" (and  
>>> the transaction ID was generated by remote end)
>>
>> Note also that the AN may not even care that much whether it is a  
>> response or a spontaneous request, because the two are idempotent.
>>
>> Francois
>>
>>
>>>
>>>
>>>> One option would be for the sender to look at the Result field:
>>>> * if it is set to Success/Failure, then this message is a  
>>>> "response" to an earlier request (and its Transaction ID echoed  
>>>> the one of the request)
>>>> * if it is set to Ack/Nack, then this messages is a request (and  
>>>> the transaction ID was generated by remote end)
>>>>
>>>>>
>>>>>
>>>>> regards,
>>>>> Stefaan
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>>> Sent: dinsdag 14 oktober 2008 15:33
>>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>>> Sanjay
>>>>> Wadhwa
>>>>> Cc: ancp@ietf.org
>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>> Control
>>>>> Extensions
>>>>>
>>>>>
>>>>> Ok, just wanted to make sure what you meant.
>>>>>
>>>>> So, this means a Multicast Replication Control Message would be  
>>>>> used
>>>>> both as a reply to an authorization as well as a directive.  I  
>>>>> tend to
>>>>> agree with this, although, we might review that case when we  
>>>>> define the
>>>>> authorization message and if the reply from the server would carry
>>>>> roughly the same information as the directive. I would assume it  
>>>>> would.
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]
>>>>>> Sent: Tuesday, October 14, 2008 9:22 AM
>>>>>> To: Philippe Champagne (pchamp); DE CNODDER Stefaan; Wojciech Dec
>>>>>> (wdec); Sanjay Wadhwa
>>>>>> Cc: ancp@ietf.org
>>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>>> Control
>>>>>> Extensions
>>>>>>
>>>>>> Hi Phil,
>>>>>>     please see inline.
>>>>>>
>>>>>> Regards,
>>>>>> Roberta
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philippe Champagne (pchamp) [mailto:pchamp@cisco.com]
>>>>>> Sent: Tuesday, October 14, 2008 2:50 PM
>>>>>> To: Maglione Roberta; DE CNODDER Stefaan; Wojciech Dec (wdec);  
>>>>>> Sanjay
>>>>>> Wadhwa
>>>>>> Cc: ancp@ietf.org
>>>>>> Subject: RE: Proposal for changing messages names in Multicast  
>>>>>> Control
>>>>>> Extensions
>>>>>>
>>>>>>
>>>>>>> I'm ok with those renaming.
>>>>>> [RM] Great
>>>>>>
>>>>>>> Do you mean that when the ANCP client ask authorization for a  
>>>>>>> Join,
>>>>>>> its request is a Multicast Replication Control Message and the  
>>>>>>> reply
>>>>>>> from the server is the same or different:____
>>>>>>
>>>>>> [RM] not exactly, what I meant is slightly different:  when an  
>>>>>> ANCP
>>>>>> client asks for authorization to Join a multicast flow, it uses  
>>>>>> an ANCP
>>>>>
>>>>>> message (not defined yet), while when the server replies to the
>>>>>> authorization message sent by the client it could use a Multicast
>>>>>> Replication Control Message
>>>>>>
>>>>>>> While if the server is sending
>>>>>>> a directive to the ANCP client to have a port join a
>>>>>> multicast, do you
>>>>>>> mean this is also called Multicast Replication Control Message?
>>>>>>
>>>>>> [RM] yes this is current scenario where the server uses a  
>>>>>> Multicast
>>>>>> Replication Control Message to send a directive to the ANCP  
>>>>>> client to
>>>>>> have a port join or leave a multicast flow.
>>>>>> Does it make sense?
>>>>>>
>>>>>> Thanks,
>>>>>> Roberta
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Maglione Roberta  
>>>>>>> [mailto:roberta.maglione@telecomitalia.it]
>>>>>>> Sent: Tuesday, October 14, 2008 7:46 AM
>>>>>>> To: Philippe Champagne (pchamp); 'DE CNODDER Stefaan';  
>>>>>>> Wojciech Dec
>>>>>>> (wdec); 'Sanjay Wadhwa'
>>>>>>> Subject: Proposal for changing messages names in Multicast  
>>>>>>> Control
>>>>>>> Extensions
>>>>>>>
>>>>>>>
>>>>>>> Hello,
>>>>>>>     I'm currently merging draft-ancp-mc-extensions with
>>>>>>> draft-ietf-ancp-protocol, and I am thinking it could be useful  
>>>>>>> to
>>>>>>> simplify the terminology in terms of multicast message names.
>>>>>>> In particular I'd like to rename:
>>>>>>> - Multicast Replication Control Request Message in just  
>>>>>>> Multicast
>>>>>>> Replication Control Message
>>>>>>> - Multicast Status Response Message and in Multicast Status  
>>>>>>> Message
>>>>>>>
>>>>>>> This change would allow re-using the same message type for  
>>>>>>> different
>>>>>>> purposes/use cases if needed in future, without affecting  
>>>>>>> current
>>>>>>> scenario.
>>>>>>>
>>>>>>> Please let me know what's your opinion on this proposal.
>>>>>>>
>>>>>>> Thanks and best regards,
>>>>>>>
>>>>>>> Roberta
>>>>>>>
>>>>>>>
>>>>>>> CONFIDENTIALITY NOTICE
>>>>>>>
>>>>>>> This message and its attachments are addressed solely to the  
>>>>>>> persons
>>>>>>> above and may contain confidential information. If you have  
>>>>>>> received
>>>>>>> the message in error, be informed that any use of the content
>>>>>> hereof is
>>>>>>> prohibited. Please return it immediately to the sender and  
>>>>>>> delete the
>>>>>>> message. Should you have any questions, please contact us by  
>>>>>>> replying
>>>>>>> to webmaster@telecomitalia.it.
>>>>>>>
>>>>>>>     Thank you
>>>>>>>
>>>>>>>                                     www.telecomitalia.it
>>>>>>>
>>>>>>
>>>>>>
>>>>>> CONFIDENTIALITY NOTICE
>>>>>>
>>>>>> This message and its attachments are addressed solely to the  
>>>>>> persons
>>>>>> above and may contain confidential information. If you have  
>>>>>> received
>>>>>> the message in error, be informed that any use of the content  
>>>>>> hereof is
>>>>>
>>>>>> prohibited. Please return it immediately to the sender and  
>>>>>> delete the
>>>>>> message. Should you have any questions, please contact us by  
>>>>>> replying
>>>>>> to webmaster@telecomitalia.it.
>>>>>>
>>>>>>     Thank you
>>>>>>
>>>>>>                                     www.telecomitalia.it
>>>>>>
>>>>> _______________________________________________
>>>>> ANCP mailing list
>>>>> ANCP@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ancp
>>>>
>>>
>>
>


--Apple-Mail-2-1020743513
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Philippe, =
Stefaan,<div><br><div><div>On 15 Oct 2008, at 20:08, Philippe Champagne =
(pchamp) wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"> <div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008">Hi Stefaan</span></font></div> <div =
dir=3D"ltr" align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"><span class=3D"439305517-15102008"></span></font>&nbsp;</div> =
<div dir=3D"ltr" align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"><span class=3D"439305517-15102008">I think it could go this =
way:</span></font></div> <div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008"></span></font>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008">Either the AN also sends the Leave to the =
NAS - which will be processed serially by the NAS after the Join, and =
the NAS therefore will reply for the leave shortly after. In this case, =
the AN gets a leave.</span></font></div> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008">or</span></font></div> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008">The AN does not sends the Leave to the NAS =
but holds it for a specific time (the time we should expect such join =
from the server). </span></font></div> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008"></span></font>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008">For the fire and forget, I personally =
prefer the first option, I mean, if we have to have the AN holding info, =
might as well be the whole thing where&nbsp;it knows also about the =
JOIN&nbsp;sent&nbsp;shortly before for which&nbsp;it is awaiting a =
response.</span></font></div> <div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"439305517-15102008"></span></font>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"439305517-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">The question is then, which way to =
go?&nbsp; Can we allow "fire and forget" and "remember the states" to =
both be used at the discretion of the implementor of the ANCP client or =
do we force one way to go.&nbsp; </font></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"439305517-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">It depends if the ANCP server needs to know =
about bandwidth&nbsp;usage&nbsp;for bandwidth requirement decision, in =
which case, it would need to know about Leave as well, isn't =
it?&nbsp;&nbsp; Can that behavior (bandwith decision)&nbsp;be =
configurable, allowing&nbsp;"remember the states" (where Leaves are not =
necessarily&nbsp;forwarded) to exist in other deployment =
model?</font></span></div></div></blockquote><div><br></div><div>I&nbsp;wo=
uld&nbsp;say that we already have a model to allow the AN to operate =
fairly autonomously (ie Black List &amp; White-List + Bandwidth =
delegation). In that model, the NAS does not need to track all =
join/leaves and we take advantage of that to have AN handles Join/Leave =
without having to keep NAS aware of all =
that..</div><div><br></div><div>The Admission Control request that we =
are discussing in the thread is associated with the Grey-List Model =
where the NAS is likely to need to track all join/leaves (eg because =
admission control is performed by NAS or Policy Server, perhaps for =
accounting reason, perhaps for conditional access). So to mimimze the =
number of options, I&nbsp;would&nbsp;suggest that in this case of =
Grey-List operation, we only allow a single behavior whereby the AN =
conveys all the Leave/Join transitions to NAS.</div><div>Note that the =
AN may use some liberty in how it does that (eg. it may optionally wait =
a little bit on receipt of a Leave to see if a Join is not immediately =
following to bundle that in a single ANCP request, it may decide to =
remember the state for a while or until it gets a response,...) but I =
would suggest that no matter =
what&nbsp;the&nbsp;AN&nbsp;should&nbsp;always convey all Join/Leave =
transitions (in this Grey-List Model).</div><div><br></div><div>Makes =
sense?</div><div><br></div><div>Francois</div><div><br></div><br><blockquo=
te type=3D"cite"><div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font>&nbsp;</div> <div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font>&nbsp;</div><br> =
<blockquote dir=3D"ltr" style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">  <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
 <hr tabindex=3D"-1">  <font face=3D"Tahoma" size=3D"2"><b>From:</b> DE =
CNODDER Stefaan   [<a =
href=3D"mailto:stefaan.de_cnodder@alcatel-lucent.be">mailto:stefaan.de_cno=
dder@alcatel-lucent.be</a>] <br><b>Sent:</b> Wednesday,   October 15, =
2008 12:08 PM<br><b>To:</b> Francois Le Faucheur   =
(flefauch)<br><b>Cc:</b> <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a>; Philippe Champagne   =
(pchamp)<br><b>Subject:</b> RE: [ANCP] Proposal for changing messages =
names in   Multicast Control Extensions<br></font><br></div>  =
<div></div>  <div dir=3D"ltr" align=3D"left"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">About the "fire and forget".&nbsp; I like =
it a lot   because of its simplicity but it has an =
issue:</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">1) user sends join matching grey =
list</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">2) AN sends admission request to NAS and forgets about   =
it</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">3) user sends leave, which is not doing anything since   the =
NAS has not replied yet</font></span></div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">4) AN receives possitive answer to join the =
  stream</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">In this case the multicast flow is =
replicated to the line   although the user had sent a =
leave.</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">First processing the Result field without =
knowing what   the message is about looks to me like a strange way of =
processing, but it   works.&nbsp; However, just using a different =
message type would make it easier   according to me.&nbsp; No need to =
repeat all commands or even no need to   repeat the port id, so not much =
re-use anyhow.</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">If the "fire and forget" method would work, =
there is not   really a response, and the current message as defined =
today is sufficient, but   in the above case I have some =
doubts.</font></span></div>  <div dir=3D"ltr" align=3D"left"><span =
class=3D"935315915-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><span class=3D"935315915-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">regards,</font></span></div>  <div =
dir=3D"ltr" align=3D"left"><span class=3D"935315915-15102008"><font =
face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Stefaan</font></span></div><br>  <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
 <hr tabindex=3D"-1">  <font face=3D"Tahoma" size=3D"2"><b>From:</b> =
Francois Le Faucheur IMAP   [<a =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</a>] =
<br><b>Sent:</b> woensdag 15 oktober 2008   17:53<br><b>To:</b> DE =
CNODDER Stefaan<br><b>Cc:</b> Francois Le Faucheur   IMAP; <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a>; Philippe (pchamp) =
Champagne<br><b>Subject:</b> Re: [ANCP]   Proposal for changing messages =
names in Multicast Control   Extensions<br></font><br></div>  =
<div></div>Hi Stefaan,   <div><br>  <div>  <div>On 15 Oct 2008, at =
16:36, DE CNODDER Stefaan wrote:</div><br =
class=3D"Apple-interchange-newline">  <blockquote type=3D"cite">    <div =
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">    <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font>&nbsp;</div>    <div dir=3D"ltr" align=3D"left"><span =
class=3D"503243114-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Francois,</font></span></div>    <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div>    <div =
dir=3D"ltr" align=3D"left"><span class=3D"503243114-15102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">If it is&nbsp;a request, =
then&nbsp;the AN&nbsp;just     executes the commands.&nbsp; If it is a =
response, then I would think it has     to look up the state indexed by =
trans id to clean it up, and to execute the     join which is in that =
state.</font></span></div></div></blockquote>  <div><br></div>  =
<div>First, just to make sure we don't lose the first point: if the AN =
needs   to know whether it is a request or a response, it could do so =
via the Result   code.</div>  <div><br></div>  <div>Now regarding =
whether AN needs to know, that may be implementation   dependent.</div>  =
<div>One model could be as you described above, in which case AN needs =
to   know.</div>  <div>Another model could be where the AN operates in a =
simpler "Fire and   Forget" mode:</div>  <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* AN sends   =
admission request (and AN increments its Transaction ID value)</div>  =
<div><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* =
AN forgets   about it (AN relies on TCP to make sure request reached NAS =
and relies on ANCP   behavior to get a response)</div>  <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* when AN =
gets   a Multicast Replication message, it just executes. A key =
assumption here is   that the multicast replication control message =
contains all the information   necessary for execution&nbsp;(eg "add =
channel C to port P")</div>  <div><br></div>  <div>Makes sense?</div>  =
<div><br></div>  <div>Francois</div>  <div><br></div><br>  <blockquote =
type=3D"cite">    <div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space">    <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">&nbsp; So yes, it looks to me that both are =
    different.&nbsp; Also the processing of the trans id is     =
different&nbsp;because for requests it has to check whether it is each =
time     incremented by 1, which it does not have to do for     =
responses.</font></span></div>    <div dir=3D"ltr" align=3D"left"><span =
class=3D"503243114-15102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div>    <div dir=3D"ltr" =
align=3D"left"><span class=3D"503243114-15102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">regards,</font></span></div>    <div =
dir=3D"ltr" align=3D"left"><span class=3D"503243114-15102008"><font =
face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Stefaan</font></span></div><br>    <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
   <hr tabindex=3D"-1">    <font face=3D"Tahoma" size=3D"2"><b>From:</b> =
Francois Le Faucheur IMAP [<a =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</a>]     =
<br><b>Sent:</b> woensdag 15 oktober 2008 16:27<br><b>To:</b> Francois =
Le     Faucheur IMAP<br><b>Cc:</b> DE CNODDER Stefaan; <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br><b>Subject:</b> Re: =
[ANCP]     Proposal for changing messages names in Multicast Control     =
Extensions<br></font><br></div>    <div></div>    <div>    <blockquote =
type=3D"cite">      <div>      <blockquote type=3D"cite">        =
<blockquote type=3D"cite"><font class=3D"Apple-style-span" =
color=3D"#006312"><br></font><br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">If a message =
can be used as both a request and           a reply, is the =
defitions<br></blockquote></blockquote>      <blockquote type=3D"cite">  =
      <blockquote type=3D"cite">of the Transaction Identifier still =
accurate?           &nbsp;Currently the draft =
says:<br></blockquote></blockquote>      <blockquote type=3D"cite">      =
  <blockquote type=3D"cite"><br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">- trans id =
in request is linearly           incrementing, and is per message =
type<br></blockquote></blockquote>      <blockquote type=3D"cite">       =
 <blockquote type=3D"cite">- trans id in response is copied from         =
  request<br></blockquote></blockquote>      <blockquote type=3D"cite">  =
      <blockquote type=3D"cite"><br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">If the same =
message type can be both request           and response, then how =
will<br></blockquote></blockquote>      <blockquote type=3D"cite">       =
 <blockquote type=3D"cite">the trans id behave? &nbsp;Should the =
receiver           first try to find out =
whether<br></blockquote></blockquote>      <blockquote type=3D"cite">    =
    <blockquote type=3D"cite">it is a request or a response, and then    =
       process it accordingly? &nbsp;Or =
how<br></blockquote></blockquote>      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">should it then =
work?<br></blockquote></blockquote>      <blockquote =
type=3D"cite"><br></blockquote><br>Oops, there was a typo in       =
earlier message. This should read:<br>One option would be for the =
receiver       to look at the Result field:<br><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Success/Failure, then       this message is a "response" to an =
earlier request (and its Transaction ID       echoed the one of the =
request)<br><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: =
pre"></span>* if it is set to Ack/Nack, then this       messages is a =
"request" (and the transaction ID was generated by remote       =
end)</div></blockquote>    <div><br></div>    <div>Note also that the AN =
may not even care that much whether it is a     response or a =
spontaneous request, because the two are idempotent.</div>    =
<div><br></div>    <div>Francois</div>    <div><br></div><br>    =
<blockquote type=3D"cite">      <div><br><br>      <blockquote =
type=3D"cite">One option would be for the sender to look at         the =
Result field:<br></blockquote>      <blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Success/Failure, then         this message is a "response" to an =
earlier request (and its Transaction         ID echoed the one of the =
request)<br></blockquote>      <blockquote type=3D"cite"><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* if it is =
set to Ack/Nack, then this         messages is a request (and the =
transaction ID was generated by remote         end)<br></blockquote>     =
 <blockquote type=3D"cite"><br></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite">regards,<br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite">Stefaan<br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">-----Original       =
Message-----<br></blockquote></blockquote>      <blockquote type=3D"cite">=
        <blockquote type=3D"cite">From: Philippe Champagne (pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote>      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Sent: dinsdag 14 oktober 2008         =
15:33<br></blockquote></blockquote>      <blockquote type=3D"cite">      =
  <blockquote type=3D"cite">To: Maglione Roberta; DE CNODDER Stefaan;    =
       Wojciech Dec (wdec); Sanjay<br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te>      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">Subject: RE: Proposal for changing messages           =
names in Multicast Control<br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">Ok, just wanted to make =
sure what you           meant.<br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">So, this means a =
Multicast Replication Control           Message would be =
used<br></blockquote></blockquote>      <blockquote type=3D"cite">       =
 <blockquote type=3D"cite">both as a reply to an authorization as well =
as           a directive. &nbsp;I tend to<br></blockquote></blockquote>  =
    <blockquote type=3D"cite">        <blockquote type=3D"cite">agree =
with this, although, we might review           that case when we define =
the<br></blockquote></blockquote>      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">authorization message and if the reply from    =
       the server would carry<br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">roughly the =
same information as the directive.           I would assume it =
would.<br></blockquote></blockquote>      <blockquote type=3D"cite">     =
   <blockquote type=3D"cite"><br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">-----Original         =
Message-----<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">From: Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">Sent: Tuesday, October 14, 2008 9:22           =
AM<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">To: Philippe Champagne (pchamp); DE CNODDER             =
Stefaan; Wojciech Dec<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">(wdec); Sanjay         =
Wadhwa<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote>      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote type=3D"cite">Subject: RE: Proposal =
for changing messages             names in Multicast =
Control<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">Hi =
Phil,<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see             =
inline.<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote =
type=3D"cite">Regards,<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">-----Original         =
Message-----<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">From: Philippe Champagne (pchamp) [<a =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</a>]<br></blockqu=
ote></blockquote></blockquote>      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote type=3D"cite">Sent: =
Tuesday, October 14, 2008 2:50           =
PM<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">To: Maglione Roberta; DE CNODDER Stefaan;             =
Wojciech Dec (wdec); Sanjay<br></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote =
type=3D"cite">Wadhwa<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br></blockquote></blockquo=
te></blockquote>      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">          <blockquote type=3D"cite">Subject: RE: Proposal =
for changing messages             names in Multicast =
Control<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">I'm ok =
with those           =
renaming.<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">[RM]       =
Great<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">Do you =
mean that when the ANCP client ask               authorization for a     =
  Join,<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">its =
request is a Multicast Replication               Control Message and the =
      reply<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">from the =
server is the same or               =
different:____<br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">[RM] not exactly, what I meant is slightly     =
        different: &nbsp;when an =
ANCP<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">client asks for authorization to Join a             =
multicast flow, it uses an =
ANCP<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">message (not defined yet), while when the             =
server replies to the<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">authorization message sent by the client it    =
         could use a =
Multicast<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">Replication Control         =
Message<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">While if =
the server is             =
sending<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">a =
directive to the ANCP client to have a               port join =
a<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">multicast, do       =
you<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">            <blockquote type=3D"cite">mean this is also =
called Multicast               Replication Control       =
Message?<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">[RM] yes this is current scenario where the    =
         server uses a =
Multicast<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">Replication Control Message to send a             =
directive to the ANCP client =
to<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">have a port join or leave a multicast             =
flow.<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">Does it make       =
sense?<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote =
type=3D"cite">Thanks,<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">-----Original           =
Message-----<br></blockquote></blockquote></blockquote></blockquote>     =
 <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">From: =
Maglione Roberta [<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@=
telecomitalia.it</a>]<br></blockquote></blockquote></blockquote></blockquo=
te>      <blockquote type=3D"cite">        <blockquote type=3D"cite">    =
      <blockquote type=3D"cite">            <blockquote =
type=3D"cite">Sent: Tuesday, October 14, 2008 7:46             =
AM<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">To: =
Philippe Champagne (pchamp); 'DE               CNODDER Stefaan'; =
Wojciech       =
Dec<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">(wdec); =
'Sanjay           =
Wadhwa'<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">Subject: =
Proposal for changing messages               names in Multicast       =
Control<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">Extensions<br></blockquote></blockquote></blockquote></block=
quote>      <blockquote type=3D"cite">        <blockquote type=3D"cite"> =
         <blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">Hello,<br></blockquote></blockquote></blockquote></blockquot=
e>      <blockquote type=3D"cite">        <blockquote type=3D"cite">     =
     <blockquote type=3D"cite">            <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm currently               =
merging draft-ancp-mc-extensions         =
with<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">draft-ietf-ancp-protocol, and I am               thinking =
it could be useful       =
to<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">simplify =
the terminology in terms of               multicast message       =
names.<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">In =
particular I'd like to             =
rename:<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">- =
Multicast Replication Control Request               Message in just      =
 Multicast<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">Replication Control           =
Message<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">- =
Multicast Status Response Message and in               Multicast Status  =
     Message<br></blockquote></blockquote></blockquote></blockquote>     =
 <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">This =
change would allow re-using the same               message type for      =
 different<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">purposes/use cases if needed in future,               =
without affecting       =
current<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">scenario.<br></blockquote></blockquote></blockquote></blockq=
uote>      <blockquote type=3D"cite">        <blockquote type=3D"cite">  =
        <blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">Please =
let me know what's your opinion on               this =
proposal.<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">Thanks =
and best           =
regards,<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">Roberta<br></blockquote></blockquote></blockquote></blockquo=
te>      <blockquote type=3D"cite">        <blockquote type=3D"cite">    =
      <blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">CONFIDENTIALITY           =
NOTICE<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">This =
message and its attachments are               addressed solely to the    =
     persons<br></blockquote></blockquote></blockquote></blockquote>     =
 <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">above =
and may contain confidential               information. If you have      =
   received<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">the =
message in error, be informed that any               use of the =
content<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">hereof       =
is<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">            <blockquote type=3D"cite">prohibited. Please =
return it immediately               to the sender and delete       =
the<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">message. =
Should you have any questions,               please contact us by       =
replying<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank             =
you<br></blockquote></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">            <blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">            <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote>   =
   <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite"><br></blockquote></blockquote></blockquote>    =
  <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">CONFIDENTIALITY         =
NOTICE<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">This message and its attachments are           =
  addressed solely to the =
persons<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">above and may contain confidential             =
information. If you have       =
received<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">the message in error, be informed that any             use =
of the content hereof is<br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite"><br></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">prohibited. Please return it immediately to             =
the sender and delete the<br></blockquote></blockquote></blockquote>     =
 <blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">message. Should you have any questions,        =
     please contact us by =
replying<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite">to <a =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</a>.=
<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank           =
you<br></blockquote></blockquote></blockquote>      <blockquote =
type=3D"cite">        <blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite">          =
<blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;<a =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</a><br></blockqu=
ote></blockquote></blockquote>      <blockquote type=3D"cite">        =
<blockquote type=3D"cite">          <blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote>      <blockquote type=3D"cite">        <blockquote =
type=3D"cite">ANCP mailing list<br></blockquote></blockquote>      =
<blockquote type=3D"cite">        <blockquote type=3D"cite"><a =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br></blockquote></blockquo=
te>      <blockquote type=3D"cite">        <blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><br></blockquote></blockquote>      <blockquote =
type=3D"cite"><br></blockquote><br></div></blockquote></div><br></div></bl=
ockquote></div><br></div></blockquote></div></blockquote></div><br></div><=
/body></html>=

--Apple-Mail-2-1020743513--

--===============0203618941==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0203618941==--


From ancp-bounces@ietf.org  Thu Oct 16 04:44:20 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C46E33A6B74;
	Thu, 16 Oct 2008 04:44:20 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C2B213A6B70
	for <ancp@core3.amsl.com>; Thu, 16 Oct 2008 04:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 gSmcDBMahqtg for <ancp@core3.amsl.com>;
	Thu, 16 Oct 2008 04:44:17 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 148133A6AC0
	for <ancp@ietf.org>; Thu, 16 Oct 2008 04:44:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,422,1220227200"; 
	d="scan'208,217";a="108905353"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 16 Oct 2008 11:45:13 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9GBjDXp020319; 
	Thu, 16 Oct 2008 04:45:13 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9GBjD1Q026940;
	Thu, 16 Oct 2008 11:45:13 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 04:45:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 16 Oct 2008 04:45:11 -0700
Message-ID: <48214755113BB04F84D958B4F0DE261C06935412@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <68005082-BEE6-4215-8F68-509C047EDE28@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Proposal for changing messages names in Multicast Control
	Extensions
Thread-Index: AckvXmyHRoRNWxwBSeO5WMsJQKpU9wAJaujQ
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
	<87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
	<48214755113BB04F84D958B4F0DE261C069350E2@xmb-sjc-222.amer.cisco.com>
	<68005082-BEE6-4215-8F68-509C047EDE28@cisco.com>
From: "Philippe Champagne (pchamp)" <pchamp@cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 16 Oct 2008 11:45:13.0743 (UTC)
	FILETIME=[A6CD49F0:01C92F84]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=67721; t=1224157513;
	x=1225021513; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pchamp@cisco.com;
	z=From:=20=22Philippe=20Champagne=20(pchamp)=22=20<pchamp@ci
	sco.com>
	|Subject:=20RE=3A=20[ANCP]=20Proposal=20for=20changing=20me
	ssages=20names=20in=20Multicast=20Control=20Extensions
	|Sender:=20; bh=JbVS82NEclT88Lb1GgrquGLNVOuHy5dABXgDg46OuVk=;
	b=bDCd5ycowS+oaCF5sIpS3zU6ijNf1atSpM9J9QMTP2lOkMVFXneFuRxOok
	E/OWL1XX35k/Fgu72ZIqBeWEBKq3NnfXT9vdcKHbshxD8pjX6RHEjBxYUP9O
	LzLi0VeMbGJYaRUiO2ujuB0ihNwI7d1vktsfiJUAGA4LasV9/ftOI=;
Authentication-Results: sj-dkim-1; header.From=pchamp@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0384715801=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0384715801==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92F84.A6668081"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92F84.A6668081
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes, that's true, I forgot to mention the greylist as the white list
makes the AN able to operate autonomously.
And yes, I think it make more sense for the AN to sends the leaves as
well.
=20
=20


________________________________

	From: Francois Le Faucheur (flefauch)=20
	Sent: Thursday, October 16, 2008 3:11 AM
	To: Philippe Champagne (pchamp)
	Cc: Francois Le Faucheur (flefauch); DE CNODDER Stefaan;
ancp@ietf.org
	Subject: Re: [ANCP] Proposal for changing messages names in
Multicast Control Extensions
=09
=09
	Philippe, Stefaan,=20

	On 15 Oct 2008, at 20:08, Philippe Champagne (pchamp) wrote:


		Hi Stefaan
		=20
		I think it could go this way:
		=20
		Either the AN also sends the Leave to the NAS - which
will be processed serially by the NAS after the Join, and the NAS
therefore will reply for the leave shortly after. In this case, the AN
gets a leave.
		or
		The AN does not sends the Leave to the NAS but holds it
for a specific time (the time we should expect such join from the
server).=20
		=20
		For the fire and forget, I personally prefer the first
option, I mean, if we have to have the AN holding info, might as well be
the whole thing where it knows also about the JOIN sent shortly before
for which it is awaiting a response.
		=20
		The question is then, which way to go?  Can we allow
"fire and forget" and "remember the states" to both be used at the
discretion of the implementor of the ANCP client or do we force one way
to go. =20
		It depends if the ANCP server needs to know about
bandwidth usage for bandwidth requirement decision, in which case, it
would need to know about Leave as well, isn't it?   Can that behavior
(bandwith decision) be configurable, allowing "remember the states"
(where Leaves are not necessarily forwarded) to exist in other
deployment model?


	I would say that we already have a model to allow the AN to
operate fairly autonomously (ie Black List & White-List + Bandwidth
delegation). In that model, the NAS does not need to track all
join/leaves and we take advantage of that to have AN handles Join/Leave
without having to keep NAS aware of all that..

	The Admission Control request that we are discussing in the
thread is associated with the Grey-List Model where the NAS is likely to
need to track all join/leaves (eg because admission control is performed
by NAS or Policy Server, perhaps for accounting reason, perhaps for
conditional access). So to mimimze the number of options, I would
suggest that in this case of Grey-List operation, we only allow a single
behavior whereby the AN conveys all the Leave/Join transitions to NAS.
	Note that the AN may use some liberty in how it does that (eg.
it may optionally wait a little bit on receipt of a Leave to see if a
Join is not immediately following to bundle that in a single ANCP
request, it may decide to remember the state for a while or until it
gets a response,...) but I would suggest that no matter what the AN
should always convey all Join/Leave transitions (in this Grey-List
Model).

	Makes sense?

	Francois



		=20
		=20


________________________________

			From: DE CNODDER Stefaan
[mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
			Sent: Wednesday, October 15, 2008 12:08 PM
			To: Francois Le Faucheur (flefauch)
			Cc: ancp@ietf.org; Philippe Champagne (pchamp)
			Subject: RE: [ANCP] Proposal for changing
messages names in Multicast Control Extensions
		=09
		=09
			=20
			About the "fire and forget".  I like it a lot
because of its simplicity but it has an issue:
			=20
			1) user sends join matching grey list
			2) AN sends admission request to NAS and forgets
about it
			3) user sends leave, which is not doing anything
since the NAS has not replied yet
			4) AN receives possitive answer to join the
stream
			=20
			In this case the multicast flow is replicated to
the line although the user had sent a leave.
			=20
			First processing the Result field without
knowing what the message is about looks to me like a strange way of
processing, but it works.  However, just using a different message type
would make it easier according to me.  No need to repeat all commands or
even no need to repeat the port id, so not much re-use anyhow.
			=20
			If the "fire and forget" method would work,
there is not really a response, and the current message as defined today
is sufficient, but in the above case I have some doubts.
			=20
			regards,
			Stefaan

________________________________

			From: Francois Le Faucheur IMAP
[mailto:flefauch@cisco.com]=20
			Sent: woensdag 15 oktober 2008 17:53
			To: DE CNODDER Stefaan
			Cc: Francois Le Faucheur IMAP; ancp@ietf.org;
Philippe (pchamp) Champagne
			Subject: Re: [ANCP] Proposal for changing
messages names in Multicast Control Extensions
		=09
		=09
			Hi Stefaan,=20

			On 15 Oct 2008, at 16:36, DE CNODDER Stefaan
wrote:


				=20
				Francois,
				=20
				If it is a request, then the AN just
executes the commands.  If it is a response, then I would think it has
to look up the state indexed by trans id to clean it up, and to execute
the join which is in that state.


			First, just to make sure we don't lose the first
point: if the AN needs to know whether it is a request or a response, it
could do so via the Result code.

			Now regarding whether AN needs to know, that may
be implementation dependent.
			One model could be as you described above, in
which case AN needs to know.
			Another model could be where the AN operates in
a simpler "Fire and Forget" mode:
			* AN sends admission request (and AN increments
its Transaction ID value)
			* AN forgets about it (AN relies on TCP to make
sure request reached NAS and relies on ANCP behavior to get a response)
			* when AN gets a Multicast Replication message,
it just executes. A key assumption here is that the multicast
replication control message contains all the information necessary for
execution (eg "add channel C to port P")

			Makes sense?

			Francois



				  So yes, it looks to me that both are
different.  Also the processing of the trans id is different because for
requests it has to check whether it is each time incremented by 1, which
it does not have to do for responses.
				=20
				regards,
				Stefaan

________________________________

				From: Francois Le Faucheur IMAP
[mailto:flefauch@cisco.com]=20
				Sent: woensdag 15 oktober 2008 16:27
				To: Francois Le Faucheur IMAP
				Cc: DE CNODDER Stefaan; ancp@ietf.org
				Subject: Re: [ANCP] Proposal for
changing messages names in Multicast Control Extensions
			=09
			=09

			=09
			=09
			=09

				If a message can be used as both a
request and a reply, is the defitions
			=09

				of the Transaction Identifier still
accurate?  Currently the draft says:
			=09


				- trans id in request is linearly
incrementing, and is per message type
			=09

				- trans id in response is copied from
request
			=09


				If the same message type can be both
request and response, then how will
			=09

				the trans id behave?  Should the
receiver first try to find out whether
			=09

				it is a request or a response, and then
process it accordingly?  Or how
			=09

				should it then work?
			=09



				Oops, there was a typo in earlier
message. This should read:
				One option would be for the receiver to
look at the Result field:
				* if it is set to Success/Failure, then
this message is a "response" to an earlier request (and its Transaction
ID echoed the one of the request)
				* if it is set to Ack/Nack, then this
messages is a "request" (and the transaction ID was generated by remote
end)


				Note also that the AN may not even care
that much whether it is a response or a spontaneous request, because the
two are idempotent.

				Francois





				One option would be for the sender to
look at the Result field:
			=09

				* if it is set to Success/Failure, then
this message is a "response" to an earlier request (and its Transaction
ID echoed the one of the request)
			=09

				* if it is set to Ack/Nack, then this
messages is a request (and the transaction ID was generated by remote
end)
			=09




				regards,
			=09

				Stefaan
			=09



				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: dinsdag 14 oktober 2008 15:33
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				Ok, just wanted to make sure what you
meant.
			=09


				So, this means a Multicast Replication
Control Message would be used
			=09

				both as a reply to an authorization as
well as a directive.  I tend to
			=09

				agree with this, although, we might
review that case when we define the
			=09

				authorization message and if the reply
from the server would carry
			=09

				roughly the same information as the
directive. I would assume it would.
			=09




				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 9:22 AM
			=09

				To: Philippe Champagne (pchamp); DE
CNODDER Stefaan; Wojciech Dec
			=09

				(wdec); Sanjay Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09


				Hi Phil,
			=09

				    please see inline.
			=09


				Regards,
			=09

				Roberta
			=09


				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: Tuesday, October 14, 2008 2:50 PM
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				I'm ok with those renaming.
			=09

				[RM] Great
			=09


				Do you mean that when the ANCP client
ask authorization for a Join,
			=09

				its request is a Multicast Replication
Control Message and the reply
			=09

				from the server is the same or
different:____
			=09


				[RM] not exactly, what I meant is
slightly different:  when an ANCP
			=09

				client asks for authorization to Join a
multicast flow, it uses an ANCP
			=09


				message (not defined yet), while when
the server replies to the
			=09

				authorization message sent by the client
it could use a Multicast
			=09

				Replication Control Message
			=09


				While if the server is sending
			=09

				a directive to the ANCP client to have a
port join a
			=09

				multicast, do you
			=09

				mean this is also called Multicast
Replication Control Message?
			=09


				[RM] yes this is current scenario where
the server uses a Multicast
			=09

				Replication Control Message to send a
directive to the ANCP client to
			=09

				have a port join or leave a multicast
flow.
			=09

				Does it make sense?
			=09


				Thanks,
			=09

				Roberta
			=09





				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 7:46 AM
			=09

				To: Philippe Champagne (pchamp); 'DE
CNODDER Stefaan'; Wojciech Dec
			=09

				(wdec); 'Sanjay Wadhwa'
			=09

				Subject: Proposal for changing messages
names in Multicast Control
			=09

				Extensions
			=09



				Hello,
			=09

				    I'm currently merging
draft-ancp-mc-extensions with
			=09

				draft-ietf-ancp-protocol, and I am
thinking it could be useful to
			=09

				simplify the terminology in terms of
multicast message names.
			=09

				In particular I'd like to rename:
			=09

				- Multicast Replication Control Request
Message in just Multicast
			=09

				Replication Control Message
			=09

				- Multicast Status Response Message and
in Multicast Status Message
			=09


				This change would allow re-using the
same message type for different
			=09

				purposes/use cases if needed in future,
without affecting current
			=09

				scenario.
			=09


				Please let me know what's your opinion
on this proposal.
			=09


				Thanks and best regards,
			=09


				Roberta
			=09



				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content
			=09

				hereof is
			=09

				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09




				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content hereof is
			=09


				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09


=09
_______________________________________________
			=09

				ANCP mailing list
			=09

				ANCP@ietf.org
			=09

=09
https://www.ietf.org/mailman/listinfo/ancp
			=09







------_=_NextPart_001_01C92F84.A6668081
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D451144111-16102008>Yes, that's true, I forgot to&nbsp;mention =
the greylist=20
as the white list makes the AN able to operate =
autonomously.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D451144111-16102008>And yes, I think it make more sense for the =
AN to sends=20
the leaves as well.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D451144111-16102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur =
(flefauch)=20
  <BR><B>Sent:</B> Thursday, October 16, 2008 3:11 AM<BR><B>To:</B> =
Philippe=20
  Champagne (pchamp)<BR><B>Cc:</B> Francois Le Faucheur (flefauch); DE =
CNODDER=20
  Stefaan; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Proposal for =
changing=20
  messages names in Multicast Control Extensions<BR></FONT><BR></DIV>
  <DIV></DIV>Philippe, Stefaan,
  <DIV><BR>
  <DIV>
  <DIV>On 15 Oct 2008, at 20:08, Philippe Champagne (pchamp) =
wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite">
    <DIV=20
    style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008>Hi Stefaan</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008>I think it could go this =
way:</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008>Either the AN also sends the Leave to the =
NAS -=20
    which will be processed serially by the NAS after the Join, and the =
NAS=20
    therefore will reply for the leave shortly after. In this case, the =
AN gets=20
    a leave.</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008>or</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008>The AN does not sends the Leave to the =
NAS but=20
    holds it for a specific time (the time we should expect such join =
from the=20
    server). </SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008>For the fire and forget, I personally =
prefer the=20
    first option, I mean, if we have to have the AN holding info, might =
as well=20
    be the whole thing where&nbsp;it knows also about the=20
    JOIN&nbsp;sent&nbsp;shortly before for which&nbsp;it is awaiting a=20
    response.</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D439305517-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>The question is then, which way to =
go?&nbsp; Can we=20
    allow "fire and forget" and "remember the states" to both be used at =
the=20
    discretion of the implementor of the ANCP client or do we force one =
way to=20
    go.&nbsp; </FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D439305517-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>It depends if the ANCP server needs to know =
about=20
    bandwidth&nbsp;usage&nbsp;for bandwidth requirement decision, in =
which case,=20
    it would need to know about Leave as well, isn't it?&nbsp;&nbsp; Can =
that=20
    behavior (bandwith decision)&nbsp;be configurable, =
allowing&nbsp;"remember=20
    the states" (where Leaves are not necessarily&nbsp;forwarded) to =
exist in=20
    other deployment model?</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>I&nbsp;would&nbsp;say that we already have a model to allow the =
AN to=20
  operate fairly autonomously (ie Black List &amp; White-List + =
Bandwidth=20
  delegation). In that model, the NAS does not need to track all =
join/leaves and=20
  we take advantage of that to have AN handles Join/Leave without having =
to keep=20
  NAS aware of all that..</DIV>
  <DIV><BR></DIV>
  <DIV>The Admission Control request that we are discussing in the =
thread is=20
  associated with the Grey-List Model where the NAS is likely to need to =
track=20
  all join/leaves (eg because admission control is performed by NAS or =
Policy=20
  Server, perhaps for accounting reason, perhaps for conditional =
access). So to=20
  mimimze the number of options, I&nbsp;would&nbsp;suggest that in this =
case of=20
  Grey-List operation, we only allow a single behavior whereby the AN =
conveys=20
  all the Leave/Join transitions to NAS.</DIV>
  <DIV>Note that the AN may use some liberty in how it does that (eg. it =
may=20
  optionally wait a little bit on receipt of a Leave to see if a Join is =
not=20
  immediately following to bundle that in a single ANCP request, it may =
decide=20
  to remember the state for a while or until it gets a response,...) but =
I would=20
  suggest that no matter what&nbsp;the&nbsp;AN&nbsp;should&nbsp;always =
convey=20
  all Join/Leave transitions (in this Grey-List Model).</DIV>
  <DIV><BR></DIV>
  <DIV>Makes sense?</DIV>
  <DIV><BR></DIV>
  <DIV>Francois</DIV>
  <DIV><BR></DIV><BR>
  <BLOCKQUOTE type=3D"cite">
    <DIV=20
    style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT>&nbsp;</DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> DE CNODDER Stefaan [<A=20
      =
href=3D"mailto:stefaan.de_cnodder@alcatel-lucent.be">mailto:stefaan.de_cn=
odder@alcatel-lucent.be</A>]=20
      <BR><B>Sent:</B> Wednesday, October 15, 2008 12:08 =
PM<BR><B>To:</B>=20
      Francois Le Faucheur (flefauch)<BR><B>Cc:</B> <A=20
      href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A>; Philippe =
Champagne=20
      (pchamp)<BR><B>Subject:</B> RE: [ANCP] Proposal for changing =
messages=20
      names in Multicast Control Extensions<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
      size=3D2></FONT>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>About the "fire and forget".&nbsp; I like =
it a lot=20
      because of its simplicity but it has an issue:</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>1) user sends join matching grey=20
      list</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>2) AN sends admission request to NAS and =
forgets=20
      about it</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>3) user sends leave, which is not doing =
anything=20
      since the NAS has not replied yet</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>4) AN receives possitive answer to join =
the=20
      stream</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>In this case the multicast flow is =
replicated to the=20
      line although the user had sent a leave.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>First processing the Result field without =
knowing=20
      what the message is about looks to me like a strange way of =
processing,=20
      but it works.&nbsp; However, just using a different message type =
would=20
      make it easier according to me.&nbsp; No need to repeat all =
commands or=20
      even no need to repeat the port id, so not much re-use=20
      anyhow.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>If the "fire and forget" method would =
work, there is=20
      not really a response, and the current message as defined today is =

      sufficient, but in the above case I have some =
doubts.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur =
IMAP [<A=20
      href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
      <BR><B>Sent:</B> woensdag 15 oktober 2008 17:53<BR><B>To:</B> DE =
CNODDER=20
      Stefaan<BR><B>Cc:</B> Francois Le Faucheur IMAP; <A=20
      href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A>; Philippe (pchamp) =

      Champagne<BR><B>Subject:</B> Re: [ANCP] Proposal for changing =
messages=20
      names in Multicast Control Extensions<BR></FONT><BR></DIV>
      <DIV></DIV>Hi Stefaan,=20
      <DIV><BR>
      <DIV>
      <DIV>On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:</DIV><BR=20
      class=3DApple-interchange-newline>
      <BLOCKQUOTE type=3D"cite">
        <DIV=20
        style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
        size=3D2></FONT>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just=20
        executes the commands.&nbsp; If it is a response, then I would =
think it=20
        has to look up the state indexed by trans id to clean it up, and =
to=20
        execute the join which is in that=20
      state.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
      <DIV><BR></DIV>
      <DIV>First, just to make sure we don't lose the first point: if =
the AN=20
      needs to know whether it is a request or a response, it could do =
so via=20
      the Result code.</DIV>
      <DIV><BR></DIV>
      <DIV>Now regarding whether AN needs to know, that may be =
implementation=20
      dependent.</DIV>
      <DIV>One model could be as you described above, in which case AN =
needs to=20
      know.</DIV>
      <DIV>Another model could be where the AN operates in a simpler =
"Fire and=20
      Forget" mode:</DIV>
      <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>* AN sends=20
      admission request (and AN increments its Transaction ID =
value)</DIV>
      <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>* AN=20
      forgets about it (AN relies on TCP to make sure request reached =
NAS and=20
      relies on ANCP behavior to get a response)</DIV>
      <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>* when AN=20
      gets a Multicast Replication message, it just executes. A key =
assumption=20
      here is that the multicast replication control message contains =
all the=20
      information necessary for execution&nbsp;(eg "add channel C to =
port=20
      P")</DIV>
      <DIV><BR></DIV>
      <DIV>Makes sense?</DIV>
      <DIV><BR></DIV>
      <DIV>Francois</DIV>
      <DIV><BR></DIV><BR>
      <BLOCKQUOTE type=3D"cite">
        <DIV=20
        style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>&nbsp; So yes, it looks to me that both =
are=20
        different.&nbsp; Also the processing of the trans id is=20
        different&nbsp;because for requests it has to check whether it =
is each=20
        time incremented by 1, which it does not have to do for=20
        responses.</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D503243114-15102008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur =
IMAP [<A=20
        =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
        <BR><B>Sent:</B> woensdag 15 oktober 2008 16:27<BR><B>To:</B> =
Francois=20
        Le Faucheur IMAP<BR><B>Cc:</B> DE CNODDER Stefaan; <A=20
        =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> Re:=20
        [ANCP] Proposal for changing messages names in Multicast Control =

        Extensions<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV>
        <BLOCKQUOTE type=3D"cite">
          <DIV>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><FONT class=3DApple-style-span=20
              color=3D#006312><BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">If a message can be used as both a =
request=20
              and a reply, is the =
defitions<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">of the Transaction Identifier =
still=20
              accurate? &nbsp;Currently the draft=20
says:<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">- trans id in request is linearly=20
              incrementing, and is per message =
type<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">- trans id in response is copied =
from=20
              request<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">If the same message type can be =
both=20
              request and response, then how =
will<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">the trans id behave? &nbsp;Should =
the=20
              receiver first try to find out =
whether<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">it is a request or a response, and =
then=20
              process it accordingly? &nbsp;Or =
how<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">should it then=20
          work?<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE><BR>Oops, there was =
a typo in=20
          earlier message. This should read:<BR>One option would be for =
the=20
          receiver to look at the Result field:<BR><SPAN =
class=3DApple-tab-span=20
          style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure,=20
          then this message is a "response" to an earlier request (and =
its=20
          Transaction ID echoed the one of the request)<BR><SPAN=20
          class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* if =
it is set to=20
          Ack/Nack, then this messages is a "request" (and the =
transaction ID=20
          was generated by remote end)</DIV></BLOCKQUOTE>
        <DIV><BR></DIV>
        <DIV>Note also that the AN may not even care that much whether =
it is a=20
        response or a spontaneous request, because the two are =
idempotent.</DIV>
        <DIV><BR></DIV>
        <DIV>Francois</DIV>
        <DIV><BR></DIV><BR>
        <BLOCKQUOTE type=3D"cite">
          <DIV><BR><BR>
          <BLOCKQUOTE type=3D"cite">One option would be for the sender =
to look=20
            at the Result field:<BR></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
            style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure,=20
            then this message is a "response" to an earlier request (and =
its=20
            Transaction ID echoed the one of the =
request)<BR></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
            style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Ack/Nack, then=20
            this messages is a request (and the transaction ID was =
generated by=20
            remote end)<BR></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite">regards,<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite">Stefaan<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">-----Original=20
          Message-----<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) =
[<A=20
              =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Sent: dinsdag 14 oktober 2008=20
            15:33<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
              Wojciech Dec (wdec); Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Cc: <A=20
              =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =

              messages names in Multicast =
Control<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Ok, just wanted to make sure what =
you=20
              meant.<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">So, this means a Multicast =
Replication=20
              Control Message would be =
used<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">both as a reply to an =
authorization as=20
              well as a directive. &nbsp;I tend =
to<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">agree with this, although, we =
might review=20
              that case when we define the<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">authorization message and if the =
reply=20
              from the server would carry<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">roughly the same information as =
the=20
              directive. I would assume it =
would.<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">-----Original=20
            Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
                =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 =
9:22=20
                AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); =
DE=20
                CNODDER Stefaan; Wojciech=20
          Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">(wdec); Sanjay=20
            Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Cc: <A=20
                =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for =
changing=20
                messages names in Multicast=20
          Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Hi=20
          Phil,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please =
see=20
                inline.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">-----Original=20
            Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">From: Philippe Champagne =
(pchamp) [<A=20
                =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 =
2:50=20
                PM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =

                Stefaan; Wojciech Dec (wdec);=20
          Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Cc: <A=20
                =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for =
changing=20
                messages names in Multicast=20
          Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">I'm ok with those=20
                =
renaming.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">[RM]=20
          Great<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">Do you mean that when the ANCP =
client=20
                  ask authorization for a=20
            =
Join,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">its request is a Multicast =
Replication=20
                  Control Message and the=20
            =
reply<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">from the server is the same or =

                  =
different:____<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">[RM] not exactly, what I meant =
is=20
                slightly different: &nbsp;when an=20
          ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">client asks for authorization to =
Join a=20
                multicast flow, it uses an=20
          ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">message (not defined yet), while =
when=20
                the server replies to =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">authorization message sent by =
the client=20
                it could use a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Replication Control=20
              Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">While if the server is=20
                =
sending<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">a directive to the ANCP client =
to have=20
                  a port join =
a<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">multicast, do=20
            you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">mean this is also called =
Multicast=20
                  Replication Control=20
            =
Message?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">[RM] yes this is current =
scenario where=20
                the server uses a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Replication Control Message to =
send a=20
                directive to the ANCP client=20
          to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">have a port join or leave a =
multicast=20
                flow.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Does it make=20
            sense?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Thanks,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">-----Original=20
                =
Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
                  =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, =
2008 7:46=20
                  =
AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">To: Philippe Champagne =
(pchamp); 'DE=20
                  CNODDER Stefaan'; Wojciech=20
            Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">(wdec); 'Sanjay=20
              =
Wadhwa'<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">Subject: Proposal for changing =

                  messages names in Multicast=20
            =
Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
            =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
            =
type=3D"cite">Hello,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm =
currently=20
                  merging draft-ancp-mc-extensions=20
            with<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">draft-ietf-ancp-protocol, and =
I am=20
                  thinking it could be useful=20
            to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">simplify the terminology in =
terms of=20
                  multicast message=20
          names.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">In particular I'd like to=20
                =
rename:<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">- Multicast Replication =
Control=20
                  Request Message in just=20
            =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">Replication Control=20
                =
Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">- Multicast Status Response =
Message=20
                  and in Multicast Status=20
            =
Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">This change would allow =
re-using the=20
                  same message type for=20
            =
different<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">purposes/use cases if needed =
in=20
                  future, without affecting=20
            =
current<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
            =
type=3D"cite">scenario.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">Please let me know what's your =
opinion=20
                  on this=20
          =
proposal.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">Thanks and best=20
              =
regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
            =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQU=
OTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
              =
NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">This message and its =
attachments are=20
                  addressed solely to the=20
            =
persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">above and may contain =
confidential=20
                  information. If you have=20
            =
received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">the message in error, be =
informed that=20
                  any use of the=20
          =
content<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">hereof=20
          is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">prohibited. Please return it=20
                  immediately to the sender and delete=20
              =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">message. Should you have any=20
                  questions, please contact us by=20
              =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">to <A=20
                  =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
                =
you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
                  =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
                  =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">
                <BLOCKQUOTE=20
          =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
            NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">This message and its attachments =
are=20
                addressed solely to the=20
          persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">above and may contain =
confidential=20
                information. If you have=20
          received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">the message in error, be =
informed that=20
                any use of the content hereof=20
          is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately=20
                to the sender and delete=20
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions,=20
                please contact us by=20
          replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">to <A=20
                =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
              you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
                =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
                =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
              =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">ANCP mailing=20
list<BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><A=20
              =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite"><A=20
              =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></BLOCKQUOTE></BLOCKQUOTE>
          <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE><BR></DIV></BLOCKQUOTE></DIV><BR></DIV></B=
LOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></DIV=
></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C92F84.A6668081--

--===============0384715801==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0384715801==--


From ancp-bounces@ietf.org  Fri Oct 17 02:02:06 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 523623A6A29;
	Fri, 17 Oct 2008 02:02:06 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F9FD3A6A2A
	for <ancp@core3.amsl.com>; Fri, 17 Oct 2008 02:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	HTML_MESSAGE=0.001]
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 4QxkjEktp4J1 for <ancp@core3.amsl.com>;
	Fri, 17 Oct 2008 02:02:02 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id AA92E3A6A06
	for <ancp@ietf.org>; Fri, 17 Oct 2008 02:02:01 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9H91SnT017864; 
	Fri, 17 Oct 2008 11:02:52 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 17 Oct 2008 11:02:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Oct 2008 11:02:42 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E0262E44D@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <68005082-BEE6-4215-8F68-509C047EDE28@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Proposal for changing messages names in Multicast Control
	Extensions
Thread-Index: AckvXnSiFh+ChgfiQpGOfbgXoSWIGQA2GhqA
References: <A1F769BC58A8B146B2EEA818EAE052A20129491FF5@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A71@xmb-sjc-222.amer.cisco.com>
	<A1F769BC58A8B146B2EEA818EAE052A20129491FF6@GRFMBX702RM001.griffon.local>
	<48214755113BB04F84D958B4F0DE261C06934A78@xmb-sjc-222.amer.cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DA9A@FRVELSMBS22.ad2.ad.alcatel.com>
	<494C598F-DBAE-481A-9E0C-D5959B889C9B@cisco.com>
	<74F3BED2-0895-46E6-9425-4AFB1550146E@cisco.com>
	<DF8EB6AC-6E42-4A4B-91BB-1E2F1534F51D@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DBF5@FRVELSMBS22.ad2.ad.alcatel.com>
	<87E20368-84F4-47E6-810C-4037B5C15F5E@cisco.com>
	<7A6D4815C5E8F74988784FEBD50F2F1E0262DC70@FRVELSMBS22.ad2.ad.alcatel.com>
	<48214755113BB04F84D958B4F0DE261C069350E2@xmb-sjc-222.amer.cisco.com>
	<68005082-BEE6-4215-8F68-509C047EDE28@cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>,
	"Philippe Champagne (pchamp)" <pchamp@cisco.com>
X-OriginalArrivalTime: 17 Oct 2008 09:02:43.0761 (UTC)
	FILETIME=[1DC5DA10:01C93037]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
	Control Extensions
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0863944560=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0863944560==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93037.1D8A4D0B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93037.1D8A4D0B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
Makes sense to me as well. =20

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: donderdag 16 oktober 2008 9:11
To: Philippe Champagne (pchamp)
Cc: Francois Le Faucheur IMAP; DE CNODDER Stefaan; ancp@ietf.org
Subject: Re: [ANCP] Proposal for changing messages names in Multicast
Control Extensions


Philippe, Stefaan,=20

On 15 Oct 2008, at 20:08, Philippe Champagne (pchamp) wrote:


	Hi Stefaan
	=20
	I think it could go this way:
	=20
	Either the AN also sends the Leave to the NAS - which will be
processed serially by the NAS after the Join, and the NAS therefore will
reply for the leave shortly after. In this case, the AN gets a leave.
	or
	The AN does not sends the Leave to the NAS but holds it for a
specific time (the time we should expect such join from the server).=20
	=20
	For the fire and forget, I personally prefer the first option, I
mean, if we have to have the AN holding info, might as well be the whole
thing where it knows also about the JOIN sent shortly before for which
it is awaiting a response.
	=20
	The question is then, which way to go?  Can we allow "fire and
forget" and "remember the states" to both be used at the discretion of
the implementor of the ANCP client or do we force one way to go. =20
	It depends if the ANCP server needs to know about bandwidth
usage for bandwidth requirement decision, in which case, it would need
to know about Leave as well, isn't it?   Can that behavior (bandwith
decision) be configurable, allowing "remember the states" (where Leaves
are not necessarily forwarded) to exist in other deployment model?


I would say that we already have a model to allow the AN to operate
fairly autonomously (ie Black List & White-List + Bandwidth delegation).
In that model, the NAS does not need to track all join/leaves and we
take advantage of that to have AN handles Join/Leave without having to
keep NAS aware of all that..

The Admission Control request that we are discussing in the thread is
associated with the Grey-List Model where the NAS is likely to need to
track all join/leaves (eg because admission control is performed by NAS
or Policy Server, perhaps for accounting reason, perhaps for conditional
access). So to mimimze the number of options, I would suggest that in
this case of Grey-List operation, we only allow a single behavior
whereby the AN conveys all the Leave/Join transitions to NAS.
Note that the AN may use some liberty in how it does that (eg. it may
optionally wait a little bit on receipt of a Leave to see if a Join is
not immediately following to bundle that in a single ANCP request, it
may decide to remember the state for a while or until it gets a
response,...) but I would suggest that no matter what the AN should
always convey all Join/Leave transitions (in this Grey-List Model).

Makes sense?

Francois



	=20
	=20


________________________________

		From: DE CNODDER Stefaan
[mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
		Sent: Wednesday, October 15, 2008 12:08 PM
		To: Francois Le Faucheur (flefauch)
		Cc: ancp@ietf.org; Philippe Champagne (pchamp)
		Subject: RE: [ANCP] Proposal for changing messages names
in Multicast Control Extensions
	=09
	=09
		=20
		About the "fire and forget".  I like it a lot because of
its simplicity but it has an issue:
		=20
		1) user sends join matching grey list
		2) AN sends admission request to NAS and forgets about
it
		3) user sends leave, which is not doing anything since
the NAS has not replied yet
		4) AN receives possitive answer to join the stream
		=20
		In this case the multicast flow is replicated to the
line although the user had sent a leave.
		=20
		First processing the Result field without knowing what
the message is about looks to me like a strange way of processing, but
it works.  However, just using a different message type would make it
easier according to me.  No need to repeat all commands or even no need
to repeat the port id, so not much re-use anyhow.
		=20
		If the "fire and forget" method would work, there is not
really a response, and the current message as defined today is
sufficient, but in the above case I have some doubts.
		=20
		regards,
		Stefaan

________________________________

		From: Francois Le Faucheur IMAP
[mailto:flefauch@cisco.com]=20
		Sent: woensdag 15 oktober 2008 17:53
		To: DE CNODDER Stefaan
		Cc: Francois Le Faucheur IMAP; ancp@ietf.org; Philippe
(pchamp) Champagne
		Subject: Re: [ANCP] Proposal for changing messages names
in Multicast Control Extensions
	=09
	=09
		Hi Stefaan,=20

		On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:


			=20
			Francois,
			=20
			If it is a request, then the AN just executes
the commands.  If it is a response, then I would think it has to look up
the state indexed by trans id to clean it up, and to execute the join
which is in that state.


		First, just to make sure we don't lose the first point:
if the AN needs to know whether it is a request or a response, it could
do so via the Result code.

		Now regarding whether AN needs to know, that may be
implementation dependent.
		One model could be as you described above, in which case
AN needs to know.
		Another model could be where the AN operates in a
simpler "Fire and Forget" mode:
		* AN sends admission request (and AN increments its
Transaction ID value)
		* AN forgets about it (AN relies on TCP to make sure
request reached NAS and relies on ANCP behavior to get a response)
		* when AN gets a Multicast Replication message, it just
executes. A key assumption here is that the multicast replication
control message contains all the information necessary for execution (eg
"add channel C to port P")

		Makes sense?

		Francois



			  So yes, it looks to me that both are
different.  Also the processing of the trans id is different because for
requests it has to check whether it is each time incremented by 1, which
it does not have to do for responses.
			=20
			regards,
			Stefaan

________________________________

			From: Francois Le Faucheur IMAP
[mailto:flefauch@cisco.com]=20
			Sent: woensdag 15 oktober 2008 16:27
			To: Francois Le Faucheur IMAP
			Cc: DE CNODDER Stefaan; ancp@ietf.org
			Subject: Re: [ANCP] Proposal for changing
messages names in Multicast Control Extensions
		=09
		=09

			=09
			=09
			=09

				If a message can be used as both a
request and a reply, is the defitions
			=09

				of the Transaction Identifier still
accurate?  Currently the draft says:
			=09


				- trans id in request is linearly
incrementing, and is per message type
			=09

				- trans id in response is copied from
request
			=09


				If the same message type can be both
request and response, then how will
			=09

				the trans id behave?  Should the
receiver first try to find out whether
			=09

				it is a request or a response, and then
process it accordingly?  Or how
			=09

				should it then work?
			=09



				Oops, there was a typo in earlier
message. This should read:
				One option would be for the receiver to
look at the Result field:
				* if it is set to Success/Failure, then
this message is a "response" to an earlier request (and its Transaction
ID echoed the one of the request)
				* if it is set to Ack/Nack, then this
messages is a "request" (and the transaction ID was generated by remote
end)


			Note also that the AN may not even care that
much whether it is a response or a spontaneous request, because the two
are idempotent.

			Francois





				One option would be for the sender to
look at the Result field:
			=09

				* if it is set to Success/Failure, then
this message is a "response" to an earlier request (and its Transaction
ID echoed the one of the request)
			=09

				* if it is set to Ack/Nack, then this
messages is a request (and the transaction ID was generated by remote
end)
			=09




				regards,
			=09

				Stefaan
			=09



				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: dinsdag 14 oktober 2008 15:33
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				Ok, just wanted to make sure what you
meant.
			=09


				So, this means a Multicast Replication
Control Message would be used
			=09

				both as a reply to an authorization as
well as a directive.  I tend to
			=09

				agree with this, although, we might
review that case when we define the
			=09

				authorization message and if the reply
from the server would carry
			=09

				roughly the same information as the
directive. I would assume it would.
			=09




				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 9:22 AM
			=09

				To: Philippe Champagne (pchamp); DE
CNODDER Stefaan; Wojciech Dec
			=09

				(wdec); Sanjay Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09


				Hi Phil,
			=09

				    please see inline.
			=09


				Regards,
			=09

				Roberta
			=09


				-----Original Message-----
			=09

				From: Philippe Champagne (pchamp)
[mailto:pchamp@cisco.com]
			=09

				Sent: Tuesday, October 14, 2008 2:50 PM
			=09

				To: Maglione Roberta; DE CNODDER
Stefaan; Wojciech Dec (wdec); Sanjay
			=09

				Wadhwa
			=09

				Cc: ancp@ietf.org
			=09

				Subject: RE: Proposal for changing
messages names in Multicast Control
			=09

				Extensions
			=09



				I'm ok with those renaming.
			=09

				[RM] Great
			=09


				Do you mean that when the ANCP client
ask authorization for a Join,
			=09

				its request is a Multicast Replication
Control Message and the reply
			=09

				from the server is the same or
different:____
			=09


				[RM] not exactly, what I meant is
slightly different:  when an ANCP
			=09

				client asks for authorization to Join a
multicast flow, it uses an ANCP
			=09


				message (not defined yet), while when
the server replies to the
			=09

				authorization message sent by the client
it could use a Multicast
			=09

				Replication Control Message
			=09


				While if the server is sending
			=09

				a directive to the ANCP client to have a
port join a
			=09

				multicast, do you
			=09

				mean this is also called Multicast
Replication Control Message?
			=09


				[RM] yes this is current scenario where
the server uses a Multicast
			=09

				Replication Control Message to send a
directive to the ANCP client to
			=09

				have a port join or leave a multicast
flow.
			=09

				Does it make sense?
			=09


				Thanks,
			=09

				Roberta
			=09





				-----Original Message-----
			=09

				From: Maglione Roberta
[mailto:roberta.maglione@telecomitalia.it]
			=09

				Sent: Tuesday, October 14, 2008 7:46 AM
			=09

				To: Philippe Champagne (pchamp); 'DE
CNODDER Stefaan'; Wojciech Dec
			=09

				(wdec); 'Sanjay Wadhwa'
			=09

				Subject: Proposal for changing messages
names in Multicast Control
			=09

				Extensions
			=09



				Hello,
			=09

				    I'm currently merging
draft-ancp-mc-extensions with
			=09

				draft-ietf-ancp-protocol, and I am
thinking it could be useful to
			=09

				simplify the terminology in terms of
multicast message names.
			=09

				In particular I'd like to rename:
			=09

				- Multicast Replication Control Request
Message in just Multicast
			=09

				Replication Control Message
			=09

				- Multicast Status Response Message and
in Multicast Status Message
			=09


				This change would allow re-using the
same message type for different
			=09

				purposes/use cases if needed in future,
without affecting current
			=09

				scenario.
			=09


				Please let me know what's your opinion
on this proposal.
			=09


				Thanks and best regards,
			=09


				Roberta
			=09



				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content
			=09

				hereof is
			=09

				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09




				CONFIDENTIALITY NOTICE
			=09


				This message and its attachments are
addressed solely to the persons
			=09

				above and may contain confidential
information. If you have received
			=09

				the message in error, be informed that
any use of the content hereof is
			=09


				prohibited. Please return it immediately
to the sender and delete the
			=09

				message. Should you have any questions,
please contact us by replying
			=09

				to webmaster@telecomitalia.it.
			=09


				    Thank you
			=09


=09
www.telecomitalia.it
			=09


=09
_______________________________________________
			=09

				ANCP mailing list
			=09

				ANCP@ietf.org
			=09

=09
https://www.ietf.org/mailman/listinfo/ancp
			=09







------_=_NextPart_001_01C93037.1D8A4D0B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D257550009-17102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Makes sense to me as well.&nbsp; =
</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> donderdag 16 oktober 2008=20
9:11<BR><B>To:</B> Philippe Champagne (pchamp)<BR><B>Cc:</B> Francois Le =

Faucheur IMAP; DE CNODDER Stefaan; ancp@ietf.org<BR><B>Subject:</B> Re: =
[ANCP]=20
Proposal for changing messages names in Multicast Control=20
Extensions<BR></FONT><BR></DIV>
<DIV></DIV>Philippe, Stefaan,
<DIV><BR>
<DIV>
<DIV>On 15 Oct 2008, at 20:08, Philippe Champagne (pchamp) =
wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008>Hi Stefaan</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008>I think it could go this =
way:</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008>Either the AN also sends the Leave to the =
NAS - which=20
  will be processed serially by the NAS after the Join, and the NAS =
therefore=20
  will reply for the leave shortly after. In this case, the AN gets a=20
  leave.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008>or</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008>The AN does not sends the Leave to the NAS =
but holds=20
  it for a specific time (the time we should expect such join from the =
server).=20
  </SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008>For the fire and forget, I personally =
prefer the=20
  first option, I mean, if we have to have the AN holding info, might as =
well be=20
  the whole thing where&nbsp;it knows also about the =
JOIN&nbsp;sent&nbsp;shortly=20
  before for which&nbsp;it is awaiting a response.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D439305517-15102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D439305517-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The question is then, which way to go?&nbsp; =
Can we allow=20
  "fire and forget" and "remember the states" to both be used at the =
discretion=20
  of the implementor of the ANCP client or do we force one way to =
go.&nbsp;=20
  </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D439305517-15102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>It depends if the ANCP server needs to know =
about=20
  bandwidth&nbsp;usage&nbsp;for bandwidth requirement decision, in which =
case,=20
  it would need to know about Leave as well, isn't it?&nbsp;&nbsp; Can =
that=20
  behavior (bandwith decision)&nbsp;be configurable, =
allowing&nbsp;"remember the=20
  states" (where Leaves are not necessarily&nbsp;forwarded) to exist in =
other=20
  deployment model?</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>I&nbsp;would&nbsp;say that we already have a model to allow the AN =
to=20
operate fairly autonomously (ie Black List &amp; White-List + Bandwidth=20
delegation). In that model, the NAS does not need to track all =
join/leaves and=20
we take advantage of that to have AN handles Join/Leave without having =
to keep=20
NAS aware of all that..</DIV>
<DIV><BR></DIV>
<DIV>The Admission Control request that we are discussing in the thread =
is=20
associated with the Grey-List Model where the NAS is likely to need to =
track all=20
join/leaves (eg because admission control is performed by NAS or Policy =
Server,=20
perhaps for accounting reason, perhaps for conditional access). So to =
mimimze=20
the number of options, I&nbsp;would&nbsp;suggest that in this case of =
Grey-List=20
operation, we only allow a single behavior whereby the AN conveys all =
the=20
Leave/Join transitions to NAS.</DIV>
<DIV>Note that the AN may use some liberty in how it does that (eg. it =
may=20
optionally wait a little bit on receipt of a Leave to see if a Join is =
not=20
immediately following to bundle that in a single ANCP request, it may =
decide to=20
remember the state for a while or until it gets a response,...) but I =
would=20
suggest that no matter what&nbsp;the&nbsp;AN&nbsp;should&nbsp;always =
convey all=20
Join/Leave transitions (in this Grey-List Model).</DIV>
<DIV><BR></DIV>
<DIV>Makes sense?</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV>
<DIV><BR></DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> DE CNODDER Stefaan [<A=20
    =
href=3D"mailto:stefaan.de_cnodder@alcatel-lucent.be">mailto:stefaan.de_cn=
odder@alcatel-lucent.be</A>]=20
    <BR><B>Sent:</B> Wednesday, October 15, 2008 12:08 PM<BR><B>To:</B> =
Francois=20
    Le Faucheur (flefauch)<BR><B>Cc:</B> <A=20
    href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A>; Philippe Champagne=20
    (pchamp)<BR><B>Subject:</B> RE: [ANCP] Proposal for changing =
messages names=20
    in Multicast Control Extensions<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
    size=3D2></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>About the "fire and forget".&nbsp; I like =
it a lot=20
    because of its simplicity but it has an issue:</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>1) user sends join matching grey=20
    list</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>2) AN sends admission request to NAS and =
forgets about=20
    it</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>3) user sends leave, which is not doing =
anything since=20
    the NAS has not replied yet</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>4) AN receives possitive answer to join the =

    stream</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>In this case the multicast flow is =
replicated to the=20
    line although the user had sent a leave.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>First processing the Result field without =
knowing what=20
    the message is about looks to me like a strange way of processing, =
but it=20
    works.&nbsp; However, just using a different message type would make =
it=20
    easier according to me.&nbsp; No need to repeat all commands or even =
no need=20
    to repeat the port id, so not much re-use =
anyhow.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>If the "fire and forget" method would work, =
there is=20
    not really a response, and the current message as defined today is=20
    sufficient, but in the above case I have some =
doubts.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D935315915-15102008><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A=20
    href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
    <BR><B>Sent:</B> woensdag 15 oktober 2008 17:53<BR><B>To:</B> DE =
CNODDER=20
    Stefaan<BR><B>Cc:</B> Francois Le Faucheur IMAP; <A=20
    href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A>; Philippe (pchamp)=20
    Champagne<BR><B>Subject:</B> Re: [ANCP] Proposal for changing =
messages names=20
    in Multicast Control Extensions<BR></FONT><BR></DIV>
    <DIV></DIV>Hi Stefaan,=20
    <DIV><BR>
    <DIV>
    <DIV>On 15 Oct 2008, at 16:36, DE CNODDER Stefaan wrote:</DIV><BR=20
    class=3DApple-interchange-newline>
    <BLOCKQUOTE type=3D"cite">
      <DIV=20
      style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
      size=3D2></FONT>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>If it is&nbsp;a request, then&nbsp;the =
AN&nbsp;just=20
      executes the commands.&nbsp; If it is a response, then I would =
think it=20
      has to look up the state indexed by trans id to clean it up, and =
to=20
      execute the join which is in that=20
    state.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
    <DIV><BR></DIV>
    <DIV>First, just to make sure we don't lose the first point: if the =
AN needs=20
    to know whether it is a request or a response, it could do so via =
the Result=20
    code.</DIV>
    <DIV><BR></DIV>
    <DIV>Now regarding whether AN needs to know, that may be =
implementation=20
    dependent.</DIV>
    <DIV>One model could be as you described above, in which case AN =
needs to=20
    know.</DIV>
    <DIV>Another model could be where the AN operates in a simpler "Fire =
and=20
    Forget" mode:</DIV>
    <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>* AN sends=20
    admission request (and AN increments its Transaction ID value)</DIV>
    <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>* AN forgets=20
    about it (AN relies on TCP to make sure request reached NAS and =
relies on=20
    ANCP behavior to get a response)</DIV>
    <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>* when AN=20
    gets a Multicast Replication message, it just executes. A key =
assumption=20
    here is that the multicast replication control message contains all =
the=20
    information necessary for execution&nbsp;(eg "add channel C to port=20
P")</DIV>
    <DIV><BR></DIV>
    <DIV>Makes sense?</DIV>
    <DIV><BR></DIV>
    <DIV>Francois</DIV>
    <DIV><BR></DIV><BR>
    <BLOCKQUOTE type=3D"cite">
      <DIV=20
      style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>&nbsp; So yes, it looks to me that both =
are=20
      different.&nbsp; Also the processing of the trans id is=20
      different&nbsp;because for requests it has to check whether it is =
each=20
      time incremented by 1, which it does not have to do for=20
      responses.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D503243114-15102008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur =
IMAP [<A=20
      href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
      <BR><B>Sent:</B> woensdag 15 oktober 2008 16:27<BR><B>To:</B> =
Francois Le=20
      Faucheur IMAP<BR><B>Cc:</B> DE CNODDER Stefaan; <A=20
      href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> =
Re:=20
      [ANCP] Proposal for changing messages names in Multicast Control=20
      Extensions<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV>
      <BLOCKQUOTE type=3D"cite">
        <DIV>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><FONT class=3DApple-style-span=20
            color=3D#006312><BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">If a message can be used as both a =
request=20
            and a reply, is the defitions<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">of the Transaction Identifier still=20
            accurate? &nbsp;Currently the draft =
says:<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">- trans id in request is linearly=20
            incrementing, and is per message =
type<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">- trans id in response is copied =
from=20
            request<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">If the same message type can be both =
request=20
            and response, then how will<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">the trans id behave? &nbsp;Should =
the=20
            receiver first try to find out =
whether<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">it is a request or a response, and =
then=20
            process it accordingly? &nbsp;Or =
how<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">should it then=20
        work?<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE><BR>Oops, there was a =
typo in=20
        earlier message. This should read:<BR>One option would be for =
the=20
        receiver to look at the Result field:<BR><SPAN =
class=3DApple-tab-span=20
        style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure, then=20
        this message is a "response" to an earlier request (and its =
Transaction=20
        ID echoed the one of the request)<BR><SPAN =
class=3DApple-tab-span=20
        style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, =
then this=20
        messages is a "request" (and the transaction ID was generated by =
remote=20
        end)</DIV></BLOCKQUOTE>
      <DIV><BR></DIV>
      <DIV>Note also that the AN may not even care that much whether it =
is a=20
      response or a spontaneous request, because the two are =
idempotent.</DIV>
      <DIV><BR></DIV>
      <DIV>Francois</DIV>
      <DIV><BR></DIV><BR>
      <BLOCKQUOTE type=3D"cite">
        <DIV><BR><BR>
        <BLOCKQUOTE type=3D"cite">One option would be for the sender to =
look at=20
          the Result field:<BR></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
          style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to =
Success/Failure,=20
          then this message is a "response" to an earlier request (and =
its=20
          Transaction ID echoed the one of the request)<BR></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-tab-span=20
          style=3D"WHITE-SPACE: pre"></SPAN>* if it is set to Ack/Nack, =
then this=20
          messages is a request (and the transaction ID was generated by =
remote=20
          end)<BR></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">regards,<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">Stefaan<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">-----Original=20
        Message-----<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) =
[<A=20
            =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Sent: dinsdag 14 oktober 2008=20
          15:33<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
            Wojciech Dec (wdec); Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Cc: <A=20
            =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =
messages=20
            names in Multicast Control<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">Ok, just wanted to make sure what =
you=20
            meant.<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">So, this means a Multicast =
Replication=20
            Control Message would be used<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">both as a reply to an authorization =
as well=20
            as a directive. &nbsp;I tend =
to<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">agree with this, although, we might =
review=20
            that case when we define the<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">authorization message and if the =
reply from=20
            the server would carry<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">roughly the same information as the=20
            directive. I would assume it =
would.<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">-----Original=20
          Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
              =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 =
9:22=20
            AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); =
DE=20
              CNODDER Stefaan; Wojciech =
Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">(wdec); Sanjay=20
          Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Cc: <A=20
              =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =

              messages names in Multicast=20
        Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Hi=20
        Phil,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;please see =

              inline.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        =
type=3D"cite">Regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">-----Original=20
          Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">From: Philippe Champagne (pchamp) =
[<A=20
              =
href=3D"mailto:pchamp@cisco.com">mailto:pchamp@cisco.com</A>]<BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 =
2:50=20
            PM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">To: Maglione Roberta; DE CNODDER =
Stefaan;=20
              Wojciech Dec (wdec); =
Sanjay<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
type=3D"cite">Wadhwa<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Cc: <A=20
              =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Subject: RE: Proposal for changing =

              messages names in Multicast=20
        Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">I'm ok with those=20
              =
renaming.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">[RM]=20
        Great<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Do you mean that when the ANCP =
client=20
                ask authorization for a=20
          Join,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">its request is a Multicast =
Replication=20
                Control Message and the=20
          reply<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">from the server is the same or=20
                =
different:____<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">[RM] not exactly, what I meant is =
slightly=20
              different: &nbsp;when an =
ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">client asks for authorization to =
Join a=20
              multicast flow, it uses an=20
        ANCP<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">message (not defined yet), while =
when the=20
              server replies to =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">authorization message sent by the =
client=20
              it could use a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Replication Control=20
          Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">While if the server is=20
              =
sending<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">a directive to the ANCP client =
to have a=20
                port join =
a<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">multicast, do=20
        you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">mean this is also called =
Multicast=20
                Replication Control=20
        Message?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">[RM] yes this is current scenario =
where=20
              the server uses a =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Replication Control Message to =
send a=20
              directive to the ANCP client=20
        to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">have a port join or leave a =
multicast=20
              flow.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">Does it make=20
          sense?<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        type=3D"cite">Thanks,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
        type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">-----Original=20
            =
Message-----<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">From: Maglione Roberta [<A=20
                =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</A>]<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Sent: Tuesday, October 14, 2008 =
7:46=20
                =
AM<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">To: Philippe Champagne (pchamp); =
'DE=20
                CNODDER Stefaan'; Wojciech=20
          Dec<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">(wdec); 'Sanjay=20
            =
Wadhwa'<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Subject: Proposal for changing =
messages=20
                names in Multicast=20
        Control<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Extensions<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOC=
KQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Hello,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;I'm =
currently=20
                merging draft-ancp-mc-extensions=20
          with<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">draft-ietf-ancp-protocol, and I =
am=20
                thinking it could be useful=20
          to<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">simplify the terminology in =
terms of=20
                multicast message=20
        names.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">In particular I'd like to=20
              =
rename:<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">- Multicast Replication Control =
Request=20
                Message in just=20
        =
Multicast<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Replication Control=20
              =
Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">- Multicast Status Response =
Message and=20
                in Multicast Status=20
        Message<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">This change would allow re-using =
the=20
                same message type for=20
          =
different<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">purposes/use cases if needed in =
future,=20
                without affecting=20
        current<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">scenario.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Please let me know what's your =
opinion=20
                on this=20
proposal.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">Thanks and best=20
            =
regards,<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
          =
type=3D"cite">Roberta<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQU=
OTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
            =
NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">This message and its attachments =
are=20
                addressed solely to the=20
          =
persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">above and may contain =
confidential=20
                information. If you have=20
          =
received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">the message in error, be =
informed that=20
                any use of the=20
        content<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">hereof=20
        is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately=20
                to the sender and delete=20
        the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions,=20
                please contact us by=20
          =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">to <A=20
                =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
              =
you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
                =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
                =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">
              <BLOCKQUOTE=20
        =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">CONFIDENTIALITY=20
          NOTICE<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">This message and its attachments =
are=20
              addressed solely to the=20
        persons<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">above and may contain confidential =

              information. If you have=20
        received<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">the message in error, be informed =
that any=20
              use of the content hereof =
is<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">prohibited. Please return it =
immediately=20
              to the sender and delete =
the<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">message. Should you have any =
questions,=20
              please contact us by =
replying<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">to <A=20
              =
href=3D"mailto:webmaster@telecomitalia.it">webmaster@telecomitalia.it</A>=
.<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;Thank=20
            you<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE=20
              =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;<A=20
              =
href=3D"http://www.telecomitalia.it">www.telecomitalia.it</A><BR></BLOCKQ=
UOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">
            <BLOCKQUOTE =
type=3D"cite"><BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE=20
            =
type=3D"cite">_______________________________________________<BR></BLOCKQ=
UOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite">ANCP mailing =
list<BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><A=20
            =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR></BLOCKQUOTE></BLOCKQU=
OTE>
        <BLOCKQUOTE type=3D"cite">
          <BLOCKQUOTE type=3D"cite"><A=20
            =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></BLOCKQUOTE></BLOCKQUOTE>
        <BLOCKQUOTE=20
      =
type=3D"cite"><BR></BLOCKQUOTE><BR></DIV></BLOCKQUOTE></DIV><BR></DIV></B=
LOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></DIV=
></BODY></HTML>

------_=_NextPart_001_01C93037.1D8A4D0B--

--===============0863944560==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0863944560==--


From ancp-bounces@ietf.org  Fri Oct 17 02:24:44 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFCC63A682C;
	Fri, 17 Oct 2008 02:24:44 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC0CF3A682C
	for <ancp@core3.amsl.com>; Fri, 17 Oct 2008 02:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 9ujo-ti0qQC4 for <ancp@core3.amsl.com>;
	Fri, 17 Oct 2008 02:24:40 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27])
	by core3.amsl.com (Postfix) with ESMTP id 1596B3A63D2
	for <ancp@ietf.org>; Fri, 17 Oct 2008 02:24:39 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9H9OMGa007426
	for <ancp@ietf.org>; Fri, 17 Oct 2008 11:25:37 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 17 Oct 2008 11:23:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Oct 2008 11:23:26 +0200
Message-ID: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ANCP Framework update
Thread-Index: AckwOgJsIJe9VJgbRHSt5ybOabbM2w==
From: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 17 Oct 2008 09:23:28.0576 (UTC)
	FILETIME=[03BD8C00:01C9303A]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1795784349=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1795784349==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9303A.032A85D2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9303A.032A85D2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I've been updating the ANCP framework draft according to the suggested
changes from Roberta and Francois. Below I have copy-pasted the sections
that have undergone changes. Indented text has been changed. I think I
captured the essence of the notion of "bandwidth delegation". Please
review and see if this is capturing the agreements.

Regards,
Sven


3.4.2.  Multicast Admission Control

   The successful delivery of Triple Play Broadband services is quickly
   becoming a big capacity planning challenge for most of the Service
   Providers nowadays.  Solely increasing available bandwidth is not
   always practical, cost-economical and/or sufficient to satisfy end
   user experience given not only the strict requirements of unicast
   delay sensitive applications like VoIP and Video, but also the fast
   growth of multicast interactive applications such as
   videoconferencing, digital TV, digital audio, online movies and
   networked gaming.  These applications are typically characterized by
   a delay sensitive nature, an extremely loss sensitive nature and
   intensive bandwidth requirements.  They are also typically "non-
   elastic", which means that they operate at a fixed bandwidth, that
   cannot be dynamically adjusted to the currently available bandwidth.

   Therefore a Connection Admission Control (CAC) mechanism covering
   admission of multicast traffic over the DSL Broadband access is
   required, in order to avoid oversubscribing the available bandwidth
   and negatively impacting the end user experience.

   Considering specifically admission control over the access line,
   before honoring a user request to join a new multicast flow, the
   combination of AN and NAS MUST ensure admission control is performed
   to validate that there is enough "video" bandwidth remaining on the
   access line to carry the new flow (in addition to all other existing
   multicast and unicast video traffic).  The solution needs to cope
   with multiple flows per access line and needs to allow access line
   bandwidth to be dynamically shared across multicast and unicast
   traffic (irrespective of whether unicast CAC is performed by NAS or
   by some off-path Policy Server).

   Thus, supporting CAC for the access line requires some form of
   synchronization between the entity performing multicast CAC (e.g. the
   NAS or the AN) and the entity performing unicast CAC (e.g. the NAS or
   a Policy Server) and the entity actually enforcing the multicast
   replication (i.e. the AN).  This synchronization can be achieved in a
   number of ways:

   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.

      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop, and perform video bandwidth accounting for the
         Access Loop.  Upon receiving an Admission Request from the AN,
         the NAS can check available "video" bandwidth before admitting
         or denying the multicast flow.  In the process, the NAS may
         communicate with the Policy Server.  For unicast video services
         such as Video on Demand (VoD), the NAS may also be queried (by
         a Policy Server or via on-path CAC signaling), so that it can
         perform admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.

      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List whose entry is flagged as
         "Bandwidth Delegation", the AN must perform the necessary
         bandwidth admission control check for the new multicast flow,
         before starting the multicast flow replication.

      The ANCP requirements to support this approach are specified in
      this document.

   o  In case the subscriber communicates the "join/leave" information
      with the NAS (e.g. by terminating all subscriber IGMP signaling on
      the NAS, or by using some form of application level signaling),
      the approach is very similar.  In this case, the NAS may locally
      maintain available "video" bandwidth on the Access Loop, perform
      video bandwidth accounting, and perform CAC for unicast and
      multicast flows.  The NAS can set the replication state on the AN
      using ANCP if the flow is admitted.  For unicast video services
      the NAS may be queried (by a policy server or via on-path CAC
      signaling) to perform admission control for the unicast flow, and
      update the available video bandwidth maintained by the NAS.  The
      ANCP requirements to support this approach (where the AN queries
      the NAS) are specified in this document;

   o  In a third approach, the Policy Server queries the AN directly so
      that both unicast and multicast CAC for the access line are
      performed by the AN.  In this case, a subscriber request for a
      unicast flow (e.g. a Video on Demand session) will trigger a
      resource request message towards a Policy Server; the latter will
      then query the AN, that in turn will perform unicast CAC for the
      access line and respond, indicating whether the unicast request is
      to be honored or denied.  In this scenario the Policy Server
      queries the AN directly, the approach doesn't require the use of
      ANCP.  It is therefore beyond the scope of this document.


4.2.  ANCP Multicast Requirements

   o  The ANCP MUST support providing multicast conditional access
      information to Access Ports on an Access Node, using Black, Grey
      and White lists.

   o  The ANCP MUST support binding a particular Black, Grey and White
      List to a given Access Port.

   o  Upon receiving a join to a multicast flow which matches the Grey
      List the ANCP MUST allow the AN to query the NAS to request an
      admission decision for replicating that multicast flow to a
      particular Access Port.

   o  The ANCP MUST allow the NAS to send an admission decision to the
      AN indicating whether or not a multicast flow may be replicated to
      a particular Access Port.

   o  The ANCP must allow the NAS to indicate to the AN whether or not
      Admission Control is needed for some multicast flows on a given
      Access Port and where needed whether or not it is to be performed
      with AN Bandwidth Delegation.

   o  In case of Admission Control without AN Bandwidth Delegation, the
      ANCP must allow the NAS to reply to a query from the AN indicating
      whether or not a multicast flow may be replicated to a particular
      Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the
      ANCP must allow the NAS to delegate a certain amount of bandwidth
      to the AN for a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the
      ANCP must allow the AN to query the NAS to request additional
      multicast bandwidth on a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the
      ANCP must allow the NAS to query (or to instruct) the AN to reduce
      the amount of bandwidth previously delegated on a given Access
      Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the
      ANCP must allow the AN to autonomous release redundant multicast
      bandwidth on a given Access Port.

   o  The ANCP MUST allow the AN to send an Information Report message
      to the NAS whenever replication of a multicast flow on a
      particular Access Port start or ends.

   o  The ANCP MUST allow the AN to send an Information Report message
      to the NAS indicating the multicast traffic volume that has been
      replicated on that port.

   o  The ANCP MUST allow the NAS to indicate to the AN whether or not
      multicast accounting is needed for a multicast flow on a
      particular Access Port.

   o  In case multicast accounting is needed for a multicast flow on a
      particular Access Port, the ANCP MUST allow the NAS to indicate to
      the AN whether or not additional volume accounting information is
      required.

   o  The ANCP MUST allow the NAS to revoke a decision to replicate a
      multicast flow to a particular Access Port, which had been
      conveyed earlier to an AN.

   o  The ANCP MUST support partial updates of the White, Grey and Black
      lists.

   o  The ANCP MUST allow the NAS to query the AN to obtain information
      on what multicast flows are currently being replicated on a given
      Access Port, what Access Ports are currently receiving a given
      multicast flow, or what multicast flows are currently replicated
      on each Access Port.


Access Node multicast requirements (section 4.7.6)

   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.

   o  The AN must accept any join to a multicast flow matching the White
      List and not flagged as "Bandwidth Delegation" for the relevant
      Access Port.

   o  Upon receiving a join to a multicast flow which matches the White
      List whose entry is flagged as "Bandwidth Delegation" for the
      relevant Access Port, the AN must perform the necessary bandwidth
      admission control check for the new flow before starting the
      multicast flow replication.

   o  Upon receiving a join to a multicast flow which matches the Grey
      List whose entry is flagged as "no Bandwidth Delegation" for the
      relevant Access Port, the AN must support using ANCP to query the
      NAS to receive a response indicating whether that join is to be
      honored or denied.  In this case, the NAS will perform both the
      necessary conditional access and the admission control checks for
      the new flow.

   o  Upon receiving a join to a multicast flow which matches the Grey
      List whose entry is flagged as "Bandwidth Delegation" for the
      relevant Access Port, the AN must first perform the necessary
      bandwidth admission control check for the new flow.  If
      successful, the AN must support using ANCP to query the NAS to
      receive a response indicating whether that join is to be honored
      or denied.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.

   o  If the requested multicast flow is not part of any list associated
      with the Access Port, the AN must discard the message.

   o  If the requested multicast flow is part of multiple lists
      associated with the Access Port, the AN must use the most specific
      match.

   o  If the requested multicast flow has the same most specific match
      in multiple lists, the AN must give precedence to the Black list,
      followed by the Grey list, and then the White list.

   o  The AN must support configuring a "catch-all" statement in the
      Black, White or Grey list in order to enforce a default behavior
      for a join to a multicast flow which doesn't match any other entry
      in a list for the relevant Access Port.

   o  Upon querying the NAS, the AN must not propagate the join message
      before the successful authorization from the NAS is received.

   o  Upon receiving a leave for a multicast flow which matches the Grey
      List, the AN should be able to autonomously stop replication and
      advertise this event to the NAS.

   o  The AN must support using ANCP to send an Information Report
      message to the NAS whenever replication starts or ends.

   o  The AN should support using ANCP to send an Information Report
      message to the NAS indicating the multicast traffic volume that
      has been replicated on that port.

   o  Upon request by the NAS, the AN must support using ANCP to send an
      Information Report message to the NAS, indicating what multicast
      flows are currently being replicated on a given Access Port.

   o  Upon request by the NAS, the AN must support using ANCP to send an
      Information Report message to the NAS, indicating what Access
      Ports are currently receiving a given multicast flow.

   o  Upon request by the NAS, the AN must support using ANCP to send an
      Information Report message to the NAS, indicating what multicast
      flows are currently being replicated on each Access Port.

   o  Upon receiving an Admission Response from the NAS, indicating that
      replication of a multicast flow is to start or stop on a given
      access port of the AN, the AN must enforce this decision.  This
      decision must be taken irrespective of whether or not a
      corresponding Admission Request was issued by the AN earlier on.


NAS multication requirements (section 4.8.6)

   o  The NAS must support using ANCP to configure multicast conditional
      access information to Access Ports on an Access Node, using Black
      Lists, Grey Lists and White Lists.

   o  The NAS must support using ANCP to indicate to the AN whether or
      not Admission Control is needed for some multicast flows on a
      given Access Port and where needed whether or not it is to be
      performed with AN Bandwidth Delegation.

   o  Upon receiving a query from the AN for a request to replicate a
      multicast flow to a particular Access Port, and no AN Bandwidth
      Delegation is needed for that flow, the NAS must be able to
      perform the necessary checks (conditional access and/or admission
      control) for the new flow.  The NAS must support using ANCP to
      reply to the AN indicating whether the request is to be honored or
      denied.

   o  Upon receiving a query from the AN for a request to replicate a
      multicast flow to a particular Access Port, and Admission Control
      with AN Bandwidth Delegation is needed for that flow, the NAS must
      be able to perform the conditional access checks (if needed), and
      must support using ANCP to delegate a certain amount of bandwidth
      to the AN for a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the AN requesting to
      increase the delegated multicast bandwidth on a given Access Port,
      the NAS must support using ANCP to send a Bandwidth Delegation
      Response indicating the new delegating multicast bandwidth.

   o  In case of Admission Control with AN Bandwidth Delegation, the NAS
      must support using ANCP to send a request the AN to decrease the
      amount of multicast bandwidth previously delegated on a given
      Access Port; the NAS should be able to specify both the minimum
      and the preferred amount decrement of multicast bandwidth
      requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving an ANCP Bandwidth Release message, the NAS must be able
      to update accordingly its view of the multicast bandwidth
      delegated to the AN.

   o  The NAS must support using ANCP to configure the Access Node with
      the "maximum number of multicast streams" allowed to be received
      concurrently per Access Port.

   o  The NAS must support using ANCP to incrementally add, remove and
      modify individual entries in White, Black and Grey lists.

   o  The NAS must support using ANCP to indicate to the AN whether or
      not multicast accounting is needed for a multicast flow on a
      particular Access Port.

   o  In case multicast accounting is needed for a multicast flow on a
      particular Access Port, the NAS should support using ANCP to
      indicate to the AN whether or not additional volume accounting
      information is required.

   o  The NAS must support using ANCP to query the AN to obtain
      information on what multicast flows are currently replicated on a
      given Access Port.

   o  The NAS must support using ANCP to query the AN to obtain
      information on what Access Ports are currently receiving a given
      multicast flow.

   o  The NAS must support using ANCP to query the AN to obtain
      information on what multicast flows are currently replicated on
      each Access Port.

   o  When Multicast replication occurs on the AN, the NAS must support
      using ANCP to revoke the authorization to replicate a multicast
      flow to a particular Access Port.

   o  The NAS should support using ANCP to indicate to the AN that
      replication of a multicast flow is to start or stop on a given
      access port of the AN, without having received a corresponding
      Admission Request from the AN earlier on.

---

Sven Ooghe
Alcatel-Lucent
CTO Office, Access Division
Copernicuslaan 50, 2018 Antwerp, Belgium
tel.: +32 3 240 42 26
fax: +32 3 240 40 73

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  If you are not the intended recipient, you should
delete this message.  Any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited
without the prior consent of its author.


------_=_NextPart_001_01C9303A.032A85D2
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>ANCP Framework update</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I've been updating the ANCP framework =
draft according to the suggested changes from Roberta and Francois. =
Below I have copy-pasted the sections that have undergone changes.<I> =
Indented text</I> has been changed. I think I captured the essence of =
the notion of &quot;bandwidth delegation&quot;. Please review and see if =
this is capturing the agreements.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Sven</FONT>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">3.4.2.&nbsp; Multicast Admission =
Control</FONT></B>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; The successful delivery of =
Triple Play Broadband services is quickly</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; becoming a big capacity =
planning challenge for most of the Service</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Providers nowadays.&nbsp; =
Solely increasing available bandwidth is not</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; always practical, =
cost-economical and/or sufficient to satisfy end</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; user experience given not =
only the strict requirements of unicast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; delay sensitive =
applications like VoIP and Video, but also the fast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; growth of multicast =
interactive applications such as</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; videoconferencing, =
digital TV, digital audio, online movies and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; networked gaming.&nbsp; =
These applications are typically characterized by</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; a delay sensitive nature, =
an extremely loss sensitive nature and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; intensive bandwidth =
requirements.&nbsp; They are also typically &quot;non-</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; elastic&quot;, which =
means that they operate at a fixed bandwidth, that</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; cannot be dynamically =
adjusted to the currently available bandwidth.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Therefore a Connection =
Admission Control (CAC) mechanism covering</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; admission of multicast =
traffic over the DSL Broadband access is</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; required, in order to =
avoid oversubscribing the available bandwidth</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; and negatively impacting =
the end user experience.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Considering specifically =
admission control over the access line,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; before honoring a user =
request to join a new multicast flow, the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; combination of AN and NAS =
MUST ensure admission control is performed</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; to validate that there is =
enough &quot;video&quot; bandwidth remaining on the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; access line to carry the =
new flow (in addition to all other existing</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; multicast and unicast =
video traffic).&nbsp; The solution needs to cope</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; with multiple flows per =
access line and needs to allow access line</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; bandwidth to be =
dynamically shared across multicast and unicast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; traffic (irrespective of =
whether unicast CAC is performed by NAS or</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; by some off-path Policy =
Server).</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Thus, supporting CAC for =
the access line requires some form of</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; synchronization between =
the entity performing multicast CAC (e.g. the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; NAS or the AN) and the =
entity performing unicast CAC (e.g. the NAS or</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; a Policy Server) and the =
entity actually enforcing the multicast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; replication (i.e. the =
AN).&nbsp; This synchronization can be achieved in a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; number of ways:</FONT>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; One approach is =
for the AN to query the NAS so that Admission</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Control for the access line is performed by the NAS (possibly =
with</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
interactions with a Policy Server).&nbsp; This can be done with =
or</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
without &quot;bandwidth delegation&quot; to the AN.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp; In case of Admission Control without AN Bandwidth =
Delegation,</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
can use ANCP to query the NAS, that in turn performs</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast Admission Control check for the new multicast flow</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =
responds to the AN indicating whether the join is to be</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored =
(and hence replication performed by the AN) or denied.</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS =
may locally maintain available &quot;video&quot; bandwidth on =
the</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access =
Loop, and perform video bandwidth accounting for the</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access =
Loop.&nbsp; Upon receiving an Admission Request from the AN,</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS =
can check available &quot;video&quot; bandwidth before =
admitting</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or =
denying the multicast flow.&nbsp; In the process, the NAS may</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
communicate with the Policy Server.&nbsp; For unicast video =
services</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; such as =
Video on Demand (VoD), the NAS may also be queried (by</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a Policy =
Server or via on-path CAC signaling), so that it can</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; perform =
admission control for the unicast flow, and update the</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
available video bandwidth maintained by the NAS.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp; In case of Admission Control with AN Bandwidth Delegation, =
the</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =
(possibly with interactions with a Policy Server) manages</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for video admission, performs unicast admission</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control =
and uses ANCP to delegate a certain amount of bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast flows to the Access Node.&nbsp; In this scenario,</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =
receiving a join to a multicast flow which matches an</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in =
the White or Grey List whose entry is flagged as</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;Bandwidth Delegation&quot;, the AN must perform the =
necessary</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bandwidth admission control check for the new multicast flow,</FONT></I>

<BR><I><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before =
starting the multicast flow replication.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
ANCP requirements to support this approach are specified in</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this =
document.</FONT></I>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case the =
subscriber communicates the &quot;join/leave&quot; information</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
the NAS (e.g. by terminating all subscriber IGMP signaling on</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
NAS, or by using some form of application level signaling),</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
approach is very similar.&nbsp; In this case, the NAS may locally</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
maintain available &quot;video&quot; bandwidth on the Access Loop, =
perform</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video =
bandwidth accounting, and perform CAC for unicast and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flows.&nbsp; The NAS can set the replication state on the =
AN</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using =
ANCP if the flow is admitted.&nbsp; For unicast video services</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS =
may be queried (by a policy server or via on-path CAC</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
signaling) to perform admission control for the unicast flow, and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; update =
the available video bandwidth maintained by the NAS.&nbsp; The</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP =
requirements to support this approach (where the AN queries</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
NAS) are specified in this document;</FONT><I></I>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In a third =
approach, the Policy Server queries the AN directly so</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that =
both unicast and multicast CAC for the access line are</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
performed by the AN.&nbsp; In this case, a subscriber request for =
a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; unicast =
flow (e.g. a Video on Demand session) will trigger a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
resource request message towards a Policy Server; the latter will</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then =
query the AN, that in turn will perform unicast CAC for the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access =
line and respond, indicating whether the unicast request is</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to be =
honored or denied.&nbsp; In this scenario the Policy Server</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; queries =
the AN directly, the approach doesn't require the use of</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
ANCP.&nbsp; It is therefore beyond the scope of this =
document.</FONT><I></I>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">4.2.&nbsp; ANCP Multicast =
Requirements</FONT></B>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
support providing multicast conditional access</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
information to Access Ports on an Access Node, using Black, Grey</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =
White lists.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
support binding a particular Black, Grey and White</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List to =
a given Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving a =
join to a multicast flow which matches the Grey</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
the ANCP MUST allow the AN to query the NAS to request an</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
admission decision for replicating that multicast flow to a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
allow the NAS to send an admission decision to the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AN =
indicating whether or not a multicast flow may be replicated to</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
particular Access Port.</FONT>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP must =
allow the NAS to indicate to the AN whether or not</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Admission Control is needed for some multicast flows on a =
given</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Access Port and where needed whether or not it is to be =
performed</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
AN Bandwidth Delegation.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control without AN Bandwidth Delegation, the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP =
must allow the NAS to reply to a query from the AN indicating</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
whether or not a multicast flow may be replicated to a =
particular</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Access Port.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP =
must allow the NAS to delegate a certain amount of bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to =
the AN for a given Access Port.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP =
must allow the AN to query the NAS to request additional</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast bandwidth on a given Access Port.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP =
must allow the NAS to query (or to instruct) the AN to reduce</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
amount of bandwidth previously delegated on a given Access</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Port.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP =
must allow the AN to autonomous release redundant multicast</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bandwidth on a given Access Port.</FONT></I>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
allow the AN to send an Information Report message</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the =
NAS whenever replication of a multicast flow on a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular Access Port start or ends.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
allow the AN to send an Information Report message</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the =
NAS indicating the multicast traffic volume that has been</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
replicated on that port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
allow the NAS to indicate to the AN whether or not</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast accounting is needed for a multicast flow on a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case multicast =
accounting is needed for a multicast flow on a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular Access Port, the ANCP MUST allow the NAS to indicate =
to</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
whether or not additional volume accounting information is</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
required.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
allow the NAS to revoke a decision to replicate a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flow to a particular Access Port, which had been</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
conveyed earlier to an AN.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
support partial updates of the White, Grey and Black</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
lists.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST =
allow the NAS to query the AN to obtain information</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on what =
multicast flows are currently being replicated on a given</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access =
Port, what Access Ports are currently receiving a given</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flow, or what multicast flows are currently replicated</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on each =
Access Port.</FONT>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">Access Node multicast requirements =
(section 4.7.6)</FONT></B>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The AN must deny =
any join to a multicast flow matching the Black</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
for the relevant Access Port.</FONT>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The AN must =
accept any join to a multicast flow matching the White</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
and not flagged as &quot;Bandwidth Delegation&quot; for the =
relevant</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Access Port.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving =
a join to a multicast flow which matches the White</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
whose entry is flagged as &quot;Bandwidth Delegation&quot; for =
the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
relevant Access Port, the AN must perform the necessary =
bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
admission control check for the new flow before starting the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flow replication.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving =
a join to a multicast flow which matches the Grey</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
whose entry is flagged as &quot;no Bandwidth Delegation&quot; for =
the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
relevant Access Port, the AN must support using ANCP to query =
the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =
to receive a response indicating whether that join is to be</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
honored or denied.&nbsp; In this case, the NAS will perform both =
the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
necessary conditional access and the admission control checks =
for</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
new flow.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving =
a join to a multicast flow which matches the Grey</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
whose entry is flagged as &quot;Bandwidth Delegation&quot; for =
the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
relevant Access Port, the AN must first perform the necessary</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bandwidth admission control check for the new flow.&nbsp; If</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
successful, the AN must support using ANCP to query the NAS =
to</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
receive a response indicating whether that join is to be =
honored</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or =
denied.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the AN</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using ANCP to notify the NAS when the the user leaves</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast flow.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the AN</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using ANCP to query the NAS to request additional</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
delegated multicast bandwidth on a given Access Port; the AN</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
should be able to specify both the minimum and the preferred</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
amount of additional multicast bandwidth requested.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, upon</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
receiving a Bandwidth Delegation Request from the NAS querying =
or</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
instructing to decrease the delegated multicast bandwidth on =
a</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
given Access Port, the AN must support using ANCP to send a</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Bandwidth Delegation Response indicating the new delegated</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast bandwidth.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the AN</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using ANCP to send a Bandwidth Release message to the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =
in order to release unused delegated multicast bandwidth on a</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
given Access Port.</FONT></I>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; If the requested =
multicast flow is not part of any list associated</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
the Access Port, the AN must discard the message.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; If the requested =
multicast flow is part of multiple lists</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
associated with the Access Port, the AN must use the most =
specific</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
match.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; If the requested =
multicast flow has the same most specific match</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in =
multiple lists, the AN must give precedence to the Black list,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
followed by the Grey list, and then the White list.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The AN must =
support configuring a &quot;catch-all&quot; statement in the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Black, =
White or Grey list in order to enforce a default behavior</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for a =
join to a multicast flow which doesn't match any other entry</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in a =
list for the relevant Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon querying the =
NAS, the AN must not propagate the join message</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before =
the successful authorization from the NAS is received.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving a =
leave for a multicast flow which matches the Grey</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List, =
the AN should be able to autonomously stop replication and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
advertise this event to the NAS.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The AN must =
support using ANCP to send an Information Report</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message =
to the NAS whenever replication starts or ends.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The AN should =
support using ANCP to send an Information Report</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message =
to the NAS indicating the multicast traffic volume that</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has =
been replicated on that port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon request by =
the NAS, the AN must support using ANCP to send an</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Information Report message to the NAS, indicating what multicast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flows =
are currently being replicated on a given Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon request by =
the NAS, the AN must support using ANCP to send an</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Information Report message to the NAS, indicating what Access</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ports =
are currently receiving a given multicast flow.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon request by =
the NAS, the AN must support using ANCP to send an</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Information Report message to the NAS, indicating what multicast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flows =
are currently being replicated on each Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving an =
Admission Response from the NAS, indicating that</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
replication of a multicast flow is to start or stop on a given</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access =
port of the AN, the AN must enforce this decision.&nbsp; This</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
decision must be taken irrespective of whether or not a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
corresponding Admission Request was issued by the AN earlier on.</FONT>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">NAS multication requirements =
(section 4.8.6)</FONT></B>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to configure multicast conditional</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access =
information to Access Ports on an Access Node, using Black</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lists, =
Grey Lists and White Lists.</FONT>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to indicate to the AN whether or</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not =
Admission Control is needed for some multicast flows on a</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
given Access Port and where needed whether or not it is to be</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
performed with AN Bandwidth Delegation.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving =
a query from the AN for a request to replicate a</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flow to a particular Access Port, and no AN =
Bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Delegation is needed for that flow, the NAS must be able to</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
perform the necessary checks (conditional access and/or =
admission</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
control) for the new flow.&nbsp; The NAS must support using ANCP =
to</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
reply to the AN indicating whether the request is to be honored =
or</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
denied.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving =
a query from the AN for a request to replicate a</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flow to a particular Access Port, and Admission =
Control</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with =
AN Bandwidth Delegation is needed for that flow, the NAS must</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be =
able to perform the conditional access checks (if needed), =
and</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using ANCP to delegate a certain amount of bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to =
the AN for a given Access Port.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, upon</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
receiving a Bandwidth Delegation Request from the AN requesting =
to</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
increase the delegated multicast bandwidth on a given Access =
Port,</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
NAS must support using ANCP to send a Bandwidth Delegation</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Response indicating the new delegating multicast bandwidth.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, the NAS</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using ANCP to send a request the AN to decrease the</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
amount of multicast bandwidth previously delegated on a given</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Access Port; the NAS should be able to specify both the =
minimum</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =
the preferred amount decrement of multicast bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
requested.</FONT></I>
</P>

<P><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case of =
Admission Control with AN Bandwidth Delegation, upon</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
receiving an ANCP Bandwidth Release message, the NAS must be =
able</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to =
update accordingly its view of the multicast bandwidth</FONT></I>

<BR><I><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
delegated to the AN.</FONT></I>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to configure the Access Node with</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
&quot;maximum number of multicast streams&quot; allowed to be =
received</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
concurrently per Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to incrementally add, remove and</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; modify =
individual entries in White, Black and Grey lists.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to indicate to the AN whether or</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not =
multicast accounting is needed for a multicast flow on a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; In case multicast =
accounting is needed for a multicast flow on a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
particular Access Port, the NAS should support using ANCP to</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
indicate to the AN whether or not additional volume accounting</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
information is required.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to query the AN to obtain</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
information on what multicast flows are currently replicated on a</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given =
Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to query the AN to obtain</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
information on what Access Ports are currently receiving a given</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast flow.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS must =
support using ANCP to query the AN to obtain</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
information on what multicast flows are currently replicated on</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; each =
Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; When Multicast =
replication occurs on the AN, the NAS must support</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using =
ANCP to revoke the authorization to replicate a multicast</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flow to =
a particular Access Port.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o&nbsp; The NAS should =
support using ANCP to indicate to the AN that</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
replication of a multicast flow is to start or stop on a given</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access =
port of the AN, without having received a corresponding</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Admission Request from the AN earlier on.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">---</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Sven Ooghe</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Alcatel-Lucent</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">CTO Office, Access Division</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Copernicuslaan 50, 2018 Antwerp, =
Belgium</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">tel.: +32 3 240 42 26</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">fax: +32 3 240 40 73</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This message (including any =
attachments) contains confidential information intended for a specific =
individual and purpose, and is protected by law.&nbsp; If you are not =
the intended recipient, you should delete this message.&nbsp; Any =
disclosure, copying, or distribution of this message, or the taking of =
any action based on it, is strictly prohibited without the prior consent =
of its author.</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C9303A.032A85D2--

--===============1795784349==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1795784349==--


From ancp-bounces@ietf.org  Mon Oct 20 03:00:15 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 949DF3A69F9;
	Mon, 20 Oct 2008 03:00:15 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E54F13A69A3
	for <ancp@core3.amsl.com>; Mon, 20 Oct 2008 03:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 S69Adfli5IM1 for <ancp@core3.amsl.com>;
	Mon, 20 Oct 2008 03:00:13 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 668163A68E6
	for <ancp@ietf.org>; Mon, 20 Oct 2008 03:00:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,451,1220227200"; d="scan'208,217";a="23110772"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Oct 2008 10:01:22 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9KA1MZq022358; 
	Mon, 20 Oct 2008 12:01:22 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9KA1MWH015780;
	Mon, 20 Oct 2008 10:01:22 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 12:01:22 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 12:01:21 +0200
Message-Id: <FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: OOGHE Sven <Sven.Ooghe@alcatel-lucent.be>
In-Reply-To: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 12:01:20 +0200
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Oct 2008 10:01:21.0866 (UTC)
	FILETIME=[CDF752A0:01C9329A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6834; t=1224496882;
	x=1225360882; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com> |Subject:=20Re=3A=20[ANCP]=20ANCP=20Framework=20update
	|Sender:=20; bh=Xq2zKPhu2FaLaM7vhocPAMaETpi7wBTm9gPzgiKK3k4=;
	b=mYMCC/eDGH/nIDJAMG9UniRNk90N1QJrP1oDtlGKmy7QkxRTHOQ9hXBw8T
	KXjjHIXo8IX/yfV35hdQNXkvwNjRcI17nP1hN0D05pcRReNbf32GEZSBjORy
	MkbYoRacMQ;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1539216725=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============1539216725==
Content-Type: multipart/alternative; boundary=Apple-Mail-4--770938890


--Apple-Mail-4--770938890
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Sven and all,

>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List whose entry is flagged as "no Bandwidth Delegation" for the
>       relevant Access Port, the AN must support using ANCP to query  
> the
>       NAS to receive a response indicating whether that join is to be
>       honored or denied.  In this case, the NAS will perform both the
>       necessary conditional access and the admission control checks  
> for
>       the new flow.
>

Roberta, Tom and myself have started drafting an I-D that will propose  
ANCP protocol extensions supporting some of those requirements  
(building on top of ancp-mc-multicast).
In doing so, we revisited a point that came up multiple times: do we  
really need to provision a flag in each and every Grey/White List  
entry to activate/deactivate Bandwidth Delegation?

The current approach (as correctly reflected in the updated Framework)  
is:
	* define a flag in each Grey/White List entry
	* assume that this flag will normally either always be set in all  
entries or never set.
	* setting/no-setting the flag is all entries effectively acts as the  
knob to enable/disable Bandwidth Delegation, therefore we did not need  
to specify a specific knob to enable/disable Bandwidth Delegation.

Another approach would be:
	* remove flag from White/Grey list entries
	* define a specific knob to enable/disable Bandwidth Delegation at  
the AN granularity
	* in fact, define a generic AN-level provisioning method that could  
be used to enable/disable BAndwidth delegation, but could also be used  
for provisioning the "Service Profiles" that are currently assumed to  
be configured in AN, as well as provisioning the Multicast White/Grey/ 
Black Profiles

Considering that:
	- we got several times the feedback that per-entry BAndwidth  
Delegation flag was confusing since Bandwidth Delegation granularity  
is more AN-level (and may lead to difficulties if it is set on some  
entries and not on others)
	- it is likely that we'll need, anyways, a mechanism to provision  
things at AN level, that could be easily used to convey Bandwidth  
Delegation enable/disable knob.
we would like to propose to evolve to the newer approach.

Thoughts?

Francois

PS: Sven, if we go for the new approach, we can document in an email  
the deltas that would be needed to reflect that in framework.


--Apple-Mail-4--770938890
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Sven and =
all,<div><br></div><div><div><blockquote type=3D"cite"><div><p><i><font =
size=3D"2" face=3D"Arial">&nbsp;&nbsp; o&nbsp; Upon receiving a join to =
a multicast flow which matches the Grey</font></i> <br><i><font size=3D"2"=
 face=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is =
flagged as "no Bandwidth Delegation" for the</font></i> <br><i><font =
size=3D"2" face=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access =
Port, the AN must support using ANCP to query the</font></i> =
<br><i><font size=3D"2" face=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
NAS to receive a response indicating whether that join is to =
be</font></i> <br><i><font size=3D"2" =
face=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; =
In this case, the NAS will perform both the</font></i> <br><i><font =
size=3D"2" face=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
conditional access and the admission control checks for</font></i> =
<br><i><font size=3D"2" face=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the new =
flow.</font></i></p></div></blockquote><br></div><div><div>Roberta, Tom =
and myself have started drafting an I-D that will propose ANCP protocol =
extensions supporting some of those requirements (building on top of =
ancp-mc-multicast).</div><div>In doing so, we revisited a point that =
came up multiple times: do we really need to provision a flag in each =
and every Grey/White List entry =
to&nbsp;activate/deactivate&nbsp;Bandwidth =
Delegation?</div><div><br></div><div>The current approach (as correctly =
reflected in the updated Framework) is:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* define =
a flag in each Grey/White List entry<br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* assume =
that this flag will normally either always be set in all entries or =
never set.<br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* setting/no-setting the flag is =
all entries effectively acts as the knob to enable/disable Bandwidth =
Delegation, therefore we did not need to specify a specific knob to =
enable/disable Bandwidth =
Delegation.<br></div><div><br></div><div>Another approach would =
be:</div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>* remove flag from White/Grey list entries<br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* define =
a specific knob to enable/disable Bandwidth Delegation at the AN =
granularity</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* in fact, define a =
generic&nbsp;AN-level provisioning method that could be used to =
enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for provisioning the "Service Profiles" that are currently assumed to be =
configured in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles<br></div><div><br></div><div>Considering that:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>- we got =
several times the feedback that per-entry BAndwidth Delegation flag was =
confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and may lead to difficulties if it is set on some entries and not on =
others)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>- it is likely that we'll need, =
anyways, a mechanism to provision things at AN level, that could be =
easily used to convey Bandwidth Delegation enable/disable =
knob.<br></div><div>we&nbsp;would&nbsp;like to propose =
to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer =
approach.</div><div><br></div><div>Thoughts?</div><div><br></div><div>Fran=
cois</div><div><br></div><div>PS: Sven, if we go for&nbsp;the&nbsp;new =
approach, we can document in an email the deltas that&nbsp;would&nbsp;be =
needed to reflect that in =
framework.</div><div><br></div></div></div></body></html>=

--Apple-Mail-4--770938890--

--===============1539216725==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1539216725==--


From ancp-bounces@ietf.org  Mon Oct 20 03:21:10 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95B4D3A68F0;
	Mon, 20 Oct 2008 03:21:10 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F26DC3A68F0
	for <ancp@core3.amsl.com>; Mon, 20 Oct 2008 03:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 v4BGRxBc5B9T for <ancp@core3.amsl.com>;
	Mon, 20 Oct 2008 03:21:07 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27])
	by core3.amsl.com (Postfix) with ESMTP id B20CC3A63D2
	for <ancp@ietf.org>; Mon, 20 Oct 2008 03:21:06 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9KAM9Es009915; 
	Mon, 20 Oct 2008 12:22:13 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Mon, 20 Oct 2008 12:22:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 12:22:02 +0200
Message-ID: <7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP Framework update
Thread-Index: AckymtFGfrfEofrPQoGeMfpEnpFKqQAAiiIA
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
	<FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com>
From: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
X-OriginalArrivalTime: 20 Oct 2008 10:22:10.0577 (UTC)
	FILETIME=[B6418010:01C9329D]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0266664799=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0266664799==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9329D.B12360E5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9329D.B12360E5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Francois,
=20
Another approach we could take is to let the framework requirements be
agnostic as to how the Access Node knows whether or not Bandwidth
Delegation applies. We could describe the notion of Bandwidth Delegation
and the respective requirements for the Access Node and NAS in this
case.
=20
The details of how the use of Bandwidth Delegation is communicated to
the Access Node - using a flag, some "on/off" knob or both - would be
left to the actual protocol specification work.
=20
I think following this path would require relatively small edits to the
document. I'm ok to take a first shot at it.
=20
Regards,
Sven

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:01
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update


Sven and all,=20



	   o  Upon receiving a join to a multicast flow which matches
the Grey=20
	      List whose entry is flagged as "no Bandwidth Delegation"
for the=20
	      relevant Access Port, the AN must support using ANCP to
query the=20
	      NAS to receive a response indicating whether that join is
to be=20
	      honored or denied.  In this case, the NAS will perform
both the=20
	      necessary conditional access and the admission control
checks for=20
	      the new flow.


Roberta, Tom and myself have started drafting an I-D that will propose
ANCP protocol extensions supporting some of those requirements (building
on top of ancp-mc-multicast).
In doing so, we revisited a point that came up multiple times: do we
really need to provision a flag in each and every Grey/White List entry
to activate/deactivate Bandwidth Delegation?


The current approach (as correctly reflected in the updated Framework)
is:
* define a flag in each Grey/White List entry

* assume that this flag will normally either always be set in all
entries or never set.

* setting/no-setting the flag is all entries effectively acts as the
knob to enable/disable Bandwidth Delegation, therefore we did not need
to specify a specific knob to enable/disable Bandwidth Delegation.



Another approach would be:
* remove flag from White/Grey list entries

* define a specific knob to enable/disable Bandwidth Delegation at the
AN granularity
* in fact, define a generic AN-level provisioning method that could be
used to enable/disable BAndwidth delegation, but could also be used for
provisioning the "Service Profiles" that are currently assumed to be
configured in AN, as well as provisioning the Multicast White/Grey/Black
Profiles



Considering that:
- we got several times the feedback that per-entry BAndwidth Delegation
flag was confusing since Bandwidth Delegation granularity is more
AN-level (and may lead to difficulties if it is set on some entries and
not on others)
- it is likely that we'll need, anyways, a mechanism to provision things
at AN level, that could be easily used to convey Bandwidth Delegation
enable/disable knob.

we would like to propose to evolve to the newer approach.


Thoughts?

Francois

PS: Sven, if we go for the new approach, we can document in an email the
deltas that would be needed to reflect that in framework.


------_=_NextPart_001_01C9329D.B12360E5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Another approach we could take is to let the =
framework=20
requirements be agnostic as to how the Access Node knows whether or not=20
Bandwidth Delegation applies. We could describe the notion of Bandwidth=20
Delegation and the respective requirements for the Access Node and NAS =
in this=20
case.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The details of how the use of Bandwidth =
Delegation is=20
communicated to the Access Node - using a flag, some "on/off" knob or =
both -=20
would be left to the actual protocol specification =
work.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think following this path would require =
relatively small=20
edits to the document. I'm ok to take a first shot at =
it.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> maandag 20 oktober 2008=20
12:01<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV></DIV>Sven and all,
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
<DIV>
<DIV>
<BLOCKQUOTE type=3D"cite">
  <DIV>
  <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; Upon receiving =
a join to a=20
  multicast flow which matches the Grey</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is flagged as =
"no=20
  Bandwidth Delegation" for the</FONT></I> <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, the AN =
must=20
  support using ANCP to query the</FONT></I> <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a response =
indicating=20
  whether that join is to be</FONT></I> <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; In =
this case,=20
  the NAS will perform both the</FONT></I> <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional access =
and the=20
  admission control checks for</FONT></I> <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
flow.</FONT></I></P></DIV></BLOCKQUOTE><BR></DIV>
<DIV>
<DIV>Roberta, Tom and myself have started drafting an I-D that will =
propose ANCP=20
protocol extensions supporting some of those requirements (building on =
top of=20
ancp-mc-multicast).</DIV>
<DIV>In doing so, we revisited a point that came up multiple times: do =
we really=20
need to provision a flag in each and every Grey/White List entry=20
to&nbsp;activate/deactivate&nbsp;Bandwidth Delegation?</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial color=3D#0000ff=20
size=3D2></FONT><BR></DIV>
<DIV>The current approach (as correctly reflected in the updated =
Framework)=20
is:</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a flag=20
in each Grey/White List entry<BR></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
assume that=20
this flag will normally either always be set in all entries or never=20
set.<BR></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>*=20
setting/no-setting the flag is all entries effectively acts as the knob =
to=20
enable/disable Bandwidth Delegation, therefore we did not need to =
specify a=20
specific knob to enable/disable Bandwidth Delegation.<BR></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
<DIV>Another approach would be:</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
remove flag=20
from White/Grey list entries<BR></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
specific knob to enable/disable Bandwidth Delegation at the AN =
granularity</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* in =
fact,=20
define a generic&nbsp;AN-level provisioning method that could be used to =

enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for=20
provisioning the "Service Profiles" that are currently assumed to be =
configured=20
in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles<BR></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
<DIV>Considering that:</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- we =
got several=20
times the feedback that per-entry BAndwidth Delegation flag was =
confusing=20
since&nbsp;Bandwidth Delegation granularity is more AN-level (and may =
lead to=20
difficulties if it is set on some entries and not on others)</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- it =
is likely=20
that we'll need, anyways, a mechanism to provision things at AN level, =
that=20
could be easily used to convey Bandwidth Delegation enable/disable=20
knob.<BR></DIV>
<DIV>we&nbsp;would&nbsp;like to propose=20
to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
<DIV>Thoughts?</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV>
<DIV><BR></DIV>
<DIV>PS: Sven, if we go for&nbsp;the&nbsp;new approach, we can document =
in an=20
email the deltas that&nbsp;would&nbsp;be needed to reflect that in=20
framework.</DIV>
<DIV><BR></DIV></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C9329D.B12360E5--

--===============0266664799==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0266664799==--


From ancp-bounces@ietf.org  Mon Oct 20 03:57:22 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A5713A696E;
	Mon, 20 Oct 2008 03:57:22 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4B1C3A67BD
	for <ancp@core3.amsl.com>; Mon, 20 Oct 2008 03:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
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 VFhUzHO1elRs for <ancp@core3.amsl.com>;
	Mon, 20 Oct 2008 03:57:19 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 007DA3A6971
	for <ancp@ietf.org>; Mon, 20 Oct 2008 03:57:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,451,1220227200"; d="scan'208,217";a="23119806"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Oct 2008 10:58:28 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9KAwSCQ006454; 
	Mon, 20 Oct 2008 12:58:28 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9KAwRG1007359;
	Mon, 20 Oct 2008 10:58:28 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 12:58:27 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 12:58:26 +0200
Message-Id: <B574433E-1B70-4243-8A48-87B832982F98@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>
In-Reply-To: <7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 12:58:25 +0200
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
	<FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com>
	<7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Oct 2008 10:58:26.0416 (UTC)
	FILETIME=[C7282F00:01C932A2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12064; t=1224500308;
	x=1225364308; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com> |Subject:=20Re=3A=20[ANCP]=20ANCP=20Framework=20update
	|Sender:=20; bh=BFBrSYW3OiorsF9JfNezVNOvv114YzaFZs019ab9Ps4=;
	b=oaI5KTABWmrC1LzBZof+JIMRPsMd1eteUTNSKoZsG5tsRMw+C8t0B4HLdj
	d6z6+/2Kznrmrd4ZqD2kISEdYQ54EDhft0GDWUbDtbSZBx+Mhw+1v7uD/uyT
	kPqnHNl9SP;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0215823117=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============0215823117==
Content-Type: multipart/alternative; boundary=Apple-Mail-5--767514234


--Apple-Mail-5--767514234
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On 20 Oct 2008, at 12:22, OOGHE Sven wrote:

> Francois,
>
> Another approach we could take is to let the framework requirements  
> be agnostic as to how the Access Node knows whether or not Bandwidth  
> Delegation applies. We could describe the notion of Bandwidth  
> Delegation and the respective requirements for the Access Node and  
> NAS in this case.
>
> The details of how the use of Bandwidth Delegation is communicated  
> to the Access Node - using a flag, some "on/off" knob or both -  
> would be left to the actual protocol specification work.

Good idea. It will avoid these cross dependencies between framework  
and protocol, which indeed reflect that we are probably trying to be  
too precise/prescriptive in the framework.

>
> I think following this path would require relatively small edits to  
> the document. I'm ok to take a first shot at it.

That would be good.

Thanks

Francois

>
> Regards,
> Sven
>
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: maandag 20 oktober 2008 12:01
> To: OOGHE Sven
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> Subject: Re: [ANCP] ANCP Framework update
>
> Sven and all,
>
>>    o  Upon receiving a join to a multicast flow which matches the  
>> Grey
>>       List whose entry is flagged as "no Bandwidth Delegation" for  
>> the
>>       relevant Access Port, the AN must support using ANCP to query  
>> the
>>       NAS to receive a response indicating whether that join is to be
>>       honored or denied.  In this case, the NAS will perform both the
>>       necessary conditional access and the admission control checks  
>> for
>>       the new flow.
>>
>
> Roberta, Tom and myself have started drafting an I-D that will  
> propose ANCP protocol extensions supporting some of those  
> requirements (building on top of ancp-mc-multicast).
> In doing so, we revisited a point that came up multiple times: do we  
> really need to provision a flag in each and every Grey/White List  
> entry to activate/deactivate Bandwidth Delegation?
>
> The current approach (as correctly reflected in the updated  
> Framework) is:
> * define a flag in each Grey/White List entry
> * assume that this flag will normally either always be set in all  
> entries or never set.
> * setting/no-setting the flag is all entries effectively acts as the  
> knob to enable/disable Bandwidth Delegation, therefore we did not  
> need to specify a specific knob to enable/disable Bandwidth  
> Delegation.
>
> Another approach would be:
> * remove flag from White/Grey list entries
> * define a specific knob to enable/disable Bandwidth Delegation at  
> the AN granularity
> * in fact, define a generic AN-level provisioning method that could  
> be used to enable/disable BAndwidth delegation, but could also be  
> used for provisioning the "Service Profiles" that are currently  
> assumed to be configured in AN, as well as provisioning the  
> Multicast White/Grey/Black Profiles
>
> Considering that:
> - we got several times the feedback that per-entry BAndwidth  
> Delegation flag was confusing since Bandwidth Delegation granularity  
> is more AN-level (and may lead to difficulties if it is set on some  
> entries and not on others)
> - it is likely that we'll need, anyways, a mechanism to provision  
> things at AN level, that could be easily used to convey Bandwidth  
> Delegation enable/disable knob.
> we would like to propose to evolve to the newer approach.
>
> Thoughts?
>
> Francois
>
> PS: Sven, if we go for the new approach, we can document in an email  
> the deltas that would be needed to reflect that in framework.
>


--Apple-Mail-5--767514234
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On 20 Oct 2008, =
at 12:22, OOGHE Sven wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"> <div =
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><span class=3D"427541610-20102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Francois,</font></span></div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"427541610-20102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> =
<div dir=3D"ltr" align=3D"left"><span class=3D"427541610-20102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">Another approach we could =
take is to let the framework requirements be agnostic as to how the =
Access Node knows whether or not Bandwidth Delegation applies. We could =
describe the notion of Bandwidth Delegation and the respective =
requirements for the Access Node and NAS in this =
case.</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"427541610-20102008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"427541610-20102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">The details of how the use of Bandwidth =
Delegation is communicated to the Access Node - using a flag, some =
"on/off" knob or both - would be left to the actual protocol =
specification =
work.</font></span></div></div></blockquote><div><br></div><div>Good =
idea. It will avoid these cross dependencies between framework and =
protocol, which indeed reflect that we are probably trying to be too =
precise/prescriptive in&nbsp;the&nbsp;framework.</div><br><blockquote =
type=3D"cite"><div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><span class=3D"427541610-20102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"427541610-20102008"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2">I think following this path would require =
relatively small edits to the document. I'm ok to take a first shot at =
it.</font></span></div></div></blockquote><div><br></div><div>That would =
be =
good.</div><div><br></div><div>Thanks</div><div><br></div><div>Francois</d=
iv><br><blockquote type=3D"cite"><div style=3D"WORD-WRAP: break-word; =
webkit-nbsp-mode: space; webkit-line-break: after-white-space"> <div =
dir=3D"ltr" align=3D"left"><span class=3D"427541610-20102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> =
<div dir=3D"ltr" align=3D"left"><span class=3D"427541610-20102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">Regards,</font></span></div> =
<div dir=3D"ltr" align=3D"left"><span class=3D"427541610-20102008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">Sven</font></span></div><br> =
<div class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" =
align=3D"left"> <hr tabindex=3D"-1"> <font face=3D"Tahoma" =
size=3D"2"><b>From:</b> Francois Le Faucheur IMAP [<a =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</a>] =
<br><b>Sent:</b> maandag 20 oktober 2008 12:01<br><b>To:</b> OOGHE =
Sven<br><b>Cc:</b> Francois Le Faucheur IMAP; <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br><b>Subject:</b> Re: =
[ANCP] ANCP Framework update<br></font><br></div> <div></div>Sven and =
all, <div><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><br></div> <div> <div> <blockquote type=3D"cite">  =
<div><p><i><font face=3D"Arial" size=3D"2">&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to a   multicast flow which matches the Grey</font></i> =
<br><i><font face=3D"Arial" size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List whose entry is flagged as "no   Bandwidth Delegation" for =
the</font></i> <br><i><font face=3D"Arial" =
size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, the AN =
must   support using ANCP to query the</font></i> <br><i><font =
face=3D"Arial" size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive =
a response indicating   whether that join is to be</font></i> =
<br><i><font face=3D"Arial" size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
honored or denied.&nbsp; In this case,   the NAS will perform both =
the</font></i> <br><i><font face=3D"Arial" =
size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional access =
and the   admission control checks for</font></i> <br><i><font =
face=3D"Arial" size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow.</font></i></p></div></blockquote><br></div> <div> <div>Roberta, =
Tom and myself have started drafting an I-D that will propose ANCP =
protocol extensions supporting some of those requirements (building on =
top of ancp-mc-multicast).</div> <div>In doing so, we revisited a point =
that came up multiple times: do we really need to provision a flag in =
each and every Grey/White List entry =
to&nbsp;activate/deactivate&nbsp;Bandwidth Delegation?</div> <div><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"></font><br></div> <div>The current approach =
(as correctly reflected in the updated Framework) is:</div> <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* define a =
flag in each Grey/White List entry<br></div> <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* assume that =
this flag will normally either always be set in all entries or never =
set.<br></div> <div><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: =
pre"></span>* setting/no-setting the flag is all entries effectively =
acts as the knob to enable/disable Bandwidth Delegation, therefore we =
did not need to specify a specific knob to enable/disable Bandwidth =
Delegation.<br></div> <div><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><br></div> <div>Another approach would be:</div> =
<div><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* =
remove flag from White/Grey list entries<br></div> <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>* define a =
specific knob to enable/disable Bandwidth Delegation at the AN =
granularity</div> <div><span class=3D"Apple-tab-span" =
style=3D"WHITE-SPACE: pre"></span>* in fact, define a =
generic&nbsp;AN-level provisioning method that could be used to =
enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for provisioning the "Service Profiles" that are currently assumed to be =
configured in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles<br></div> <div><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><br></div> <div>Considering that:</div> <div><span =
class=3D"Apple-tab-span" style=3D"WHITE-SPACE: pre"></span>- we got =
several times the feedback that per-entry BAndwidth Delegation flag was =
confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and may lead to difficulties if it is set on some entries and not on =
others)</div> <div><span class=3D"Apple-tab-span" style=3D"WHITE-SPACE: =
pre"></span>- it is likely that we'll need, anyways, a mechanism to =
provision things at AN level, that could be easily used to convey =
Bandwidth Delegation enable/disable knob.<br></div> =
<div>we&nbsp;would&nbsp;like to propose =
to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</div> <div><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font><br></div> =
<div>Thoughts?</div> <div><br></div> <div>Francois</div> <div><br></div> =
<div>PS: Sven, if we go for&nbsp;the&nbsp;new approach, we can document =
in an email the deltas that&nbsp;would&nbsp;be needed to reflect that in =
framework.</div> =
<div><br></div></div></div></div></blockquote></div><br></body></html>=

--Apple-Mail-5--767514234--

--===============0215823117==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0215823117==--


From ancp-bounces@ietf.org  Wed Oct 22 03:40:55 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC3C63A6A92;
	Wed, 22 Oct 2008 03:40:55 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01E593A6A0F
	for <ancp@core3.amsl.com>; Wed, 22 Oct 2008 03:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_LOW=-1]
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 5QrxTu72B19G for <ancp@core3.amsl.com>;
	Wed, 22 Oct 2008 03:40:51 -0700 (PDT)
Received: from tcmail12.telekom.de (tcmail12.telekom.de [217.5.214.82])
	by core3.amsl.com (Postfix) with ESMTP id F3FDD3A685D
	for <ancp@ietf.org>; Wed, 22 Oct 2008 03:40:49 -0700 (PDT)
Received: from s4de8psaans.mitte.t-com.de (s4de8psaans.mitte.t-com.de
	[10.151.180.168]) by tcmail11.telekom.de with ESMTP;
	Wed, 22 Oct 2008 12:42:02 +0200
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by
	s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 22 Oct 2008 12:42:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 12:42:01 +0200
Message-Id: <5661758E3E93364685B91DD8272F28763BCB2C@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <1B6169C658325341A3B8066E23919E1C013455FD@S4DE8PSAANK.mitte.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP Framework update
Thread-Index: AckwOgJsIJe9VJgbRHSt5ybOabbM2wDEwJggAAAlFrgANTaq0A==
References: <1B6169C658325341A3B8066E23919E1C013455FD@S4DE8PSAANK.mitte.t-com.de>
From: "Haag, Thomas" <HaagT@telekom.de>
To: <sven.ooghe@alcatel-lucent.be>
X-OriginalArrivalTime: 22 Oct 2008 10:42:02.0378 (UTC)
	FILETIME=[D17366A0:01C93432]
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0718562315=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0718562315==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93432.D12E6748"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93432.D12E6748
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Sven,
=20
please see my comments inline.=20
=20
Regards=20
Thomas Haag=20
Deutsche Telekom AG
Zentrum Technik Einf=FChrung
TE5-22, Internationale Standardisierung
Heinrich-Hertz-Stra=DFe 3-7, 64295 Darmstadt
+49 6151 628-2088 (Tel.)
+49 521 9210-8411 (Fax)
+49 171 56 44 739 (Mobil)
Neu: Email: haagt@telekom.de
http://www.telekom.com <http://www.telekom.com/> =20
=20


________________________________


Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von =
OOGHE Sven
Gesendet: Freitag, 17. Oktober 2008 11:23
An: ancp@ietf.org
Betreff: [ANCP] ANCP Framework update

=20

Hi,=20

I've been updating the ANCP framework draft according to the suggested =
changes from Roberta and Francois. Below I have copy-pasted the sections =
that have undergone changes. Indented text has been changed. I think I =
captured the essence of the notion of "bandwidth delegation". Please =
review and see if this is capturing the agreements.

Regards,=20
Sven=20

=20

3.4.2.  Multicast Admission Control=20

   The successful delivery of Triple Play Broadband services is quickly=20
   becoming a big capacity planning challenge for most of the Service=20
   Providers nowadays.  Solely increasing available bandwidth is not=20
   always practical, cost-economical and/or sufficient to satisfy end=20
   user experience given not only the strict requirements of unicast=20
   delay sensitive applications like VoIP and Video, but also the fast=20
   growth of multicast interactive applications such as=20
   videoconferencing, digital TV, digital audio, online movies and=20
   networked gaming.  These applications are typically characterized by=20
   a delay sensitive nature, an extremely loss sensitive nature and=20
   intensive bandwidth requirements.  They are also typically "non-=20
   elastic", which means that they operate at a fixed bandwidth, that=20
   cannot be dynamically adjusted to the currently available bandwidth.=20

   Therefore a Connection Admission Control (CAC) mechanism covering=20
   admission of multicast traffic over the DSL Broadband access is=20
   required, in order to avoid oversubscribing the available bandwidth=20
   and negatively impacting the end user experience.=20

   Considering specifically admission control over the access line,=20
   before honoring a user request to join a new multicast flow, the=20
   combination of AN and NAS MUST ensure admission control is performed=20
   to validate that there is enough "video" bandwidth remaining on the=20
   access line to carry the new flow (in addition to all other existing=20
   multicast and unicast video traffic).  The solution needs to cope=20
   with multiple flows per access line and needs to allow access line=20
   bandwidth to be dynamically shared across multicast and unicast=20
   traffic (irrespective of whether unicast CAC is performed by NAS or=20
   by some off-path Policy Server).=20

   Thus, supporting CAC for the access line requires some form of=20
   synchronization between the entity performing multicast CAC (e.g. the =

   NAS or the AN) and the entity performing unicast CAC (e.g. the NAS or =

   a Policy Server) and the entity actually enforcing the multicast  =
[T.H.: Is that correct as stated "NAS or Policy server"?; My =
understanding: Policy Server: Policy decission point; NAS controls AN by =
ANCP;AN: policy enforcement point] =20
   replication (i.e. the AN).  This synchronization can be achieved in a =

   number of ways:=20

   o  One approach is for the AN to query the NAS so that Admission=20
      Control for the access line is performed by the NAS (possibly with =

      interactions with a Policy Server).  This can be done with or=20
      without "bandwidth delegation" to the AN.=20

      *  In case of Admission Control without AN Bandwidth Delegation,=20
         the AN can use ANCP to query the NAS, that in turn performs=20
         multicast Admission Control check for the new multicast flow=20
         and responds to the AN indicating whether the join is to be=20
         honored (and hence replication performed by the AN) or denied.=20
         The NAS may locally maintain available "video" bandwidth  =
[T.H.:]  (net data rate) on the=20
         Access Loop, and perform video bandwidth accounting for the=20
         Access Loop.  Upon receiving an Admission Request from the AN,=20
         the NAS can check available "video" bandwidth before admitting=20
         or denying the multicast flow.  In the process, the NAS may=20
         communicate with the Policy Server.  For unicast video services =

         such as Video on Demand (VoD), the NAS may also be queried (by=20
         a Policy Server or via on-path CAC signaling), so that it can=20
         perform admission control for the unicast flow, and update the=20
         available video bandwidth maintained by the NAS.=20

      *  In case of Admission Control with AN Bandwidth Delegation, the=20
         NAS (possibly with interactions with a Policy Server) manages=20
         total bandwidth for video admission, performs unicast admission =

         control and uses ANCP to delegate a certain amount of bandwidth =

         for some multicast flows to the Access Node.  In this scenario, =

         upon receiving a join to a multicast flow which matches an=20
         entry in the White or Grey List whose entry is flagged as=20
         "Bandwidth Delegation", the AN must perform the necessary=20
         bandwidth admission control check for the new multicast flow,=20
         before starting the multicast flow replication.=20

      The ANCP requirements to support this approach are specified in=20
      this document.=20

   o  In case the subscriber communicates the "join/leave" information=20
      with the NAS (e.g. by terminating all subscriber IGMP signaling on =

      the NAS, or by using some form of application level signaling),=20
      the approach is very similar.  In this case, the NAS may locally=20
      maintain available "video" bandwidth on the Access Loop, perform=20
      video bandwidth accounting, and perform CAC for unicast and=20
      multicast flows.  The NAS can set the replication state on the AN=20
      using ANCP if the flow is admitted.  For unicast video services=20
      the NAS may be queried (by a policy server or via on-path CAC=20
      signaling) to perform admission control for the unicast flow, and=20
      update the available video bandwidth maintained by the NAS.  The=20
      ANCP requirements to support this approach (where the AN queries=20
      the NAS) are specified in this document;=20

   o  In a third approach, the Policy Server queries the AN directly so=20
      that both unicast and multicast CAC for the access line are=20
      performed by the AN.  In this case, a subscriber request for a=20
      unicast flow (e.g. a Video on Demand session) will trigger a=20
      resource request message towards a Policy Server; the latter will=20
      then query the AN, that in turn will perform unicast CAC for the=20
      access line and respond, indicating whether the unicast request is =

      to be honored or denied.  In this scenario the Policy Server=20
      queries the AN directly, the approach doesn't require the use of=20
      ANCP.  It is therefore beyond the scope of this document.=20

=20

4.2.  ANCP Multicast Requirements=20

   o  The ANCP MUST support providing multicast conditional access=20
      information to Access Ports on an Access Node, using Black, Grey=20
      and White lists.=20

   o  The ANCP MUST support binding a particular Black, Grey and White=20
      List to a given Access Port.=20

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List the ANCP MUST allow the AN to query the NAS to request an=20
      admission decision for replicating that multicast flow to a=20
      particular Access Port.=20

   o  The ANCP MUST allow the NAS to send an admission decision to the=20
      AN indicating whether or not a multicast flow may be replicated to =

      a particular Access Port.=20

   o  The ANCP must allow the NAS to indicate to the AN whether or not=20
      Admission Control is needed for some multicast flows on a given=20
      Access Port and where needed whether or not it is to be performed=20
      with AN Bandwidth Delegation.=20

   o  In case of Admission Control without AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to reply to a query from the AN indicating =

      whether or not a multicast flow may be replicated to a particular=20
      Access Port.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to delegate a certain amount of bandwidth=20
      to the AN for a given Access Port.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the AN to query the NAS to request additional=20
      multicast bandwidth on a given Access Port.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to query (or to instruct) the AN to reduce =

      the amount of bandwidth previously delegated on a given Access=20
      Port.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the AN to autonomous release redundant multicast=20
      bandwidth on a given Access Port.=20

   o  The ANCP MUST allow the AN to send an Information Report message=20
      to the NAS whenever replication of a multicast flow on a=20
      particular Access Port start or ends.=20

   o  The ANCP MUST allow the AN to send an Information Report message=20
      to the NAS indicating the multicast traffic volume that has been=20
      replicated on that port.=20

   o  The ANCP MUST allow the NAS to indicate to the AN whether or not=20
      multicast accounting is needed for a multicast flow on a=20
      particular Access Port.=20

   o  In case multicast accounting is needed for a multicast flow on a=20
      particular Access Port, the ANCP MUST allow the NAS to indicate to =

      the AN whether or not additional volume accounting information is=20
      required.=20

   o  The ANCP MUST allow the NAS to revoke a decision to replicate a=20
      multicast flow to a particular Access Port, which had been=20
      conveyed earlier to an AN.=20

   o  The ANCP MUST support partial updates of the White, Grey and Black =

      lists.=20

   o  The ANCP MUST allow the NAS to query the AN to obtain information=20
      on what multicast flows are currently being replicated on a given=20
      Access Port, what Access Ports are currently receiving a given=20
      multicast flow, or what multicast flows are currently replicated=20
      on each Access Port.=20

=20

Access Node multicast requirements (section 4.7.6)=20

   o  The AN must deny any join to a multicast flow matching the Black=20
      List for the relevant Access Port.=20

   o  The AN must accept any join to a multicast flow matching the White =

      List and not flagged as "Bandwidth Delegation" for the relevant=20
      Access Port.=20

   o  Upon receiving a join to a multicast flow which matches the White=20
      List whose entry is flagged as "Bandwidth Delegation" for the=20
      relevant Access Port, the AN must perform the necessary bandwidth=20
      admission control check for the new flow before starting the=20
      multicast flow replication.=20

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List whose entry is flagged as "no Bandwidth Delegation" for the=20
      relevant Access Port, the AN must support using ANCP to query the=20
      NAS to receive a response indicating whether that join is to be=20
      honored or denied.  In this case, the NAS will perform both the=20
      necessary conditional access and the admission control checks for=20
      the new flow.=20

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List whose entry is flagged as "Bandwidth Delegation" for the=20
      relevant Access Port, the AN must first perform the necessary=20
      bandwidth admission control check for the new flow.  If=20
      successful, the AN must support using ANCP to query the NAS to=20
      receive a response indicating whether that join is to be honored=20
      or denied.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to notify the NAS when the the user leaves =

      the multicast flow.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to query the NAS to request additional=20
      delegated multicast bandwidth on a given Access Port; the AN=20
      should be able to specify both the minimum and the preferred=20
      amount of additional multicast bandwidth requested.=20

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving a Bandwidth Delegation Request from the NAS querying or=20
      instructing to decrease the delegated multicast bandwidth on a=20
      given Access Port, the AN must support using ANCP to send a=20
      Bandwidth Delegation Response indicating the new delegated=20
      multicast bandwidth.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to send a Bandwidth Release message to the =

      NAS in order to release unused delegated multicast bandwidth on a=20
      given Access Port.=20

   o  If the requested multicast flow is not part of any list associated =

      with the Access Port, the AN must discard the message.=20

   o  If the requested multicast flow is part of multiple lists=20
      associated with the Access Port, the AN must use the most specific =

      match.=20

   o  If the requested multicast flow has the same most specific match=20
      in multiple lists, the AN must give precedence to the Black list,=20
      followed by the Grey list, and then the White list.=20

   o  The AN must support configuring a "catch-all" statement in the=20
      Black, White or Grey list in order to enforce a default behavior=20
      for a join to a multicast flow which doesn't match any other entry =

      in a list for the relevant Access Port.=20

   o  Upon querying the NAS, the AN must not propagate the join message=20
      before the successful authorization from the NAS is received.=20

   o  Upon receiving a leave for a multicast flow which matches the Grey =

      List, the AN should be able to autonomously stop replication and=20
      advertise this event to the NAS.=20

   o  The AN must support using ANCP to send an Information Report=20
      message to the NAS whenever replication starts or ends  [T.H:] or =
fails .=20

   o  The AN should support using ANCP to send an Information Report=20
      message to the NAS indicating the multicast traffic volume that=20
      has been replicated on that port.=20

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what multicast=20
      flows are currently being replicated on a given Access Port.=20

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what Access=20
      Ports are currently receiving a given multicast flow.=20

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what multicast=20
      flows are currently being replicated on each Access Port.=20

   o  Upon receiving an Admission Response from the NAS, indicating that =

      replication of a multicast flow is to start or stop on a given=20
      access port of the AN, the AN must enforce this decision.  This=20
      decision must be taken irrespective of whether or not a=20
      corresponding Admission Request was issued by the AN earlier on.=20

=20

NAS multication requirements (section 4.8.6)=20

   o  The NAS must support using ANCP to configure multicast conditional =

      access information to Access Ports on an Access Node, using Black=20
      Lists, Grey Lists and White Lists.=20

   o  The NAS must support using ANCP to indicate to the AN whether or=20
      not Admission Control is needed for some multicast flows on a=20
      given Access Port and where needed whether or not it is to be=20
      performed with AN Bandwidth Delegation.=20

   o  Upon receiving a query from the AN for a request to replicate a=20
      multicast flow to a particular Access Port, and no AN Bandwidth=20
      Delegation is needed for that flow, the NAS must be able to=20
      perform the necessary checks (conditional access and/or admission=20
      control) for the new flow.  The NAS must support using ANCP to=20
      reply to the AN indicating whether the request is to be honored or =

      denied.=20

   o  Upon receiving a query from the AN for a request to replicate a=20
      multicast flow to a particular Access Port, and Admission Control=20
      with AN Bandwidth Delegation is needed for that flow, the NAS must =

      be able to perform the conditional access checks (if needed), and=20
      must support using ANCP to delegate a certain amount of bandwidth=20
      to the AN for a given Access Port.=20

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving a Bandwidth Delegation Request from the AN requesting to =

      increase the delegated multicast bandwidth on a given Access Port, =

      the NAS must support using ANCP to send a Bandwidth Delegation=20
      Response indicating the new delegating multicast bandwidth.=20

   o  In case of Admission Control with AN Bandwidth Delegation, the NAS =

      must support using ANCP to send a request the AN to decrease the=20
      amount of multicast bandwidth previously delegated on a given=20
      Access Port; the NAS should be able to specify both the minimum=20
      and the preferred amount decrement of multicast bandwidth=20
      requested.=20

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving an ANCP Bandwidth Release message, the NAS must be able=20
      to update accordingly its view of the multicast bandwidth=20
      delegated to the AN.=20

   o  The NAS must support using ANCP to configure the Access Node with=20
      the "maximum number of multicast streams" allowed to be received=20
      concurrently per Access Port.=20

   o  The NAS must support using ANCP to incrementally add, remove and=20
      modify individual entries in White, Black and Grey lists.=20

   o  The NAS must support using ANCP to indicate to the AN whether or=20
      not multicast accounting is needed for a multicast flow on a=20
      particular Access Port.=20

   o  In case multicast accounting is needed for a multicast flow on a=20
      particular Access Port, the NAS should support using ANCP to=20
      indicate to the AN whether or not additional volume accounting=20
      information is required.=20

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what multicast flows are currently replicated on a=20
      given Access Port.=20

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what Access Ports are currently receiving a given=20
      multicast flow.=20

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what multicast flows are currently replicated on=20
      each Access Port.=20

   o  When Multicast replication occurs on the AN, the NAS must support=20
      using ANCP to revoke the authorization to replicate a multicast=20
      flow to a particular Access Port.=20

   o  The NAS should support using ANCP to indicate to the AN that=20
      replication of a multicast flow is to start or stop on a given=20
      access port of the AN, without having received a corresponding=20
      Admission Request from the AN earlier on.=20

---=20

Sven Ooghe=20
Alcatel-Lucent=20
CTO Office, Access Division=20
Copernicuslaan 50, 2018 Antwerp, Belgium=20
tel.: +32 3 240 42 26=20
fax: +32 3 240 40 73=20

This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly prohibited =
without the prior consent of its author.


------_=_NextPart_001_01C93432.D12E6748
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>ANCP Framework =
update</TITLE>

<META content=3D"MSHTML 6.00.2900.3354" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
   BEHAVIOR: url(#default#VML)
}
o\:* {
   BEHAVIOR: url(#default#VML)
}
w\:* {
   BEHAVIOR: url(#default#VML)
}
.shape {
   BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
   font-family: MS Mincho;
}
@font-face {
   font-family: Tahoma;
}
@font-face {
   font-family: @MS Mincho;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 70.85pt 2.0cm =
70.85pt; }
P.MsoNormal {
   FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
   FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
   FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
   COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
   COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
   COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
   COLOR: purple; TEXT-DECORATION: underline
}
P {
   FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.E-MailFormatvorlage18 {
   COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
   page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DDE vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D734534408-22102008>Hi Sven,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D734534408-22102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D734534408-22102008>please see my comments inline. =
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D734534408-22102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D734534408-22102008></SPAN></FONT><B><SPAN lang=3Dde><FONT =
size=3D2><SPAN=20
class=3D734534408-22102008>R</SPAN>egards</FONT></SPAN></B><SPAN =
lang=3Dde></SPAN>=20
<BR><SPAN lang=3Dde><B><FONT size=3D2>Thomas Haag</FONT></B></SPAN> =
<BR><SPAN=20
lang=3Dde><FONT color=3D#808080 size=3D2>Deutsche Telekom AG<BR>Zentrum =
Technik=20
Einf&#xFC;hrung<BR>TE5-22, Internationale =
Standardisierung<BR>Heinrich-Hertz-Stra&#xDF;e=20
3-7, 64295 Darmstadt<BR>+49 6151 628-2088 (Tel.)<BR>+49 521 9210-8411=20
(Fax)<BR>+49 171 56 44 739 (Mobil)</FONT><B><BR></B><FONT =
color=3D#ff0000=20
size=3D2>Neu:</FONT> <FONT color=3D#808080 size=3D2>Email:</FONT><U> =
<FONT=20
color=3D#0000ff size=3D2>haagt@telekom.de</FONT></U><FONT =
color=3D#808080=20
size=3D2><BR></FONT></SPAN><A href=3D"http://www.telekom.com/"><SPAN=20
lang=3Dde><U></U><U><FONT color=3D#0000ff=20
size=3D2>http://www.telekom.com</FONT></U></SPAN></A><SPAN =
lang=3Dde><FONT=20
color=3D#808080 size=3D2></FONT> </SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV><FONT face=3DArial=20
color=3D#0000ff size=3D2></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><BR>
<DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<DIV class=3DSection1>
<DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">Von:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
style=3D"FONT-WEIGHT: bold">Im Auftrag von </SPAN></B>OOGHE =
Sven<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B> Freitag, 17. Oktober =
2008=20
11:23<BR><B><SPAN style=3D"FONT-WEIGHT: bold">An:</SPAN></B>=20
ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Betreff:</SPAN></B> [ANCP]=20
ANCP Framework update</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT> =
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I've been updating the =
ANCP=20
framework draft according to the suggested changes from Roberta and =
Francois.=20
Below I have copy-pasted the sections that have undergone =
changes.<I><SPAN=20
style=3D"FONT-STYLE: italic"> Indented text</SPAN></I> has been changed. =
I think I=20
captured the essence of the notion of "bandwidth delegation". Please =
review and=20
see if this is capturing the agreements.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Regards,</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sven</SPAN></FONT> =
<o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">3.4.2.&nbsp;=20
Multicast Admission Control</SPAN></FONT></B> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; The =
successful delivery=20
of Triple Play Broadband services is quickly</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; becoming a=20
big capacity planning challenge for most of the Service</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
Providers nowadays.&nbsp; Solely increasing available bandwidth is=20
not</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; always =
practical,=20
cost-economical and/or sufficient to satisfy end</SPAN></FONT> <BR><FONT =

face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
user experience given not only the strict requirements of =
unicast</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; delay =
sensitive=20
applications like VoIP and Video, but also the fast</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
growth of multicast interactive applications such as</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
videoconferencing, digital TV, digital audio, online movies =
and</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; networked =
gaming.&nbsp;=20
These applications are typically characterized by</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
a delay sensitive nature, an extremely loss sensitive nature =
and</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; intensive =
bandwidth=20
requirements.&nbsp; They are also typically "non-</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
elastic", which means that they operate at a fixed bandwidth, =
that</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; cannot be =
dynamically=20
adjusted to the currently available bandwidth.</SPAN></FONT> =
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Therefore a =
Connection=20
Admission Control (CAC) mechanism covering</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; admission=20
of multicast traffic over the DSL Broadband access is</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
required, in order to avoid oversubscribing the available=20
bandwidth</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; and =
negatively=20
impacting the end user experience.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Considering=20
specifically admission control over the access line,</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
before honoring a user request to join a new multicast flow, =
the</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; combination =
of AN and=20
NAS MUST ensure admission control is performed</SPAN></FONT> <BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
to validate that there is enough "video" bandwidth remaining on=20
the</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; access line =
to carry=20
the new flow (in addition to all other existing</SPAN></FONT> <BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
multicast and unicast video traffic).&nbsp; The solution needs to=20
cope</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; with multiple =
flows per=20
access line and needs to allow access line</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; bandwidth=20
to be dynamically shared across multicast and unicast</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
traffic (irrespective of whether unicast CAC is performed by NAS=20
or</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; by some =
off-path Policy=20
Server).</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Thus, =
supporting CAC=20
for the access line requires some form of</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
synchronization between the entity performing multicast CAC (e.g.=20
the</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; NAS or the =
AN) and the=20
entity performing unicast CAC (e.g. the NAS or</SPAN></FONT> <BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; a Policy =
Server) and=20
the entity actually enforcing the multicast<SPAN =
class=3D734534408-22102008><FONT=20
color=3D#0000ff>&nbsp; [T.H.: Is that correct as stated "NAS or Policy =
server"?;=20
My understanding: Policy Server: Policy&nbsp;decission point;&nbsp;NAS =
controls=20
AN&nbsp;by ANCP;AN: policy enforcement=20
point]&nbsp;</FONT></SPAN></SPAN>&nbsp;<BR><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; replication =
(i.e. the=20
AN).&nbsp; This synchronization can be achieved in a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
number of ways:</SPAN></FONT> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; One approach is for the AN to query the NAS so that=20
Admission</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Control for the access line is performed by the NAS (possibly=20
with</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
interactions with a Policy Server).&nbsp; This can be done with=20
or</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
without "bandwidth delegation" to the AN.</SPAN></FONT></I> =
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
*&nbsp; In case of Admission Control without AN Bandwidth=20
Delegation,</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the AN can use ANCP to query the NAS, that in turn =
performs</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast Admission Control check for the new multicast =
flow</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
and responds to the AN indicating whether the join is to =
be</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
honored (and hence replication performed by the AN) or =
denied.</SPAN></FONT></I>=20
<BR><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The NAS may locally maintain available "video" bandwidth&nbsp;<FONT=20
color=3D#0000ff><SPAN =
class=3D734534408-22102008>&nbsp;[T.H.:]&nbsp;</SPAN><SPAN=20
class=3D734534408-22102008>&nbsp;(net data rate)&nbsp;</SPAN></FONT>on =
the</SPAN>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Loop, and perform video bandwidth accounting for =
the</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Loop.&nbsp; Upon receiving an Admission Request from the=20
AN,</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the NAS can check available "video" bandwidth before =
admitting</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
or denying the multicast flow.&nbsp; In the process, the NAS=20
may</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
communicate with the Policy Server.&nbsp; For unicast video=20
services</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
such as Video on Demand (VoD), the NAS may also be queried =
(by</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
a Policy Server or via on-path CAC signaling), so that it =
can</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
perform admission control for the unicast flow, and update =
the</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
available video bandwidth maintained by the NAS.</SPAN></FONT></I>=20
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
*&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
NAS (possibly with interactions with a Policy Server) =
manages</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
total bandwidth for video admission, performs unicast=20
admission</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
control and uses ANCP to delegate a certain amount of=20
bandwidth</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
for some multicast flows to the Access Node.&nbsp; In this=20
scenario,</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
upon receiving a join to a multicast flow which matches =
an</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
entry in the White or Grey List whose entry is flagged =
as</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"Bandwidth Delegation", the AN must perform the =
necessary</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
bandwidth admission control check for the new multicast =
flow,</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
before starting the multicast flow replication.</SPAN></FONT></I>=20
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The ANCP requirements to support this approach are specified=20
in</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
this document.</SPAN></FONT></I> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
case the=20
subscriber communicates the "join/leave" information</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with=20
the NAS (e.g. by terminating all subscriber IGMP signaling =
on</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
NAS, or by using some form of application level =
signaling),</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
approach is very similar.&nbsp; In this case, the NAS may =
locally</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
maintain available "video" bandwidth on the Access Loop, =
perform</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video=20
bandwidth accounting, and perform CAC for unicast and</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flows.&nbsp; The NAS can set the replication state on the=20
AN</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using=20
ANCP if the flow is admitted.&nbsp; For unicast video =
services</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
NAS may be queried (by a policy server or via on-path CAC</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
signaling) to perform admission control for the unicast flow, =
and</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
update the available video bandwidth maintained by the NAS.&nbsp;=20
The</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP=20
requirements to support this approach (where the AN =
queries</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
NAS) are specified in this document;</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In a =
third=20
approach, the Policy Server queries the AN directly so</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that=20
both unicast and multicast CAC for the access line are</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
performed by the AN.&nbsp; In this case, a subscriber request for=20
a</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
unicast flow (e.g. a Video on Demand session) will trigger =
a</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
resource request message towards a Policy Server; the latter =
will</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then=20
query the AN, that in turn will perform unicast CAC for =
the</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
access line and respond, indicating whether the unicast request =
is</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to be=20
honored or denied.&nbsp; In this scenario the Policy =
Server</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
queries the AN directly, the approach doesn't require the use =
of</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
ANCP.&nbsp; It is therefore beyond the scope of this =
document.</SPAN></FONT>=20
<o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">4.2.&nbsp; ANCP=20
Multicast Requirements</SPAN></FONT></B> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
support providing multicast conditional access</SPAN></FONT> <BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
information to Access Ports on an Access Node, using Black, =
Grey</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and=20
White lists.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
support binding a particular Black, Grey and White</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List=20
to a given Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
receiving=20
a join to a multicast flow which matches the Grey</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List=20
the ANCP MUST allow the AN to query the NAS to request an</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
admission decision for replicating that multicast flow to =
a</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
particular Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
allow the NAS to send an admission decision to the</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AN=20
indicating whether or not a multicast flow may be replicated =
to</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=20
particular Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; The ANCP must allow the NAS to indicate to the AN whether or=20
not</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Admission Control is needed for some multicast flows on a=20
given</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Port and where needed whether or not it is to be=20
performed</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
with AN Bandwidth Delegation.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control without AN Bandwidth Delegation,=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
ANCP must allow the NAS to reply to a query from the AN=20
indicating</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
whether or not a multicast flow may be replicated to a=20
particular</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
ANCP must allow the NAS to delegate a certain amount of=20
bandwidth</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
to the AN for a given Access Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
ANCP must allow the AN to query the NAS to request =
additional</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast bandwidth on a given Access Port.</SPAN></FONT></I> =
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
ANCP must allow the NAS to query (or to instruct) the AN to=20
reduce</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the amount of bandwidth previously delegated on a given =
Access</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
ANCP must allow the AN to autonomous release redundant=20
multicast</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
bandwidth on a given Access Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
allow the AN to send an Information Report message</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to=20
the NAS whenever replication of a multicast flow on a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
particular Access Port start or ends.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
allow the AN to send an Information Report message</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to=20
the NAS indicating the multicast traffic volume that has =
been</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
replicated on that port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
allow the NAS to indicate to the AN whether or not</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast accounting is needed for a multicast flow on a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
particular Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
case=20
multicast accounting is needed for a multicast flow on a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
particular Access Port, the ANCP MUST allow the NAS to indicate =
to</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
AN whether or not additional volume accounting information =
is</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
required.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
allow the NAS to revoke a decision to replicate a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flow to a particular Access Port, which had been</SPAN></FONT> =

<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
conveyed earlier to an AN.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
support partial updates of the White, Grey and Black</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
lists.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
allow the NAS to query the AN to obtain information</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on=20
what multicast flows are currently being replicated on a =
given</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Port, what Access Ports are currently receiving a =
given</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flow, or what multicast flows are currently =
replicated</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on=20
each Access Port.</SPAN></FONT> <o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Access =
Node=20
multicast requirements (section 4.7.6)</SPAN></FONT></B> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must=20
deny any join to a multicast flow matching the Black</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List=20
for the relevant Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; The AN must accept any join to a multicast flow matching the=20
White</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
List and not flagged as "Bandwidth Delegation" for the=20
relevant</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; Upon receiving a join to a multicast flow which matches the=20
White</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
List whose entry is flagged as "Bandwidth Delegation" for =
the</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
relevant Access Port, the AN must perform the necessary=20
bandwidth</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
admission control check for the new flow before starting =
the</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flow replication.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; Upon receiving a join to a multicast flow which matches the=20
Grey</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
List whose entry is flagged as "no Bandwidth Delegation" for=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
relevant Access Port, the AN must support using ANCP to query=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
NAS to receive a response indicating whether that join is to=20
be</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
honored or denied.&nbsp; In this case, the NAS will perform both=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
necessary conditional access and the admission control checks=20
for</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the new flow.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; Upon receiving a join to a multicast flow which matches the=20
Grey</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
List whose entry is flagged as "Bandwidth Delegation" for =
the</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
relevant Access Port, the AN must first perform the =
necessary</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
bandwidth admission control check for the new flow.&nbsp; =
If</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
successful, the AN must support using ANCP to query the NAS =
to</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
receive a response indicating whether that join is to be=20
honored</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
or denied.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the=20
AN</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
must support using ANCP to notify the NAS when the the user=20
leaves</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the multicast flow.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the=20
AN</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
must support using ANCP to query the NAS to request =
additional</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
delegated multicast bandwidth on a given Access Port; the =
AN</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
should be able to specify both the minimum and the =
preferred</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
amount of additional multicast bandwidth requested.</SPAN></FONT></I>=20
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
upon</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
receiving a Bandwidth Delegation Request from the NAS querying=20
or</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
instructing to decrease the delegated multicast bandwidth on =
a</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
given Access Port, the AN must support using ANCP to send =
a</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Bandwidth Delegation Response indicating the new =
delegated</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast bandwidth.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the=20
AN</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
must support using ANCP to send a Bandwidth Release message to=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
NAS in order to release unused delegated multicast bandwidth on=20
a</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
given Access Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the=20
requested multicast flow is not part of any list =
associated</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with=20
the Access Port, the AN must discard the message.</SPAN></FONT> =
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the=20
requested multicast flow is part of multiple lists</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
associated with the Access Port, the AN must use the most =
specific</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
match.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the=20
requested multicast flow has the same most specific match</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
multiple lists, the AN must give precedence to the Black =
list,</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
followed by the Grey list, and then the White list.</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must=20
support configuring a "catch-all" statement in the</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Black, White or Grey list in order to enforce a default =
behavior</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for a=20
join to a multicast flow which doesn't match any other =
entry</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in a=20
list for the relevant Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
querying=20
the NAS, the AN must not propagate the join message</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
before the successful authorization from the NAS is =
received.</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
receiving=20
a leave for a multicast flow which matches the Grey</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List,=20
the AN should be able to autonomously stop replication and</SPAN></FONT> =

<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
advertise this event to the NAS.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must=20
support using ANCP to send an Information Report</SPAN></FONT> <BR><SPAN =

style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
message to the NAS whenever replication starts or ends<SPAN=20
class=3D734534408-22102008><FONT color=3D#0000ff>&nbsp; [T.H:] or=20
fails&nbsp;</FONT></SPAN>.</SPAN> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN should=20
support using ANCP to send an Information Report</SPAN></FONT> <BR><FONT =

face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
message to the NAS indicating the multicast traffic volume =
that</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has=20
been replicated on that port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
request by=20
the NAS, the AN must support using ANCP to send an</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Information Report message to the NAS, indicating what =
multicast</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flows=20
are currently being replicated on a given Access Port.</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
request by=20
the NAS, the AN must support using ANCP to send an</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Information Report message to the NAS, indicating what =
Access</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ports=20
are currently receiving a given multicast flow.</SPAN></FONT> =
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
request by=20
the NAS, the AN must support using ANCP to send an</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Information Report message to the NAS, indicating what =
multicast</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flows=20
are currently being replicated on each Access Port.</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
receiving=20
an Admission Response from the NAS, indicating that</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
replication of a multicast flow is to start or stop on a =
given</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
access port of the AN, the AN must enforce this decision.&nbsp;=20
This</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
decision must be taken irrespective of whether or not a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
corresponding Admission Request was issued by the AN earlier =
on.</SPAN></FONT>=20
<o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P><B><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">NAS =
multication=20
requirements (section 4.8.6)</SPAN></FONT></B> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to configure multicast conditional</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
access information to Access Ports on an Access Node, using =
Black</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Lists, Grey Lists and White Lists.</SPAN></FONT> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; The NAS must support using ANCP to indicate to the AN whether=20
or</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
not Admission Control is needed for some multicast flows on =
a</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
given Access Port and where needed whether or not it is to =
be</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
performed with AN Bandwidth Delegation.</SPAN></FONT></I> =
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; Upon receiving a query from the AN for a request to replicate=20
a</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flow to a particular Access Port, and no AN=20
Bandwidth</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Delegation is needed for that flow, the NAS must be able =
to</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
perform the necessary checks (conditional access and/or=20
admission</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
control) for the new flow.&nbsp; The NAS must support using ANCP=20
to</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
reply to the AN indicating whether the request is to be honored=20
or</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
denied.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; Upon receiving a query from the AN for a request to replicate=20
a</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flow to a particular Access Port, and Admission=20
Control</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
with AN Bandwidth Delegation is needed for that flow, the NAS=20
must</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
be able to perform the conditional access checks (if needed),=20
and</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
must support using ANCP to delegate a certain amount of=20
bandwidth</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
to the AN for a given Access Port.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
upon</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
receiving a Bandwidth Delegation Request from the AN requesting=20
to</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
increase the delegated multicast bandwidth on a given Access=20
Port,</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the NAS must support using ANCP to send a Bandwidth =
Delegation</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Response indicating the new delegating multicast =
bandwidth.</SPAN></FONT></I>=20
<o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the=20
NAS</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
must support using ANCP to send a request the AN to decrease=20
the</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
amount of multicast bandwidth previously delegated on a =
given</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Port; the NAS should be able to specify both the=20
minimum</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
and the preferred amount decrement of multicast =
bandwidth</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
requested.</SPAN></FONT></I> <o:p></o:p></P>
<P><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
upon</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
receiving an ANCP Bandwidth Release message, the NAS must be=20
able</SPAN></FONT></I> <BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
to update accordingly its view of the multicast =
bandwidth</SPAN></FONT></I>=20
<BR><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
delegated to the AN.</SPAN></FONT></I> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to configure the Access Node with</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
"maximum number of multicast streams" allowed to be =
received</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
concurrently per Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to incrementally add, remove and</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
modify individual entries in White, Black and Grey lists.</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to indicate to the AN whether or</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not=20
multicast accounting is needed for a multicast flow on a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
particular Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
case=20
multicast accounting is needed for a multicast flow on a</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
particular Access Port, the NAS should support using ANCP =
to</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
indicate to the AN whether or not additional volume =
accounting</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
information is required.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to query the AN to obtain</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
information on what multicast flows are currently replicated on =
a</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given=20
Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to query the AN to obtain</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
information on what Access Ports are currently receiving a =
given</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
multicast flow.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
support using ANCP to query the AN to obtain</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
information on what multicast flows are currently replicated =
on</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; each=20
Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; When =
Multicast=20
replication occurs on the AN, the NAS must support</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using=20
ANCP to revoke the authorization to replicate a multicast</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flow=20
to a particular Access Port.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS should=20
support using ANCP to indicate to the AN that</SPAN></FONT> <BR><FONT =
face=3DArial=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
replication of a multicast flow is to start or stop on a =
given</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
access port of the AN, without having received a =
corresponding</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Admission Request from the AN earlier on.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">---</SPAN></FONT> =
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sven Ooghe</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Alcatel-Lucent</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">CTO Office, Access=20
Division</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Copernicuslaan 50, 2018 =
Antwerp,=20
Belgium</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">tel.: +32 3 240 42 =
26</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">fax: +32 3 240 40 =
73</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This message (including =
any=20
attachments) contains confidential information intended for a specific=20
individual and purpose, and is protected by law.&nbsp; If you are not =
the=20
intended recipient, you should delete this message.&nbsp; Any =
disclosure,=20
copying, or distribution of this message, or the taking of any action =
based on=20
it, is strictly prohibited without the prior consent of its=20
author.</SPAN></FONT><o:p></o:p></P></DIV></BODY></HTML>

------_=_NextPart_001_01C93432.D12E6748--

--===============0718562315==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0718562315==--


From ancp-bounces@ietf.org  Wed Oct 22 04:51:19 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 763833A69C5;
	Wed, 22 Oct 2008 04:51:19 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7EB228C128
	for <ancp@core3.amsl.com>; Wed, 22 Oct 2008 04:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.436
X-Spam-Level: 
X-Spam-Status: No, score=0.436 tagged_above=-999 required=5 tests=[AWL=0.930, 
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 TBdyp+jo9Gi5 for <ancp@core3.amsl.com>;
	Wed, 22 Oct 2008 04:51:15 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67])
	by core3.amsl.com (Postfix) with ESMTP id 4B7CF3A67F2
	for <ancp@ietf.org>; Wed, 22 Oct 2008 04:51:14 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9500C0S2B88H@szxga04-in.huawei.com> for
	ancp@ietf.org; Wed, 22 Oct 2008 19:52:20 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K950095K2B7I5@szxga04-in.huawei.com> for
	ancp@ietf.org; Wed, 22 Oct 2008 19:52:20 +0800 (CST)
Received: from [192.168.0.100]
	(56.73.61.58.broad.sz.gd.dynamic.163data.com.cn [58.61.73.56])
	by szxml01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006))
	with ESMTPA id <0K9500FZA2B3QS@szxml01-in.huawei.com>; Wed,
	22 Oct 2008 19:52:19 +0800 (CST)
Date: Wed, 22 Oct 2008 19:52:15 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <5661758E3E93364685B91DD8272F28763BCB2C@S4DE8PSAAQC.mitte.t-com.de>
To: "Haag, Thomas" <HaagT@telekom.de>
Message-id: <2DD715E8-D3C9-4DF3-BF95-0D52BBB3B96B@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.929.2)
References: <1B6169C658325341A3B8066E23919E1C013455FD@S4DE8PSAANK.mitte.t-com.de>
	<5661758E3E93364685B91DD8272F28763BCB2C@S4DE8PSAAQC.mitte.t-com.de>
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0196023899=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============0196023899==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_PySLYHjJQctGWyb9vDmAjg)"


--Boundary_(ID_PySLYHjJQctGWyb9vDmAjg)
Content-type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-transfer-encoding: quoted-printable

Hi all,
I agree with Thomas' comments.


B. R.
Tina

Messengers:

MSN: tinatsou6@hotmail.com   Yahoo: tina_tsou    Skype: tinaTSOU    =20
Jabber: tina@jabber.org    Google talk: tinatsou6@gmail.com

+86-755-28971872 (Office)    +86-13922884380(Mobile)



On Oct 22, 2008, at 6:42 PM, Haag, Thomas wrote:

> Hi Sven,
>
> please see my comments inline.
>
> Regards
> Thomas Haag
> Deutsche Telekom AG
> Zentrum Technik Einf=FChrung
> TE5-22, Internationale Standardisierung
> Heinrich-Hertz-Stra=DFe 3-7, 64295 Darmstadt
> +49 6151 628-2088 (Tel.)
> +49 521 9210-8411 (Fax)
> +49 171 56 44 739 (Mobil)
> Neu: Email: haagt@telekom.de
> http://www.telekom.com
>
>
> Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag =20=

> von OOGHE Sven
> Gesendet: Freitag, 17. Oktober 2008 11:23
> An: ancp@ietf.org
> Betreff: [ANCP] ANCP Framework update
>
> Hi,
>
> I've been updating the ANCP framework draft according to the =20
> suggested changes from Roberta and Francois. Below I have copy-=20
> pasted the sections that have undergone changes. Indented text has =20
> been changed. I think I captured the essence of the notion of =20
> "bandwidth delegation". Please review and see if this is capturing =20
> the agreements.
>
> Regards,
> Sven
>
>
> 3.4.2.  Multicast Admission Control
>
>    The successful delivery of Triple Play Broadband services is =20
> quickly
>    becoming a big capacity planning challenge for most of the Service
>    Providers nowadays.  Solely increasing available bandwidth is not
>    always practical, cost-economical and/or sufficient to satisfy end
>    user experience given not only the strict requirements of unicast
>    delay sensitive applications like VoIP and Video, but also the fast
>    growth of multicast interactive applications such as
>    videoconferencing, digital TV, digital audio, online movies and
>    networked gaming.  These applications are typically characterized =20=

> by
>    a delay sensitive nature, an extremely loss sensitive nature and
>    intensive bandwidth requirements.  They are also typically "non-
>    elastic", which means that they operate at a fixed bandwidth, that
>    cannot be dynamically adjusted to the currently available =20
> bandwidth.
>
>    Therefore a Connection Admission Control (CAC) mechanism covering
>    admission of multicast traffic over the DSL Broadband access is
>    required, in order to avoid oversubscribing the available bandwidth
>    and negatively impacting the end user experience.
>
>    Considering specifically admission control over the access line,
>    before honoring a user request to join a new multicast flow, the
>    combination of AN and NAS MUST ensure admission control is =20
> performed
>    to validate that there is enough "video" bandwidth remaining on the
>    access line to carry the new flow (in addition to all other =20
> existing
>    multicast and unicast video traffic).  The solution needs to cope
>    with multiple flows per access line and needs to allow access line
>    bandwidth to be dynamically shared across multicast and unicast
>    traffic (irrespective of whether unicast CAC is performed by NAS or
>    by some off-path Policy Server).
>
>    Thus, supporting CAC for the access line requires some form of
>    synchronization between the entity performing multicast CAC (e.g. =20=

> the
>    NAS or the AN) and the entity performing unicast CAC (e.g. the =20
> NAS or
>    a Policy Server) and the entity actually enforcing the multicast  =20=

> [T.H.: Is that correct as stated "NAS or Policy server"?; My =20
> understanding: Policy Server: Policy decission point; NAS controls =20
> AN by ANCP;AN: policy enforcement point]
>    replication (i.e. the AN).  This synchronization can be achieved =20=

> in a
>    number of ways:
>
>    o  One approach is for the AN to query the NAS so that Admission
>       Control for the access line is performed by the NAS (possibly =20=

> with
>       interactions with a Policy Server).  This can be done with or
>       without "bandwidth delegation" to the AN.
>
>       *  In case of Admission Control without AN Bandwidth Delegation,
>          the AN can use ANCP to query the NAS, that in turn performs
>          multicast Admission Control check for the new multicast flow
>          and responds to the AN indicating whether the join is to be
>          honored (and hence replication performed by the AN) or =20
> denied.
>          The NAS may locally maintain available "video" bandwidth  =20
> [T.H.:]  (net data rate) on the
>          Access Loop, and perform video bandwidth accounting for the
>          Access Loop.  Upon receiving an Admission Request from the =20=

> AN,
>          the NAS can check available "video" bandwidth before =20
> admitting
>          or denying the multicast flow.  In the process, the NAS may
>          communicate with the Policy Server.  For unicast video =20
> services
>          such as Video on Demand (VoD), the NAS may also be queried =20=

> (by
>          a Policy Server or via on-path CAC signaling), so that it can
>          perform admission control for the unicast flow, and update =20=

> the
>          available video bandwidth maintained by the NAS.
>
>       *  In case of Admission Control with AN Bandwidth Delegation, =20=

> the
>          NAS (possibly with interactions with a Policy Server) manages
>          total bandwidth for video admission, performs unicast =20
> admission
>          control and uses ANCP to delegate a certain amount of =20
> bandwidth
>          for some multicast flows to the Access Node.  In this =20
> scenario,
>          upon receiving a join to a multicast flow which matches an
>          entry in the White or Grey List whose entry is flagged as
>          "Bandwidth Delegation", the AN must perform the necessary
>          bandwidth admission control check for the new multicast flow,
>          before starting the multicast flow replication.
>
>       The ANCP requirements to support this approach are specified in
>       this document.
>
>    o  In case the subscriber communicates the "join/leave" information
>       with the NAS (e.g. by terminating all subscriber IGMP =20
> signaling on
>       the NAS, or by using some form of application level signaling),
>       the approach is very similar.  In this case, the NAS may locally
>       maintain available "video" bandwidth on the Access Loop, perform
>       video bandwidth accounting, and perform CAC for unicast and
>       multicast flows.  The NAS can set the replication state on the =20=

> AN
>       using ANCP if the flow is admitted.  For unicast video services
>       the NAS may be queried (by a policy server or via on-path CAC
>       signaling) to perform admission control for the unicast flow, =20=

> and
>       update the available video bandwidth maintained by the NAS.  The
>       ANCP requirements to support this approach (where the AN queries
>       the NAS) are specified in this document;
>
>    o  In a third approach, the Policy Server queries the AN directly =20=

> so
>       that both unicast and multicast CAC for the access line are
>       performed by the AN.  In this case, a subscriber request for a
>       unicast flow (e.g. a Video on Demand session) will trigger a
>       resource request message towards a Policy Server; the latter =20
> will
>       then query the AN, that in turn will perform unicast CAC for the
>       access line and respond, indicating whether the unicast =20
> request is
>       to be honored or denied.  In this scenario the Policy Server
>       queries the AN directly, the approach doesn't require the use of
>       ANCP.  It is therefore beyond the scope of this document.
>
>
> 4.2.  ANCP Multicast Requirements
>
>    o  The ANCP MUST support providing multicast conditional access
>       information to Access Ports on an Access Node, using Black, Grey
>       and White lists.
>
>    o  The ANCP MUST support binding a particular Black, Grey and White
>       List to a given Access Port.
>
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List the ANCP MUST allow the AN to query the NAS to request an
>       admission decision for replicating that multicast flow to a
>       particular Access Port.
>
>    o  The ANCP MUST allow the NAS to send an admission decision to the
>       AN indicating whether or not a multicast flow may be =20
> replicated to
>       a particular Access Port.
>
>    o  The ANCP must allow the NAS to indicate to the AN whether or not
>       Admission Control is needed for some multicast flows on a given
>       Access Port and where needed whether or not it is to be =20
> performed
>       with AN Bandwidth Delegation.
>
>    o  In case of Admission Control without AN Bandwidth Delegation, =20=

> the
>       ANCP must allow the NAS to reply to a query from the AN =20
> indicating
>       whether or not a multicast flow may be replicated to a =20
> particular
>       Access Port.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the
>       ANCP must allow the NAS to delegate a certain amount of =20
> bandwidth
>       to the AN for a given Access Port.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the
>       ANCP must allow the AN to query the NAS to request additional
>       multicast bandwidth on a given Access Port.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the
>       ANCP must allow the NAS to query (or to instruct) the AN to =20
> reduce
>       the amount of bandwidth previously delegated on a given Access
>       Port.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the
>       ANCP must allow the AN to autonomous release redundant multicast
>       bandwidth on a given Access Port.
>
>    o  The ANCP MUST allow the AN to send an Information Report message
>       to the NAS whenever replication of a multicast flow on a
>       particular Access Port start or ends.
>
>    o  The ANCP MUST allow the AN to send an Information Report message
>       to the NAS indicating the multicast traffic volume that has been
>       replicated on that port.
>
>    o  The ANCP MUST allow the NAS to indicate to the AN whether or not
>       multicast accounting is needed for a multicast flow on a
>       particular Access Port.
>
>    o  In case multicast accounting is needed for a multicast flow on a
>       particular Access Port, the ANCP MUST allow the NAS to =20
> indicate to
>       the AN whether or not additional volume accounting information =20=

> is
>       required.
>
>    o  The ANCP MUST allow the NAS to revoke a decision to replicate a
>       multicast flow to a particular Access Port, which had been
>       conveyed earlier to an AN.
>
>    o  The ANCP MUST support partial updates of the White, Grey and =20
> Black
>       lists.
>
>    o  The ANCP MUST allow the NAS to query the AN to obtain =20
> information
>       on what multicast flows are currently being replicated on a =20
> given
>       Access Port, what Access Ports are currently receiving a given
>       multicast flow, or what multicast flows are currently replicated
>       on each Access Port.
>
>
> Access Node multicast requirements (section 4.7.6)
>
>    o  The AN must deny any join to a multicast flow matching the Black
>       List for the relevant Access Port.
>
>    o  The AN must accept any join to a multicast flow matching the =20
> White
>       List and not flagged as "Bandwidth Delegation" for the relevant
>       Access Port.
>
>    o  Upon receiving a join to a multicast flow which matches the =20
> White
>       List whose entry is flagged as "Bandwidth Delegation" for the
>       relevant Access Port, the AN must perform the necessary =20
> bandwidth
>       admission control check for the new flow before starting the
>       multicast flow replication.
>
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List whose entry is flagged as "no Bandwidth Delegation" for the
>       relevant Access Port, the AN must support using ANCP to query =20=

> the
>       NAS to receive a response indicating whether that join is to be
>       honored or denied.  In this case, the NAS will perform both the
>       necessary conditional access and the admission control checks =20=

> for
>       the new flow.
>
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List whose entry is flagged as "Bandwidth Delegation" for the
>       relevant Access Port, the AN must first perform the necessary
>       bandwidth admission control check for the new flow.  If
>       successful, the AN must support using ANCP to query the NAS to
>       receive a response indicating whether that join is to be honored
>       or denied.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the =20=

> AN
>       must support using ANCP to notify the NAS when the the user =20
> leaves
>       the multicast flow.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the =20=

> AN
>       must support using ANCP to query the NAS to request additional
>       delegated multicast bandwidth on a given Access Port; the AN
>       should be able to specify both the minimum and the preferred
>       amount of additional multicast bandwidth requested.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving a Bandwidth Delegation Request from the NAS querying =20=

> or
>       instructing to decrease the delegated multicast bandwidth on a
>       given Access Port, the AN must support using ANCP to send a
>       Bandwidth Delegation Response indicating the new delegated
>       multicast bandwidth.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the =20=

> AN
>       must support using ANCP to send a Bandwidth Release message to =20=

> the
>       NAS in order to release unused delegated multicast bandwidth =20
> on a
>       given Access Port.
>
>    o  If the requested multicast flow is not part of any list =20
> associated
>       with the Access Port, the AN must discard the message.
>
>    o  If the requested multicast flow is part of multiple lists
>       associated with the Access Port, the AN must use the most =20
> specific
>       match.
>
>    o  If the requested multicast flow has the same most specific match
>       in multiple lists, the AN must give precedence to the Black =20
> list,
>       followed by the Grey list, and then the White list.
>
>    o  The AN must support configuring a "catch-all" statement in the
>       Black, White or Grey list in order to enforce a default behavior
>       for a join to a multicast flow which doesn't match any other =20
> entry
>       in a list for the relevant Access Port.
>
>    o  Upon querying the NAS, the AN must not propagate the join =20
> message
>       before the successful authorization from the NAS is received.
>
>    o  Upon receiving a leave for a multicast flow which matches the =20=

> Grey
>       List, the AN should be able to autonomously stop replication and
>       advertise this event to the NAS.
>
>    o  The AN must support using ANCP to send an Information Report
>       message to the NAS whenever replication starts or ends  [T.H:] =20=

> or fails .
>
>    o  The AN should support using ANCP to send an Information Report
>       message to the NAS indicating the multicast traffic volume that
>       has been replicated on that port.
>
>    o  Upon request by the NAS, the AN must support using ANCP to =20
> send an
>       Information Report message to the NAS, indicating what multicast
>       flows are currently being replicated on a given Access Port.
>
>    o  Upon request by the NAS, the AN must support using ANCP to =20
> send an
>       Information Report message to the NAS, indicating what Access
>       Ports are currently receiving a given multicast flow.
>
>    o  Upon request by the NAS, the AN must support using ANCP to =20
> send an
>       Information Report message to the NAS, indicating what multicast
>       flows are currently being replicated on each Access Port.
>
>    o  Upon receiving an Admission Response from the NAS, indicating =20=

> that
>       replication of a multicast flow is to start or stop on a given
>       access port of the AN, the AN must enforce this decision.  This
>       decision must be taken irrespective of whether or not a
>       corresponding Admission Request was issued by the AN earlier on.
>
>
> NAS multication requirements (section 4.8.6)
>
>    o  The NAS must support using ANCP to configure multicast =20
> conditional
>       access information to Access Ports on an Access Node, using =20
> Black
>       Lists, Grey Lists and White Lists.
>
>    o  The NAS must support using ANCP to indicate to the AN whether or
>       not Admission Control is needed for some multicast flows on a
>       given Access Port and where needed whether or not it is to be
>       performed with AN Bandwidth Delegation.
>
>    o  Upon receiving a query from the AN for a request to replicate a
>       multicast flow to a particular Access Port, and no AN Bandwidth
>       Delegation is needed for that flow, the NAS must be able to
>       perform the necessary checks (conditional access and/or =20
> admission
>       control) for the new flow.  The NAS must support using ANCP to
>       reply to the AN indicating whether the request is to be =20
> honored or
>       denied.
>
>    o  Upon receiving a query from the AN for a request to replicate a
>       multicast flow to a particular Access Port, and Admission =20
> Control
>       with AN Bandwidth Delegation is needed for that flow, the NAS =20=

> must
>       be able to perform the conditional access checks (if needed), =20=

> and
>       must support using ANCP to delegate a certain amount of =20
> bandwidth
>       to the AN for a given Access Port.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving a Bandwidth Delegation Request from the AN =20
> requesting to
>       increase the delegated multicast bandwidth on a given Access =20
> Port,
>       the NAS must support using ANCP to send a Bandwidth Delegation
>       Response indicating the new delegating multicast bandwidth.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, the =20=

> NAS
>       must support using ANCP to send a request the AN to decrease the
>       amount of multicast bandwidth previously delegated on a given
>       Access Port; the NAS should be able to specify both the minimum
>       and the preferred amount decrement of multicast bandwidth
>       requested.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving an ANCP Bandwidth Release message, the NAS must be =20
> able
>       to update accordingly its view of the multicast bandwidth
>       delegated to the AN.
>
>    o  The NAS must support using ANCP to configure the Access Node =20
> with
>       the "maximum number of multicast streams" allowed to be received
>       concurrently per Access Port.
>
>    o  The NAS must support using ANCP to incrementally add, remove and
>       modify individual entries in White, Black and Grey lists.
>
>    o  The NAS must support using ANCP to indicate to the AN whether or
>       not multicast accounting is needed for a multicast flow on a
>       particular Access Port.
>
>    o  In case multicast accounting is needed for a multicast flow on a
>       particular Access Port, the NAS should support using ANCP to
>       indicate to the AN whether or not additional volume accounting
>       information is required.
>
>    o  The NAS must support using ANCP to query the AN to obtain
>       information on what multicast flows are currently replicated =20
> on a
>       given Access Port.
>
>    o  The NAS must support using ANCP to query the AN to obtain
>       information on what Access Ports are currently receiving a given
>       multicast flow.
>
>    o  The NAS must support using ANCP to query the AN to obtain
>       information on what multicast flows are currently replicated on
>       each Access Port.
>
>    o  When Multicast replication occurs on the AN, the NAS must =20
> support
>       using ANCP to revoke the authorization to replicate a multicast
>       flow to a particular Access Port.
>
>    o  The NAS should support using ANCP to indicate to the AN that
>       replication of a multicast flow is to start or stop on a given
>       access port of the AN, without having received a corresponding
>       Admission Request from the AN earlier on.
>
> ---
>
> Sven Ooghe
> Alcatel-Lucent
> CTO Office, Access Division
> Copernicuslaan 50, 2018 Antwerp, Belgium
> tel.: +32 3 240 42 26
> fax: +32 3 240 40 73
>
> This message (including any attachments) contains confidential =20
> information intended for a specific individual and purpose, and is =20
> protected by law.  If you are not the intended recipient, you should =20=

> delete this message.  Any disclosure, copying, or distribution of =20
> this message, or the taking of any action based on it, is strictly =20
> prohibited without the prior consent of its author.
>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp


--Boundary_(ID_PySLYHjJQctGWyb9vDmAjg)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Hi all,</div><div>I agree =
with Thomas' comments.</div><div><br></div><br><div =
apple-content-edited=3D"true"> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>B. =
R.</div><div>Tina</div><div><br></div><div><p align=3D"">Messengers:</p><p=
 align=3D"">MSN: <a =
href=3D"mailto:tinatsou6@hotmail.com">tinatsou6@hotmail.com</a>&nbsp;&nbsp=
; Yahoo: tina_tsou&nbsp;&nbsp;&nbsp; Skype: tinaTSOU&nbsp;&nbsp;&nbsp; =
Jabber: <a =
href=3D"mailto:tina@jabber.org">tina@jabber.org</a>&nbsp;&nbsp;&nbsp; =
Google talk: <a =
href=3D"mailto:tinatsou6@gmail.com">tinatsou6@gmail.com</a></p><p =
align=3D"">+86-755-28971872 (Office)&nbsp;&nbsp;&nbsp; =
+86-13922884380(Mobile)</p></div></div></div></span></div></span></div></s=
pan></div></span></div></span></div></span></div></span></div></span></div=
></span></div><div><br></div><br><div><div>On Oct 22, 2008, at 6:42 PM, =
Haag, Thomas wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div lang=3D"DE" vlink=3D"purple" =
link=3D"blue"><div dir=3D"ltr" align=3D"left"><font face=3D"Arial" =
color=3D"#0000ff" size=3D"2"><span class=3D"734534408-22102008">Hi =
Sven,</span></font></div><div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008"></span></font>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008">please see my comments =
inline.</span></font></div><div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008"></span></font>&nbsp;</div><div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008"></span></font><b><span lang=3D"de"><font =
size=3D"2"><span =
class=3D"734534408-22102008">R</span>egards</font></span></b><span =
lang=3D"de"></span><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span =
lang=3D"de"><b><font size=3D"2">Thomas Haag</font></b></span><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span lang=3D"de"><font =
color=3D"#808080" size=3D"2">Deutsche Telekom AG<br>Zentrum Technik =
Einf=FChrung<br>TE5-22, Internationale =
Standardisierung<br>Heinrich-Hertz-Stra=DFe 3-7, 64295 Darmstadt<br>+49 =
6151 628-2088 (Tel.)<br>+49 521 9210-8411 (Fax)<br>+49 171 56 44 739 =
(Mobil)</font><b><br></b><font color=3D"#ff0000" =
size=3D"2">Neu:</font><span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#808080" =
size=3D"2">Email:</font><u><span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#0000ff" =
size=3D"2"><a href=3D"mailto:haagt@telekom.de" style=3D"color: blue; =
text-decoration: underline; ">haagt@telekom.de</a></font></u><font =
color=3D"#808080" size=3D"2"><br></font></span><a =
href=3D"http://www.telekom.com/" style=3D"color: blue; text-decoration: =
underline; "><span lang=3D"de"><u></u><u><font color=3D"#0000ff" =
size=3D"2">http://www.telekom.com</font></u></span></a><span =
lang=3D"de"><font color=3D"#808080" =
size=3D"2"></font></span></div><div><font face=3D"Arial" color=3D"#0000ff"=
 size=3D"2"></font>&nbsp;</div><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><br><div class=3D"OutlookMessageHeader" lang=3D"de" =
dir=3D"ltr" align=3D"left"><font face=3D"Times New Roman" size=3D"3"><span=
 style=3D"font-size: 12pt; "><hr tabindex=3D"-1" align=3D"center" =
width=3D"100%" size=3D"2"></span></font></div><div =
class=3D"Section1"><div><div style=3D"font-size: 12pt; margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0pt; margin-left: 0cm; font-family: =
'Times New Roman'; "><b><font face=3D"Tahoma" size=3D"2"><span =
style=3D"font-weight: bold; font-size: 10pt; font-family: Tahoma; =
">Von:</span></font></b><font face=3D"Tahoma" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Tahoma; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a> [<a =
href=3D"mailto:ancp-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">mailto:ancp-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b><span =
style=3D"font-weight: bold; ">Im Auftrag von<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b>OOGHE =
Sven<br><b><span style=3D"font-weight: bold; ">Gesendet:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Freitag, 17. Oktober 2008 =
11:23<br><b><span style=3D"font-weight: bold; ">An:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ancp@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">ancp@ietf.org</a><br><b><span style=3D"font-weight: bold; =
">Betreff:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>[ANCP] ANCP Framework =
update</span></font><o:p></o:p></div></div><div style=3D"font-size: =
12pt; margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; =
margin-left: 0cm; font-family: 'Times New Roman'; "><font face=3D"Times =
New Roman" size=3D"3"><span style=3D"font-size: 12pt; =
"><o:p>&nbsp;</o:p></span></font></div><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">Hi,</span></font><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">I've been updating the =
ANCP framework draft according to the suggested changes from Roberta and =
Francois. Below I have copy-pasted the sections that have undergone =
changes.<i><span style=3D"font-style: italic; "><span =
class=3D"Apple-converted-space">&nbsp;</span>Indented =
text</span></i><span class=3D"Apple-converted-space">&nbsp;</span>has =
been changed. I think I captured the essence of the notion of "bandwidth =
delegation". Please review and see if this is capturing the =
agreements.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">Regards,</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">Sven</span></font><o:p></o:p></p><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"Times New Roman" =
size=3D"3"><span style=3D"font-size: 12pt; =
"><o:p>&nbsp;</o:p></span></font></div><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><b><font face=3D"Arial" size=3D"2"><span style=3D"font-weight: bold; =
font-size: 10pt; font-family: Arial; ">3.4.2.&nbsp; Multicast Admission =
Control</span></font></b><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; The successful delivery of Triple =
Play Broadband services is quickly</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; becoming a big capacity planning challenge for most of =
the Service</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; Providers nowadays.&nbsp; Solely increasing available =
bandwidth is not</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; always practical, cost-economical and/or sufficient to =
satisfy end</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; user experience given not only the strict requirements of =
unicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; delay sensitive applications like VoIP and Video, but =
also the fast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; growth of multicast interactive applications such =
as</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; videoconferencing, digital TV, digital audio, online =
movies and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; networked gaming.&nbsp; These applications are typically =
characterized by</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; a delay sensitive nature, an extremely loss sensitive =
nature and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; intensive bandwidth requirements.&nbsp; They are also =
typically "non-</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; elastic", which means that they operate at a fixed =
bandwidth, that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; cannot be dynamically adjusted to the currently available =
bandwidth.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; Therefore a Connection Admission =
Control (CAC) mechanism covering</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; admission of multicast traffic over the DSL Broadband =
access is</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; required, in order to avoid oversubscribing the available =
bandwidth</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; and negatively impacting the end user =
experience.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; Considering specifically admission =
control over the access line,</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; before honoring a user request to join a new multicast =
flow, the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; combination of AN and NAS MUST ensure admission control =
is performed</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; to validate that there is enough "video" bandwidth =
remaining on the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; access line to carry the new flow (in addition to all =
other existing</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; multicast and unicast video traffic).&nbsp; The solution =
needs to cope</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; with multiple flows per access line and needs to allow =
access line</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; bandwidth to be dynamically shared across multicast and =
unicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; traffic (irrespective of whether unicast CAC is performed =
by NAS or</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; by some off-path Policy =
Server).</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; Thus, supporting CAC for the access =
line requires some form of</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; synchronization between the entity performing multicast =
CAC (e.g. the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; NAS or the AN) and the entity performing unicast CAC =
(e.g. the NAS or</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span style=3D"font-size:=
 10pt; font-family: Arial; ">&nbsp;&nbsp; a Policy Server) and the =
entity actually enforcing the multicast<span =
class=3D"734534408-22102008"><font color=3D"#0000ff">&nbsp; [T.H.: Is =
that correct as stated "NAS or Policy server"?; My understanding: Policy =
Server: Policy&nbsp;decission point;&nbsp;NAS controls AN&nbsp;by =
ANCP;AN: policy enforcement =
point]&nbsp;</font></span></span>&nbsp;<br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; replication (i.e. the AN).&nbsp; This synchronization can =
be achieved in a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp; number of ways:</span></font><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><i><font face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-style: italic; font-family: Arial; =
">&nbsp;&nbsp; o&nbsp; One approach is for the AN to query the NAS so =
that Admission</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the =
access line is performed by the NAS (possibly =
with</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interactions with a =
Policy Server).&nbsp; This can be done with or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth =
delegation" to the AN.</span></font></i><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><i><font face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-style: italic; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission Control =
without AN Bandwidth Delegation,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the AN can use ANCP to query the NAS, that in turn =
performs</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast Admission Control check for the new multicast =
flow</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and responds to the AN indicating whether the join is to =
be</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
honored (and hence replication performed by the AN) or =
denied.</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span style=3D"font-size:=
 10pt; font-style: italic; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may locally =
maintain available "video" bandwidth&nbsp;<font color=3D"#0000ff"><span =
class=3D"734534408-22102008">&nbsp;[T.H.:]&nbsp;</span><span =
class=3D"734534408-22102008">&nbsp;(net data rate)&nbsp;</span></font>on =
the</span><span class=3D"Apple-converted-space">&nbsp;</span><br><i><font =
face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; font-style: =
italic; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop, and =
perform video bandwidth accounting for the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Access Loop.&nbsp; Upon receiving an Admission Request from the =
AN,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the NAS can check available "video" bandwidth before =
admitting</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
or denying the multicast flow.&nbsp; In the process, the NAS =
may</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
communicate with the Policy Server.&nbsp; For unicast video =
services</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
such as Video on Demand (VoD), the NAS may also be queried =
(by</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
Policy Server or via on-path CAC signaling), so that it =
can</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
perform admission control for the unicast flow, and update =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
available video bandwidth maintained by the =
NAS.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp; In case of Admission Control with AN Bandwidth Delegation, =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
NAS (possibly with interactions with a Policy Server) =
manages</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
total bandwidth for video admission, performs unicast =
admission</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
control and uses ANCP to delegate a certain amount of =
bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
for some multicast flows to the Access Node.&nbsp; In this =
scenario,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
upon receiving a join to a multicast flow which matches =
an</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
entry in the White or Grey List whose entry is flagged =
as</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"Bandwidth Delegation", the AN must perform the =
necessary</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bandwidth admission control check for the new multicast =
flow,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
before starting the multicast flow =
replication.</span></font></i><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-style: italic; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The ANCP requirements to support this =
approach are specified in</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this =
document.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case the subscriber =
communicates the "join/leave" information</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the NAS (e.g. by terminating all =
subscriber IGMP signaling on</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS, or by using some form of =
application level signaling),</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the approach is very similar.&nbsp; In =
this case, the NAS may locally</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maintain available "video" bandwidth on =
the Access Loop, perform</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bandwidth accounting, and perform =
CAC for unicast and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flows.&nbsp; The NAS can set =
the replication state on the AN</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using ANCP if the flow is =
admitted.&nbsp; For unicast video services</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS may be queried (by a policy =
server or via on-path CAC</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signaling) to perform admission control =
for the unicast flow, and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; update the available video bandwidth =
maintained by the NAS.&nbsp; The</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP requirements to support this =
approach (where the AN queries</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS) are specified in this =
document;</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In a third approach, the =
Policy Server queries the AN directly so</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that both unicast and multicast CAC for =
the access line are</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; performed by the AN.&nbsp; In this =
case, a subscriber request for a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; unicast flow (e.g. a Video on Demand =
session) will trigger a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; resource request message towards a =
Policy Server; the latter will</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then query the AN, that in turn will =
perform unicast CAC for the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access line and respond, indicating =
whether the unicast request is</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to be honored or denied.&nbsp; In this =
scenario the Policy Server</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; queries the AN directly, the approach =
doesn't require the use of</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP.&nbsp; It is therefore beyond the =
scope of this document.</span></font><o:p></o:p></p><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size: =
12pt; "><o:p>&nbsp;</o:p></span></font></div><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><b><font face=3D"Arial" size=3D"2"><span style=3D"font-weight: =
bold; font-size: 10pt; font-family: Arial; ">4.2.&nbsp; ANCP Multicast =
Requirements</span></font></b><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST support =
providing multicast conditional access</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information to Access Ports on an =
Access Node, using Black, Grey</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and White =
lists.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST support binding =
a particular Black, Grey and White</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List to a given Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon receiving a join to a =
multicast flow which matches the Grey</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List the ANCP MUST allow the AN to =
query the NAS to request an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission decision for replicating that =
multicast flow to a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST allow the NAS =
to send an admission decision to the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AN indicating whether or not a =
multicast flow may be replicated to</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP =
must allow the NAS to indicate to the AN whether or =
not</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Admission Control =
is needed for some multicast flows on a given</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Port and =
where needed whether or not it is to be performed</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with AN Bandwidth =
Delegation.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control without AN Bandwidth Delegation, =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP must allow the =
NAS to reply to a query from the AN indicating</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; whether or not a =
multicast flow may be replicated to a particular</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access =
Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP must allow the =
NAS to delegate a certain amount of bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the AN for a =
given Access Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation, =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP must allow the =
AN to query the NAS to request additional</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast bandwidth =
on a given Access Port.</span></font></i><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><i><font face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-style: italic; font-family: Arial; =
">&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN Bandwidth =
Delegation, the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP must allow the =
NAS to query (or to instruct) the AN to reduce</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the amount of =
bandwidth previously delegated on a given Access</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP must allow the =
AN to autonomous release redundant multicast</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bandwidth on a =
given Access Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST allow the =
AN to send an Information Report message</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the NAS whenever replication of a =
multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; particular Access Port start or =
ends.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST allow the AN to =
send an Information Report message</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the NAS indicating the multicast =
traffic volume that has been</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replicated on that =
port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST allow the NAS =
to indicate to the AN whether or not</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast accounting is needed for a =
multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case multicast accounting =
is needed for a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; particular Access Port, the ANCP MUST =
allow the NAS to indicate to</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN whether or not additional volume =
accounting information is</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
required.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST allow the NAS =
to revoke a decision to replicate a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow to a particular Access =
Port, which had been</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; conveyed earlier to an =
AN.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The ANCP MUST support partial =
updates of the White, Grey and Black</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lists.</span></font><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST allow the NAS to query the AN to obtain =
information</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on what multicast flows are currently =
being replicated on a given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Port, what Access Ports are =
currently receiving a given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow, or what multicast flows =
are currently replicated</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on each Access =
Port.</span></font><o:p></o:p></p><div style=3D"font-size: 12pt; =
margin-top: 0cm; margin-right: 0cm; margin-bottom: 0pt; margin-left: =
0cm; font-family: 'Times New Roman'; "><font face=3D"Times New Roman" =
size=3D"3"><span style=3D"font-size: 12pt; =
"><o:p>&nbsp;</o:p></span></font></div><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><b><font face=3D"Arial" size=3D"2"><span style=3D"font-weight: bold; =
font-size: 10pt; font-family: Arial; ">Access Node multicast =
requirements (section 4.7.6)</span></font></b><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The =
AN must deny any join to a multicast flow matching the =
Black</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List for the relevant Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The AN =
must accept any join to a multicast flow matching the =
White</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and not =
flagged as "Bandwidth Delegation" for the =
relevant</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access =
Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to a multicast flow which matches the =
White</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is =
flagged as "Bandwidth Delegation" for the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access =
Port, the AN must perform the necessary bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission control =
check for the new flow before starting the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow =
replication.</span></font></i><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; =
Upon receiving a join to a multicast flow which matches the =
Grey</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is =
flagged as "no Bandwidth Delegation" for the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access =
Port, the AN must support using ANCP to query the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a =
response indicating whether that join is to be</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or =
denied.&nbsp; In this case, the NAS will perform both =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
conditional access and the admission control checks =
for</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to a multicast flow which matches the =
Grey</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is =
flagged as "Bandwidth Delegation" for the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access =
Port, the AN must first perform the necessary</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bandwidth admission =
control check for the new flow.&nbsp; If</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; successful, the AN =
must support using ANCP to query the NAS to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receive a response =
indicating whether that join is to be honored</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or =
denied.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, the =
AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to notify the NAS when the the user leaves</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =
flow.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, the =
AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to query the NAS to request additional</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated multicast =
bandwidth on a given Access Port; the AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be able to =
specify both the minimum and the preferred</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount of =
additional multicast bandwidth =
requested.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, =
upon</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a =
Bandwidth Delegation Request from the NAS querying =
or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instructing to =
decrease the delegated multicast bandwidth on a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, =
the AN must support using ANCP to send a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth =
Delegation Response indicating the new delegated</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
bandwidth.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, the =
AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to send a Bandwidth Release message to the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to =
release unused delegated multicast bandwidth on a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access =
Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; If the requested multicast =
flow is not part of any list associated</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the Access Port, the AN must =
discard the message.</span></font><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; If the requested =
multicast flow is part of multiple lists</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; associated with the Access Port, the AN =
must use the most specific</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; match.</span></font><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; If =
the requested multicast flow has the same most specific =
match</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in multiple lists, the AN must give =
precedence to the Black list,</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; followed by the Grey list, and then the =
White list.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The AN must support =
configuring a "catch-all" statement in the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Black, White or Grey list in order to =
enforce a default behavior</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for a join to a multicast flow which =
doesn't match any other entry</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in a list for the relevant Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon querying the NAS, the AN =
must not propagate the join message</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before the successful authorization =
from the NAS is received.</span></font><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; =
Upon receiving a leave for a multicast flow which matches the =
Grey</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List, the AN should be able to =
autonomously stop replication and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertise this event to the =
NAS.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The AN must support using =
ANCP to send an Information Report</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span style=3D"font-size:=
 10pt; font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message to =
the NAS whenever replication starts or ends<span =
class=3D"734534408-22102008"><font color=3D"#0000ff">&nbsp; [T.H:] or =
fails&nbsp;</font></span>.</span><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The AN should support =
using ANCP to send an Information Report</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message to the NAS indicating the =
multicast traffic volume that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has been replicated on that =
port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon request by the NAS, the =
AN must support using ANCP to send an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Information Report message to the NAS, =
indicating what multicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flows are currently being replicated on =
a given Access Port.</span></font><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon request by the =
NAS, the AN must support using ANCP to send an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Information Report message to the NAS, =
indicating what Access</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ports are currently receiving a given =
multicast flow.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon request by the NAS, the =
AN must support using ANCP to send an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Information Report message to the NAS, =
indicating what multicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flows are currently being replicated on =
each Access Port.</span></font><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon receiving an =
Admission Response from the NAS, indicating that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replication of a multicast flow is to =
start or stop on a given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access port of the AN, the AN must =
enforce this decision.&nbsp; This</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decision must be taken irrespective of =
whether or not a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; corresponding Admission Request was =
issued by the AN earlier on.</span></font><o:p></o:p></p><div =
style=3D"font-size: 12pt; margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0pt; margin-left: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Times New Roman" size=3D"3"><span style=3D"font-size: =
12pt; "><o:p>&nbsp;</o:p></span></font></div><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><b><font face=3D"Arial" size=3D"2"><span style=3D"font-weight: =
bold; font-size: 10pt; font-family: Arial; ">NAS multication =
requirements (section 4.8.6)</span></font></b><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The =
NAS must support using ANCP to configure multicast =
conditional</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access information to Access Ports on =
an Access Node, using Black</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lists, Grey Lists and White =
Lists.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS =
must support using ANCP to indicate to the AN whether =
or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not Admission =
Control is needed for some multicast flows on a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port =
and where needed whether or not it is to be</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; performed with AN =
Bandwidth Delegation.</span></font></i><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><i><font face=3D"Arial" size=3D"2"><span=
 style=3D"font-size: 10pt; font-style: italic; font-family: Arial; =
">&nbsp;&nbsp; o&nbsp; Upon receiving a query from the AN for a request =
to replicate a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow to a =
particular Access Port, and no AN Bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Delegation is =
needed for that flow, the NAS must be able to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; perform the =
necessary checks (conditional access and/or =
admission</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control) for the =
new flow.&nbsp; The NAS must support using ANCP =
to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; reply to the AN =
indicating whether the request is to be honored =
or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
denied.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; Upon =
receiving a query from the AN for a request to replicate =
a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow to a =
particular Access Port, and Admission Control</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with AN Bandwidth =
Delegation is needed for that flow, the NAS must</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be able to perform =
the conditional access checks (if needed), and</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to delegate a certain amount of bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to the AN for a =
given Access Port.</span></font></i><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation, =
upon</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a =
Bandwidth Delegation Request from the AN requesting =
to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; increase the =
delegated multicast bandwidth on a given Access =
Port,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS must =
support using ANCP to send a Bandwidth Delegation</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Response indicating =
the new delegating multicast =
bandwidth.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, the =
NAS</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to send a request the AN to decrease the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount of multicast =
bandwidth previously delegated on a given</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Port; the =
NAS should be able to specify both the minimum</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the preferred =
amount decrement of multicast bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
requested.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><i><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-style: italic; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case =
of Admission Control with AN Bandwidth Delegation, =
upon</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving an ANCP =
Bandwidth Release message, the NAS must be able</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to update =
accordingly its view of the multicast bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-style: italic; =
font-family: Arial; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated to the =
AN.</span></font></i><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS must support using =
ANCP to configure the Access Node with</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the "maximum number of multicast =
streams" allowed to be received</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; concurrently per Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS must support using =
ANCP to incrementally add, remove and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; modify individual entries in White, =
Black and Grey lists.</span></font><o:p></o:p></p><p style=3D"font-size: =
12pt; margin-left: 0cm; margin-right: 0cm; font-family: 'Times New =
Roman'; "><font face=3D"Arial" size=3D"2"><span style=3D"font-size: =
10pt; font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS must support =
using ANCP to indicate to the AN whether or</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not multicast accounting is needed for =
a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; In case multicast accounting =
is needed for a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; particular Access Port, the NAS should =
support using ANCP to</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicate to the AN whether or not =
additional volume accounting</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information is =
required.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS must support using =
ANCP to query the AN to obtain</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information on what multicast flows are =
currently replicated on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS must support using =
ANCP to query the AN to obtain</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information on what Access Ports are =
currently receiving a given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
flow.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS must support using =
ANCP to query the AN to obtain</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information on what multicast flows are =
currently replicated on</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; each Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; When Multicast replication =
occurs on the AN, the NAS must support</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using ANCP to revoke the authorization =
to replicate a multicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flow to a particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">&nbsp;&nbsp; o&nbsp; The NAS should support using =
ANCP to indicate to the AN that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; replication of a multicast flow is to =
start or stop on a given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access port of the AN, without having =
received a corresponding</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Admission Request from the AN earlier =
on.</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">---</span></font><o:p></o:p></p><p =
style=3D"font-size: 12pt; margin-left: 0cm; margin-right: 0cm; =
font-family: 'Times New Roman'; "><font face=3D"Arial" size=3D"2"><span =
style=3D"font-size: 10pt; font-family: Arial; ">Sven =
Ooghe</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">Alcatel-Lucent</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; ">CTO =
Office, Access Division</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; =
">Copernicuslaan 50, 2018 Antwerp, Belgium</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; ">tel.: =
+32 3 240 42 26</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"font-size: 10pt; font-family: Arial; ">fax: =
+32 3 240 40 73</span></font><o:p></o:p></p><p style=3D"font-size: 12pt; =
margin-left: 0cm; margin-right: 0cm; font-family: 'Times New Roman'; =
"><font face=3D"Arial" size=3D"2"><span style=3D"font-size: 10pt; =
font-family: Arial; ">This message (including any attachments) contains =
confidential information intended for a specific individual and purpose, =
and is protected by law.&nbsp; If you are not the intended recipient, =
you should delete this message.&nbsp; Any disclosure, copying, or =
distribution of this message, or the taking of any action based on it, =
is strictly prohibited without the prior consent of its =
author.</span></font><o:p></o:p></p></div>________________________________=
_______________<br>ANCP mailing list<br><a href=3D"mailto:ANCP@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">ANCP@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/ancp</a><br></div></span></blockqu=
ote></div><br></body></html>=

--Boundary_(ID_PySLYHjJQctGWyb9vDmAjg)--

--===============0196023899==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0196023899==--


From ancp-bounces@ietf.org  Thu Oct 23 03:56:25 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DB063A6C57;
	Thu, 23 Oct 2008 03:56:25 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9673C3A6C57
	for <ancp@core3.amsl.com>; Thu, 23 Oct 2008 03:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 Ch5+-ObsBh75 for <ancp@core3.amsl.com>;
	Thu, 23 Oct 2008 03:56:14 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 5B2383A6C52
	for <ancp@ietf.org>; Thu, 23 Oct 2008 03:56:13 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9NAvAHL027296
	for <ancp@ietf.org>; Thu, 23 Oct 2008 12:57:12 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 23 Oct 2008 12:57:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 12:57:08 +0200
Message-ID: <7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <B574433E-1B70-4243-8A48-87B832982F98@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP Framework update
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQ
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
	<FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com>
	<7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com>
	<B574433E-1B70-4243-8A48-87B832982F98@cisco.com>
From: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 23 Oct 2008 10:57:09.0790 (UTC)
	FILETIME=[18B93BE0:01C934FE]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1719355174=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1719355174==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C934FE.187D2AD9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C934FE.187D2AD9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
Here's the updated text. I removed any notion of "flags" or how the
Access Node is told whether or not Bandwidth Delegation applies. I also
covered Thomas' comments. Actually not that much work: the general ANCP
requirements as well as the NAS requirements were written in a
high-level way already. I only had to update the general text and some
of the Access Node requirements. Below the extracted text, let me know
your comments.
=20
Regards,
Sven
=20
---
=20
General text
=20
   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.
=20
      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop (as a portion of the Access Loop net data rate),
         and perform video bandwidth accounting for the Access Loop.
         Upon receiving an Admission Request from the AN, the NAS can
         check available "video" bandwidth before admitting or denying
         the multicast flow.  In the process, the NAS may communicate
         with the Policy Server.  For unicast video services such as
         Video on Demand (VoD), the NAS may also be queried (by a Policy
         Server or via on-path CAC signaling), so that it can perform
         admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.
=20
      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List, the AN must perform the
         necessary bandwidth admission control check for the new
         multicast flow, before starting the multicast flow replication.

Access Node requirements
=20
   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.
=20
   o  The AN must accept any join to a multicast flow matching the White
      List and for which no Bandwidth Delegation is required.
=20
   o  Upon receiving a join to a multicast flow which matches the White
      List whose and for which Bandwidth Delegation is required, the AN
      must perform the necessary bandwidth admission control check for
      the new flow before starting the multicast flow replication.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which no Bandwidth Delegation is required, the AN
      must support using ANCP to query the NAS to receive a response
      indicating whether that join is to be honored or denied.  In this
      case, the NAS will perform both the necessary conditional access
      and the admission control checks for the new flow.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which Bandwidth Delegation is required, the AN must
      first perform the necessary bandwidth admission control check for
      the new flow.  If successful, the AN must support using ANCP to
      query the NAS to receive a response indicating whether that join
      is to be honored or denied.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.
=20
Regards,
Sven

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:58
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update




On 20 Oct 2008, at 12:22, OOGHE Sven wrote:


	Francois,
	=20
	Another approach we could take is to let the framework
requirements be agnostic as to how the Access Node knows whether or not
Bandwidth Delegation applies. We could describe the notion of Bandwidth
Delegation and the respective requirements for the Access Node and NAS
in this case.
	=20
	The details of how the use of Bandwidth Delegation is
communicated to the Access Node - using a flag, some "on/off" knob or
both - would be left to the actual protocol specification work.


Good idea. It will avoid these cross dependencies between framework and
protocol, which indeed reflect that we are probably trying to be too
precise/prescriptive in the framework.


	=20
	I think following this path would require relatively small edits
to the document. I'm ok to take a first shot at it.


That would be good.

Thanks

Francois


	=20
	Regards,
	Sven

________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update
=09
=09
	Sven and all,=20
=09
=09

		   o  Upon receiving a join to a multicast flow which
matches the Grey=20
		      List whose entry is flagged as "no Bandwidth
Delegation" for the=20
		      relevant Access Port, the AN must support using
ANCP to query the=20
		      NAS to receive a response indicating whether that
join is to be=20
		      honored or denied.  In this case, the NAS will
perform both the=20
		      necessary conditional access and the admission
control checks for=20
		      the new flow.


	Roberta, Tom and myself have started drafting an I-D that will
propose ANCP protocol extensions supporting some of those requirements
(building on top of ancp-mc-multicast).
	In doing so, we revisited a point that came up multiple times:
do we really need to provision a flag in each and every Grey/White List
entry to activate/deactivate Bandwidth Delegation?
=09
=09
	The current approach (as correctly reflected in the updated
Framework) is:
	* define a flag in each Grey/White List entry
=09
	* assume that this flag will normally either always be set in
all entries or never set.
=09
	* setting/no-setting the flag is all entries effectively acts as
the knob to enable/disable Bandwidth Delegation, therefore we did not
need to specify a specific knob to enable/disable Bandwidth Delegation.
=09
=09
=09
	Another approach would be:
	* remove flag from White/Grey list entries
=09
	* define a specific knob to enable/disable Bandwidth Delegation
at the AN granularity
	* in fact, define a generic AN-level provisioning method that
could be used to enable/disable BAndwidth delegation, but could also be
used for provisioning the "Service Profiles" that are currently assumed
to be configured in AN, as well as provisioning the Multicast
White/Grey/Black Profiles
=09
=09
=09
	Considering that:
	- we got several times the feedback that per-entry BAndwidth
Delegation flag was confusing since Bandwidth Delegation granularity is
more AN-level (and may lead to difficulties if it is set on some entries
and not on others)
	- it is likely that we'll need, anyways, a mechanism to
provision things at AN level, that could be easily used to convey
Bandwidth Delegation enable/disable knob.
=09
	we would like to propose to evolve to the newer approach.
=09
=09
	Thoughts?

	Francois

	PS: Sven, if we go for the new approach, we can document in an
email the deltas that would be needed to reflect that in framework.




------_=_NextPart_001_01C934FE.187D2AD9
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Here's the updated text. I removed any notion =
of "flags" or=20
how the Access Node is told whether or not Bandwidth Delegation applies. =
I also=20
covered Thomas' comments. Actually not that much work: the general ANCP=20
requirements as well as the NAS requirements were written in a =
high-level=20
way&nbsp;already. I only had to update the general text and some of the =
Access=20
Node requirements. Below the extracted text, let me know your=20
comments.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>---</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><STRONG>General =
text</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; One approach is for the AN =
to query=20
the NAS so that Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for =
the=20
access line is performed by the NAS (possibly=20
with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interactions with a Policy =
Server).&nbsp;=20
This can be done with or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without =
"bandwidth=20
delegation" to the AN.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In =
case of=20
Admission Control without AN Bandwidth=20
Delegation,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
can use=20
ANCP to query the NAS, that in turn=20
performs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
Admission=20
Control check for the new multicast=20
flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and responds to =
the AN=20
indicating whether the join is to=20
be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored (and =
hence=20
replication performed by the AN) or=20
denied.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may =
locally=20
maintain available "video" bandwidth on=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop (as =
a=20
portion of the Access Loop net data=20
rate),<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and perform =
video=20
bandwidth accounting for the Access=20
Loop.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon receiving =
an=20
Admission Request from the AN, the NAS=20
can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check available =
"video"=20
bandwidth before admitting or=20
denying<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast=20
flow.&nbsp; In the process, the NAS may=20
communicate</EM></FONT></SPAN></DIV><SPAN class=3D852244910-23102008>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the =
Policy=20
Server.&nbsp; For unicast video services such=20
as<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video on Demand =
(VoD),=20
the NAS may also be queried (by a=20
Policy<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server or via =
on-path=20
CAC signaling), so that it can=20
perform<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission =
control=20
for the unicast flow, and update=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available video=20
bandwidth maintained by the NAS.</EM></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission =
Control=20
with AN Bandwidth Delegation,=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS (possibly =
with=20
interactions with a Policy Server)=20
manages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for=20
video admission, performs unicast=20
admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control =
and uses=20
ANCP to delegate a certain amount of=20
bandwidth<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast=20
flows to the Access Node.&nbsp; In this=20
scenario,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =
receiving a=20
join to a multicast flow which matches=20
an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or=20
Grey List, the AN must perform=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
bandwidth=20
admission control check for the=20
new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow, =
before=20
starting the multicast flow replication.<BR></EM></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><STRONG>Access Node=20
requirements</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must deny any join =
to a=20
multicast flow matching the Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
for the=20
relevant Access Port.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must accept any =
join to a=20
multicast flow matching the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
and for=20
which no Bandwidth Delegation is required.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List=20
whose and for which Bandwidth Delegation is required, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must perform the necessary =
bandwidth=20
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow=20
before starting the multicast flow replication.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and=20
for which no Bandwidth Delegation is required, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS to=20
receive a response<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating whether =
that=20
join is to be honored or denied.&nbsp; In =
this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
case, the NAS will perform both the necessary conditional=20
access<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the admission control =
checks for=20
the new flow.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and=20
for which Bandwidth Delegation is required, the AN=20
must<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first perform the necessary =
bandwidth=20
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
flow.&nbsp; If successful, the AN must support using ANCP=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the NAS to receive a response =

indicating whether that join<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored=20
or denied.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN=20
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to notify the NAS when the the user=20
leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =
flow.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN=20
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to query the NAS to request=20
additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated multicast =
bandwidth on a=20
given Access Port; the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be =
able to=20
specify both the minimum and the =
preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
amount of additional multicast bandwidth requested.</FONT></SPAN></DIV>
<DIV><SPAN class=3D852244910-23102008><FONT face=3DArial color=3D#0000ff =

size=3D2><BR>&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN =
Bandwidth=20
Delegation, upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =

Delegation Request from the NAS querying =
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
instructing to decrease the delegated multicast bandwidth on=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support using=20
ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth Delegation =
Response=20
indicating the new delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =

bandwidth.</DIV>
<DIV>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with=20
AN Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to send a Bandwidth Release message to=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to release unused =
delegated=20
multicast bandwidth on a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access=20
Port.</DIV>
<DIV>&nbsp;</DIV></FONT></SPAN></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> maandag 20 oktober 2008=20
12:58<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT><BR>
<DIV>
<DIV>On 20 Oct 2008, at 12:22, OOGHE Sven wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Another approach we could take is to let the =
framework=20
  requirements be agnostic as to how the Access Node knows whether or =
not=20
  Bandwidth Delegation applies. We could describe the notion of =
Bandwidth=20
  Delegation and the respective requirements for the Access Node and NAS =
in this=20
  case.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The details of how the use of Bandwidth =
Delegation is=20
  communicated to the Access Node - using a flag, some "on/off" knob or =
both -=20
  would be left to the actual protocol specification=20
  work.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Good idea. It will avoid these cross dependencies between framework =
and=20
protocol, which indeed reflect that we are probably trying to be too=20
precise/prescriptive in&nbsp;the&nbsp;framework.</DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I think following this path would require =
relatively=20
  small edits to the document. I'm ok to take a first shot at=20
  it.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>That would be good.</DIV>
<DIV><BR></DIV>
<DIV>Thanks</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A=20
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
  <BR><B>Sent:</B> maandag 20 oktober 2008 12:01<BR><B>To:</B> OOGHE=20
  Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP; <A=20
  href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> Re: =
[ANCP]=20
  ANCP Framework update<BR></FONT><BR></DIV>
  <DIV></DIV>Sven and all,=20
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>
  <DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to=20
    a multicast flow which matches the Grey</FONT></I> <BR><I><FONT =
face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is flagged =
as "no=20
    Bandwidth Delegation" for the</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, the AN =
must=20
    support using ANCP to query the</FONT></I> <BR><I><FONT face=3DArial =

    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a response =
indicating=20
    whether that join is to be</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; In =
this case,=20
    the NAS will perform both the</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional access =
and the=20
    admission control checks for</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
  flow.</FONT></I></P></DIV></BLOCKQUOTE><BR></DIV>
  <DIV>
  <DIV>Roberta, Tom and myself have started drafting an I-D that will =
propose=20
  ANCP protocol extensions supporting some of those requirements =
(building on=20
  top of ancp-mc-multicast).</DIV>
  <DIV>In doing so, we revisited a point that came up multiple times: do =
we=20
  really need to provision a flag in each and every Grey/White List =
entry=20
  to&nbsp;activate/deactivate&nbsp;Bandwidth Delegation?</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>The current approach (as correctly reflected in the updated =
Framework)=20
  is:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
  flag in each Grey/White List entry<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
assume that=20
  this flag will normally either always be set in all entries or never=20
  set.<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>*=20
  setting/no-setting the flag is all entries effectively acts as the =
knob to=20
  enable/disable Bandwidth Delegation, therefore we did not need to =
specify a=20
  specific knob to enable/disable Bandwidth Delegation.<BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Another approach would be:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
remove flag=20
  from White/Grey list entries<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
  specific knob to enable/disable Bandwidth Delegation at the AN=20
  granularity</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
in fact,=20
  define a generic&nbsp;AN-level provisioning method that could be used =
to=20
  enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for=20
  provisioning the "Service Profiles" that are currently assumed to be=20
  configured in AN, as well as provisioning the Multicast =
White/Grey/Black=20
  Profiles<BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Considering that:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
we got=20
  several times the feedback that per-entry BAndwidth Delegation flag =
was=20
  confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and=20
  may lead to difficulties if it is set on some entries and not on =
others)</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
it is likely=20
  that we'll need, anyways, a mechanism to provision things at AN level, =
that=20
  could be easily used to convey Bandwidth Delegation enable/disable=20
  knob.<BR></DIV>
  <DIV>we&nbsp;would&nbsp;like to propose=20
  to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Thoughts?</DIV>
  <DIV><BR></DIV>
  <DIV>Francois</DIV>
  <DIV><BR></DIV>
  <DIV>PS: Sven, if we go for&nbsp;the&nbsp;new approach, we can =
document in an=20
  email the deltas that&nbsp;would&nbsp;be needed to reflect that in=20
  framework.</DIV>
  <DIV><BR></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

------_=_NextPart_001_01C934FE.187D2AD9--

--===============1719355174==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1719355174==--


From ancp-bounces@ietf.org  Thu Oct 23 20:54:52 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E10C3A67DB;
	Thu, 23 Oct 2008 20:54:52 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7CF943A67DB
	for <ancp@core3.amsl.com>; Thu, 23 Oct 2008 20:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.791
X-Spam-Level: ***
X-Spam-Status: No, score=3.791 tagged_above=-999 required=5
	tests=[BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3,
	MY_CID_AND_ARIAL2=1.46, RDNS_NONE=0.1, SARE_SUB_ENC_UTF8=0.152]
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 6Wx01zVMOJbr for <ancp@core3.amsl.com>;
	Thu, 23 Oct 2008 20:54:46 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64])
	by core3.amsl.com (Postfix) with ESMTP id 88B173A6781
	for <ancp@ietf.org>; Thu, 23 Oct 2008 20:54:45 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9800KIR5L0F3@szxga01-in.huawei.com> for
	ancp@ietf.org; Fri, 24 Oct 2008 11:55:49 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K98002TU5L0JG@szxga01-in.huawei.com> for
	ancp@ietf.org; Fri, 24 Oct 2008 11:55:48 +0800 (CST)
Received: from h36145c ([10.70.39.123])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K98009T05KXJI@szxml03-in.huawei.com> for
	ancp@ietf.org; Fri, 24 Oct 2008 11:55:48 +0800 (CST)
Date: Fri, 24 Oct 2008 11:55:45 +0800
From: Fortune HUANG <fqhuang@huawei.com>
In-reply-to: <2DD715E8-D3C9-4DF3-BF95-0D52BBB3B96B@huawei.com>
To: 'Tina TSOU' <tena@huawei.com>, "'Haag, Thomas'" <HaagT@telekom.de>
Message-id: <002101c9358c$64b66b60$7b27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Ack0PJk3HP/pE3OPRjW1bWTnrdDu9gBSiBRw
Cc: ancp@ietf.org
Subject: [ANCP] =?utf-8?b?562U5aSNOiAgQU5DUCBGcmFtZXdvcmsgdXBkYXRl?=
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2023835625=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2023835625==
Content-type: multipart/related; boundary="Boundary_(ID_BH5kNYF9EwFK31yWYnA0eg)"

This is a multi-part message in MIME format.

--Boundary_(ID_BH5kNYF9EwFK31yWYnA0eg)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_jutcE5eYQ18b8WjOQK9XCQ)"


--Boundary_(ID_jutcE5eYQ18b8WjOQK9XCQ)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable

Hi all,
=20
=20
The name "PS/Policy Server" used in this draft is also kind of confusing =
to me in this draft.
=20
The entity descriped in this draft is actually an entity which manages =
(part of) the network bandwidth/resource and performs admission control =
for the unicast service. These functionalites are not quite clearly =
reflected by the name "Policy Server".
=20
Therefore, I suggest we find a better name for this entity.
=20
My proposal is to replace the "PS/Policy Server" with "RACS / Resource =
and Admission Control Subsystem" which is defined in ETSI TISPAN.
I think the name "RACS"can reflect the requirement for this entity =
precisely.
=20
=20
Best Regards,
Fortune

Huawei Technologies Co., Ltd. huawei_logo=20


Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =
518129, P.R. China
Tel: +86-755-28971871
Fax: +86-755-28972352
Mobile: +8615013838060
Email: fqhuang@huawei.com
http://www.huawei.com
-------------------------------------------------------------------------=
------------------------------------------------------------
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81
=E6=AD=A2=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=
=BD=95=E5=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=
=86=E4=B8=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=
=E5=9C=B0=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=
=95=A3=E5=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD
=E7=9A=84=E4=BF=A1=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=
=94=B6=E4=BA=86=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=
=8B=E5=8D=B3=E7=94=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=
=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=
=BB=B6=EF=BC=81
This e-mail and its attachments contain confidential information from =
HUAWEI, which=20
is intended only for the person or entity whose address is listed above. =
Any use of the=20
information contained herein in any way (including, but not limited to, =
total or partial=20
disclosure, reproduction, or dissemination) by persons other than the =
intended=20
recipient(s) is prohibited. If you receive this e-mail in error, please =
notify the sender by=20
phone or email immediately and delete it!

=20

  _____ =20

=E5=8F=91=E4=BB=B6=E4=BA=BA: Tina TSOU [mailto:tena@huawei.com]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2008=E5=B9=B410=E6=9C=8822=E6=97=A5 19:52
=E6=94=B6=E4=BB=B6=E4=BA=BA: Haag, Thomas
=E6=8A=84=E9=80=81: sven.ooghe@alcatel-lucent.be; ancp@ietf.org
=E4=B8=BB=E9=A2=98: Re: [ANCP] ANCP Framework update


Hi all,
I agree with Thomas' comments.


B. R.
Tina


Messengers:

MSN: tinatsou6@hotmail.com   Yahoo: tina_tsou    Skype: tinaTSOU    =
Jabber: tina@jabber.org    Google talk: tinatsou6@gmail.com

+86-755-28971872 (Office)    +86-13922884380(Mobile)



On Oct 22, 2008, at 6:42 PM, Haag, Thomas wrote:



Hi Sven,
=20
please see my comments inline.
=20
Regards=20
Thomas Haag=20
Deutsche Telekom AG
Zentrum Technik Einf=C3=BChrung
TE5-22, Internationale Standardisierung
Heinrich-Hertz-Stra=C3=9Fe 3-7, 64295 Darmstadt
+49 6151 628-2088 (Tel.)
+49 521 9210-8411 (Fax)
+49 171 56 44 739 (Mobil)
Neu: Email: haagt@telekom.de
 <http://www.telekom.com/> http://www.telekom.com
=20



  _____ =20

Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von =
OOGHE Sven
Gesendet: Freitag, 17. Oktober 2008 11:23
An: ancp@ietf.org
Betreff: [ANCP] ANCP Framework update


Hi,

I've been updating the ANCP framework draft according to the suggested =
changes from Roberta and Francois. Below I have copy-pasted the sections =
that have undergone changes. Indented text has been changed. I think I =
captured the essence of the notion of "bandwidth delegation". Please =
review and see if this is capturing the agreements.

Regards,=20
Sven



3.4.2.  Multicast Admission Control

   The successful delivery of Triple Play Broadband services is quickly=20
   becoming a big capacity planning challenge for most of the Service=20
   Providers nowadays.  Solely increasing available bandwidth is not=20
   always practical, cost-economical and/or sufficient to satisfy end=20
   user experience given not only the strict requirements of unicast=20
   delay sensitive applications like VoIP and Video, but also the fast=20
   growth of multicast interactive applications such as=20
   videoconferencing, digital TV, digital audio, online movies and=20
   networked gaming.  These applications are typically characterized by=20
   a delay sensitive nature, an extremely loss sensitive nature and=20
   intensive bandwidth requirements.  They are also typically "non-=20
   elastic", which means that they operate at a fixed bandwidth, that=20
   cannot be dynamically adjusted to the currently available bandwidth.

   Therefore a Connection Admission Control (CAC) mechanism covering=20
   admission of multicast traffic over the DSL Broadband access is=20
   required, in order to avoid oversubscribing the available bandwidth=20
   and negatively impacting the end user experience.

   Considering specifically admission control over the access line,=20
   before honoring a user request to join a new multicast flow, the=20
   combination of AN and NAS MUST ensure admission control is performed=20
   to validate that there is enough "video" bandwidth remaining on the=20
   access line to carry the new flow (in addition to all other existing=20
   multicast and unicast video traffic).  The solution needs to cope=20
   with multiple flows per access line and needs to allow access line=20
   bandwidth to be dynamically shared across multicast and unicast=20
   traffic (irrespective of whether unicast CAC is performed by NAS or=20
   by some off-path Policy Server).

   Thus, supporting CAC for the access line requires some form of=20
   synchronization between the entity performing multicast CAC (e.g. the =

   NAS or the AN) and the entity performing unicast CAC (e.g. the NAS or =

   a Policy Server) and the entity actually enforcing the multicast  =
[T.H.: Is that correct as stated "NAS or Policy server"?; My =
understanding: Policy Server: Policy decission point; NAS controls AN by =
ANCP;AN: policy enforcement point] =20
   replication (i.e. the AN).  This synchronization can be achieved in a =

   number of ways:

   o  One approach is for the AN to query the NAS so that Admission=20
      Control for the access line is performed by the NAS (possibly with =

      interactions with a Policy Server).  This can be done with or=20
      without "bandwidth delegation" to the AN.

      *  In case of Admission Control without AN Bandwidth Delegation,=20
         the AN can use ANCP to query the NAS, that in turn performs=20
         multicast Admission Control check for the new multicast flow=20
         and responds to the AN indicating whether the join is to be=20
         honored (and hence replication performed by the AN) or denied.=20
         The NAS may locally maintain available "video" bandwidth  =
[T.H.:]  (net data rate) on the=20
         Access Loop, and perform video bandwidth accounting for the=20
         Access Loop.  Upon receiving an Admission Request from the AN,=20
         the NAS can check available "video" bandwidth before admitting=20
         or denying the multicast flow.  In the process, the NAS may=20
         communicate with the Policy Server.  For unicast video services =

         such as Video on Demand (VoD), the NAS may also be queried (by=20
         a Policy Server or via on-path CAC signaling), so that it can=20
         perform admission control for the unicast flow, and update the=20
         available video bandwidth maintained by the NAS.

      *  In case of Admission Control with AN Bandwidth Delegation, the=20
         NAS (possibly with interactions with a Policy Server) manages=20
         total bandwidth for video admission, performs unicast admission =

         control and uses ANCP to delegate a certain amount of bandwidth =

         for some multicast flows to the Access Node.  In this scenario, =

         upon receiving a join to a multicast flow which matches an=20
         entry in the White or Grey List whose entry is flagged as=20
         "Bandwidth Delegation", the AN must perform the necessary=20
         bandwidth admission control check for the new multicast flow,=20
         before starting the multicast flow replication.

      The ANCP requirements to support this approach are specified in=20
      this document.

   o  In case the subscriber communicates the "join/leave" information=20
      with the NAS (e.g. by terminating all subscriber IGMP signaling on =

      the NAS, or by using some form of application level signaling),=20
      the approach is very similar.  In this case, the NAS may locally=20
      maintain available "video" bandwidth on the Access Loop, perform=20
      video bandwidth accounting, and perform CAC for unicast and=20
      multicast flows.  The NAS can set the replication state on the AN=20
      using ANCP if the flow is admitted.  For unicast video services=20
      the NAS may be queried (by a policy server or via on-path CAC=20
      signaling) to perform admission control for the unicast flow, and=20
      update the available video bandwidth maintained by the NAS.  The=20
      ANCP requirements to support this approach (where the AN queries=20
      the NAS) are specified in this document;

   o  In a third approach, the Policy Server queries the AN directly so=20
      that both unicast and multicast CAC for the access line are=20
      performed by the AN.  In this case, a subscriber request for a=20
      unicast flow (e.g. a Video on Demand session) will trigger a=20
      resource request message towards a Policy Server; the latter will=20
      then query the AN, that in turn will perform unicast CAC for the=20
      access line and respond, indicating whether the unicast request is =

      to be honored or denied.  In this scenario the Policy Server=20
      queries the AN directly, the approach doesn't require the use of=20
      ANCP.  It is therefore beyond the scope of this document.



4.2.  ANCP Multicast Requirements

   o  The ANCP MUST support providing multicast conditional access=20
      information to Access Ports on an Access Node, using Black, Grey=20
      and White lists.

   o  The ANCP MUST support binding a particular Black, Grey and White=20
      List to a given Access Port.

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List the ANCP MUST allow the AN to query the NAS to request an=20
      admission decision for replicating that multicast flow to a=20
      particular Access Port.

   o  The ANCP MUST allow the NAS to send an admission decision to the=20
      AN indicating whether or not a multicast flow may be replicated to =

      a particular Access Port.

   o  The ANCP must allow the NAS to indicate to the AN whether or not=20
      Admission Control is needed for some multicast flows on a given=20
      Access Port and where needed whether or not it is to be performed=20
      with AN Bandwidth Delegation.

   o  In case of Admission Control without AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to reply to a query from the AN indicating =

      whether or not a multicast flow may be replicated to a particular=20
      Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to delegate a certain amount of bandwidth=20
      to the AN for a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the AN to query the NAS to request additional=20
      multicast bandwidth on a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to query (or to instruct) the AN to reduce =

      the amount of bandwidth previously delegated on a given Access=20
      Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the AN to autonomous release redundant multicast=20
      bandwidth on a given Access Port.

   o  The ANCP MUST allow the AN to send an Information Report message=20
      to the NAS whenever replication of a multicast flow on a=20
      particular Access Port start or ends.

   o  The ANCP MUST allow the AN to send an Information Report message=20
      to the NAS indicating the multicast traffic volume that has been=20
      replicated on that port.

   o  The ANCP MUST allow the NAS to indicate to the AN whether or not=20
      multicast accounting is needed for a multicast flow on a=20
      particular Access Port.

   o  In case multicast accounting is needed for a multicast flow on a=20
      particular Access Port, the ANCP MUST allow the NAS to indicate to =

      the AN whether or not additional volume accounting information is=20
      required.

   o  The ANCP MUST allow the NAS to revoke a decision to replicate a=20
      multicast flow to a particular Access Port, which had been=20
      conveyed earlier to an AN.

   o  The ANCP MUST support partial updates of the White, Grey and Black =

      lists.

   o  The ANCP MUST allow the NAS to query the AN to obtain information=20
      on what multicast flows are currently being replicated on a given=20
      Access Port, what Access Ports are currently receiving a given=20
      multicast flow, or what multicast flows are currently replicated=20
      on each Access Port.



Access Node multicast requirements (section 4.7.6)

   o  The AN must deny any join to a multicast flow matching the Black=20
      List for the relevant Access Port.

   o  The AN must accept any join to a multicast flow matching the White =

      List and not flagged as "Bandwidth Delegation" for the relevant=20
      Access Port.

   o  Upon receiving a join to a multicast flow which matches the White=20
      List whose entry is flagged as "Bandwidth Delegation" for the=20
      relevant Access Port, the AN must perform the necessary bandwidth=20
      admission control check for the new flow before starting the=20
      multicast flow replication.

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List whose entry is flagged as "no Bandwidth Delegation" for the=20
      relevant Access Port, the AN must support using ANCP to query the=20
      NAS to receive a response indicating whether that join is to be=20
      honored or denied.  In this case, the NAS will perform both the=20
      necessary conditional access and the admission control checks for=20
      the new flow.

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List whose entry is flagged as "Bandwidth Delegation" for the=20
      relevant Access Port, the AN must first perform the necessary=20
      bandwidth admission control check for the new flow.  If=20
      successful, the AN must support using ANCP to query the NAS to=20
      receive a response indicating whether that join is to be honored=20
      or denied.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to notify the NAS when the the user leaves =

      the multicast flow.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to query the NAS to request additional=20
      delegated multicast bandwidth on a given Access Port; the AN=20
      should be able to specify both the minimum and the preferred=20
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving a Bandwidth Delegation Request from the NAS querying or=20
      instructing to decrease the delegated multicast bandwidth on a=20
      given Access Port, the AN must support using ANCP to send a=20
      Bandwidth Delegation Response indicating the new delegated=20
      multicast bandwidth.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to send a Bandwidth Release message to the =

      NAS in order to release unused delegated multicast bandwidth on a=20
      given Access Port.

   o  If the requested multicast flow is not part of any list associated =

      with the Access Port, the AN must discard the message.

   o  If the requested multicast flow is part of multiple lists=20
      associated with the Access Port, the AN must use the most specific =

      match.

   o  If the requested multicast flow has the same most specific match=20
      in multiple lists, the AN must give precedence to the Black list,=20
      followed by the Grey list, and then the White list.

   o  The AN must support configuring a "catch-all" statement in the=20
      Black, White or Grey list in order to enforce a default behavior=20
      for a join to a multicast flow which doesn't match any other entry =

      in a list for the relevant Access Port.

   o  Upon querying the NAS, the AN must not propagate the join message=20
      before the successful authorization from the NAS is received.

   o  Upon receiving a leave for a multicast flow which matches the Grey =

      List, the AN should be able to autonomously stop replication and=20
      advertise this event to the NAS.

   o  The AN must support using ANCP to send an Information Report=20
      message to the NAS whenever replication starts or ends  [T.H:] or =
fails .

   o  The AN should support using ANCP to send an Information Report=20
      message to the NAS indicating the multicast traffic volume that=20
      has been replicated on that port.

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what multicast=20
      flows are currently being replicated on a given Access Port.

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what Access=20
      Ports are currently receiving a given multicast flow.

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what multicast=20
      flows are currently being replicated on each Access Port.

   o  Upon receiving an Admission Response from the NAS, indicating that =

      replication of a multicast flow is to start or stop on a given=20
      access port of the AN, the AN must enforce this decision.  This=20
      decision must be taken irrespective of whether or not a=20
      corresponding Admission Request was issued by the AN earlier on.



NAS multication requirements (section 4.8.6)

   o  The NAS must support using ANCP to configure multicast conditional =

      access information to Access Ports on an Access Node, using Black=20
      Lists, Grey Lists and White Lists.

   o  The NAS must support using ANCP to indicate to the AN whether or=20
      not Admission Control is needed for some multicast flows on a=20
      given Access Port and where needed whether or not it is to be=20
      performed with AN Bandwidth Delegation.

   o  Upon receiving a query from the AN for a request to replicate a=20
      multicast flow to a particular Access Port, and no AN Bandwidth=20
      Delegation is needed for that flow, the NAS must be able to=20
      perform the necessary checks (conditional access and/or admission=20
      control) for the new flow.  The NAS must support using ANCP to=20
      reply to the AN indicating whether the request is to be honored or =

      denied.

   o  Upon receiving a query from the AN for a request to replicate a=20
      multicast flow to a particular Access Port, and Admission Control=20
      with AN Bandwidth Delegation is needed for that flow, the NAS must =

      be able to perform the conditional access checks (if needed), and=20
      must support using ANCP to delegate a certain amount of bandwidth=20
      to the AN for a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving a Bandwidth Delegation Request from the AN requesting to =

      increase the delegated multicast bandwidth on a given Access Port, =

      the NAS must support using ANCP to send a Bandwidth Delegation=20
      Response indicating the new delegating multicast bandwidth.

   o  In case of Admission Control with AN Bandwidth Delegation, the NAS =

      must support using ANCP to send a request the AN to decrease the=20
      amount of multicast bandwidth previously delegated on a given=20
      Access Port; the NAS should be able to specify both the minimum=20
      and the preferred amount decrement of multicast bandwidth=20
      requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving an ANCP Bandwidth Release message, the NAS must be able=20
      to update accordingly its view of the multicast bandwidth=20
      delegated to the AN.

   o  The NAS must support using ANCP to configure the Access Node with=20
      the "maximum number of multicast streams" allowed to be received=20
      concurrently per Access Port.

   o  The NAS must support using ANCP to incrementally add, remove and=20
      modify individual entries in White, Black and Grey lists.

   o  The NAS must support using ANCP to indicate to the AN whether or=20
      not multicast accounting is needed for a multicast flow on a=20
      particular Access Port.

   o  In case multicast accounting is needed for a multicast flow on a=20
      particular Access Port, the NAS should support using ANCP to=20
      indicate to the AN whether or not additional volume accounting=20
      information is required.

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what multicast flows are currently replicated on a=20
      given Access Port.

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what Access Ports are currently receiving a given=20
      multicast flow.

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what multicast flows are currently replicated on=20
      each Access Port.

   o  When Multicast replication occurs on the AN, the NAS must support=20
      using ANCP to revoke the authorization to replicate a multicast=20
      flow to a particular Access Port.

   o  The NAS should support using ANCP to indicate to the AN that=20
      replication of a multicast flow is to start or stop on a given=20
      access port of the AN, without having received a corresponding=20
      Admission Request from the AN earlier on.

---

Sven Ooghe=20
Alcatel-Lucent=20
CTO Office, Access Division=20
Copernicuslaan 50, 2018 Antwerp, Belgium=20
tel.: +32 3 240 42 26=20
fax: +32 3 240 40 73

This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly prohibited =
without the prior consent of its author.

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp




--Boundary_(ID_jutcE5eYQ18b8WjOQK9XCQ)
Content-type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>Hi all,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>The name "PS/Policy Server" used in this draft =
is also kind=20
of confusing to me in this draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>The entity descriped in this draft is actually =
an entity=20
which manages (part of) the network bandwidth/resource and performs =
admission=20
control for the unicast service. These functionalites are not quite =
clearly=20
reflected by the name "Policy Server".</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>Therefore, I suggest we find a better name for =
this=20
entity.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>My proposal&nbsp;is to replace the "PS/Policy =
Server" with=20
"RACS / Resource and Admission Control Subsystem" which is defined in =
ETSI=20
TISPAN.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>I think the&nbsp;name "RACS"</FONT></SPAN><SPAN =

class=3D157111503-24102008><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2>can&nbsp;reflect the=20
requirement for this entity precisely.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>Best Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>Fortune</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN><FONT =
face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dblack=20
size=3D2><BR></FONT><FONT face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 =
color=3Dgray size=3D2>Huawei Technologies Co.,=20
Ltd. </FONT><IMG id=3DridImg alt=3Dhuawei_logo hspace=3D0=20
src=3D"cid:157111503@24102008-255F" align=3Dleft> </DIV>
<P></P><BR><FONT face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 =
color=3Dgray size=3D1>Addr: Section F, Huawei Industrial=20
Base, Bantian Longgang, Shenzhen 518129, P.R. China<BR>Tel:=20
+86-755-28971871<BR>Fax: +86-755-28972352<BR>Mobile: =
+8615013838060<BR>Email:=20
fqhuang@huawei.com<BR>http://www.huawei.com<BR></FONT><FONT =
face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dgray=20
size=3D1>----------------------------------------------------------------=
---------------------------------------------------------------------<BR>=
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81<BR>=E6=AD=A2=
=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=BD=95=E5=
=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=86=E4=B8=
=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=E5=9C=B0=
=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=95=A3=E5=
=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD<BR>=E7=9A=84=E4=BF=A1=
=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=94=B6=E4=BA=86=E6=
=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=8B=E5=8D=B3=E7=94=
=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=E5=8F=91=E4=BB=B6=
=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=81<=
BR></FONT><FONT=20
face=3DArial color=3Dgray size=3D1>This e-mail and its attachments =
contain=20
confidential information from HUAWEI, which <BR>is intended only for the =
person=20
or entity whose address is listed above. Any use of the <BR>information=20
contained herein in any way (including, but not limited to, total or =
partial=20
<BR>disclosure, reproduction, or dissemination) by persons other than =
the=20
intended <BR>recipient(s) is prohibited. If you receive this e-mail in =
error,=20
please notify the sender by <BR>phone or email immediately and delete=20
it!<BR></FONT>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dzh-cn dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3D=E5=AE=8B=E4=BD=93 =
size=3D2><B>=E5=8F=91=E4=BB=B6=E4=BA=BA:</B> Tina TSOU =
[mailto:tena@huawei.com]=20
<BR><B>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:</B> =
2008=E5=B9=B410=E6=9C=8822=E6=97=A5 =
19:52<BR><B>=E6=94=B6=E4=BB=B6=E4=BA=BA:</B> Haag, =
Thomas<BR><B>=E6=8A=84=E9=80=81:</B>=20
sven.ooghe@alcatel-lucent.be; =
ancp@ietf.org<BR><B>=E4=B8=BB=E9=A2=98:</B> Re: [ANCP] ANCP=20
Framework update<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi all,</DIV>
<DIV>I agree with Thomas' comments.</DIV>
<DIV><BR></DIV><BR>
<DIV apple-content-edited=3D"true"><SPAN class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
<DIV=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV>
<DIV>B. R.</DIV>
<DIV>Tina</DIV>
<DIV><BR></DIV>
<DIV>
<P>Messengers:</P>
<P>MSN: <A=20
href=3D"mailto:tinatsou6@hotmail.com">tinatsou6@hotmail.com</A>&nbsp;&nbs=
p; Yahoo:=20
tina_tsou&nbsp;&nbsp;&nbsp; Skype: tinaTSOU&nbsp;&nbsp;&nbsp; Jabber: <A =

href=3D"mailto:tina@jabber.org">tina@jabber.org</A>&nbsp;&nbsp;&nbsp; =
Google talk:=20
<A href=3D"mailto:tinatsou6@gmail.com">tinatsou6@gmail.com</A></P>
<P>+86-755-28971872 (Office)&nbsp;&nbsp;&nbsp;=20
+86-13922884380(Mobile)</P></DIV></DIV></DIV></SPAN></DIV></SPAN></DIV></=
SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></D=
IV></SPAN></DIV>
<DIV><BR></DIV><BR>
<DIV>
<DIV>On Oct 22, 2008, at 6:42 PM, Haag, Thomas wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">
  <DIV lang=3DDE link=3D"blue" vlink=3D"purple">
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D734534408-22102008>Hi Sven,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D734534408-22102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D734534408-22102008>please see my comments =
inline.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D734534408-22102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D734534408-22102008></SPAN></FONT><B><SPAN lang=3Dde><FONT =
size=3D2><SPAN=20
  class=3D734534408-22102008>R</SPAN>egards</FONT></SPAN></B><SPAN=20
  lang=3Dde></SPAN><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
  lang=3Dde><B><FONT size=3D2>Thomas Haag</FONT></B></SPAN><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN lang=3Dde><FONT =
color=3D#808080=20
  size=3D2>Deutsche Telekom AG<BR>Zentrum Technik =
Einf=C3=BChrung<BR>TE5-22,=20
  Internationale Standardisierung<BR>Heinrich-Hertz-Stra=C3=9Fe 3-7, =
64295=20
  Darmstadt<BR>+49 6151 628-2088 (Tel.)<BR>+49 521 9210-8411 =
(Fax)<BR>+49 171 56=20
  44 739 (Mobil)</FONT><B><BR></B><FONT color=3D#ff0000 =
size=3D2>Neu:</FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><FONT color=3D#808080=20
  size=3D2>Email:</FONT><U><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><FONT=20
  color=3D#0000ff size=3D2><A style=3D"COLOR: blue; TEXT-DECORATION: =
underline"=20
  href=3D"mailto:haagt@telekom.de">haagt@telekom.de</A></FONT></U><FONT=20
  color=3D#808080 size=3D2><BR></FONT></SPAN><A=20
  style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
  href=3D"http://www.telekom.com/"><SPAN lang=3Dde><U></U><U><FONT =
color=3D#0000ff=20
  size=3D2>http://www.telekom.com</FONT></U></SPAN></A><SPAN =
lang=3Dde><FONT=20
  color=3D#808080 size=3D2></FONT></SPAN></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV><FONT face=3DArial=20
  color=3D#0000ff size=3D2></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><FONT=20
  face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT><BR>
  <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr =
align=3Dleft><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <DIV class=3DSection1>
  <DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><B><FONT=20
  face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">Von:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><A=20
  href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</A> [<A=20
  style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
  =
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>]<S=
PAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><B><SPAN =
style=3D"FONT-WEIGHT: bold">Im=20
  Auftrag von<SPAN =
class=3DApple-converted-space>&nbsp;</SPAN></SPAN></B>OOGHE=20
  Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN>Freitag, 17. Oktober 2008=20
  11:23<BR><B><SPAN style=3D"FONT-WEIGHT: bold">An:</SPAN></B><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><A=20
  style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
  href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN>[ANCP] ANCP Framework=20
  update</SPAN></FONT><O:P></O:P></DIV></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">I've been=20
  updating the ANCP framework draft according to the suggested changes =
from=20
  Roberta and Francois. Below I have copy-pasted the sections that have=20
  undergone changes.<I><SPAN style=3D"FONT-STYLE: italic"><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN>Indented =
text</SPAN></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN>has been changed. I think I =
captured=20
  the essence of the notion of "bandwidth delegation". Please review and =
see if=20
  this is capturing the agreements.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><O:P></O:P></P>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">3.4.2.&nbsp;=20
  Multicast Admission Control</SPAN></FONT></B><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; The =
successful=20
  delivery of Triple Play Broadband services is =
quickly</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; becoming a =
big=20
  capacity planning challenge for most of the Service</SPAN></FONT><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Providers=20
  nowadays.&nbsp; Solely increasing available bandwidth is=20
  not</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; always =
practical,=20
  cost-economical and/or sufficient to satisfy end</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; user =
experience given=20
  not only the strict requirements of unicast</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; delay =
sensitive=20
  applications like VoIP and Video, but also the fast</SPAN></FONT><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; growth of =
multicast=20
  interactive applications such as</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
videoconferencing,=20
  digital TV, digital audio, online movies and</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; networked=20
  gaming.&nbsp; These applications are typically characterized=20
  by</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; a delay =
sensitive=20
  nature, an extremely loss sensitive nature and</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; intensive =
bandwidth=20
  requirements.&nbsp; They are also typically "non-</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; elastic", =
which means=20
  that they operate at a fixed bandwidth, that</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; cannot be =
dynamically=20
  adjusted to the currently available =
bandwidth.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Therefore a =

  Connection Admission Control (CAC) mechanism =
covering</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; admission =
of=20
  multicast traffic over the DSL Broadband access is</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; required, =
in order to=20
  avoid oversubscribing the available bandwidth</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; and =
negatively=20
  impacting the end user experience.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Considering =

  specifically admission control over the access =
line,</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; before =
honoring a=20
  user request to join a new multicast flow, the</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; combination =
of AN and=20
  NAS MUST ensure admission control is performed</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; to validate =
that=20
  there is enough "video" bandwidth remaining on the</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; access line =
to carry=20
  the new flow (in addition to all other existing</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; multicast =
and unicast=20
  video traffic).&nbsp; The solution needs to cope</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; with =
multiple flows=20
  per access line and needs to allow access line</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; bandwidth =
to be=20
  dynamically shared across multicast and unicast</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; traffic =
(irrespective=20
  of whether unicast CAC is performed by NAS or</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; by some =
off-path=20
  Policy Server).</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Thus, =
supporting CAC=20
  for the access line requires some form of</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
synchronization=20
  between the entity performing multicast CAC (e.g. =
the</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; NAS or the =
AN) and=20
  the entity performing unicast CAC (e.g. the NAS or</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; a Policy =
Server) and=20
  the entity actually enforcing the multicast<SPAN=20
  class=3D734534408-22102008><FONT color=3D#0000ff>&nbsp; [T.H.: Is that =
correct as=20
  stated "NAS or Policy server"?; My understanding: Policy Server:=20
  Policy&nbsp;decission point;&nbsp;NAS controls AN&nbsp;by ANCP;AN: =
policy=20
  enforcement point]&nbsp;</FONT></SPAN></SPAN>&nbsp;<BR><FONT =
face=3DArial=20
  size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  replication (i.e. the AN).&nbsp; This synchronization can be achieved =
in=20
  a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; number of=20
  ways:</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; One approach is for the AN to query the NAS so that=20
  Admission</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Control for the access line is performed by the NAS (possibly=20
  with</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  interactions with a Policy Server).&nbsp; This can be done with=20
  or</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  without "bandwidth delegation" to the =
AN.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  *&nbsp; In case of Admission Control without AN Bandwidth=20
  Delegation,</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the AN can use ANCP to query the NAS, that in turn=20
  performs</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast Admission Control check for the new multicast=20
  flow</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  and responds to the AN indicating whether the join is to=20
  be</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  honored (and hence replication performed by the AN) or=20
  denied.</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The NAS may locally maintain available "video" bandwidth&nbsp;<FONT=20
  color=3D#0000ff><SPAN =
class=3D734534408-22102008>&nbsp;[T.H.:]&nbsp;</SPAN><SPAN=20
  class=3D734534408-22102008>&nbsp;(net data rate)&nbsp;</SPAN></FONT>on =

  the</SPAN><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Loop, and perform video bandwidth accounting for=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Loop.&nbsp; Upon receiving an Admission Request from the=20
  AN,</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the NAS can check available "video" bandwidth before=20
  admitting</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  or denying the multicast flow.&nbsp; In the process, the NAS=20
  may</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  communicate with the Policy Server.&nbsp; For unicast video=20
  services</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  such as Video on Demand (VoD), the NAS may also be queried=20
  (by</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  a Policy Server or via on-path CAC signaling), so that it=20
  can</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  perform admission control for the unicast flow, and update=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  available video bandwidth maintained by the=20
  NAS.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  *&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  NAS (possibly with interactions with a Policy Server)=20
  manages</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  total bandwidth for video admission, performs unicast=20
  admission</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  control and uses ANCP to delegate a certain amount of=20
  bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  for some multicast flows to the Access Node.&nbsp; In this=20
  scenario,</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  upon receiving a join to a multicast flow which matches=20
  an</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  entry in the White or Grey List whose entry is flagged=20
  as</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "Bandwidth Delegation", the AN must perform the=20
  necessary</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  bandwidth admission control check for the new multicast=20
  flow,</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  before starting the multicast flow=20
  replication.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The ANCP requirements to support this approach are specified=20
  in</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  this document.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
case the=20
  subscriber communicates the "join/leave" =
information</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  with the NAS (e.g. by terminating all subscriber IGMP signaling=20
  on</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  NAS, or by using some form of application level =
signaling),</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  approach is very similar.&nbsp; In this case, the NAS may=20
  locally</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  maintain available "video" bandwidth on the Access Loop,=20
  perform</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  video bandwidth accounting, and perform CAC for unicast =
and</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flows.&nbsp; The NAS can set the replication state on the=20
  AN</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  using ANCP if the flow is admitted.&nbsp; For unicast video=20
  services</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  NAS may be queried (by a policy server or via on-path =
CAC</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  signaling) to perform admission control for the unicast flow,=20
  and</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  update the available video bandwidth maintained by the NAS.&nbsp;=20
  The</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP requirements to support this approach (where the AN=20
  queries</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  NAS) are specified in this document;</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
a third=20
  approach, the Policy Server queries the AN directly =
so</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  that both unicast and multicast CAC for the access line =
are</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  performed by the AN.&nbsp; In this case, a subscriber request for=20
  a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  unicast flow (e.g. a Video on Demand session) will trigger=20
  a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  resource request message towards a Policy Server; the latter=20
  will</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  then query the AN, that in turn will perform unicast CAC for=20
  the</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  access line and respond, indicating whether the unicast request=20
  is</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to=20
  be honored or denied.&nbsp; In this scenario the Policy=20
  Server</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  queries the AN directly, the approach doesn't require the use=20
  of</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP.&nbsp; It is therefore beyond the scope of this=20
  document.</SPAN></FONT><O:P></O:P></P>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">4.2.&nbsp; ANCP=20
  Multicast Requirements</SPAN></FONT></B><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  support providing multicast conditional access</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  information to Access Ports on an Access Node, using Black,=20
  Grey</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and=20
  White lists.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  support binding a particular Black, Grey and White</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List to a given Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
  receiving a join to a multicast flow which matches the =
Grey</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List the ANCP MUST allow the AN to query the NAS to request=20
  an</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  admission decision for replicating that multicast flow to =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  particular Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  allow the NAS to send an admission decision to the</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AN=20
  indicating whether or not a multicast flow may be replicated=20
  to</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=20
  particular Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; The ANCP must allow the NAS to indicate to the AN whether or=20
  not</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Admission Control is needed for some multicast flows on a=20
  given</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Port and where needed whether or not it is to be=20
  performed</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  with AN Bandwidth Delegation.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control without AN Bandwidth Delegation,=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP must allow the NAS to reply to a query from the AN=20
  indicating</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  whether or not a multicast flow may be replicated to a=20
  particular</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP must allow the NAS to delegate a certain amount of=20
  bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  to the AN for a given Access Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP must allow the AN to query the NAS to request=20
  additional</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast bandwidth on a given Access =
Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP must allow the NAS to query (or to instruct) the AN to=20
  reduce</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the amount of bandwidth previously delegated on a given=20
  Access</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ANCP must allow the AN to autonomous release redundant=20
  multicast</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  bandwidth on a given Access Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  allow the AN to send an Information Report message</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to=20
  the NAS whenever replication of a multicast flow on =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  particular Access Port start or ends.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  allow the AN to send an Information Report message</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to=20
  the NAS indicating the multicast traffic volume that has=20
  been</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  replicated on that port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  allow the NAS to indicate to the AN whether or not</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  particular Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
case=20
  multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  particular Access Port, the ANCP MUST allow the NAS to indicate=20
  to</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  AN whether or not additional volume accounting information=20
  is</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  required.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  allow the NAS to revoke a decision to replicate a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow to a particular Access Port, which had =
been</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  conveyed earlier to an AN.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  support partial updates of the White, Grey and =
Black</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  lists.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
ANCP MUST=20
  allow the NAS to query the AN to obtain information</SPAN></FONT><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on=20
  what multicast flows are currently being replicated on a=20
  given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Port, what Access Ports are currently receiving a=20
  given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow, or what multicast flows are currently=20
  replicated</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on=20
  each Access Port.</SPAN></FONT><O:P></O:P></P>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Access Node=20
  multicast requirements (section =
4.7.6)</SPAN></FONT></B><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must=20
  deny any join to a multicast flow matching the =
Black</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List for the relevant Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; The AN must accept any join to a multicast flow matching the=20
  White</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List and not flagged as "Bandwidth Delegation" for the=20
  relevant</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; Upon receiving a join to a multicast flow which matches the=20
  White</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List whose entry is flagged as "Bandwidth Delegation" for=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  relevant Access Port, the AN must perform the necessary=20
  bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  admission control check for the new flow before starting=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow replication.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; Upon receiving a join to a multicast flow which matches the=20
  Grey</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List whose entry is flagged as "no Bandwidth Delegation" for=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  relevant Access Port, the AN must support using ANCP to query=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  NAS to receive a response indicating whether that join is to=20
  be</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  honored or denied.&nbsp; In this case, the NAS will perform both=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  necessary conditional access and the admission control checks=20
  for</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the new flow.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; Upon receiving a join to a multicast flow which matches the=20
  Grey</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List whose entry is flagged as "Bandwidth Delegation" for=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  relevant Access Port, the AN must first perform the=20
  necessary</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  bandwidth admission control check for the new flow.&nbsp;=20
  If</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  successful, the AN must support using ANCP to query the NAS=20
  to</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  receive a response indicating whether that join is to be=20
  honored</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  or denied.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the =

  AN</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  must support using ANCP to notify the NAS when the the user=20
  leaves</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the multicast flow.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the =

  AN</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  must support using ANCP to query the NAS to request=20
  additional</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  delegated multicast bandwidth on a given Access Port; the=20
  AN</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  should be able to specify both the minimum and the=20
  preferred</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  amount of additional multicast bandwidth=20
  requested.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  upon</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  receiving a Bandwidth Delegation Request from the NAS querying=20
  or</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  instructing to decrease the delegated multicast bandwidth on=20
  a</SPAN></FONT></I><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  given Access Port, the AN must support using ANCP to send=20
  a</SPAN></FONT></I><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Bandwidth Delegation Response indicating the new=20
  delegated</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast bandwidth.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the =

  AN</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  must support using ANCP to send a Bandwidth Release message to=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  NAS in order to release unused delegated multicast bandwidth on=20
  a</SPAN></FONT></I><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  given Access Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the=20
  requested multicast flow is not part of any list =
associated</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  with the Access Port, the AN must discard the=20
  message.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the=20
  requested multicast flow is part of multiple lists</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  associated with the Access Port, the AN must use the most=20
  specific</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  match.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the=20
  requested multicast flow has the same most specific =
match</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
  multiple lists, the AN must give precedence to the Black=20
  list,</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  followed by the Grey list, and then the White=20
  list.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must=20
  support configuring a "catch-all" statement in the</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Black, White or Grey list in order to enforce a default=20
  behavior</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for=20
  a join to a multicast flow which doesn't match any other=20
  entry</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
  a list for the relevant Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon querying=20
  the NAS, the AN must not propagate the join message</SPAN></FONT><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  before the successful authorization from the NAS is=20
  received.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
  receiving a leave for a multicast flow which matches the=20
  Grey</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List, the AN should be able to autonomously stop replication=20
  and</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  advertise this event to the NAS.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must=20
  support using ANCP to send an Information Report</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  message to the NAS whenever replication starts or ends<SPAN=20
  class=3D734534408-22102008><FONT color=3D#0000ff>&nbsp; [T.H:] or=20
  fails&nbsp;</FONT></SPAN>.</SPAN><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN should=20
  support using ANCP to send an Information Report</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  message to the NAS indicating the multicast traffic volume=20
  that</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has=20
  been replicated on that port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon request=20
  by the NAS, the AN must support using ANCP to send =
an</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Information Report message to the NAS, indicating what=20
  multicast</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  flows are currently being replicated on a given Access=20
  Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon request=20
  by the NAS, the AN must support using ANCP to send =
an</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Information Report message to the NAS, indicating what=20
  Access</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Ports are currently receiving a given multicast=20
  flow.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon request=20
  by the NAS, the AN must support using ANCP to send =
an</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Information Report message to the NAS, indicating what=20
  multicast</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  flows are currently being replicated on each Access=20
  Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
  receiving an Admission Response from the NAS, indicating=20
  that</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  replication of a multicast flow is to start or stop on a=20
  given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  access port of the AN, the AN must enforce this decision.&nbsp;=20
  This</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  decision must be taken irrespective of whether or not =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  corresponding Admission Request was issued by the AN earlier=20
  on.</SPAN></FONT><O:P></O:P></P>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">NAS =
multication=20
  requirements (section 4.8.6)</SPAN></FONT></B><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to configure multicast =
conditional</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  access information to Access Ports on an Access Node, using=20
  Black</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Lists, Grey Lists and White Lists.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; The NAS must support using ANCP to indicate to the AN whether=20
  or</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  not Admission Control is needed for some multicast flows on=20
  a</SPAN></FONT></I><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  given Access Port and where needed whether or not it is to=20
  be</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  performed with AN Bandwidth =
Delegation.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; Upon receiving a query from the AN for a request to replicate=20
  a</SPAN></FONT></I><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow to a particular Access Port, and no AN=20
  Bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Delegation is needed for that flow, the NAS must be able=20
  to</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  perform the necessary checks (conditional access and/or=20
  admission</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  control) for the new flow.&nbsp; The NAS must support using ANCP=20
  to</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  reply to the AN indicating whether the request is to be honored=20
  or</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  denied.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; Upon receiving a query from the AN for a request to replicate=20
  a</SPAN></FONT></I><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow to a particular Access Port, and Admission=20
  Control</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  with AN Bandwidth Delegation is needed for that flow, the NAS=20
  must</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  be able to perform the conditional access checks (if needed),=20
  and</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  must support using ANCP to delegate a certain amount of=20
  bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  to the AN for a given Access Port.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  upon</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  receiving a Bandwidth Delegation Request from the AN requesting=20
  to</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  increase the delegated multicast bandwidth on a given Access=20
  Port,</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the NAS must support using ANCP to send a Bandwidth=20
  Delegation</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Response indicating the new delegating multicast=20
  bandwidth.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation, the =

  NAS</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  must support using ANCP to send a request the AN to decrease=20
  the</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  amount of multicast bandwidth previously delegated on a=20
  given</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Port; the NAS should be able to specify both the=20
  minimum</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  and the preferred amount decrement of multicast=20
  bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  requested.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  upon</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  receiving an ANCP Bandwidth Release message, the NAS must be=20
  able</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  to update accordingly its view of the multicast=20
  bandwidth</SPAN></FONT></I><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  delegated to the AN.</SPAN></FONT></I><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to configure the Access Node =
with</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
  "maximum number of multicast streams" allowed to be=20
  received</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  concurrently per Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to incrementally add, remove and</SPAN></FONT><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  modify individual entries in White, Black and Grey=20
  lists.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to indicate to the AN whether or</SPAN></FONT><SPAN =

  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not=20
  multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  particular Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In =
case=20
  multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  particular Access Port, the NAS should support using ANCP=20
  to</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  indicate to the AN whether or not additional volume=20
  accounting</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  information is required.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to query the AN to obtain</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  information on what multicast flows are currently replicated on=20
  a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  given Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to query the AN to obtain</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  information on what Access Ports are currently receiving a=20
  given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must=20
  support using ANCP to query the AN to obtain</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  information on what multicast flows are currently replicated=20
  on</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  each Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
When=20
  Multicast replication occurs on the AN, the NAS must=20
  support</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  using ANCP to revoke the authorization to replicate a=20
  multicast</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  flow to a particular Access Port.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS=20
  should support using ANCP to indicate to the AN =
that</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  replication of a multicast flow is to start or stop on a=20
  given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  access port of the AN, without having received a=20
  corresponding</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Admission Request from the AN earlier on.</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">---</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sven=20
  Ooghe</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Alcatel-Lucent</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">CTO Office, Access=20
  Division</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Copernicuslaan 50, 2018 =
Antwerp,=20
  Belgium</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
  face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">tel.: +32=20
  3 240 42 26</SPAN></FONT><SPAN=20
  class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">fax: +32 3 240 40=20
  73</SPAN></FONT><O:P></O:P></P>
  <P=20
  style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
  face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">This=20
  message (including any attachments) contains confidential information =
intended=20
  for a specific individual and purpose, and is protected by law.&nbsp; =
If you=20
  are not the intended recipient, you should delete this message.&nbsp; =
Any=20
  disclosure, copying, or distribution of this message, or the taking of =
any=20
  action based on it, is strictly prohibited without the prior consent =
of its=20
  =
author.</SPAN></FONT><O:P></O:P></P></DIV>_______________________________=
________________<BR>ANCP=20
  mailing list<BR><A style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
  href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR><A=20
  style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></DIV></SPAN></BLOCKQUOTE></DIV><BR></BODY><=
/HTML>

--Boundary_(ID_jutcE5eYQ18b8WjOQK9XCQ)--

--Boundary_(ID_BH5kNYF9EwFK31yWYnA0eg)
Content-id: <157111503@24102008-255F>
Content-type: image/jpeg; name=outlook_huawei_logo_cn.jpg
Content-transfer-encoding: base64
Content-disposition: attachment; filename=outlook_huawei_logo_cn.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/7QxmUGhvdG9zaG9wIDMuMAA4QklNBCUAAAAAABAAAAAAAAAA
AAAAAAAAAAAAOEJJTQPtAAAAAAAQAEgAAAABAAIASAAAAAEAAjhCSU0EJgAAAAAADgAAAAAAAAAA
AAA/gAAAOEJJTQQNAAAAAAAEAAAAHjhCSU0EGQAAAAAABAAAAB44QklNA/MAAAAAAAkAAAAAAAAA
AAEAOEJJTQQKAAAAAAABAAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgAB
AGxmZgAGAAAAAAABAC9mZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0A
AAAGAAAAAAABOEJJTQP4AAAAAABwAAD/////////////////////////////A+gAAAAA////////
/////////////////////wPoAAAAAP////////////////////////////8D6AAAAAD/////////
////////////////////A+gAADhCSU0EAAAAAAAAAgAAOEJJTQQCAAAAAAACAAA4QklNBDAAAAAA
AAEBADhCSU0ELQAAAAAABgABAAAABjhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBB4A
AAAAAAQAAAAAOEJJTQQaAAAAAAM9AAAABgAAAAAAAAAAAAAAIAAAAGYAAAAEAGwAbwBnAG8AAAAB
AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAGYAAAAgAAAAAAAAAAAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAAAAAAAAAEAAAAAEAAAAAAABudWxsAAAAAgAAAAZib3VuZHNPYmpjAAAAAQAAAAAA
AFJjdDEAAAAEAAAAAFRvcCBsb25nAAAAAAAAAABMZWZ0bG9uZwAAAAAAAAAAQnRvbWxvbmcAAAAg
AAAAAFJnaHRsb25nAAAAZgAAAAZzbGljZXNWbExzAAAAAU9iamMAAAABAAAAAAAFc2xpY2UAAAAS
AAAAB3NsaWNlSURsb25nAAAAAAAAAAdncm91cElEbG9uZwAAAAAAAAAGb3JpZ2luZW51bQAAAAxF
U2xpY2VPcmlnaW4AAAANYXV0b0dlbmVyYXRlZAAAAABUeXBlZW51bQAAAApFU2xpY2VUeXBlAAAA
AEltZyAAAAAGYm91bmRzT2JqYwAAAAEAAAAAAABSY3QxAAAABAAAAABUb3AgbG9uZwAAAAAAAAAA
TGVmdGxvbmcAAAAAAAAAAEJ0b21sb25nAAAAIAAAAABSZ2h0bG9uZwAAAGYAAAADdXJsVEVYVAAA
AAEAAAAAAABudWxsVEVYVAAAAAEAAAAAAABNc2dlVEVYVAAAAAEAAAAAAAZhbHRUYWdURVhUAAAA
AQAAAAAADmNlbGxUZXh0SXNIVE1MYm9vbAEAAAAIY2VsbFRleHRURVhUAAAAAQAAAAAACWhvcnpB
bGlnbmVudW0AAAAPRVNsaWNlSG9yekFsaWduAAAAB2RlZmF1bHQAAAAJdmVydEFsaWduZW51bQAA
AA9FU2xpY2VWZXJ0QWxpZ24AAAAHZGVmYXVsdAAAAAtiZ0NvbG9yVHlwZWVudW0AAAARRVNsaWNl
QkdDb2xvclR5cGUAAAAATm9uZQAAAAl0b3BPdXRzZXRsb25nAAAAAAAAAApsZWZ0T3V0c2V0bG9u
ZwAAAAAAAAAMYm90dG9tT3V0c2V0bG9uZwAAAAAAAAALcmlnaHRPdXRzZXRsb25nAAAAAAA4QklN
BCgAAAAAAAwAAAABP/AAAAAAAAA4QklNBBEAAAAAAAEBADhCSU0EFAAAAAAABAAAAAg4QklNBAwA
AAAABnAAAAABAAAAZgAAACAAAAE0AAAmgAAABlQAGAAB/9j/4AAQSkZJRgABAgAASABIAAD/7QAM
QWRvYmVfQ00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUT
ExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4O
Dg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMB
IgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEB
AAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSR
obFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSF
tJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIR
AyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVV
NnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEA
AhEDEQA/APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC6
6f56f3t30Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUs
VaDHl/dl/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5Vtns
U/qp1vqPUvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9
w9+kqfV+qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVh
fWLCzerW9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX
146P1azqFWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKeh
SWDk/XHpVHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8t
bvSU9Ikucy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uo
JBeNpMtfRc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxb
qtG20uI0PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv
/QXjOu9COI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5F
ztrrn/usXoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4
HX+6yY/jQHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v
6hNyW9Q6jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m
+u1tQc9n0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6
tfRj2YnTgMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJ
JT5b0bpfUrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6r
WuLnfpNjXu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z
OEJJTQQhAAAAAABVAAAAAQEAAAAPAEEAZABvAGIAZQAgAFAAaABvAHQAbwBzAGgAbwBwAAAAEwBB
AGQAbwBiAGUAIABQAGgAbwB0AG8AcwBoAG8AcAAgAEMAUwAyAAAAAQA4QklNBAYAAAAAAAcABQAA
AAEBAP/hB4ZFeGlmAABJSSoACAAAAAcAEgEDAAEAAAABAAAAGgEFAAEAAABiAAAAGwEFAAEAAABq
AAAAKAEDAAEAAAACAAAAMQECABwAAAByAAAAMgECABQAAACOAAAAaYcEAAEAAACiAAAAzAAAAID8
CgAQJwAAgPwKABAnAABBZG9iZSBQaG90b3Nob3AgQ1MyIFdpbmRvd3MAMjAwNzowMjoyNiAxNjox
ODo1MwADAAGgAwABAAAA/////wKgBAABAAAAZgAAAAOgBAABAAAAIAAAAAAAAAAGAAMBAwABAAAA
BgAAABoBBQABAAAAGgEAABsBBQABAAAAIgEAACgBAwABAAAAAgAAAAECBAABAAAAKgEAAAICBAAB
AAAAVAYAAAAAAABIAAAAAQAAAEgAAAABAAAA/9j/4AAQSkZJRgABAgAASABIAAD/7QAMQWRvYmVf
Q00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwM
DAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwM
DAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMBIgACEQED
EQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAA
AAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQV
UsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0
pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRB
UWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKz
hMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/
APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC66f56f3t3
0Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUsVaDHl/dl
/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5VtnsU/qp1vqP
UvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9w9+kqfV+
qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVhfWLCzerW
9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX146P1azq
FWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKehSWDk/XHp
VHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8tbvSU9Iku
cy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uoJBeNpMtf
Rc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxbqtG20uI0
PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv/QXjOu9C
OI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5Fztrrn/us
XoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4HX+6yY/j
QHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v6hNyW9Q6
jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m+u1tQc9n
0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6tfRj2YnT
gMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJJT5b0bpf
UrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6rWuLnfpNj
Xu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z/9sAQwAI
BgYHBgUIBwcHCQkICgwUDQwLCwwZEhMPFB0aHx4dGhwcICQuJyAiLCMcHCg3KSwwMTQ0NB8nOT04
MjwuMzQy/9sAQwEJCQkMCwwYDQ0YMiEcITIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIy/8AAEQgAIABmAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAA
AAABAgMEBQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGh
CCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV
1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkK
C//EALURAAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy
0QoWJDThJfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKD
hIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm
5+jp6vLz9PX29/j5+v/aAAwDAQACEQMRAD8A99LKCASAT0FcOvxDin8XjRre2Bt1l8mS4Zud3Tge
ma5X4j67qukeObG5hdkhto1e3H8L5+9n1z0rnriVIvF9pqdmP9E1CdLiPn7pLDcp9wcj8q8+vimn
yx0sz6zLsihOj7WtrzxbXk/87a/f2PazrqpqL27oBEsnlhwec+4rYyCSM8jtXj0OupJ4hvZbhytr
aSvNOfYHhfqTgVJ4G8R6nrfxAuLklzbTRMZlz8qKPu/THSnSxT5rS1u9Dlr5HNU5VVooxu/8vX/g
dz1+iszX9at/Dug3mr3Su9vax+Y4jGWI9qz9U8ZafpXgtfFE0U7WTQpKEVRvw2McZ967z506Oiuf
03xbY6n4juNDhjmFzBaR3bMw+Xa4BA+vIp2leKrHV9d1nSIElSfSXVJ2cAKdwyMH8KAN6iuM0P4l
6J4hn1eDTkuJJdNRpCpUAzICQWTnkZFK/wASdEj8Ar4wInNiSF8sKPMD7tu3GcZBoA7KiuSu/iDo
9p4NsvE22eW0vWRII41BkZ2OAuM9Rg/lVbUviXptnq82lWem6pql7bgfaUsbfzBCT2Y5xn2oA7ai
uB134q6V4b0nTb7VdM1K3N/v2W7xASJtOPmGeOtFAHnupab4l8P3s+kX+nT6ro/mFoCVLgAngo45
RvUfpWr4a8NnUmFrB5qwxyrcol0hSS3YEZB7MrDjI74r0TxX4MtPFSRNLd3VpcRcLNbyEHHcEdDV
zQPDGn+G7XyrNZHdv9ZPM5d3+p/oK4/q153ex9Is9ccNyrSfktL93/wN+uh5n4m8NNp8ssEvm+Rc
TtcyC2QvJOSTtUDsqjue5NZumaX4h1meLStP06fTNLLgzHaV3Ad3c8sfbp7V7Frnh6w8QWohvEcM
v3JYmKun0P8AjVHwx4PtfDJleO7urueQYMk75wvoB0FTLC+/psa0s/UcLaWtRbXWl++/57dNCp8S
reR/hjrlvBG8shtNqqilmbkdhXmniXwPqEPweS7XW/EFzKbWE/2dI+6MHjK7MZwP6V73RXcfLHj8
V+3g34ivrOq2F9/ZmoaPbwx3MFu0oWRAMqwUZB4rDe/1hIPGWsaXpl/HJ4lu4rPTPMhZXIwQ0hGM
qAO59a98ooA8Fl0Dxb4DvvDmuXNnp8tlpiiwnTTUdpJIHPJcEc4Jzx3pkOgagvj2HwV9gmfw+dY/
thZmQ+X5XllvLPGOuePWvfaKAPBfD2iapL48svB91ZTLpGhalPqKTsp2SKeY1B6cE5/Oqg0u58Le
LfEMes33imwjvLs3FvcaOheKdSSfmwCcjOK+haKAPm34sWlxqvhPwrJpi6zqcY8/M13CxnPzD74x
ke3tRX0lRQB//9k=

--Boundary_(ID_BH5kNYF9EwFK31yWYnA0eg)--

--===============2023835625==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============2023835625==--


From ancp-bounces@ietf.org  Thu Oct 23 23:10:52 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CBB13A6851;
	Thu, 23 Oct 2008 23:10:52 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C67753A67D1
	for <ancp@core3.amsl.com>; Thu, 23 Oct 2008 23:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 T3vnB8E3fZq5 for <ancp@core3.amsl.com>;
	Thu, 23 Oct 2008 23:10:50 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it
	(grfedg702rm001.telecomitalia.it [217.169.121.21])
	by core3.amsl.com (Postfix) with ESMTP id BB9003A6851
	for <ancp@ietf.org>; Thu, 23 Oct 2008 23:10:49 -0700 (PDT)
Received: from grfhub701rm001.griffon.local (10.19.3.8) by
	GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP
	Server (TLS) id 8.1.291.1; Fri, 24 Oct 2008 08:10:55 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by
	grfhub701rm001.griffon.local ([10.19.9.234]) with mapi; Fri, 24 Oct 2008
	08:12:08 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "ancp@ietf.org" <ancp@ietf.org>
Date: Fri, 24 Oct 2008 08:12:07 +0200
Thread-Topic: Result field
Thread-Index: AQHJNZ9xOlLrCrg5ZkCSjuTF00KdQQ==
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2033DE77582@GRFMBX702RM001.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
MIME-Version: 1.0
Subject: [ANCP] Result field
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hello,
        I am currently updating the ancp-protocol draft and I would like to incorporate the topics recently discussed in this alias. In particular a couple of weeks ago we talked about the use of Result Field in ANCP messages in order to try to rationalize the codes for this field, coming from GSMP, and actually useful for ANCP protocol.
http://www.ietf.org/mail-archive/web/ancp/current/msg00661.html

According to this thread the useful codes for Result field in ANCP use cases seem to be:
"AckAll": (always send a response) used in OAM use case;
"NAck": (generate a response only in case of an error condition) for Multicast use case;
0 used in Topology Discover use case.

The value 0 for Result field is not defined in GSMP RFC, but it is actually used in one of the ANCP use case. In order to guarantee backward compatibility with current implementations it's reasonable to keep the code 0 for Result field, the proposal on previous email thread was to define in ANCP protocol draft  a semantic for Result = 0x00.

The proposed semantic was Result = 0x00 meaning "No Response required".

Please let me know if this semantic for Result field is ok for you or you have any additional comment on this proposal.
Thanks
Best Regards,
Roberta


CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Fri Oct 24 05:12:55 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E995A28C11F;
	Fri, 24 Oct 2008 05:12:55 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29CD628C11A
	for <ancp@core3.amsl.com>; Fri, 24 Oct 2008 05:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.232
X-Spam-Level: 
X-Spam-Status: No, score=-5.232 tagged_above=-999 required=5
	tests=[AWL=-1.366, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884,
	HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 YdBZixhpWEGD for <ancp@core3.amsl.com>;
	Fri, 24 Oct 2008 05:12:50 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 2BFFA28C17A
	for <ancp@ietf.org>; Fri, 24 Oct 2008 05:12:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208,217";a="23636019"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 24 Oct 2008 12:14:07 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OCE7xZ000892; 
	Fri, 24 Oct 2008 14:14:07 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9OCE7dI026724;
	Fri, 24 Oct 2008 12:14:07 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 14:14:07 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 14:14:01 +0200
Message-Id: <1D2B54B0-EB7A-4302-A75F-77EBC7CB9909@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Fortune HUANG <fqhuang@huawei.com>
In-Reply-To: <002101c9358c$64b66b60$7b27460a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 14:13:59 +0200
References: <002101c9358c$64b66b60$7b27460a@china.huawei.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 24 Oct 2008 12:14:01.0725 (UTC)
	FILETIME=[00106AD0:01C935D2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=131894; t=1224850447;
	x=1225714447; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20=3D?UTF-8?Q?Re=3A_[ANCP]_=3DE7=3DAD=3D94=3DE5=3
	DA4=3D8D=3A__ANCP_Framework_update?=3D |Sender:=20;
	bh=pHY5jkap15T2I4Jen/40XEPKahNnBJaGveJ7aoormEs=;
	b=qy/cKiTdU1MhaRtZMnoFApwQrVyi6CX+5oHivXAuotAhjxXW9JxrnS6U5f
	TTkr5HmMwZJfNqA0FBGGLjglZHlD1lV8nP0Aq2syN/7QcEBZHERxZ7foywpV
	di9ZqScszk;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: "'Haag, Thomas'" <HaagT@telekom.de>, ancp@ietf.org
Subject: Re: [ANCP] =?utf-8?b?562U5aSNOiAgQU5DUCBGcmFtZXdvcmsgdXBkYXRl?=
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1045365453=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============1045365453==
Content-Type: multipart/alternative; boundary=Apple-Mail-12--417379431


--Apple-Mail-12--417379431
Content-Type: text/plain;
	charset=UTF-8;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable

Fortune,

I don't think it is a good idea to refer to this entity as RACS because:
	* as a general practise we don't want to depend on definition =
from =20
external bodies
	* i don't believe the RACS terminology is that well known in =
IETF =20
community
	* I would argue that in some scenarios some of the function =
performed =20
by the NAS belong to the RACS functional entity (so that it is not =20
correct to model the RACS as entirely outside the NAS)

As far as alternatives, perhaps we could use Policy Decision Point? =20
that is an existing IETF concept and suggests that the entity makes =20
admission decisions, some of which being bandwidth based.

In any case, the interactions with the Policy Server/Policy Decision =20
Point/xxx   are outside the scope of ANCP of course, so we only need =20
to indicate that optional communication with an entity involved in the =20=

admission decision is possible.

Francois

On 24 Oct 2008, at 05:55, Fortune HUANG wrote:

> Hi all,
>
>
> The name "PS/Policy Server" used in this draft is also kind of =20
> confusing to me in this draft.
>
> The entity descriped in this draft is actually an entity which =20
> manages (part of) the network bandwidth/resource and performs =20
> admission control for the unicast service. These functionalites are =20=

> not quite clearly reflected by the name "Policy Server".
>
> Therefore, I suggest we find a better name for this entity.
>
> My proposal is to replace the "PS/Policy Server" with "RACS / =20
> Resource and Admission Control Subsystem" which is defined in ETSI =20
> TISPAN.
> I think the name "RACS"can reflect the requirement for this entity =20
> precisely.
>
>
> Best Regards,
> Fortune
>
> Huawei Technologies Co., Ltd. <outlook_huawei_logo_cn.jpg>
>
>
> Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =20=

> 518129, P.R. China
> Tel: +86-755-28971871
> Fax: +86-755-28972352
> Mobile: +8615013838060
> Email: fqhuang@huawei.com
> http://www.huawei.com
> =
--------------------------------------------------------------------------=
-----------------------------------------------------------
> =E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=
=E6=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=
=BF=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=20
> =E9=80=81=E7=BB=99=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=
=E5=87=BA=E7=9A=84=E4=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=
=A6=81
> =E6=AD=A2=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=
=E4=BD=95=E5=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=
=BD=86=E4=B8=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=20
> =E9=83=A8=E5=88=86=E5=9C=B0=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=
=E3=80=81=E6=88=96=E6=95=A3=E5=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=
=B8=AD
> =E7=9A=84=E4=BF=A1=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=
=E6=94=B6=E4=BA=86=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=
=AB=8B=E5=8D=B3=E7=94=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=20
> =E9=80=9A=E7=9F=A5=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=
=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=81
> This e-mail and its attachments contain confidential information =20
> from HUAWEI, which
> is intended only for the person or entity whose address is listed =20
> above. Any use of the
> information contained herein in any way (including, but not limited =20=

> to, total or partial
> disclosure, reproduction, or dissemination) by persons other than =20
> the intended
> recipient(s) is prohibited. If you receive this e-mail in error, =20
> please notify the sender by
> phone or email immediately and delete it!
>
>
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Tina TSOU [mailto:tena@huawei.com]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2008=E5=B9=B410=E6=9C=8822=E6=97=A5=
 19:52
> =E6=94=B6=E4=BB=B6=E4=BA=BA: Haag, Thomas
> =E6=8A=84=E9=80=81: sven.ooghe@alcatel-lucent.be; ancp@ietf.org
> =E4=B8=BB=E9=A2=98: Re: [ANCP] ANCP Framework update
>
> Hi all,
> I agree with Thomas' comments.
>
>
> B. R.
> Tina
>
> Messengers:
>
> MSN: tinatsou6@hotmail.com   Yahoo: tina_tsou    Skype: tinaTSOU    =20=

> Jabber: tina@jabber.org    Google talk: tinatsou6@gmail.com
>
> +86-755-28971872 (Office)    +86-13922884380(Mobile)
>
>
>
> On Oct 22, 2008, at 6:42 PM, Haag, Thomas wrote:
>
>> Hi Sven,
>>
>> please see my comments inline.
>>
>> Regards
>> Thomas Haag
>> Deutsche Telekom AG
>> Zentrum Technik Einf=C3=BChrung
>> TE5-22, Internationale Standardisierung
>> Heinrich-Hertz-Stra=C3=9Fe 3-7, 64295 Darmstadt
>> +49 6151 628-2088 (Tel.)
>> +49 521 9210-8411 (Fax)
>> +49 171 56 44 739 (Mobil)
>> Neu: Email: haagt@telekom.de
>> http://www.telekom.com
>>
>>
>> Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im =20
>> Auftrag von OOGHE Sven
>> Gesendet: Freitag, 17. Oktober 2008 11:23
>> An: ancp@ietf.org
>> Betreff: [ANCP] ANCP Framework update
>> Hi,
>>
>> I've been updating the ANCP framework draft according to the =20
>> suggested changes from Roberta and Francois. Below I have copy-=20
>> pasted the sections that have undergone changes. Indented text has =20=

>> been changed. I think I captured the essence of the notion of =20
>> "bandwidth delegation". Please review and see if this is capturing =20=

>> the agreements.
>>
>> Regards,
>> Sven
>>
>> 3.4.2.  Multicast Admission Control
>>
>>    The successful delivery of Triple Play Broadband services is =20
>> quickly
>>    becoming a big capacity planning challenge for most of the Service
>>    Providers nowadays.  Solely increasing available bandwidth is not
>>    always practical, cost-economical and/or sufficient to satisfy end
>>    user experience given not only the strict requirements of unicast
>>    delay sensitive applications like VoIP and Video, but also the =20
>> fast
>>    growth of multicast interactive applications such as
>>    videoconferencing, digital TV, digital audio, online movies and
>>    networked gaming.  These applications are typically =20
>> characterized by
>>    a delay sensitive nature, an extremely loss sensitive nature and
>>    intensive bandwidth requirements.  They are also typically "non-
>>    elastic", which means that they operate at a fixed bandwidth, that
>>    cannot be dynamically adjusted to the currently available =20
>> bandwidth.
>>
>>    Therefore a Connection Admission Control (CAC) mechanism covering
>>    admission of multicast traffic over the DSL Broadband access is
>>    required, in order to avoid oversubscribing the available =20
>> bandwidth
>>    and negatively impacting the end user experience.
>>
>>    Considering specifically admission control over the access line,
>>    before honoring a user request to join a new multicast flow, the
>>    combination of AN and NAS MUST ensure admission control is =20
>> performed
>>    to validate that there is enough "video" bandwidth remaining on =20=

>> the
>>    access line to carry the new flow (in addition to all other =20
>> existing
>>    multicast and unicast video traffic).  The solution needs to cope
>>    with multiple flows per access line and needs to allow access line
>>    bandwidth to be dynamically shared across multicast and unicast
>>    traffic (irrespective of whether unicast CAC is performed by NAS =20=

>> or
>>    by some off-path Policy Server).
>>
>>    Thus, supporting CAC for the access line requires some form of
>>    synchronization between the entity performing multicast CAC =20
>> (e.g. the
>>    NAS or the AN) and the entity performing unicast CAC (e.g. the =20
>> NAS or
>>    a Policy Server) and the entity actually enforcing the =20
>> multicast  [T.H.: Is that correct as stated "NAS or Policy =20
>> server"?; My understanding: Policy Server: Policy decission point; =20=

>> NAS controls AN by ANCP;AN: policy enforcement point]
>>    replication (i.e. the AN).  This synchronization can be achieved =20=

>> in a
>>    number of ways:
>>
>>    o  One approach is for the AN to query the NAS so that Admission
>>       Control for the access line is performed by the NAS (possibly =20=

>> with
>>       interactions with a Policy Server).  This can be done with or
>>       without "bandwidth delegation" to the AN.
>>
>>       *  In case of Admission Control without AN Bandwidth =20
>> Delegation,
>>          the AN can use ANCP to query the NAS, that in turn performs
>>          multicast Admission Control check for the new multicast flow
>>          and responds to the AN indicating whether the join is to be
>>          honored (and hence replication performed by the AN) or =20
>> denied.
>>          The NAS may locally maintain available "video" bandwidth  =20=

>> [T.H.:]  (net data rate) on the
>>          Access Loop, and perform video bandwidth accounting for the
>>          Access Loop.  Upon receiving an Admission Request from the =20=

>> AN,
>>          the NAS can check available "video" bandwidth before =20
>> admitting
>>          or denying the multicast flow.  In the process, the NAS may
>>          communicate with the Policy Server.  For unicast video =20
>> services
>>          such as Video on Demand (VoD), the NAS may also be queried =20=

>> (by
>>          a Policy Server or via on-path CAC signaling), so that it =20=

>> can
>>          perform admission control for the unicast flow, and update =20=

>> the
>>          available video bandwidth maintained by the NAS.
>>
>>       *  In case of Admission Control with AN Bandwidth Delegation, =20=

>> the
>>          NAS (possibly with interactions with a Policy Server) =20
>> manages
>>          total bandwidth for video admission, performs unicast =20
>> admission
>>          control and uses ANCP to delegate a certain amount of =20
>> bandwidth
>>          for some multicast flows to the Access Node.  In this =20
>> scenario,
>>          upon receiving a join to a multicast flow which matches an
>>          entry in the White or Grey List whose entry is flagged as
>>          "Bandwidth Delegation", the AN must perform the necessary
>>          bandwidth admission control check for the new multicast =20
>> flow,
>>          before starting the multicast flow replication.
>>
>>       The ANCP requirements to support this approach are specified in
>>       this document.
>>
>>    o  In case the subscriber communicates the "join/leave" =20
>> information
>>       with the NAS (e.g. by terminating all subscriber IGMP =20
>> signaling on
>>       the NAS, or by using some form of application level signaling),
>>       the approach is very similar.  In this case, the NAS may =20
>> locally
>>       maintain available "video" bandwidth on the Access Loop, =20
>> perform
>>       video bandwidth accounting, and perform CAC for unicast and
>>       multicast flows.  The NAS can set the replication state on =20
>> the AN
>>       using ANCP if the flow is admitted.  For unicast video services
>>       the NAS may be queried (by a policy server or via on-path CAC
>>       signaling) to perform admission control for the unicast flow, =20=

>> and
>>       update the available video bandwidth maintained by the NAS.  =20=

>> The
>>       ANCP requirements to support this approach (where the AN =20
>> queries
>>       the NAS) are specified in this document;
>>
>>    o  In a third approach, the Policy Server queries the AN =20
>> directly so
>>       that both unicast and multicast CAC for the access line are
>>       performed by the AN.  In this case, a subscriber request for a
>>       unicast flow (e.g. a Video on Demand session) will trigger a
>>       resource request message towards a Policy Server; the latter =20=

>> will
>>       then query the AN, that in turn will perform unicast CAC for =20=

>> the
>>       access line and respond, indicating whether the unicast =20
>> request is
>>       to be honored or denied.  In this scenario the Policy Server
>>       queries the AN directly, the approach doesn't require the use =20=

>> of
>>       ANCP.  It is therefore beyond the scope of this document.
>>
>> 4.2.  ANCP Multicast Requirements
>>
>>    o  The ANCP MUST support providing multicast conditional access
>>       information to Access Ports on an Access Node, using Black, =20
>> Grey
>>       and White lists.
>>
>>    o  The ANCP MUST support binding a particular Black, Grey and =20
>> White
>>       List to a given Access Port.
>>
>>    o  Upon receiving a join to a multicast flow which matches the =20
>> Grey
>>       List the ANCP MUST allow the AN to query the NAS to request an
>>       admission decision for replicating that multicast flow to a
>>       particular Access Port.
>>
>>    o  The ANCP MUST allow the NAS to send an admission decision to =20=

>> the
>>       AN indicating whether or not a multicast flow may be =20
>> replicated to
>>       a particular Access Port.
>>
>>    o  The ANCP must allow the NAS to indicate to the AN whether or =20=

>> not
>>       Admission Control is needed for some multicast flows on a given
>>       Access Port and where needed whether or not it is to be =20
>> performed
>>       with AN Bandwidth Delegation.
>>
>>    o  In case of Admission Control without AN Bandwidth Delegation, =20=

>> the
>>       ANCP must allow the NAS to reply to a query from the AN =20
>> indicating
>>       whether or not a multicast flow may be replicated to a =20
>> particular
>>       Access Port.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, the
>>       ANCP must allow the NAS to delegate a certain amount of =20
>> bandwidth
>>       to the AN for a given Access Port.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, the
>>       ANCP must allow the AN to query the NAS to request additional
>>       multicast bandwidth on a given Access Port.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, the
>>       ANCP must allow the NAS to query (or to instruct) the AN to =20
>> reduce
>>       the amount of bandwidth previously delegated on a given Access
>>       Port.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, the
>>       ANCP must allow the AN to autonomous release redundant =20
>> multicast
>>       bandwidth on a given Access Port.
>>
>>    o  The ANCP MUST allow the AN to send an Information Report =20
>> message
>>       to the NAS whenever replication of a multicast flow on a
>>       particular Access Port start or ends.
>>
>>    o  The ANCP MUST allow the AN to send an Information Report =20
>> message
>>       to the NAS indicating the multicast traffic volume that has =20
>> been
>>       replicated on that port.
>>
>>    o  The ANCP MUST allow the NAS to indicate to the AN whether or =20=

>> not
>>       multicast accounting is needed for a multicast flow on a
>>       particular Access Port.
>>
>>    o  In case multicast accounting is needed for a multicast flow =20
>> on a
>>       particular Access Port, the ANCP MUST allow the NAS to =20
>> indicate to
>>       the AN whether or not additional volume accounting =20
>> information is
>>       required.
>>
>>    o  The ANCP MUST allow the NAS to revoke a decision to replicate a
>>       multicast flow to a particular Access Port, which had been
>>       conveyed earlier to an AN.
>>
>>    o  The ANCP MUST support partial updates of the White, Grey and =20=

>> Black
>>       lists.
>>
>>    o  The ANCP MUST allow the NAS to query the AN to obtain =20
>> information
>>       on what multicast flows are currently being replicated on a =20
>> given
>>       Access Port, what Access Ports are currently receiving a given
>>       multicast flow, or what multicast flows are currently =20
>> replicated
>>       on each Access Port.
>>
>> Access Node multicast requirements (section 4.7.6)
>>
>>    o  The AN must deny any join to a multicast flow matching the =20
>> Black
>>       List for the relevant Access Port.
>>
>>    o  The AN must accept any join to a multicast flow matching the =20=

>> White
>>       List and not flagged as "Bandwidth Delegation" for the relevant
>>       Access Port.
>>
>>    o  Upon receiving a join to a multicast flow which matches the =20
>> White
>>       List whose entry is flagged as "Bandwidth Delegation" for the
>>       relevant Access Port, the AN must perform the necessary =20
>> bandwidth
>>       admission control check for the new flow before starting the
>>       multicast flow replication.
>>
>>    o  Upon receiving a join to a multicast flow which matches the =20
>> Grey
>>       List whose entry is flagged as "no Bandwidth Delegation" for =20=

>> the
>>       relevant Access Port, the AN must support using ANCP to query =20=

>> the
>>       NAS to receive a response indicating whether that join is to be
>>       honored or denied.  In this case, the NAS will perform both the
>>       necessary conditional access and the admission control checks =20=

>> for
>>       the new flow.
>>
>>    o  Upon receiving a join to a multicast flow which matches the =20
>> Grey
>>       List whose entry is flagged as "Bandwidth Delegation" for the
>>       relevant Access Port, the AN must first perform the necessary
>>       bandwidth admission control check for the new flow.  If
>>       successful, the AN must support using ANCP to query the NAS to
>>       receive a response indicating whether that join is to be =20
>> honored
>>       or denied.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, =20
>> the AN
>>       must support using ANCP to notify the NAS when the the user =20
>> leaves
>>       the multicast flow.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, =20
>> the AN
>>       must support using ANCP to query the NAS to request additional
>>       delegated multicast bandwidth on a given Access Port; the AN
>>       should be able to specify both the minimum and the preferred
>>       amount of additional multicast bandwidth requested.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>>       receiving a Bandwidth Delegation Request from the NAS =20
>> querying or
>>       instructing to decrease the delegated multicast bandwidth on a
>>       given Access Port, the AN must support using ANCP to send a
>>       Bandwidth Delegation Response indicating the new delegated
>>       multicast bandwidth.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, =20
>> the AN
>>       must support using ANCP to send a Bandwidth Release message =20
>> to the
>>       NAS in order to release unused delegated multicast bandwidth =20=

>> on a
>>       given Access Port.
>>
>>    o  If the requested multicast flow is not part of any list =20
>> associated
>>       with the Access Port, the AN must discard the message.
>>
>>    o  If the requested multicast flow is part of multiple lists
>>       associated with the Access Port, the AN must use the most =20
>> specific
>>       match.
>>
>>    o  If the requested multicast flow has the same most specific =20
>> match
>>       in multiple lists, the AN must give precedence to the Black =20
>> list,
>>       followed by the Grey list, and then the White list.
>>
>>    o  The AN must support configuring a "catch-all" statement in the
>>       Black, White or Grey list in order to enforce a default =20
>> behavior
>>       for a join to a multicast flow which doesn't match any other =20=

>> entry
>>       in a list for the relevant Access Port.
>>
>>    o  Upon querying the NAS, the AN must not propagate the join =20
>> message
>>       before the successful authorization from the NAS is received.
>>
>>    o  Upon receiving a leave for a multicast flow which matches the =20=

>> Grey
>>       List, the AN should be able to autonomously stop replication =20=

>> and
>>       advertise this event to the NAS.
>>
>>    o  The AN must support using ANCP to send an Information Report
>>       message to the NAS whenever replication starts or ends  =20
>> [T.H:] or fails .
>>
>>    o  The AN should support using ANCP to send an Information Report
>>       message to the NAS indicating the multicast traffic volume that
>>       has been replicated on that port.
>>
>>    o  Upon request by the NAS, the AN must support using ANCP to =20
>> send an
>>       Information Report message to the NAS, indicating what =20
>> multicast
>>       flows are currently being replicated on a given Access Port.
>>
>>    o  Upon request by the NAS, the AN must support using ANCP to =20
>> send an
>>       Information Report message to the NAS, indicating what Access
>>       Ports are currently receiving a given multicast flow.
>>
>>    o  Upon request by the NAS, the AN must support using ANCP to =20
>> send an
>>       Information Report message to the NAS, indicating what =20
>> multicast
>>       flows are currently being replicated on each Access Port.
>>
>>    o  Upon receiving an Admission Response from the NAS, indicating =20=

>> that
>>       replication of a multicast flow is to start or stop on a given
>>       access port of the AN, the AN must enforce this decision.  This
>>       decision must be taken irrespective of whether or not a
>>       corresponding Admission Request was issued by the AN earlier =20=

>> on.
>>
>> NAS multication requirements (section 4.8.6)
>>
>>    o  The NAS must support using ANCP to configure multicast =20
>> conditional
>>       access information to Access Ports on an Access Node, using =20
>> Black
>>       Lists, Grey Lists and White Lists.
>>
>>    o  The NAS must support using ANCP to indicate to the AN whether =20=

>> or
>>       not Admission Control is needed for some multicast flows on a
>>       given Access Port and where needed whether or not it is to be
>>       performed with AN Bandwidth Delegation.
>>
>>    o  Upon receiving a query from the AN for a request to replicate a
>>       multicast flow to a particular Access Port, and no AN Bandwidth
>>       Delegation is needed for that flow, the NAS must be able to
>>       perform the necessary checks (conditional access and/or =20
>> admission
>>       control) for the new flow.  The NAS must support using ANCP to
>>       reply to the AN indicating whether the request is to be =20
>> honored or
>>       denied.
>>
>>    o  Upon receiving a query from the AN for a request to replicate a
>>       multicast flow to a particular Access Port, and Admission =20
>> Control
>>       with AN Bandwidth Delegation is needed for that flow, the NAS =20=

>> must
>>       be able to perform the conditional access checks (if needed), =20=

>> and
>>       must support using ANCP to delegate a certain amount of =20
>> bandwidth
>>       to the AN for a given Access Port.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>>       receiving a Bandwidth Delegation Request from the AN =20
>> requesting to
>>       increase the delegated multicast bandwidth on a given Access =20=

>> Port,
>>       the NAS must support using ANCP to send a Bandwidth Delegation
>>       Response indicating the new delegating multicast bandwidth.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, =20
>> the NAS
>>       must support using ANCP to send a request the AN to decrease =20=

>> the
>>       amount of multicast bandwidth previously delegated on a given
>>       Access Port; the NAS should be able to specify both the minimum
>>       and the preferred amount decrement of multicast bandwidth
>>       requested.
>>
>>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>>       receiving an ANCP Bandwidth Release message, the NAS must be =20=

>> able
>>       to update accordingly its view of the multicast bandwidth
>>       delegated to the AN.
>>
>>    o  The NAS must support using ANCP to configure the Access Node =20=

>> with
>>       the "maximum number of multicast streams" allowed to be =20
>> received
>>       concurrently per Access Port.
>>
>>    o  The NAS must support using ANCP to incrementally add, remove =20=

>> and
>>       modify individual entries in White, Black and Grey lists.
>>
>>    o  The NAS must support using ANCP to indicate to the AN whether =20=

>> or
>>       not multicast accounting is needed for a multicast flow on a
>>       particular Access Port.
>>
>>    o  In case multicast accounting is needed for a multicast flow =20
>> on a
>>       particular Access Port, the NAS should support using ANCP to
>>       indicate to the AN whether or not additional volume accounting
>>       information is required.
>>
>>    o  The NAS must support using ANCP to query the AN to obtain
>>       information on what multicast flows are currently replicated =20=

>> on a
>>       given Access Port.
>>
>>    o  The NAS must support using ANCP to query the AN to obtain
>>       information on what Access Ports are currently receiving a =20
>> given
>>       multicast flow.
>>
>>    o  The NAS must support using ANCP to query the AN to obtain
>>       information on what multicast flows are currently replicated on
>>       each Access Port.
>>
>>    o  When Multicast replication occurs on the AN, the NAS must =20
>> support
>>       using ANCP to revoke the authorization to replicate a multicast
>>       flow to a particular Access Port.
>>
>>    o  The NAS should support using ANCP to indicate to the AN that
>>       replication of a multicast flow is to start or stop on a given
>>       access port of the AN, without having received a corresponding
>>       Admission Request from the AN earlier on.
>>
>> ---
>>
>> Sven Ooghe
>> Alcatel-Lucent
>> CTO Office, Access Division
>> Copernicuslaan 50, 2018 Antwerp, Belgium
>> tel.: +32 3 240 42 26
>> fax: +32 3 240 40 73
>>
>> This message (including any attachments) contains confidential =20
>> information intended for a specific individual and purpose, and is =20=

>> protected by law.  If you are not the intended recipient, you =20
>> should delete this message.  Any disclosure, copying, or =20
>> distribution of this message, or the taking of any action based on =20=

>> it, is strictly prohibited without the prior consent of its author.
>>
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp


--Apple-Mail-12--417379431
Content-Type: text/html;
	charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Fortune,<div><br></div><div>I =
don't think it is a good idea to refer to this entity as RACS =
because:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* as a general practise we don't =
want to depend on definition from external bodies<br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* i don't =
believe the RACS terminology is that well known in IETF =
community<br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* I&nbsp;would&nbsp;argue that in =
some scenarios some of the function performed by the NAS belong to the =
RACS functional entity (so that it is not correct to model the RACS as =
entirely outside the NAS)</div><div><br></div><div>As far as =
alternatives, perhaps we could use Policy Decision Point? that is an =
existing IETF concept and suggests that the entity makes admission =
decisions, some of which being bandwidth =
based.</div><div><br></div><div>In any case, the interactions with the =
Policy Server/Policy Decision Point/xxx &nbsp; are outside the scope of =
ANCP of course, so we only need to indicate that optional communication =
with an entity involved in the admission decision is =
possible.</div><div><br></div><div>Francois =
&nbsp;</div><div><br><div><div>On 24 Oct 2008, at 05:55, Fortune HUANG =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"> <div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: =
space; webkit-line-break: after-white-space"> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2">Hi all,</font></span></div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" size=3D"2">The name =
"PS/Policy Server" used in this draft is also kind of confusing to me in =
this draft.</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2">The entity descriped in this draft =
is actually an entity which manages (part of) the network =
bandwidth/resource and performs admission control for the unicast =
service. These functionalites are not quite clearly reflected by the =
name "Policy Server".</font></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" size=3D"2">Therefore, I =
suggest we find a better name for this entity.</font></span></div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2">My proposal&nbsp;is to replace the =
"PS/Policy Server" with "RACS / Resource and Admission Control =
Subsystem" which is defined in ETSI TISPAN.</font></span></div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" size=3D"2">I think =
the&nbsp;name "RACS"</font></span><span class=3D"157111503-24102008"><font=
 face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" size=3D"2">can&nbsp;reflect=
 the requirement for this entity precisely.</font></span></div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" =
size=3D"2"></font></span>&nbsp;</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2"></font></span>&nbsp;</div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"157111503-24102008"><font =
face=3D"=E5=AE=8B=E4=BD=93" color=3D"#0000ff" size=3D"2">Best =
Regards,</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=BD=93" =
color=3D"#0000ff" size=3D"2">Fortune</font></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"157111503-24102008"><font face=3D"=E5=AE=8B=E4=
=BD=93" color=3D"#0000ff" size=3D"2"></font></span><font =
face=3D"=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91" color=3D"black" =
size=3D"2"><br></font><font face=3D"=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91" =
color=3D"gray" size=3D"2">Huawei Technologies Co., Ltd. =
</font><span>&lt;outlook_huawei_logo_cn.jpg></span> </div><div><br =
class=3D"webkit-block-placeholder"></div><br><font face=3D"=E5=8D=8E=E6=96=
=87=E7=BB=86=E9=BB=91" color=3D"gray" size=3D"1">Addr: Section F, Huawei =
Industrial Base, Bantian Longgang, Shenzhen 518129, P.R. China<br>Tel: =
+86-755-28971871<br>Fax: +86-755-28972352<br>Mobile: =
+8615013838060<br>Email: <a =
href=3D"mailto:fqhuang@huawei.com">fqhuang@huawei.com</a><br><a =
href=3D"http://www.huawei.com">http://www.huawei.com</a><br></font><font =
face=3D"=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91" color=3D"gray" =
size=3D"1">---------------------------------------------------------------=
----------------------------------------------------------------------<br>=
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81<br>=E6=AD=A2=E4=
=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=BD=95=E5=BD=
=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=86=E4=B8=8D=
=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=E5=9C=B0=E6=
=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=95=A3=E5=8F=
=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD<br>=E7=9A=84=E4=BF=A1=E6=81=
=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=94=B6=E4=BA=86=E6=9C=AC=
=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=8B=E5=8D=B3=E7=94=B5=E8=
=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=E5=8F=91=E4=BB=B6=E4=BA=
=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=81<br></fo=
nt><font face=3D"Arial" color=3D"gray" size=3D"1">This e-mail and its =
attachments contain confidential information from HUAWEI, which <br>is =
intended only for the person or entity whose address is listed above. =
Any use of the <br>information contained herein in any way (including, =
but not limited to, total or partial <br>disclosure, reproduction, or =
dissemination) by persons other than the intended <br>recipient(s) is =
prohibited. If you receive this e-mail in error, please notify the =
sender by <br>phone or email immediately and delete it!<br></font> =
<div>&nbsp;</div><br> <div class=3D"OutlookMessageHeader" lang=3D"zh-cn" =
dir=3D"ltr" align=3D"left"> <hr tabindex=3D"-1"> <font face=3D"=E5=AE=8B=E4=
=BD=93" size=3D"2"><b>=E5=8F=91=E4=BB=B6=E4=BA=BA:</b> Tina TSOU [<a =
href=3D"mailto:tena@huawei.com">mailto:tena@huawei.com</a>] =
<br><b>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:</b> 2008=E5=B9=B410=E6=9C=882=
2=E6=97=A5 19:52<br><b>=E6=94=B6=E4=BB=B6=E4=BA=BA:</b> Haag, =
Thomas<br><b>=E6=8A=84=E9=80=81:</b> <a =
href=3D"mailto:sven.ooghe@alcatel-lucent.be">sven.ooghe@alcatel-lucent.be<=
/a>; <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br><b>=E4=B8=BB=E9=
=A2=98:</b> Re: [ANCP] ANCP Framework update<br></font><br></div> =
<div></div> <div>Hi all,</div> <div>I agree with Thomas' comments.</div> =
<div><br></div><br> <div apple-content-edited=3D"true"><span =
class=3D"Apple-style-span" style=3D"WORD-SPACING: 0px; FONT: 12px =
Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; =
WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; =
orphans: 2; widows: 2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0"> <div =
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px"> =
<div style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"> <div> <div>B. R.</div> =
<div>Tina</div> <div><br></div> <div><p>Messengers:</p><p>MSN: <a =
href=3D"mailto:tinatsou6@hotmail.com">tinatsou6@hotmail.com</a>&nbsp;&nbsp=
; Yahoo: tina_tsou&nbsp;&nbsp;&nbsp; Skype: tinaTSOU&nbsp;&nbsp;&nbsp; =
Jabber: <a =
href=3D"mailto:tina@jabber.org">tina@jabber.org</a>&nbsp;&nbsp;&nbsp; =
Google talk: <a =
href=3D"mailto:tinatsou6@gmail.com">tinatsou6@gmail.com</a></p><p>+86-755-=
28971872 (Office)&nbsp;&nbsp;&nbsp; =
+86-13922884380(Mobile)</p></div></div></div></span></div></span></div></s=
pan></div></span></div></span></div></span></div></span></div></span></div=
></span></div> <div><br></div><br> <div> <div>On Oct 22, 2008, at 6:42 =
PM, Haag, Thomas wrote:</div><br class=3D"Apple-interchange-newline"> =
<blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">  <div =
lang=3D"DE" link=3D"blue" vlink=3D"purple">  <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008">Hi Sven,</span></font></div>  <div =
dir=3D"ltr" align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"><span class=3D"734534408-22102008"></span></font>&nbsp;</div> =
 <div dir=3D"ltr" align=3D"left"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"><span class=3D"734534408-22102008">please see my comments =
inline.</span></font></div>  <div dir=3D"ltr" align=3D"left"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008"></span></font>&nbsp;</div>  <div dir=3D"ltr" =
align=3D"left"><font face=3D"Arial" color=3D"#0000ff" size=3D"2"><span =
class=3D"734534408-22102008"></span></font><b><span lang=3D"de"><font =
size=3D"2"><span =
class=3D"734534408-22102008">R</span>egards</font></span></b><span =
lang=3D"de"></span><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span =
lang=3D"de"><b><font size=3D"2">Thomas Haag</font></b></span><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span lang=3D"de"><font =
color=3D"#808080" size=3D"2">Deutsche Telekom AG<br>Zentrum Technik =
Einf=C3=BChrung<br>TE5-22,   Internationale =
Standardisierung<br>Heinrich-Hertz-Stra=C3=9Fe 3-7, 64295   =
Darmstadt<br>+49 6151 628-2088 (Tel.)<br>+49 521 9210-8411 (Fax)<br>+49 =
171 56   44 739 (Mobil)</font><b><br></b><font color=3D"#ff0000" =
size=3D"2">Neu:</font><span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#808080" =
size=3D"2">Email:</font><u><span =
class=3D"Apple-converted-space">&nbsp;</span><font color=3D"#0000ff" =
size=3D"2"><a style=3D"COLOR: blue; TEXT-DECORATION: underline" =
href=3D"mailto:haagt@telekom.de">haagt@telekom.de</a></font></u><font =
color=3D"#808080" size=3D"2"><br></font></span><a style=3D"COLOR: blue; =
TEXT-DECORATION: underline" href=3D"http://www.telekom.com/"><span =
lang=3D"de"><u></u><u><font color=3D"#0000ff" =
size=3D"2">http://www.telekom.com</font></u></span></a><span =
lang=3D"de"><font color=3D"#808080" size=3D"2"></font></span></div>  =
<div><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font>&nbsp;</div><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font><br>  <div class=3D"OutlookMessageHeader" lang=3D"de" =
dir=3D"ltr" align=3D"left"><font face=3D"Times New Roman" size=3D"3"><span=
 style=3D"FONT-SIZE: 12pt">  <hr tabindex=3D"-1" align=3D"center" =
width=3D"100%" size=3D"2">  </span></font></div>  <div class=3D"Section1">=
  <div>  <div style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; =
FONT-FAMILY: 'Times New Roman'"><b><font face=3D"Tahoma" size=3D"2"><span =
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">Von:</span></font></b><font face=3D"Tahoma" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a> [<a =
style=3D"COLOR: blue; TEXT-DECORATION: underline" =
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</a>]<sp=
an class=3D"Apple-converted-space">&nbsp;</span><b><span =
style=3D"FONT-WEIGHT: bold">Im   Auftrag von<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b>OOGHE   =
Sven<br><b><span style=3D"FONT-WEIGHT: bold">Gesendet:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>Freitag, 17. Oktober 2008   =
11:23<br><b><span style=3D"FONT-WEIGHT: bold">An:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span><a style=3D"COLOR: blue; =
TEXT-DECORATION: underline" =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br><b><span =
style=3D"FONT-WEIGHT: bold">Betreff:</span></b><span =
class=3D"Apple-converted-space">&nbsp;</span>[ANCP] ANCP Framework   =
update</span></font><o:p></o:p></div></div>  <div style=3D"FONT-SIZE: =
12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New Roman'"><font =
face=3D"Times New Roman" size=3D"3"><span style=3D"FONT-SIZE: =
12pt"><o:p></o:p></span></font></div><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">Hi,</span></font><o:p></o:p></p><p style=3D"FONT-SIZE:=
 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">I've been   updating the ANCP framework draft =
according to the suggested changes from   Roberta and Francois. Below I =
have copy-pasted the sections that have   undergone changes.<i><span =
style=3D"FONT-STYLE: italic"><span =
class=3D"Apple-converted-space">&nbsp;</span>Indented =
text</span></i><span class=3D"Apple-converted-space">&nbsp;</span>has =
been changed. I think I captured   the essence of the notion of =
"bandwidth delegation". Please review and see if   this is capturing the =
agreements.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">Regards,</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sven</span></font><o:p></o:p></p>  <div style=3D"FONT-SIZE: 12pt; =
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New Roman'"><font face=3D"Times =
New Roman" size=3D"3"><span style=3D"FONT-SIZE: =
12pt"><o:p></o:p></span></font></div><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><b><font face=3D"Arial" size=3D"2"><span style=3D"FONT-WEIGHT: =
bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">3.4.2.&nbsp;   Multicast =
Admission Control</span></font></b><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; The successful   delivery of Triple =
Play Broadband services is quickly</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; becoming a big   capacity planning challenge for =
most of the Service</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; Providers   nowadays.&nbsp; Solely increasing =
available bandwidth is   not</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; always practical,   cost-economical and/or =
sufficient to satisfy end</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; user experience given   not only the strict =
requirements of unicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; delay sensitive   applications like VoIP and Video, =
but also the fast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; growth of multicast   interactive applications such =
as</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; videoconferencing,   digital TV, digital audio, =
online movies and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; networked   gaming.&nbsp; These applications are =
typically characterized   by</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; a delay sensitive   nature, an extremely loss =
sensitive nature and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; intensive bandwidth   requirements.&nbsp; They are =
also typically "non-</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; elastic", which means   that they operate at a fixed =
bandwidth, that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; cannot be dynamically   adjusted to the currently =
available bandwidth.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; Therefore a   Connection Admission =
Control (CAC) mechanism covering</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; admission of   multicast traffic over the DSL =
Broadband access is</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; required, in order to   avoid oversubscribing the =
available bandwidth</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; and negatively   impacting the end user =
experience.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; Considering   specifically admission =
control over the access line,</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; before honoring a   user request to join a new =
multicast flow, the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; combination of AN and   NAS MUST ensure admission =
control is performed</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; to validate that   there is enough "video" bandwidth =
remaining on the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; access line to carry   the new flow (in addition to =
all other existing</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; multicast and unicast   video traffic).&nbsp; The =
solution needs to cope</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; with multiple flows   per access line and needs to =
allow access line</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; bandwidth to be   dynamically shared across =
multicast and unicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; traffic (irrespective   of whether unicast CAC is =
performed by NAS or</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; by some off-path   Policy =
Server).</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; Thus, supporting CAC   for the access =
line requires some form of</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; synchronization   between the entity performing =
multicast CAC (e.g. the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; NAS or the AN) and   the entity performing unicast =
CAC (e.g. the NAS or</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span style=3D"FONT-SIZE:=
 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; a Policy Server) and   the =
entity actually enforcing the multicast<span =
class=3D"734534408-22102008"><font color=3D"#0000ff">&nbsp; [T.H.: Is =
that correct as   stated "NAS or Policy server"?; My understanding: =
Policy Server:   Policy&nbsp;decission point;&nbsp;NAS controls =
AN&nbsp;by ANCP;AN: policy   enforcement =
point]&nbsp;</font></span></span>&nbsp;<br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;   replication (i.e. the AN).&nbsp; This =
synchronization can be achieved in   a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp; number of   ways:</span></font><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><i><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;   o&nbsp; One approach is for the AN to query the =
NAS so that   Admission</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Control for the =
access line is performed by the NAS (possibly   =
with</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   interactions with a =
Policy Server).&nbsp; This can be done with   or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   without "bandwidth =
delegation" to the AN.</span></font></i><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><i><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   *&nbsp; In case of Admission =
Control without AN Bandwidth   Delegation,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
the AN can use ANCP to query the NAS, that in turn   =
performs</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
multicast Admission Control check for the new multicast   =
flow</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
and responds to the AN indicating whether the join is to   =
be</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
honored (and hence replication performed by the AN) or   =
denied.</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span style=3D"FONT-SIZE:=
 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   The NAS may =
locally maintain available "video" bandwidth&nbsp;<font =
color=3D"#0000ff"><span =
class=3D"734534408-22102008">&nbsp;[T.H.:]&nbsp;</span><span =
class=3D"734534408-22102008">&nbsp;(net data rate)&nbsp;</span></font>on =
  the</span><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
Access Loop, and perform video bandwidth accounting for   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
Access Loop.&nbsp; Upon receiving an Admission Request from the   =
AN,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
the NAS can check available "video" bandwidth before   =
admitting</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
or denying the multicast flow.&nbsp; In the process, the NAS   =
may</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
communicate with the Policy Server.&nbsp; For unicast video   =
services</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
such as Video on Demand (VoD), the NAS may also be queried   =
(by</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   a =
Policy Server or via on-path CAC signaling), so that it   =
can</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
perform admission control for the unicast flow, and update   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
available video bandwidth maintained by the   =
NAS.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   *&nbsp; In case of Admission =
Control with AN Bandwidth Delegation,   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
NAS (possibly with interactions with a Policy Server)   =
manages</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
total bandwidth for video admission, performs unicast   =
admission</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
control and uses ANCP to delegate a certain amount of   =
bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
for some multicast flows to the Access Node.&nbsp; In this   =
scenario,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
upon receiving a join to a multicast flow which matches   =
an</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
entry in the White or Grey List whose entry is flagged   =
as</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
"Bandwidth Delegation", the AN must perform the   =
necessary</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
bandwidth admission control check for the new multicast   =
flow,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
before starting the multicast flow   =
replication.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   The ANCP requirements to support =
this approach are specified   in</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   this =
document.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In case the   subscriber =
communicates the "join/leave" information</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   with the NAS (e.g. by =
terminating all subscriber IGMP signaling   on</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the   NAS, or by using some form =
of application level signaling),</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the   approach is very =
similar.&nbsp; In this case, the NAS may   locally</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   maintain available "video" =
bandwidth on the Access Loop,   perform</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   video bandwidth accounting, and =
perform CAC for unicast and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast flows.&nbsp; The NAS =
can set the replication state on the   AN</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   using ANCP if the flow is =
admitted.&nbsp; For unicast video   services</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the   NAS may be queried (by a =
policy server or via on-path CAC</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   signaling) to perform admission =
control for the unicast flow,   and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   update the available video =
bandwidth maintained by the NAS.&nbsp;   The</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP requirements to support =
this approach (where the AN   queries</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the   NAS) are specified in this =
document;</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In a third   approach, the =
Policy Server queries the AN directly so</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   that both unicast and multicast =
CAC for the access line are</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   performed by the AN.&nbsp; In =
this case, a subscriber request for   a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   unicast flow (e.g. a Video on =
Demand session) will trigger   a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   resource request message towards =
a Policy Server; the latter   will</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   then query the AN, that in turn =
will perform unicast CAC for   the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   access line and respond, =
indicating whether the unicast request   is</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to   be honored or denied.&nbsp; =
In this scenario the Policy   Server</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   queries the AN directly, the =
approach doesn't require the use   of</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP.&nbsp; It is therefore =
beyond the scope of this   document.</span></font><o:p></o:p></p>  <div =
style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Times New Roman" size=3D"3"><span =
style=3D"FONT-SIZE: 12pt"><o:p></o:p></span></font></div><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><b><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">4.2.&nbsp; ANCP   Multicast =
Requirements</span></font></b><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   support =
providing multicast conditional access</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   information to Access Ports on =
an Access Node, using Black,   Grey</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and   White =
lists.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   support binding =
a particular Black, Grey and White</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List to a given Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon   receiving a join to a =
multicast flow which matches the Grey</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List the ANCP MUST allow the AN =
to query the NAS to request   an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   admission decision for =
replicating that multicast flow to a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   allow the NAS =
to send an admission decision to the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AN   indicating whether or not a =
multicast flow may be replicated   to</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a   particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; The =
ANCP must allow the NAS to indicate to the AN whether or   =
not</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Admission Control =
is needed for some multicast flows on a   given</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Access Port and =
where needed whether or not it is to be   =
performed</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   with AN Bandwidth =
Delegation.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control without AN Bandwidth Delegation,   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP must allow the =
NAS to reply to a query from the AN   indicating</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   whether or not a =
multicast flow may be replicated to a   =
particular</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Access =
Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation,   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP must allow the =
NAS to delegate a certain amount of   bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   to the AN for a =
given Access Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation,   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP must allow the =
AN to query the NAS to request   additional</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast bandwidth =
on a given Access Port.</span></font></i><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><i><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;   o&nbsp; In case of Admission Control with AN =
Bandwidth Delegation,   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP must allow the =
NAS to query (or to instruct) the AN to   reduce</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   the amount of =
bandwidth previously delegated on a given   =
Access</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation,   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   ANCP must allow the =
AN to autonomous release redundant   multicast</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   bandwidth on a =
given Access Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   allow the AN to =
send an Information Report message</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to   the NAS whenever replication =
of a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   particular Access Port start or =
ends.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   allow the AN to =
send an Information Report message</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to   the NAS indicating the =
multicast traffic volume that has   been</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   replicated on that =
port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   allow the NAS =
to indicate to the AN whether or not</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast accounting is needed =
for a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In case   multicast accounting =
is needed for a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   particular Access Port, the ANCP =
MUST allow the NAS to indicate   to</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the   AN whether or not additional =
volume accounting information   is</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
required.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   allow the NAS =
to revoke a decision to replicate a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast flow to a particular =
Access Port, which had been</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   conveyed earlier to an =
AN.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   support partial =
updates of the White, Grey and Black</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
lists.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The ANCP MUST   allow the NAS =
to query the AN to obtain information</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on   what multicast flows are =
currently being replicated on a   given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Access Port, what Access Ports =
are currently receiving a   given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast flow, or what =
multicast flows are currently   replicated</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on   each Access =
Port.</span></font><o:p></o:p></p>  <div style=3D"FONT-SIZE: 12pt; =
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New Roman'"><font face=3D"Times =
New Roman" size=3D"3"><span style=3D"FONT-SIZE: =
12pt"><o:p></o:p></span></font></div><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><b><font face=3D"Arial" size=3D"2"><span style=3D"FONT-WEIGHT: =
bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">Access Node   multicast =
requirements (section 4.7.6)</span></font></b><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
AN must   deny any join to a multicast flow matching the =
Black</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List for the relevant Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; The =
AN must accept any join to a multicast flow matching the   =
White</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List and not =
flagged as "Bandwidth Delegation" for the   =
relevant</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Access =
Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; =
Upon receiving a join to a multicast flow which matches the   =
White</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List whose entry is =
flagged as "Bandwidth Delegation" for   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   relevant Access =
Port, the AN must perform the necessary   =
bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   admission control =
check for the new flow before starting   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast flow =
replication.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; =
Upon receiving a join to a multicast flow which matches the   =
Grey</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List whose entry is =
flagged as "no Bandwidth Delegation" for   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   relevant Access =
Port, the AN must support using ANCP to query   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   NAS to receive a =
response indicating whether that join is to   be</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   honored or =
denied.&nbsp; In this case, the NAS will perform both   =
the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   necessary =
conditional access and the admission control checks   =
for</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   the new =
flow.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; =
Upon receiving a join to a multicast flow which matches the   =
Grey</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List whose entry is =
flagged as "Bandwidth Delegation" for   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   relevant Access =
Port, the AN must first perform the   necessary</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   bandwidth admission =
control check for the new flow.&nbsp;   If</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   successful, the AN =
must support using ANCP to query the NAS   to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   receive a response =
indicating whether that join is to be   honored</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   or =
denied.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation, the   =
AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   must support using =
ANCP to notify the NAS when the the user   leaves</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   the multicast =
flow.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation, the   =
AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   must support using =
ANCP to query the NAS to request   additional</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   delegated multicast =
bandwidth on a given Access Port; the   AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   should be able to =
specify both the minimum and the   preferred</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   amount of =
additional multicast bandwidth   =
requested.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation,   =
upon</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   receiving a =
Bandwidth Delegation Request from the NAS querying   =
or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   instructing to =
decrease the delegated multicast bandwidth on   a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   given Access Port, =
the AN must support using ANCP to send   a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Bandwidth =
Delegation Response indicating the new   =
delegated</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast =
bandwidth.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation, the   =
AN</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   must support using =
ANCP to send a Bandwidth Release message to   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   NAS in order to =
release unused delegated multicast bandwidth on   =
a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   given Access =
Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If the   requested multicast =
flow is not part of any list associated</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   with the Access Port, the AN =
must discard the   message.</span></font><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If =
the   requested multicast flow is part of multiple =
lists</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   associated with the Access Port, =
the AN must use the most   specific</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
match.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; If the   requested multicast =
flow has the same most specific match</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in   multiple lists, the AN must =
give precedence to the Black   list,</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   followed by the Grey list, and =
then the White   list.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The AN must   support =
configuring a "catch-all" statement in the</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Black, White or Grey list in =
order to enforce a default   behavior</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for   a join to a multicast flow =
which doesn't match any other   entry</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in   a list for the relevant =
Access Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon querying   the NAS, the AN =
must not propagate the join message</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   before the successful =
authorization from the NAS is   received.</span></font><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon  =
 receiving a leave for a multicast flow which matches the   =
Grey</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   List, the AN should be able to =
autonomously stop replication   and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   advertise this event to the =
NAS.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The AN must   support using =
ANCP to send an Information Report</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><span style=3D"FONT-SIZE:=
 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   message to =
the NAS whenever replication starts or ends<span =
class=3D"734534408-22102008"><font color=3D"#0000ff">&nbsp; [T.H:] or   =
fails&nbsp;</font></span>.</span><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The AN should   support using =
ANCP to send an Information Report</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   message to the NAS indicating =
the multicast traffic volume   that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has   been replicated on that =
port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon request   by the NAS, the =
AN must support using ANCP to send an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Information Report message to =
the NAS, indicating what   multicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   flows are currently being =
replicated on a given Access   Port.</span></font><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon =
request   by the NAS, the AN must support using ANCP to send =
an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Information Report message to =
the NAS, indicating what   Access</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Ports are currently receiving a =
given multicast   flow.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE:=
 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon request   by the NAS, the =
AN must support using ANCP to send an</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Information Report message to =
the NAS, indicating what   multicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   flows are currently being =
replicated on each Access   Port.</span></font><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; Upon  =
 receiving an Admission Response from the NAS, indicating   =
that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   replication of a multicast flow =
is to start or stop on a   given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   access port of the AN, the AN =
must enforce this decision.&nbsp;   This</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   decision must be taken =
irrespective of whether or not a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   corresponding Admission Request =
was issued by the AN earlier   on.</span></font><o:p></o:p></p>  <div =
style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Times New Roman" size=3D"3"><span =
style=3D"FONT-SIZE: 12pt"><o:p></o:p></span></font></div><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><b><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">NAS =
multication   requirements (section =
4.8.6)</span></font></b><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS must   support using =
ANCP to configure multicast conditional</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   access information to Access =
Ports on an Access Node, using   Black</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Lists, Grey Lists and White =
Lists.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; The =
NAS must support using ANCP to indicate to the AN whether   =
or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   not Admission =
Control is needed for some multicast flows on   a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   given Access Port =
and where needed whether or not it is to   be</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   performed with AN =
Bandwidth Delegation.</span></font></i><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><i><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;   o&nbsp; Upon receiving a query from the AN for a =
request to replicate   a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast flow to a =
particular Access Port, and no AN   Bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Delegation is =
needed for that flow, the NAS must be able   to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   perform the =
necessary checks (conditional access and/or   =
admission</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   control) for the =
new flow.&nbsp; The NAS must support using ANCP   =
to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   reply to the AN =
indicating whether the request is to be honored   =
or</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
denied.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; =
Upon receiving a query from the AN for a request to replicate   =
a</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast flow to a =
particular Access Port, and Admission   Control</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   with AN Bandwidth =
Delegation is needed for that flow, the NAS   =
must</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   be able to perform =
the conditional access checks (if needed),   and</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   must support using =
ANCP to delegate a certain amount of   bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   to the AN for a =
given Access Port.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: =
12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation,   =
upon</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   receiving a =
Bandwidth Delegation Request from the AN requesting   =
to</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   increase the =
delegated multicast bandwidth on a given Access   =
Port,</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   the NAS must =
support using ANCP to send a Bandwidth   =
Delegation</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Response indicating =
the new delegating multicast   =
bandwidth.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation, the   =
NAS</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   must support using =
ANCP to send a request the AN to decrease   the</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   amount of multicast =
bandwidth previously delegated on a   given</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Access Port; the =
NAS should be able to specify both the   minimum</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   and the preferred =
amount decrement of multicast   bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   =
requested.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><i><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: =
10pt; FONT-STYLE: italic; FONT-FAMILY: Arial">&nbsp;&nbsp;   o&nbsp; In =
case of Admission Control with AN Bandwidth Delegation,   =
upon</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   receiving an ANCP =
Bandwidth Release message, the NAS must be   able</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   to update =
accordingly its view of the multicast   bandwidth</span></font></i><span =
class=3D"Apple-converted-space">&nbsp;</span><br><i><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   delegated to the =
AN.</span></font></i><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS must   support using =
ANCP to configure the Access Node with</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the   "maximum number of multicast =
streams" allowed to be   received</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   concurrently per Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS must   support using =
ANCP to incrementally add, remove and</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   modify individual entries in =
White, Black and Grey   lists.</span></font><o:p></o:p></p><p =
style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><font face=3D"Arial" size=3D"2"><span =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The =
NAS must   support using ANCP to indicate to the AN whether =
or</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not   multicast accounting is =
needed for a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; In case   multicast accounting =
is needed for a multicast flow on a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   particular Access Port, the NAS =
should support using ANCP   to</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   indicate to the AN whether or =
not additional volume   accounting</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   information is =
required.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS must   support using =
ANCP to query the AN to obtain</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   information on what multicast =
flows are currently replicated on   a</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   given Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS must   support using =
ANCP to query the AN to obtain</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   information on what Access Ports =
are currently receiving a   given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   multicast =
flow.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS must   support using =
ANCP to query the AN to obtain</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   information on what multicast =
flows are currently replicated   on</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   each Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; When   Multicast replication =
occurs on the AN, the NAS must   support</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   using ANCP to revoke the =
authorization to replicate a   multicast</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   flow to a particular Access =
Port.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; The NAS   should support using =
ANCP to indicate to the AN that</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   replication of a multicast flow =
is to start or stop on a   given</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   access port of the AN, without =
having received a   corresponding</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;   Admission Request from the AN =
earlier on.</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">---</span></font><o:p></o:p></p><p style=3D"FONT-SIZE:=
 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">Sven   Ooghe</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Alcatel-Lucent</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">CTO =
Office, Access   Division</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Copernicuslaan 50, 2018 Antwerp,   Belgium</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">tel.: +32 =
  3 240 42 26</span></font><span =
class=3D"Apple-converted-space">&nbsp;</span><br><font face=3D"Arial" =
size=3D"2"><span style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">fax: +32 =
3 240 40   73</span></font><o:p></o:p></p><p style=3D"FONT-SIZE: 12pt; =
MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: 'Times New =
Roman'"><font face=3D"Arial" size=3D"2"><span style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">This   message (including any attachments) contains =
confidential information intended   for a specific individual and =
purpose, and is protected by law.&nbsp; If you   are not the intended =
recipient, you should delete this message.&nbsp; Any   disclosure, =
copying, or distribution of this message, or the taking of any   action =
based on it, is strictly prohibited without the prior consent of its   =
author.</span></font><o:p></o:p></p></div>________________________________=
_______________<br>ANCP   mailing list<br><a style=3D"COLOR: blue; =
TEXT-DECORATION: underline" =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br><a style=3D"COLOR: =
blue; TEXT-DECORATION: underline" =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><br></div></span></blockquote></div><br></div> =
_______________________________________________<br>ANCP mailing =
list<br><a =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/ancp<br></blockquote></div><br></div></body></html>=

--Apple-Mail-12--417379431--

--===============1045365453==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1045365453==--


From ancp-bounces@ietf.org  Fri Oct 24 05:36:45 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75DD33A6ADD;
	Fri, 24 Oct 2008 05:36:45 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AC763A6ADB
	for <ancp@core3.amsl.com>; Fri, 24 Oct 2008 05:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.485
X-Spam-Level: 
X-Spam-Status: No, score=-6.485 tagged_above=-999 required=5 tests=[AWL=0.114, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 72LlWc8bAdCf for <ancp@core3.amsl.com>;
	Fri, 24 Oct 2008 05:36:43 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id B02F13A6A58
	for <ancp@ietf.org>; Fri, 24 Oct 2008 05:36:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="23639213"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 24 Oct 2008 12:37:34 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OCbYpm008824; 
	Fri, 24 Oct 2008 14:37:34 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9OCbT0i004623;
	Fri, 24 Oct 2008 12:37:34 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 14:37:29 +0200
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 14:37:29 +0200
Message-Id: <F1A3BB47-00BC-4511-83B9-D2103D452EA7@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A2033DE77582@GRFMBX702RM001.griffon.local>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 14:37:27 +0200
References: <A1F769BC58A8B146B2EEA818EAE052A2033DE77582@GRFMBX702RM001.griffon.local>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 24 Oct 2008 12:37:29.0146 (UTC)
	FILETIME=[46F3D1A0:01C935D5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3158; t=1224851854;
	x=1225715854; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com> |Subject:=20Re=3A=20[ANCP]=20Result=20field |Sender:=20;
	bh=PG67/6R7xU7si3sAftvqCD6SmoNGJ/DljIuI5TNP1gQ=;
	b=m14NBcDfOhMk3rkxsESYUpVNgsGRGtK8vZ2reX9rNcAesHpQzwBJ8kl62e
	mv0OIQGRE1Gj5VkRKfyk8MJ86hHhrqlwk+yLJOMHqeeY9oKr4jXFUSnovhJ+
	0HKpDoxKfk;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Result field
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Roberta and all,

On 24 Oct 2008, at 08:12, Maglione Roberta wrote:

> Hello,
>        I am currently updating the ancp-protocol draft and I would  
> like to incorporate the topics recently discussed in this alias. In  
> particular a couple of weeks ago we talked about the use of Result  
> Field in ANCP messages in order to try to rationalize the codes for  
> this field, coming from GSMP, and actually useful for ANCP protocol.
> http://www.ietf.org/mail-archive/web/ancp/current/msg00661.html
>
> According to this thread the useful codes for Result field in ANCP  
> use cases seem to be:
> "AckAll": (always send a response) used in OAM use case;
> "NAck": (generate a response only in case of an error condition) for  
> Multicast use case;
> 0 used in Topology Discover use case.
>
> The value 0 for Result field is not defined in GSMP RFC, but it is  
> actually used in one of the ANCP use case. In order to guarantee  
> backward compatibility with current implementations it's reasonable  
> to keep the code 0 for Result field, the proposal on previous email  
> thread was to define in ANCP protocol draft  a semantic for Result =  
> 0x00.
>
> The proposed semantic was Result = 0x00 meaning "No Response  
> required".

Can we generalize the semantics of Result = 0x00 to "Ignore this field  
on receipt and follow the procedures specified for the received  
message type"?

In the case of the Topology Discovery use case, you could specify that  
the receiver of a Port_UP message is never to respond to that message  
(assuming this is what you want). In that case, Result = 0x00 would  
effectively mean "no response", which would match the current  
implementation behaviors you're targeting.

In other use cases, Result=0x00 could also be used and the behavior on  
receipt of another message type would also be defined in the  
procedures for that message. In some cases, the responder behavior  
could be a little more subtle (e.g. respond with message X in such  
situation, respond with message Y in that situation, and don't respond  
at all in such situations ).

Francois

PS: one question: I assume the Result = "Failure" value is not  
affected by this discussion (ie it remains valid e.g. in Multicast  
Status message). right?


>
>
> Please let me know if this semantic for Result field is ok for you  
> or you have any additional comment on this proposal.
> Thanks
> Best Regards,
> Roberta
>
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons  
> above and may contain confidential information. If you have received  
> the message in error, be informed that any use of the content hereof  
> is prohibited. Please return it immediately to the sender and delete  
> the message. Should you have any questions, please contact us by  
> replying to webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Fri Oct 24 06:40:32 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F7D53A6B1F;
	Fri, 24 Oct 2008 06:40:32 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27C373A6B0C
	for <ancp@core3.amsl.com>; Fri, 24 Oct 2008 06:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_IT=0.635,
	HOST_EQ_IT=1.245]
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 V21UAnLeqtXV for <ancp@core3.amsl.com>;
	Fri, 24 Oct 2008 06:40:30 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it
	(grfedg701rm001.telecomitalia.it [217.169.121.20])
	by core3.amsl.com (Postfix) with ESMTP id B5F233A6B11
	for <ancp@ietf.org>; Fri, 24 Oct 2008 06:40:29 -0700 (PDT)
Received: from GRFHUB705RM001.griffon.local (10.19.3.69) by
	GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP
	Server (TLS) id 8.1.291.1; Fri, 24 Oct 2008 15:43:50 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by
	GRFHUB705RM001.griffon.local ([10.19.9.238]) with mapi; Fri, 24 Oct 2008
	15:39:31 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Francois Le Faucheur IMAP' <flefauch@cisco.com>
Date: Fri, 24 Oct 2008 15:39:31 +0200
Thread-Topic: [ANCP] Result field
Thread-Index: Ack11VfBb3N+8/z3S9+y9graJll3/wABofgg
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2033DAE7A4D@GRFMBX702RM001.griffon.local>
References: <A1F769BC58A8B146B2EEA818EAE052A2033DE77582@GRFMBX702RM001.griffon.local>
	<F1A3BB47-00BC-4511-83B9-D2103D452EA7@cisco.com>
In-Reply-To: <F1A3BB47-00BC-4511-83B9-D2103D452EA7@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Result field
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hello Francois,

> Can we generalize the semantics of Result = 0x00 to "Ignore this field
> on receipt and follow the procedures specified for the received
> message type"?

The semantic you are proposing looks good to me: it is inline with current behavior for Port Up message, thus it guarantees backward compatibility with existing implementations and at the same time it allows for a more flexible behavior in other use cases.

Anybody disagree with this proposal?

> PS: one question: I assume the Result = "Failure" value is not
>affected by this discussion (ie it remains valid e.g. in Multicast
> Status message). right?
That's correct, no impact on Result = "Failure" value.

Regards,
Roberta

-----Original Message-----
From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
Sent: Friday, October 24, 2008 2:37 PM
To: Maglione Roberta
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] Result field

Roberta and all,

On 24 Oct 2008, at 08:12, Maglione Roberta wrote:

> Hello,
>        I am currently updating the ancp-protocol draft and I would
> like to incorporate the topics recently discussed in this alias. In
> particular a couple of weeks ago we talked about the use of Result
> Field in ANCP messages in order to try to rationalize the codes for
> this field, coming from GSMP, and actually useful for ANCP protocol.
> http://www.ietf.org/mail-archive/web/ancp/current/msg00661.html
>
> According to this thread the useful codes for Result field in ANCP
> use cases seem to be:
> "AckAll": (always send a response) used in OAM use case;
> "NAck": (generate a response only in case of an error condition) for
> Multicast use case;
> 0 used in Topology Discover use case.
>
> The value 0 for Result field is not defined in GSMP RFC, but it is
> actually used in one of the ANCP use case. In order to guarantee
> backward compatibility with current implementations it's reasonable
> to keep the code 0 for Result field, the proposal on previous email
> thread was to define in ANCP protocol draft  a semantic for Result =
> 0x00.
>
> The proposed semantic was Result = 0x00 meaning "No Response
> required".

Can we generalize the semantics of Result = 0x00 to "Ignore this field
on receipt and follow the procedures specified for the received
message type"?

In the case of the Topology Discovery use case, you could specify that
the receiver of a Port_UP message is never to respond to that message
(assuming this is what you want). In that case, Result = 0x00 would
effectively mean "no response", which would match the current
implementation behaviors you're targeting.

In other use cases, Result=0x00 could also be used and the behavior on
receipt of another message type would also be defined in the
procedures for that message. In some cases, the responder behavior
could be a little more subtle (e.g. respond with message X in such
situation, respond with message Y in that situation, and don't respond
at all in such situations ).

Francois

PS: one question: I assume the Result = "Failure" value is not
affected by this discussion (ie it remains valid e.g. in Multicast
Status message). right?


>
>
> Please let me know if this semantic for Result field is ok for you
> or you have any additional comment on this proposal.
> Thanks
> Best Regards,
> Roberta
>
>
> CONFIDENTIALITY NOTICE
>
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please contact us by
> replying to webmaster@telecomitalia.it.
>
>        Thank you
>
>                                        www.telecomitalia.it
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp



CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Fri Oct 24 06:40:57 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A23713A6B32;
	Fri, 24 Oct 2008 06:40:57 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DCEAD28C0F4
	for <ancp@core3.amsl.com>; Fri, 24 Oct 2008 06:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 T2u+lowNlPWJ for <ancp@core3.amsl.com>;
	Fri, 24 Oct 2008 06:40:54 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 5B6153A6B2B
	for <ancp@ietf.org>; Fri, 24 Oct 2008 06:40:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="23648366"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 24 Oct 2008 13:42:07 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9ODg7Fp030957; 
	Fri, 24 Oct 2008 15:42:07 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9ODg449026833;
	Fri, 24 Oct 2008 13:42:07 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 15:42:06 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 24 Oct 2008 15:40:32 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405E37313@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <F1A3BB47-00BC-4511-83B9-D2103D452EA7@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Result field
Thread-Index: Ack11WL+RB64XIKzTu2CzfEyF2NilgAB4RvA
References: <A1F769BC58A8B146B2EEA818EAE052A2033DE77582@GRFMBX702RM001.griffon.local>
	<F1A3BB47-00BC-4511-83B9-D2103D452EA7@cisco.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
	"Maglione Roberta" <roberta.maglione@telecomitalia.it>
X-OriginalArrivalTime: 24 Oct 2008 13:42:06.0102 (UTC)
	FILETIME=[4DCC5B60:01C935DE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4300; t=1224855727;
	x=1225719727; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Result=20field |Sender:=20;
	bh=/fIgi+EGLAWCirg5dlhYs2wQvaMN/PB9DRh8YYZgI3w=;
	b=eBYrvhyKoUyLxV5LBUZ3eJZ0bFpKbuUFilVKIzjEfI+/Fm2eTZ54yn+Get
	tt/tBhPS/UeX+LoiaXxKlUZ831ljSNUZ8/fdKrfmT+xsReBLD8UZdo51d5b8
	tNGEOXDc3t;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] Result field
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

 

> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On 
> Behalf Of Francois Le Faucheur (flefauch)
> Sent: 24 October 2008 14:37
> To: Maglione Roberta
> Cc: ancp@ietf.org
> Subject: Re: [ANCP] Result field
> 
> Roberta and all,
> 
> On 24 Oct 2008, at 08:12, Maglione Roberta wrote:
> 
> > Hello,
> >        I am currently updating the ancp-protocol draft and I would 
> > like to incorporate the topics recently discussed in this alias. In 
> > particular a couple of weeks ago we talked about the use of Result 
> > Field in ANCP messages in order to try to rationalize the codes for 
> > this field, coming from GSMP, and actually useful for ANCP protocol.
> > http://www.ietf.org/mail-archive/web/ancp/current/msg00661.html
> >
> > According to this thread the useful codes for Result field 
> in ANCP use 
> > cases seem to be:
> > "AckAll": (always send a response) used in OAM use case;
> > "NAck": (generate a response only in case of an error 
> condition) for 
> > Multicast use case; 0 used in Topology Discover use case.
> >
> > The value 0 for Result field is not defined in GSMP RFC, but it is 
> > actually used in one of the ANCP use case. In order to guarantee 
> > backward compatibility with current implementations it's 
> reasonable to 
> > keep the code 0 for Result field, the proposal on previous email 
> > thread was to define in ANCP protocol draft  a semantic for 
> Result = 
> > 0x00.
> >
> > The proposed semantic was Result = 0x00 meaning "No Response 
> > required".
> 
> Can we generalize the semantics of Result = 0x00 to "Ignore 
> this field on receipt and follow the procedures specified for 
> the received message type"?

This is a fine proposal indeed.

> 
> In the case of the Topology Discovery use case, you could 
> specify that the receiver of a Port_UP message is never to 
> respond to that message (assuming this is what you want). In 
> that case, Result = 0x00 would effectively mean "no 
> response", which would match the current implementation 
> behaviors you're targeting.

 While there is no "Port-up reply" message defined, an overall gap in
the protocol and initial implementations is the inability to communicate
protocol errors. Hence it would not be wise to preculde such an "error
message" response to a flawed Port-up in the future, and I'd argue that
the same "Ignore this field on receipt" semantics should apply for the
PortUP messages too. 

Regards,
Woj.

> 
> In other use cases, Result=0x00 could also be used and the 
> behavior on receipt of another message type would also be 
> defined in the procedures for that message. In some cases, 
> the responder behavior could be a little more subtle (e.g. 
> respond with message X in such situation, respond with 
> message Y in that situation, and don't respond at all in such 
> situations ).
> 
> Francois
> 
> PS: one question: I assume the Result = "Failure" value is 
> not affected by this discussion (ie it remains valid e.g. in 
> Multicast Status message). right?
> 
> 
> >
> >
> > Please let me know if this semantic for Result field is ok 
> for you or 
> > you have any additional comment on this proposal.
> > Thanks
> > Best Regards,
> > Roberta
> >
> >
> > CONFIDENTIALITY NOTICE
> >
> > This message and its attachments are addressed solely to 
> the persons 
> > above and may contain confidential information. If you have 
> received 
> > the message in error, be informed that any use of the 
> content hereof 
> > is prohibited. Please return it immediately to the sender 
> and delete 
> > the message. Should you have any questions, please contact us by 
> > replying to webmaster@telecomitalia.it.
> >
> >        Thank you
> >
> >                                        www.telecomitalia.it 
> > _______________________________________________
> > ANCP mailing list
> > ANCP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ancp
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
> 
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Fri Oct 24 19:21:14 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D08043A688E;
	Fri, 24 Oct 2008 19:21:14 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FEC23A6830
	for <ancp@core3.amsl.com>; Fri, 24 Oct 2008 19:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.759
X-Spam-Level: ****
X-Spam-Status: No, score=4.759 tagged_above=-999 required=5 tests=[AWL=4.561, 
	BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 
	MIME_8BIT_HEADER=0.3, MY_CID_AND_ARIAL2=1.46,
	SARE_SUB_ENC_UTF8=0.152]
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 DRG6dvCjZh3z for <ancp@core3.amsl.com>;
	Fri, 24 Oct 2008 19:21:10 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65])
	by core3.amsl.com (Postfix) with ESMTP id E85843A688E
	for <ancp@ietf.org>; Fri, 24 Oct 2008 19:21:08 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K99003Q5VXHWJ@szxga02-in.huawei.com> for
	ancp@ietf.org; Sat, 25 Oct 2008 10:22:30 +0800 (CST)
Received: from huawei.com ([172.24.1.12])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K9900MC2VXH6C@szxga02-in.huawei.com> for
	ancp@ietf.org; Sat, 25 Oct 2008 10:22:29 +0800 (CST)
Received: from h36145c ([10.70.39.123])
	by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K9900F48VXDJT@szxml05-in.huawei.com> for
	ancp@ietf.org; Sat, 25 Oct 2008 10:22:29 +0800 (CST)
Date: Sat, 25 Oct 2008 10:22:25 +0800
From: Fortune HUANG <fqhuang@huawei.com>
In-reply-to: <1D2B54B0-EB7A-4302-A75F-77EBC7CB9909@cisco.com>
To: 'Francois Le Faucheur IMAP' <flefauch@cisco.com>
Message-id: <005c01c93648$8573e500$7b27460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: Ack107gcwDb0s3nSSS6RqrUuosyJUAAcK+KA
Cc: "'Haag, Thomas'" <HaagT@telekom.de>, ancp@ietf.org
Subject: [ANCP] =?utf-8?b?IOetlOWkjTogIOetlOWkjTogIEFOQ1AgRnJhbWV3b3JrIHVw?=
 =?utf-8?q?date?=
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0143481189=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0143481189==
Content-type: multipart/related; boundary="Boundary_(ID_jGVfE8ggj3mXr9OY9kYZBA)"

This is a multi-part message in MIME format.

--Boundary_(ID_jGVfE8ggj3mXr9OY9kYZBA)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_ZgGJrD8UKnKWn6RfUzrXKw)"


--Boundary_(ID_ZgGJrD8UKnKWn6RfUzrXKw)
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: quoted-printable

Hi Francois,
=20
I think there are no obvious Policy decision Point and Policy =
Enforcement Point in the model of the bidirectional bandwidth =
negotiation.
The entity performs admission control for unicast, but doesn't enforce =
any policy to the AN.
=20
If the name "RACS" is not acceptable, I would provide another =
alternative called external Resource and Admission Control Entity =
(external RACE). This name is not yet defined in other bodies and it can =
also clearly reflect the functionalities in a very straightforward way.=20
=20
=20
Best Reagards,
Fortune

Huawei Technologies Co., Ltd. huawei_logo=20


Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =
518129, P.R. China
Tel: +86-755-28971871
Fax: +86-755-28972352
Mobile: +8615013838060
Email: fqhuang@huawei.com
http://www.huawei.com
-------------------------------------------------------------------------=
------------------------------------------------------------
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81
=E6=AD=A2=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=
=BD=95=E5=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=
=86=E4=B8=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=
=E5=9C=B0=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=
=95=A3=E5=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD
=E7=9A=84=E4=BF=A1=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=
=94=B6=E4=BA=86=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=
=8B=E5=8D=B3=E7=94=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=
=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=
=BB=B6=EF=BC=81
This e-mail and its attachments contain confidential information from =
HUAWEI, which=20
is intended only for the person or entity whose address is listed above. =
Any use of the=20
information contained herein in any way (including, but not limited to, =
total or partial=20
disclosure, reproduction, or dissemination) by persons other than the =
intended=20
recipient(s) is prohibited. If you receive this e-mail in error, please =
notify the sender by=20
phone or email immediately and delete it!

=20

  _____ =20

=E5=8F=91=E4=BB=B6=E4=BA=BA: Francois Le Faucheur IMAP =
[mailto:flefauch@cisco.com]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2008=E5=B9=B410=E6=9C=8824=E6=97=A5 20:14
=E6=94=B6=E4=BB=B6=E4=BA=BA: Fortune HUANG
=E6=8A=84=E9=80=81: Francois Le Faucheur IMAP; 'Tina TSOU'; 'Haag, =
Thomas'; ancp@ietf.org
=E4=B8=BB=E9=A2=98: Re: [ANCP] =E7=AD=94=E5=A4=8D: ANCP Framework update


Fortune,=20

I don't think it is a good idea to refer to this entity as RACS because:
* as a general practise we don't want to depend on definition from =
external bodies

* i don't believe the RACS terminology is that well known in IETF =
community

* I would argue that in some scenarios some of the function performed by =
the NAS belong to the RACS functional entity (so that it is not correct =
to model the RACS as entirely outside the NAS)

As far as alternatives, perhaps we could use Policy Decision Point? that =
is an existing IETF concept and suggests that the entity makes admission =
decisions, some of which being bandwidth based.

In any case, the interactions with the Policy Server/Policy Decision =
Point/xxx   are outside the scope of ANCP of course, so we only need to =
indicate that optional communication with an entity involved in the =
admission decision is possible.

Francois =20

On 24 Oct 2008, at 05:55, Fortune HUANG wrote:


Hi all,
=20
=20
The name "PS/Policy Server" used in this draft is also kind of confusing =
to me in this draft.
=20
The entity descriped in this draft is actually an entity which manages =
(part of) the network bandwidth/resource and performs admission control =
for the unicast service. These functionalites are not quite clearly =
reflected by the name "Policy Server".
=20
Therefore, I suggest we find a better name for this entity.
=20
My proposal is to replace the "PS/Policy Server" with "RACS / Resource =
and Admission Control Subsystem" which is defined in ETSI TISPAN.
I think the name "RACS"can reflect the requirement for this entity =
precisely.
=20
=20
Best Regards,
Fortune

Huawei Technologies Co., Ltd. <outlook_huawei_logo_cn.jpg>=20


Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =
518129, P.R. China
Tel: +86-755-28971871
Fax: +86-755-28972352
Mobile: +8615013838060
Email: fqhuang@huawei.com
http://www.huawei.com
-------------------------------------------------------------------------=
------------------------------------------------------------
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81
=E6=AD=A2=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=
=BD=95=E5=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=
=86=E4=B8=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=
=E5=9C=B0=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=
=95=A3=E5=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD
=E7=9A=84=E4=BF=A1=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=
=94=B6=E4=BA=86=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=
=8B=E5=8D=B3=E7=94=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=
=E5=8F=91=E4=BB=B6=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=
=BB=B6=EF=BC=81
This e-mail and its attachments contain confidential information from =
HUAWEI, which=20
is intended only for the person or entity whose address is listed above. =
Any use of the=20
information contained herein in any way (including, but not limited to, =
total or partial=20
disclosure, reproduction, or dissemination) by persons other than the =
intended=20
recipient(s) is prohibited. If you receive this e-mail in error, please =
notify the sender by=20
phone or email immediately and delete it!

=20

  _____ =20

=E5=8F=91=E4=BB=B6=E4=BA=BA: Tina TSOU [mailto:tena@huawei.com]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2008=E5=B9=B410=E6=9C=8822=E6=97=A5 19:52
=E6=94=B6=E4=BB=B6=E4=BA=BA: Haag, Thomas
=E6=8A=84=E9=80=81: sven.ooghe@alcatel-lucent.be; ancp@ietf.org
=E4=B8=BB=E9=A2=98: Re: [ANCP] ANCP Framework update


Hi all,
I agree with Thomas' comments.











B. R.
Tina


Messengers:

MSN: tinatsou6@hotmail.com   Yahoo: tina_tsou    Skype: tinaTSOU    =
Jabber: tina@jabber.org    Google talk: tinatsou6@gmail.com

+86-755-28971872 (Office)    +86-13922884380(Mobile)



On Oct 22, 2008, at 6:42 PM, Haag, Thomas wrote:



Hi Sven,
=20
please see my comments inline.
=20
Regards=20
Thomas Haag=20
Deutsche Telekom AG
Zentrum Technik Einf=C3=BChrung
TE5-22, Internationale Standardisierung
Heinrich-Hertz-Stra=C3=9Fe 3-7, 64295 Darmstadt
+49 6151 628-2088 (Tel.)
+49 521 9210-8411 (Fax)
+49 171 56 44 739 (Mobil)
Neu: Email: haagt@telekom.de
 <http://www.telekom.com/> http://www.telekom.com
=20



  _____ =20

Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von =
OOGHE Sven
Gesendet: Freitag, 17. Oktober 2008 11:23
An: ancp@ietf.org
Betreff: [ANCP] ANCP Framework update


Hi,

I've been updating the ANCP framework draft according to the suggested =
changes from Roberta and Francois. Below I have copy-pasted the sections =
that have undergone changes. Indented text has been changed. I think I =
captured the essence of the notion of "bandwidth delegation". Please =
review and see if this is capturing the agreements.

Regards,=20
Sven



3.4.2.  Multicast Admission Control

   The successful delivery of Triple Play Broadband services is quickly=20
   becoming a big capacity planning challenge for most of the Service=20
   Providers nowadays.  Solely increasing available bandwidth is not=20
   always practical, cost-economical and/or sufficient to satisfy end=20
   user experience given not only the strict requirements of unicast=20
   delay sensitive applications like VoIP and Video, but also the fast=20
   growth of multicast interactive applications such as=20
   videoconferencing, digital TV, digital audio, online movies and=20
   networked gaming.  These applications are typically characterized by=20
   a delay sensitive nature, an extremely loss sensitive nature and=20
   intensive bandwidth requirements.  They are also typically "non-=20
   elastic", which means that they operate at a fixed bandwidth, that=20
   cannot be dynamically adjusted to the currently available bandwidth.

   Therefore a Connection Admission Control (CAC) mechanism covering=20
   admission of multicast traffic over the DSL Broadband access is=20
   required, in order to avoid oversubscribing the available bandwidth=20
   and negatively impacting the end user experience.

   Considering specifically admission control over the access line,=20
   before honoring a user request to join a new multicast flow, the=20
   combination of AN and NAS MUST ensure admission control is performed=20
   to validate that there is enough "video" bandwidth remaining on the=20
   access line to carry the new flow (in addition to all other existing=20
   multicast and unicast video traffic).  The solution needs to cope=20
   with multiple flows per access line and needs to allow access line=20
   bandwidth to be dynamically shared across multicast and unicast=20
   traffic (irrespective of whether unicast CAC is performed by NAS or=20
   by some off-path Policy Server).

   Thus, supporting CAC for the access line requires some form of=20
   synchronization between the entity performing multicast CAC (e.g. the =

   NAS or the AN) and the entity performing unicast CAC (e.g. the NAS or =

   a Policy Server) and the entity actually enforcing the multicast  =
[T.H.: Is that correct as stated "NAS or Policy server"?; My =
understanding: Policy Server: Policy decission point; NAS controls AN by =
ANCP;AN: policy enforcement point] =20
   replication (i.e. the AN).  This synchronization can be achieved in a =

   number of ways:

   o  One approach is for the AN to query the NAS so that Admission=20
      Control for the access line is performed by the NAS (possibly with =

      interactions with a Policy Server).  This can be done with or=20
      without "bandwidth delegation" to the AN.

      *  In case of Admission Control without AN Bandwidth Delegation,=20
         the AN can use ANCP to query the NAS, that in turn performs=20
         multicast Admission Control check for the new multicast flow=20
         and responds to the AN indicating whether the join is to be=20
         honored (and hence replication performed by the AN) or denied.=20
         The NAS may locally maintain available "video" bandwidth  =
[T.H.:]  (net data rate) on the=20
         Access Loop, and perform video bandwidth accounting for the=20
         Access Loop.  Upon receiving an Admission Request from the AN,=20
         the NAS can check available "video" bandwidth before admitting=20
         or denying the multicast flow.  In the process, the NAS may=20
         communicate with the Policy Server.  For unicast video services =

         such as Video on Demand (VoD), the NAS may also be queried (by=20
         a Policy Server or via on-path CAC signaling), so that it can=20
         perform admission control for the unicast flow, and update the=20
         available video bandwidth maintained by the NAS.

      *  In case of Admission Control with AN Bandwidth Delegation, the=20
         NAS (possibly with interactions with a Policy Server) manages=20
         total bandwidth for video admission, performs unicast admission =

         control and uses ANCP to delegate a certain amount of bandwidth =

         for some multicast flows to the Access Node.  In this scenario, =

         upon receiving a join to a multicast flow which matches an=20
         entry in the White or Grey List whose entry is flagged as=20
         "Bandwidth Delegation", the AN must perform the necessary=20
         bandwidth admission control check for the new multicast flow,=20
         before starting the multicast flow replication.

      The ANCP requirements to support this approach are specified in=20
      this document.

   o  In case the subscriber communicates the "join/leave" information=20
      with the NAS (e.g. by terminating all subscriber IGMP signaling on =

      the NAS, or by using some form of application level signaling),=20
      the approach is very similar.  In this case, the NAS may locally=20
      maintain available "video" bandwidth on the Access Loop, perform=20
      video bandwidth accounting, and perform CAC for unicast and=20
      multicast flows.  The NAS can set the replication state on the AN=20
      using ANCP if the flow is admitted.  For unicast video services=20
      the NAS may be queried (by a policy server or via on-path CAC=20
      signaling) to perform admission control for the unicast flow, and=20
      update the available video bandwidth maintained by the NAS.  The=20
      ANCP requirements to support this approach (where the AN queries=20
      the NAS) are specified in this document;

   o  In a third approach, the Policy Server queries the AN directly so=20
      that both unicast and multicast CAC for the access line are=20
      performed by the AN.  In this case, a subscriber request for a=20
      unicast flow (e.g. a Video on Demand session) will trigger a=20
      resource request message towards a Policy Server; the latter will=20
      then query the AN, that in turn will perform unicast CAC for the=20
      access line and respond, indicating whether the unicast request is =

      to be honored or denied.  In this scenario the Policy Server=20
      queries the AN directly, the approach doesn't require the use of=20
      ANCP.  It is therefore beyond the scope of this document.



4.2.  ANCP Multicast Requirements

   o  The ANCP MUST support providing multicast conditional access=20
      information to Access Ports on an Access Node, using Black, Grey=20
      and White lists.

   o  The ANCP MUST support binding a particular Black, Grey and White=20
      List to a given Access Port.

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List the ANCP MUST allow the AN to query the NAS to request an=20
      admission decision for replicating that multicast flow to a=20
      particular Access Port.

   o  The ANCP MUST allow the NAS to send an admission decision to the=20
      AN indicating whether or not a multicast flow may be replicated to =

      a particular Access Port.

   o  The ANCP must allow the NAS to indicate to the AN whether or not=20
      Admission Control is needed for some multicast flows on a given=20
      Access Port and where needed whether or not it is to be performed=20
      with AN Bandwidth Delegation.

   o  In case of Admission Control without AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to reply to a query from the AN indicating =

      whether or not a multicast flow may be replicated to a particular=20
      Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to delegate a certain amount of bandwidth=20
      to the AN for a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the AN to query the NAS to request additional=20
      multicast bandwidth on a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the NAS to query (or to instruct) the AN to reduce =

      the amount of bandwidth previously delegated on a given Access=20
      Port.

   o  In case of Admission Control with AN Bandwidth Delegation, the=20
      ANCP must allow the AN to autonomous release redundant multicast=20
      bandwidth on a given Access Port.

   o  The ANCP MUST allow the AN to send an Information Report message=20
      to the NAS whenever replication of a multicast flow on a=20
      particular Access Port start or ends.

   o  The ANCP MUST allow the AN to send an Information Report message=20
      to the NAS indicating the multicast traffic volume that has been=20
      replicated on that port.

   o  The ANCP MUST allow the NAS to indicate to the AN whether or not=20
      multicast accounting is needed for a multicast flow on a=20
      particular Access Port.

   o  In case multicast accounting is needed for a multicast flow on a=20
      particular Access Port, the ANCP MUST allow the NAS to indicate to =

      the AN whether or not additional volume accounting information is=20
      required.

   o  The ANCP MUST allow the NAS to revoke a decision to replicate a=20
      multicast flow to a particular Access Port, which had been=20
      conveyed earlier to an AN.

   o  The ANCP MUST support partial updates of the White, Grey and Black =

      lists.

   o  The ANCP MUST allow the NAS to query the AN to obtain information=20
      on what multicast flows are currently being replicated on a given=20
      Access Port, what Access Ports are currently receiving a given=20
      multicast flow, or what multicast flows are currently replicated=20
      on each Access Port.



Access Node multicast requirements (section 4.7.6)

   o  The AN must deny any join to a multicast flow matching the Black=20
      List for the relevant Access Port.

   o  The AN must accept any join to a multicast flow matching the White =

      List and not flagged as "Bandwidth Delegation" for the relevant=20
      Access Port.

   o  Upon receiving a join to a multicast flow which matches the White=20
      List whose entry is flagged as "Bandwidth Delegation" for the=20
      relevant Access Port, the AN must perform the necessary bandwidth=20
      admission control check for the new flow before starting the=20
      multicast flow replication.

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List whose entry is flagged as "no Bandwidth Delegation" for the=20
      relevant Access Port, the AN must support using ANCP to query the=20
      NAS to receive a response indicating whether that join is to be=20
      honored or denied.  In this case, the NAS will perform both the=20
      necessary conditional access and the admission control checks for=20
      the new flow.

   o  Upon receiving a join to a multicast flow which matches the Grey=20
      List whose entry is flagged as "Bandwidth Delegation" for the=20
      relevant Access Port, the AN must first perform the necessary=20
      bandwidth admission control check for the new flow.  If=20
      successful, the AN must support using ANCP to query the NAS to=20
      receive a response indicating whether that join is to be honored=20
      or denied.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to notify the NAS when the the user leaves =

      the multicast flow.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to query the NAS to request additional=20
      delegated multicast bandwidth on a given Access Port; the AN=20
      should be able to specify both the minimum and the preferred=20
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving a Bandwidth Delegation Request from the NAS querying or=20
      instructing to decrease the delegated multicast bandwidth on a=20
      given Access Port, the AN must support using ANCP to send a=20
      Bandwidth Delegation Response indicating the new delegated=20
      multicast bandwidth.

   o  In case of Admission Control with AN Bandwidth Delegation, the AN=20
      must support using ANCP to send a Bandwidth Release message to the =

      NAS in order to release unused delegated multicast bandwidth on a=20
      given Access Port.

   o  If the requested multicast flow is not part of any list associated =

      with the Access Port, the AN must discard the message.

   o  If the requested multicast flow is part of multiple lists=20
      associated with the Access Port, the AN must use the most specific =

      match.

   o  If the requested multicast flow has the same most specific match=20
      in multiple lists, the AN must give precedence to the Black list,=20
      followed by the Grey list, and then the White list.

   o  The AN must support configuring a "catch-all" statement in the=20
      Black, White or Grey list in order to enforce a default behavior=20
      for a join to a multicast flow which doesn't match any other entry =

      in a list for the relevant Access Port.

   o  Upon querying the NAS, the AN must not propagate the join message=20
      before the successful authorization from the NAS is received.

   o  Upon receiving a leave for a multicast flow which matches the Grey =

      List, the AN should be able to autonomously stop replication and=20
      advertise this event to the NAS.

   o  The AN must support using ANCP to send an Information Report=20
      message to the NAS whenever replication starts or ends  [T.H:] or =
fails .

   o  The AN should support using ANCP to send an Information Report=20
      message to the NAS indicating the multicast traffic volume that=20
      has been replicated on that port.

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what multicast=20
      flows are currently being replicated on a given Access Port.

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what Access=20
      Ports are currently receiving a given multicast flow.

   o  Upon request by the NAS, the AN must support using ANCP to send an =

      Information Report message to the NAS, indicating what multicast=20
      flows are currently being replicated on each Access Port.

   o  Upon receiving an Admission Response from the NAS, indicating that =

      replication of a multicast flow is to start or stop on a given=20
      access port of the AN, the AN must enforce this decision.  This=20
      decision must be taken irrespective of whether or not a=20
      corresponding Admission Request was issued by the AN earlier on.



NAS multication requirements (section 4.8.6)

   o  The NAS must support using ANCP to configure multicast conditional =

      access information to Access Ports on an Access Node, using Black=20
      Lists, Grey Lists and White Lists.

   o  The NAS must support using ANCP to indicate to the AN whether or=20
      not Admission Control is needed for some multicast flows on a=20
      given Access Port and where needed whether or not it is to be=20
      performed with AN Bandwidth Delegation.

   o  Upon receiving a query from the AN for a request to replicate a=20
      multicast flow to a particular Access Port, and no AN Bandwidth=20
      Delegation is needed for that flow, the NAS must be able to=20
      perform the necessary checks (conditional access and/or admission=20
      control) for the new flow.  The NAS must support using ANCP to=20
      reply to the AN indicating whether the request is to be honored or =

      denied.

   o  Upon receiving a query from the AN for a request to replicate a=20
      multicast flow to a particular Access Port, and Admission Control=20
      with AN Bandwidth Delegation is needed for that flow, the NAS must =

      be able to perform the conditional access checks (if needed), and=20
      must support using ANCP to delegate a certain amount of bandwidth=20
      to the AN for a given Access Port.

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving a Bandwidth Delegation Request from the AN requesting to =

      increase the delegated multicast bandwidth on a given Access Port, =

      the NAS must support using ANCP to send a Bandwidth Delegation=20
      Response indicating the new delegating multicast bandwidth.

   o  In case of Admission Control with AN Bandwidth Delegation, the NAS =

      must support using ANCP to send a request the AN to decrease the=20
      amount of multicast bandwidth previously delegated on a given=20
      Access Port; the NAS should be able to specify both the minimum=20
      and the preferred amount decrement of multicast bandwidth=20
      requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon=20
      receiving an ANCP Bandwidth Release message, the NAS must be able=20
      to update accordingly its view of the multicast bandwidth=20
      delegated to the AN.

   o  The NAS must support using ANCP to configure the Access Node with=20
      the "maximum number of multicast streams" allowed to be received=20
      concurrently per Access Port.

   o  The NAS must support using ANCP to incrementally add, remove and=20
      modify individual entries in White, Black and Grey lists.

   o  The NAS must support using ANCP to indicate to the AN whether or=20
      not multicast accounting is needed for a multicast flow on a=20
      particular Access Port.

   o  In case multicast accounting is needed for a multicast flow on a=20
      particular Access Port, the NAS should support using ANCP to=20
      indicate to the AN whether or not additional volume accounting=20
      information is required.

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what multicast flows are currently replicated on a=20
      given Access Port.

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what Access Ports are currently receiving a given=20
      multicast flow.

   o  The NAS must support using ANCP to query the AN to obtain=20
      information on what multicast flows are currently replicated on=20
      each Access Port.

   o  When Multicast replication occurs on the AN, the NAS must support=20
      using ANCP to revoke the authorization to replicate a multicast=20
      flow to a particular Access Port.

   o  The NAS should support using ANCP to indicate to the AN that=20
      replication of a multicast flow is to start or stop on a given=20
      access port of the AN, without having received a corresponding=20
      Admission Request from the AN earlier on.

---

Sven Ooghe=20
Alcatel-Lucent=20
CTO Office, Access Division=20
Copernicuslaan 50, 2018 Antwerp, Belgium=20
tel.: +32 3 240 42 26=20
fax: +32 3 240 40 73

This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly prohibited =
without the prior consent of its author.

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp



_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp




--Boundary_(ID_ZgGJrD8UKnKWn6RfUzrXKw)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D131585201-25102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>Hi Francois,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D131585201-25102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D131585201-25102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>I think there are no obvious Policy decision =
Point and=20
Policy Enforcement Point in the model of the bidirectional bandwidth=20
negotiation.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D131585201-25102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>The&nbsp;entity performs admission control for =
unicast, but=20
doesn't enforce any policy to the AN.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D131585201-25102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D131585201-25102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
color=3D#0000ff size=3D2>If the name "RACS" is not acceptable, I would =
provide=20
another alternative called external&nbsp;Resource and Admission Control =
Entity=20
(external RACE). This name is not yet defined in other bodies and it can =
also=20
clearly reflect the functionalities in a very straightforward way.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2><SPAN=20
class=3D131585201-25102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2><SPAN=20
class=3D131585201-25102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2><SPAN=20
class=3D131585201-25102008>Best Reagards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2><SPAN=20
class=3D131585201-25102008>Fortune</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2><SPAN=20
class=3D131585201-25102008></SPAN></FONT><FONT =
face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dblack=20
size=3D2><BR></FONT><FONT face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 =
color=3Dgray size=3D2>Huawei Technologies Co.,=20
Ltd. </FONT><IMG id=3DridImg alt=3Dhuawei_logo hspace=3D0=20
src=3D"cid:131585201@25102008-2EFF" align=3Dleft> </DIV>
<P></P><BR><FONT face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 =
color=3Dgray size=3D1>Addr: Section F, Huawei Industrial=20
Base, Bantian Longgang, Shenzhen 518129, P.R. China<BR>Tel:=20
+86-755-28971871<BR>Fax: +86-755-28972352<BR>Mobile: =
+8615013838060<BR>Email:=20
fqhuang@huawei.com<BR>http://www.huawei.com<BR></FONT><FONT =
face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dgray=20
size=3D1>----------------------------------------------------------------=
---------------------------------------------------------------------<BR>=
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81<BR>=E6=AD=A2=
=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=BD=95=E5=
=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=86=E4=B8=
=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=E5=9C=B0=
=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=95=A3=E5=
=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD<BR>=E7=9A=84=E4=BF=A1=
=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=94=B6=E4=BA=86=E6=
=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=8B=E5=8D=B3=E7=94=
=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=E5=8F=91=E4=BB=B6=
=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=81<=
BR></FONT><FONT=20
face=3DArial color=3Dgray size=3D1>This e-mail and its attachments =
contain=20
confidential information from HUAWEI, which <BR>is intended only for the =
person=20
or entity whose address is listed above. Any use of the <BR>information=20
contained herein in any way (including, but not limited to, total or =
partial=20
<BR>disclosure, reproduction, or dissemination) by persons other than =
the=20
intended <BR>recipient(s) is prohibited. If you receive this e-mail in =
error,=20
please notify the sender by <BR>phone or email immediately and delete=20
it!<BR></FONT>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dzh-cn dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3D=E5=AE=8B=E4=BD=93 =
size=3D2><B>=E5=8F=91=E4=BB=B6=E4=BA=BA:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] =
<BR><B>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:</B> =
2008=E5=B9=B410=E6=9C=8824=E6=97=A5 =
20:14<BR><B>=E6=94=B6=E4=BB=B6=E4=BA=BA:</B>=20
Fortune HUANG<BR><B>=E6=8A=84=E9=80=81:</B> Francois Le Faucheur IMAP; =
'Tina TSOU'; 'Haag,=20
Thomas'; ancp@ietf.org<BR><B>=E4=B8=BB=E9=A2=98:</B> Re: [ANCP] =
=E7=AD=94=E5=A4=8D: ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV></DIV>Fortune,
<DIV><BR></DIV>
<DIV>I don't think it is a good idea to refer to this entity as RACS=20
because:</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* as =
a general=20
practise we don't want to depend on definition from external =
bodies<BR></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* i =
don't=20
believe the RACS terminology is that well known in IETF =
community<BR></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>*=20
I&nbsp;would&nbsp;argue that in some scenarios some of the function =
performed by=20
the NAS belong to the RACS functional entity (so that it is not correct =
to model=20
the RACS as entirely outside the NAS)</DIV>
<DIV><BR></DIV>
<DIV>As far as alternatives, perhaps we could use Policy Decision Point? =
that is=20
an existing IETF concept and suggests that the entity makes admission =
decisions,=20
some of which being bandwidth based.</DIV>
<DIV><BR></DIV>
<DIV>In any case, the interactions with the Policy Server/Policy =
Decision=20
Point/xxx &nbsp; are outside the scope of ANCP of course, so we only =
need to=20
indicate that optional communication with an entity involved in the =
admission=20
decision is possible.</DIV>
<DIV><BR></DIV>
<DIV>Francois &nbsp;</DIV>
<DIV><BR>
<DIV>
<DIV>On 24 Oct 2008, at 05:55, Fortune HUANG wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>Hi all,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>The name "PS/Policy Server" used in this =
draft is also=20
  kind of confusing to me in this draft.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>The entity descriped in this draft is =
actually an entity=20
  which manages (part of) the network bandwidth/resource and performs =
admission=20
  control for the unicast service. These functionalites are not quite =
clearly=20
  reflected by the name "Policy Server".</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>Therefore, I suggest we find a better name =
for this=20
  entity.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>My proposal&nbsp;is to replace the "PS/Policy =
Server"=20
  with "RACS / Resource and Admission Control Subsystem" which is =
defined in=20
  ETSI TISPAN.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>I think the&nbsp;name =
"RACS"</FONT></SPAN><SPAN=20
  class=3D157111503-24102008><FONT face=3D=E5=AE=8B=E4=BD=93 =
color=3D#0000ff size=3D2>can&nbsp;reflect=20
  the requirement for this entity precisely.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>Best Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2>Fortune</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D157111503-24102008><FONT =
face=3D=E5=AE=8B=E4=BD=93=20
  color=3D#0000ff size=3D2></FONT></SPAN><FONT =
face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dblack=20
  size=3D2><BR></FONT><FONT face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 =
color=3Dgray size=3D2>Huawei Technologies Co.,=20
  Ltd. </FONT><SPAN>&lt;outlook_huawei_logo_cn.jpg&gt;</SPAN> </DIV>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV><BR><FONT =
face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dgray=20
  size=3D1>Addr: Section F, Huawei Industrial Base, Bantian Longgang, =
Shenzhen=20
  518129, P.R. China<BR>Tel: +86-755-28971871<BR>Fax:=20
  +86-755-28972352<BR>Mobile: +8615013838060<BR>Email: <A=20
  href=3D"mailto:fqhuang@huawei.com">fqhuang@huawei.com</A><BR><A=20
  =
href=3D"http://www.huawei.com">http://www.huawei.com</A><BR></FONT><FONT =

  face=3D=E5=8D=8E=E6=96=87=E7=BB=86=E9=BB=91 color=3Dgray=20
  =
size=3D1>----------------------------------------------------------------=
---------------------------------------------------------------------<BR>=
=E6=9C=AC=E9=82=AE=E4=BB=B6=E5=8F=8A=E5=85=B6=E9=99=84=E4=BB=B6=E5=90=AB=E6=
=9C=89=E5=8D=8E=E4=B8=BA=E5=85=AC=E5=8F=B8=E7=9A=84=E4=BF=9D=E5=AF=86=E4=BF=
=A1=E6=81=AF=EF=BC=8C=E4=BB=85=E9=99=90=E4=BA=8E=E5=8F=91=E9=80=81=E7=BB=99=
=E4=B8=8A=E9=9D=A2=E5=9C=B0=E5=9D=80=E4=B8=AD=E5=88=97=E5=87=BA=E7=9A=84=E4=
=B8=AA=E4=BA=BA=E6=88=96=E7=BE=A4=E7=BB=84=E3=80=82=E7=A6=81<BR>=E6=AD=A2=
=E4=BB=BB=E4=BD=95=E5=85=B6=E4=BB=96=E4=BA=BA=E4=BB=A5=E4=BB=BB=E4=BD=95=E5=
=BD=A2=E5=BC=8F=E4=BD=BF=E7=94=A8=EF=BC=88=E5=8C=85=E6=8B=AC=E4=BD=86=E4=B8=
=8D=E9=99=90=E4=BA=8E=E5=85=A8=E9=83=A8=E6=88=96=E9=83=A8=E5=88=86=E5=9C=B0=
=E6=B3=84=E9=9C=B2=E3=80=81=E5=A4=8D=E5=88=B6=E3=80=81=E6=88=96=E6=95=A3=E5=
=8F=91=EF=BC=89=E6=9C=AC=E9=82=AE=E4=BB=B6=E4=B8=AD<BR>=E7=9A=84=E4=BF=A1=
=E6=81=AF=E3=80=82=E5=A6=82=E6=9E=9C=E6=82=A8=E9=94=99=E6=94=B6=E4=BA=86=E6=
=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=8C=E8=AF=B7=E6=82=A8=E7=AB=8B=E5=8D=B3=E7=94=
=B5=E8=AF=9D=E6=88=96=E9=82=AE=E4=BB=B6=E9=80=9A=E7=9F=A5=E5=8F=91=E4=BB=B6=
=E4=BA=BA=E5=B9=B6=E5=88=A0=E9=99=A4=E6=9C=AC=E9=82=AE=E4=BB=B6=EF=BC=81<=
BR></FONT><FONT=20
  face=3DArial color=3Dgray size=3D1>This e-mail and its attachments =
contain=20
  confidential information from HUAWEI, which <BR>is intended only for =
the=20
  person or entity whose address is listed above. Any use of the =
<BR>information=20
  contained herein in any way (including, but not limited to, total or =
partial=20
  <BR>disclosure, reproduction, or dissemination) by persons other than =
the=20
  intended <BR>recipient(s) is prohibited. If you receive this e-mail in =
error,=20
  please notify the sender by <BR>phone or email immediately and delete=20
  it!<BR></FONT>
  <DIV>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Dzh-cn dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3D=E5=AE=8B=E4=BD=93 =
size=3D2><B>=E5=8F=91=E4=BB=B6=E4=BA=BA:</B> Tina TSOU [<A=20
  href=3D"mailto:tena@huawei.com">mailto:tena@huawei.com</A>] =
<BR><B>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:</B>=20
  2008=E5=B9=B410=E6=9C=8822=E6=97=A5 =
19:52<BR><B>=E6=94=B6=E4=BB=B6=E4=BA=BA:</B> Haag, =
Thomas<BR><B>=E6=8A=84=E9=80=81:</B> <A=20
  =
href=3D"mailto:sven.ooghe@alcatel-lucent.be">sven.ooghe@alcatel-lucent.be=
</A>;=20
  <A =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>=E4=B8=BB=E9=A2=98:=
</B> Re: [ANCP] ANCP=20
  Framework update<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>Hi all,</DIV>
  <DIV>I agree with Thomas' comments.</DIV>
  <DIV><BR></DIV><BR>
  <DIV apple-content-edited=3D"true"><SPAN class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space"><SPAN=20
  class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0px">
  <DIV=20
  style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
  <DIV>
  <DIV>B. R.</DIV>
  <DIV>Tina</DIV>
  <DIV><BR></DIV>
  <DIV>
  <P>Messengers:</P>
  <P>MSN: <A=20
  =
href=3D"mailto:tinatsou6@hotmail.com">tinatsou6@hotmail.com</A>&nbsp;&nbs=
p;=20
  Yahoo: tina_tsou&nbsp;&nbsp;&nbsp; Skype: tinaTSOU&nbsp;&nbsp;&nbsp; =
Jabber:=20
  <A =
href=3D"mailto:tina@jabber.org">tina@jabber.org</A>&nbsp;&nbsp;&nbsp; =
Google=20
  talk: <A =
href=3D"mailto:tinatsou6@gmail.com">tinatsou6@gmail.com</A></P>
  <P>+86-755-28971872 (Office)&nbsp;&nbsp;&nbsp;=20
  =
+86-13922884380(Mobile)</P></DIV></DIV></DIV></SPAN></DIV></SPAN></DIV></=
SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></DIV></SPAN></D=
IV></SPAN></DIV>
  <DIV><BR></DIV><BR>
  <DIV>
  <DIV>On Oct 22, 2008, at 6:42 PM, Haag, Thomas wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-style-span=20
    style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">
    <DIV lang=3DDE vlink=3D"purple" link=3D"blue">
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D734534408-22102008>Hi Sven,</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D734534408-22102008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D734534408-22102008>please see my comments =
inline.</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D734534408-22102008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
    class=3D734534408-22102008></SPAN></FONT><B><SPAN lang=3Dde><FONT =
size=3D2><SPAN=20
    class=3D734534408-22102008>R</SPAN>egards</FONT></SPAN></B><SPAN=20
    lang=3Dde></SPAN><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
    lang=3Dde><B><FONT size=3D2>Thomas Haag</FONT></B></SPAN><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN lang=3Dde><FONT =

    color=3D#808080 size=3D2>Deutsche Telekom AG<BR>Zentrum Technik=20
    Einf=C3=BChrung<BR>TE5-22, Internationale=20
    Standardisierung<BR>Heinrich-Hertz-Stra=C3=9Fe 3-7, 64295 =
Darmstadt<BR>+49 6151=20
    628-2088 (Tel.)<BR>+49 521 9210-8411 (Fax)<BR>+49 171 56 44 739=20
    (Mobil)</FONT><B><BR></B><FONT color=3D#ff0000 =
size=3D2>Neu:</FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><FONT color=3D#808080=20
    size=3D2>Email:</FONT><U><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><FONT=20
    color=3D#0000ff size=3D2><A style=3D"COLOR: blue; TEXT-DECORATION: =
underline"=20
    =
href=3D"mailto:haagt@telekom.de">haagt@telekom.de</A></FONT></U><FONT=20
    color=3D#808080 size=3D2><BR></FONT></SPAN><A=20
    style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
    href=3D"http://www.telekom.com/"><SPAN lang=3Dde><U></U><U><FONT =
color=3D#0000ff=20
    size=3D2>http://www.telekom.com</FONT></U></SPAN></A><SPAN =
lang=3Dde><FONT=20
    color=3D#808080 size=3D2></FONT></SPAN></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV><FONT=20
    face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><FONT face=3DArial=20
    color=3D#0000ff size=3D2></FONT><BR>
    <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr =
align=3Dleft><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <DIV class=3DSection1>
    <DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times =
New Roman'"><B><FONT=20
    face=3DTahoma size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">Von:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><A=20
    href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</A> [<A=20
    style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
    =
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>]<S=
PAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Im Auftrag von<SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN></SPAN></B>OOGHE =
Sven<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN>Freitag, 17. Oktober 2008 =

    11:23<BR><B><SPAN style=3D"FONT-WEIGHT: bold">An:</SPAN></B><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><A=20
    style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
    href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN>[ANCP] ANCP Framework=20
    update</SPAN></FONT><O:P></O:P></DIV></DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times =
New Roman'"><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">I've=20
    been updating the ANCP framework draft according to the suggested =
changes=20
    from Roberta and Francois. Below I have copy-pasted the sections =
that have=20
    undergone changes.<I><SPAN style=3D"FONT-STYLE: italic"><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN>Indented =
text</SPAN></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN>has been changed. I think =
I=20
    captured the essence of the notion of "bandwidth delegation". Please =
review=20
    and see if this is capturing the =
agreements.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><O:P></O:P></P>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times =
New Roman'"><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">3.4.2.&nbsp;=20
    Multicast Admission Control</SPAN></FONT></B><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; The =
successful=20
    delivery of Triple Play Broadband services is =
quickly</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; becoming =
a big=20
    capacity planning challenge for most of the =
Service</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Providers =

    nowadays.&nbsp; Solely increasing available bandwidth is=20
    not</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; always =
practical,=20
    cost-economical and/or sufficient to satisfy end</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; user =
experience=20
    given not only the strict requirements of unicast</SPAN></FONT><SPAN =

    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; delay =
sensitive=20
    applications like VoIP and Video, but also the =
fast</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; growth of =
multicast=20
    interactive applications such as</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
videoconferencing,=20
    digital TV, digital audio, online movies and</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; networked =

    gaming.&nbsp; These applications are typically characterized=20
    by</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; a delay =
sensitive=20
    nature, an extremely loss sensitive nature and</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; intensive =
bandwidth=20
    requirements.&nbsp; They are also typically "non-</SPAN></FONT><SPAN =

    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; elastic", =
which=20
    means that they operate at a fixed bandwidth, =
that</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; cannot be =

    dynamically adjusted to the currently available=20
    bandwidth.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Therefore =
a=20
    Connection Admission Control (CAC) mechanism =
covering</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; admission =
of=20
    multicast traffic over the DSL Broadband access =
is</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; required, =
in order=20
    to avoid oversubscribing the available bandwidth</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; and =
negatively=20
    impacting the end user experience.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
Considering=20
    specifically admission control over the access =
line,</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; before =
honoring a=20
    user request to join a new multicast flow, the</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
combination of AN=20
    and NAS MUST ensure admission control is =
performed</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; to =
validate that=20
    there is enough "video" bandwidth remaining on =
the</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; access =
line to=20
    carry the new flow (in addition to all other =
existing</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; multicast =
and=20
    unicast video traffic).&nbsp; The solution needs to =
cope</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; with =
multiple flows=20
    per access line and needs to allow access line</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; bandwidth =
to be=20
    dynamically shared across multicast and unicast</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; traffic=20
    (irrespective of whether unicast CAC is performed by NAS=20
    or</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; by some =
off-path=20
    Policy Server).</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Thus, =
supporting=20
    CAC for the access line requires some form of</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; =
synchronization=20
    between the entity performing multicast CAC (e.g. =
the</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; NAS or =
the AN) and=20
    the entity performing unicast CAC (e.g. the NAS =
or</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; a Policy =
Server)=20
    and the entity actually enforcing the multicast<SPAN=20
    class=3D734534408-22102008><FONT color=3D#0000ff>&nbsp; [T.H.: Is =
that correct=20
    as stated "NAS or Policy server"?; My understanding: Policy Server:=20
    Policy&nbsp;decission point;&nbsp;NAS controls AN&nbsp;by ANCP;AN: =
policy=20
    enforcement point]&nbsp;</FONT></SPAN></SPAN>&nbsp;<BR><FONT =
face=3DArial=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    replication (i.e. the AN).&nbsp; This synchronization can be =
achieved in=20
    a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; number of =

    ways:</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; One approach is for the AN to query the NAS so that=20
    Admission</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Control for the access line is performed by the NAS (possibly=20
    with</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    interactions with a Policy Server).&nbsp; This can be done with=20
    or</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    without "bandwidth delegation" to the =
AN.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    *&nbsp; In case of Admission Control without AN Bandwidth=20
    Delegation,</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the AN can use ANCP to query the NAS, that in turn=20
    performs</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast Admission Control check for the new multicast=20
    flow</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    and responds to the AN indicating whether the join is to=20
    be</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    honored (and hence replication performed by the AN) or=20
    denied.</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    The NAS may locally maintain available "video" bandwidth&nbsp;<FONT=20
    color=3D#0000ff><SPAN =
class=3D734534408-22102008>&nbsp;[T.H.:]&nbsp;</SPAN><SPAN=20
    class=3D734534408-22102008>&nbsp;(net data =
rate)&nbsp;</SPAN></FONT>on=20
    the</SPAN><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Loop, and perform video bandwidth accounting for=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Loop.&nbsp; Upon receiving an Admission Request from the=20
    AN,</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the NAS can check available "video" bandwidth before=20
    admitting</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    or denying the multicast flow.&nbsp; In the process, the NAS=20
    may</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    communicate with the Policy Server.&nbsp; For unicast video=20
    services</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    such as Video on Demand (VoD), the NAS may also be queried=20
    (by</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    a Policy Server or via on-path CAC signaling), so that it=20
    can</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    perform admission control for the unicast flow, and update=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    available video bandwidth maintained by the=20
    NAS.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    *&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    NAS (possibly with interactions with a Policy Server)=20
    manages</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    total bandwidth for video admission, performs unicast=20
    admission</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    control and uses ANCP to delegate a certain amount of=20
    bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    for some multicast flows to the Access Node.&nbsp; In this=20
    scenario,</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    upon receiving a join to a multicast flow which matches=20
    an</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    entry in the White or Grey List whose entry is flagged=20
    as</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    "Bandwidth Delegation", the AN must perform the=20
    necessary</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    bandwidth admission control check for the new multicast=20
    flow,</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    before starting the multicast flow=20
    replication.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    The ANCP requirements to support this approach are specified=20
    in</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    this document.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
In case the=20
    subscriber communicates the "join/leave" =
information</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    with the NAS (e.g. by terminating all subscriber IGMP signaling=20
    on</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the NAS, or by using some form of application level=20
    signaling),</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the approach is very similar.&nbsp; In this case, the NAS may=20
    locally</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    maintain available "video" bandwidth on the Access Loop,=20
    perform</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    video bandwidth accounting, and perform CAC for unicast=20
    and</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flows.&nbsp; The NAS can set the replication state on the=20
    AN</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    using ANCP if the flow is admitted.&nbsp; For unicast video=20
    services</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the NAS may be queried (by a policy server or via on-path=20
    CAC</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    signaling) to perform admission control for the unicast flow,=20
    and</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    update the available video bandwidth maintained by the NAS.&nbsp;=20
    The</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP requirements to support this approach (where the AN=20
    queries</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the NAS) are specified in this =
document;</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
In a third=20
    approach, the Policy Server queries the AN directly =
so</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    that both unicast and multicast CAC for the access line=20
    are</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    performed by the AN.&nbsp; In this case, a subscriber request for=20
    a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    unicast flow (e.g. a Video on Demand session) will trigger=20
    a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    resource request message towards a Policy Server; the latter=20
    will</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    then query the AN, that in turn will perform unicast CAC for=20
    the</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    access line and respond, indicating whether the unicast request=20
    is</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    to be honored or denied.&nbsp; In this scenario the Policy=20
    Server</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    queries the AN directly, the approach doesn't require the use=20
    of</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP.&nbsp; It is therefore beyond the scope of this=20
    document.</SPAN></FONT><O:P></O:P></P>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times =
New Roman'"><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">4.2.&nbsp;=20
    ANCP Multicast Requirements</SPAN></FONT></B><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST support providing multicast conditional =
access</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    information to Access Ports on an Access Node, using Black,=20
    Grey</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    and White lists.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST support binding a particular Black, Grey and =
White</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List to a given Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    receiving a join to a multicast flow which matches the=20
    Grey</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List the ANCP MUST allow the AN to query the NAS to request=20
    an</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    admission decision for replicating that multicast flow to=20
    a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    particular Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST allow the NAS to send an admission decision to =
the</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    AN indicating whether or not a multicast flow may be replicated=20
    to</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=20
    particular Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; The ANCP must allow the NAS to indicate to the AN whether or =

    not</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Admission Control is needed for some multicast flows on a=20
    given</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Port and where needed whether or not it is to be=20
    performed</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    with AN Bandwidth Delegation.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control without AN Bandwidth =
Delegation,=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP must allow the NAS to reply to a query from the AN=20
    indicating</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    whether or not a multicast flow may be replicated to a=20
    particular</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP must allow the NAS to delegate a certain amount of=20
    bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    to the AN for a given Access Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP must allow the AN to query the NAS to request=20
    additional</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast bandwidth on a given Access =
Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP must allow the NAS to query (or to instruct) the AN to=20
    reduce</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the amount of bandwidth previously delegated on a given=20
    Access</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP must allow the AN to autonomous release redundant=20
    multicast</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    bandwidth on a given Access Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST allow the AN to send an Information Report =
message</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    to the NAS whenever replication of a multicast flow on =
a</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    particular Access Port start or ends.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST allow the AN to send an Information Report =
message</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    to the NAS indicating the multicast traffic volume that has=20
    been</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    replicated on that port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST allow the NAS to indicate to the AN whether or =
not</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    particular Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
In case=20
    multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    particular Access Port, the ANCP MUST allow the NAS to indicate=20
    to</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the AN whether or not additional volume accounting information=20
    is</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    required.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST allow the NAS to revoke a decision to replicate =
a</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flow to a particular Access Port, which had=20
    been</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    conveyed earlier to an AN.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST support partial updates of the White, Grey and =
Black</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    lists.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The ANCP=20
    MUST allow the NAS to query the AN to obtain =
information</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    on what multicast flows are currently being replicated on a=20
    given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Port, what Access Ports are currently receiving a=20
    given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flow, or what multicast flows are currently=20
    replicated</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    on each Access Port.</SPAN></FONT><O:P></O:P></P>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times =
New Roman'"><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Access Node=20
    multicast requirements (section =
4.7.6)</SPAN></FONT></B><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The AN must=20
    deny any join to a multicast flow matching the =
Black</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List for the relevant Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; The AN must accept any join to a multicast flow matching the =

    White</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List and not flagged as "Bandwidth Delegation" for the=20
    relevant</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a join to a multicast flow which matches the=20
    White</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List whose entry is flagged as "Bandwidth Delegation" for=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    relevant Access Port, the AN must perform the necessary=20
    bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    admission control check for the new flow before starting=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flow replication.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a join to a multicast flow which matches the=20
    Grey</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List whose entry is flagged as "no Bandwidth Delegation" for=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    relevant Access Port, the AN must support using ANCP to query=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    NAS to receive a response indicating whether that join is to=20
    be</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    honored or denied.&nbsp; In this case, the NAS will perform both=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    necessary conditional access and the admission control checks=20
    for</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the new flow.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a join to a multicast flow which matches the=20
    Grey</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List whose entry is flagged as "Bandwidth Delegation" for=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    relevant Access Port, the AN must first perform the=20
    necessary</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    bandwidth admission control check for the new flow.&nbsp;=20
    If</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    successful, the AN must support using ANCP to query the NAS=20
    to</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    receive a response indicating whether that join is to be=20
    honored</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    or denied.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation, =
the=20
    AN</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    must support using ANCP to notify the NAS when the the user=20
    leaves</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the multicast flow.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation, =
the=20
    AN</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    must support using ANCP to query the NAS to request=20
    additional</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    delegated multicast bandwidth on a given Access Port; the=20
    AN</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    should be able to specify both the minimum and the=20
    preferred</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    amount of additional multicast bandwidth=20
    requested.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    upon</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    receiving a Bandwidth Delegation Request from the NAS querying=20
    or</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    instructing to decrease the delegated multicast bandwidth on=20
    a</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    given Access Port, the AN must support using ANCP to send=20
    a</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Bandwidth Delegation Response indicating the new=20
    delegated</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast bandwidth.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation, =
the=20
    AN</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    must support using ANCP to send a Bandwidth Release message to=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    NAS in order to release unused delegated multicast bandwidth on=20
    a</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    given Access Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
If the=20
    requested multicast flow is not part of any list=20
    associated</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    with the Access Port, the AN must discard the=20
    message.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
If the=20
    requested multicast flow is part of multiple =
lists</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    associated with the Access Port, the AN must use the most=20
    specific</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    match.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
If the=20
    requested multicast flow has the same most specific =
match</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    in multiple lists, the AN must give precedence to the Black=20
    list,</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    followed by the Grey list, and then the White=20
    list.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The AN must=20
    support configuring a "catch-all" statement in =
the</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Black, White or Grey list in order to enforce a default=20
    behavior</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    for a join to a multicast flow which doesn't match any other=20
    entry</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    in a list for the relevant Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    querying the NAS, the AN must not propagate the join=20
    message</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    before the successful authorization from the NAS is=20
    received.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    receiving a leave for a multicast flow which matches the=20
    Grey</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    List, the AN should be able to autonomously stop replication=20
    and</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    advertise this event to the NAS.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The AN must=20
    support using ANCP to send an Information Report</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    message to the NAS whenever replication starts or ends<SPAN=20
    class=3D734534408-22102008><FONT color=3D#0000ff>&nbsp; [T.H:] or=20
    fails&nbsp;</FONT></SPAN>.</SPAN><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The AN=20
    should support using ANCP to send an Information =
Report</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    message to the NAS indicating the multicast traffic volume=20
    that</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    has been replicated on that port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    request by the NAS, the AN must support using ANCP to send=20
    an</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Information Report message to the NAS, indicating what=20
    multicast</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    flows are currently being replicated on a given Access=20
    Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    request by the NAS, the AN must support using ANCP to send=20
    an</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Information Report message to the NAS, indicating what=20
    Access</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Ports are currently receiving a given multicast=20
    flow.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    request by the NAS, the AN must support using ANCP to send=20
    an</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Information Report message to the NAS, indicating what=20
    multicast</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    flows are currently being replicated on each Access=20
    Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
Upon=20
    receiving an Admission Response from the NAS, indicating=20
    that</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    replication of a multicast flow is to start or stop on a=20
    given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    access port of the AN, the AN must enforce this decision.&nbsp;=20
    This</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    decision must be taken irrespective of whether or not =
a</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    corresponding Admission Request was issued by the AN earlier=20
    on.</SPAN></FONT><O:P></O:P></P>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: 'Times =
New Roman'"><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></DIV>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><B><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Arial">NAS =

    multication requirements (section =
4.8.6)</SPAN></FONT></B><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to configure multicast=20
    conditional</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    access information to Access Ports on an Access Node, using=20
    Black</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Lists, Grey Lists and White Lists.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; The NAS must support using ANCP to indicate to the AN =
whether=20
    or</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    not Admission Control is needed for some multicast flows on=20
    a</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    given Access Port and where needed whether or not it is to=20
    be</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    performed with AN Bandwidth =
Delegation.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a query from the AN for a request to =
replicate=20
    a</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flow to a particular Access Port, and no AN=20
    Bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Delegation is needed for that flow, the NAS must be able=20
    to</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    perform the necessary checks (conditional access and/or=20
    admission</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    control) for the new flow.&nbsp; The NAS must support using ANCP=20
    to</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    reply to the AN indicating whether the request is to be honored=20
    or</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    denied.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a query from the AN for a request to =
replicate=20
    a</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flow to a particular Access Port, and Admission=20
    Control</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    with AN Bandwidth Delegation is needed for that flow, the NAS=20
    must</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    be able to perform the conditional access checks (if needed),=20
    and</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    must support using ANCP to delegate a certain amount of=20
    bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    to the AN for a given Access Port.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    upon</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    receiving a Bandwidth Delegation Request from the AN requesting=20
    to</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    increase the delegated multicast bandwidth on a given Access=20
    Port,</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the NAS must support using ANCP to send a Bandwidth=20
    Delegation</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Response indicating the new delegating multicast=20
    bandwidth.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation, =
the=20
    NAS</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    must support using ANCP to send a request the AN to decrease=20
    the</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    amount of multicast bandwidth previously delegated on a=20
    given</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Access Port; the NAS should be able to specify both the=20
    minimum</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    and the preferred amount decrement of multicast=20
    bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    requested.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><I><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;=20
    o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
    upon</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    receiving an ANCP Bandwidth Release message, the NAS must be=20
    able</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    to update accordingly its view of the multicast=20
    bandwidth</SPAN></FONT></I><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><I><FONT face=3DArial =

    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    delegated to the AN.</SPAN></FONT></I><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to configure the Access Node =
with</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the "maximum number of multicast streams" allowed to be=20
    received</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    concurrently per Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to incrementally add, remove =
and</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    modify individual entries in White, Black and Grey=20
    lists.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to indicate to the AN whether =
or</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    not multicast accounting is needed for a multicast flow on=20
    a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    particular Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
In case=20
    multicast accounting is needed for a multicast flow on =
a</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    particular Access Port, the NAS should support using ANCP=20
    to</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    indicate to the AN whether or not additional volume=20
    accounting</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    information is required.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to query the AN to obtain</SPAN></FONT><SPAN =

    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    information on what multicast flows are currently replicated on=20
    a</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    given Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to query the AN to obtain</SPAN></FONT><SPAN =

    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    information on what Access Ports are currently receiving a=20
    given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    multicast flow.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    must support using ANCP to query the AN to obtain</SPAN></FONT><SPAN =

    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    information on what multicast flows are currently replicated=20
    on</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    each Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
When=20
    Multicast replication occurs on the AN, the NAS must=20
    support</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    using ANCP to revoke the authorization to replicate a=20
    multicast</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    flow to a particular Access Port.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; o&nbsp; =
The NAS=20
    should support using ANCP to indicate to the AN =
that</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    replication of a multicast flow is to start or stop on a=20
    given</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    access port of the AN, without having received a=20
    corresponding</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Admission Request from the AN earlier =
on.</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">---</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sven=20
    Ooghe</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Alcatel-Lucent</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">CTO Office, Access=20
    Division</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Copernicuslaan 50, =
2018 Antwerp,=20
    Belgium</SPAN></FONT><SPAN=20
    class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT face=3DArial =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">tel.: +32 3 240 42=20
    26</SPAN></FONT><SPAN =
class=3DApple-converted-space>&nbsp;</SPAN><BR><FONT=20
    face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">fax: +32=20
    3 240 40 73</SPAN></FONT><O:P></O:P></P>
    <P=20
    style=3D"FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; =
FONT-FAMILY: 'Times New Roman'"><FONT=20
    face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">This=20
    message (including any attachments) contains confidential =
information=20
    intended for a specific individual and purpose, and is protected by=20
    law.&nbsp; If you are not the intended recipient, you should delete =
this=20
    message.&nbsp; Any disclosure, copying, or distribution of this =
message, or=20
    the taking of any action based on it, is strictly prohibited without =
the=20
    prior consent of its=20
    =
author.</SPAN></FONT><O:P></O:P></P></DIV>_______________________________=
________________<BR>ANCP=20
    mailing list<BR><A style=3D"COLOR: blue; TEXT-DECORATION: underline" =

    href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR><A=20
    style=3D"COLOR: blue; TEXT-DECORATION: underline"=20
    =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></DIV></SPAN></BLOCKQUOTE></DIV><BR></DIV>__=
_____________________________________________<BR>ANCP=20
  mailing list<BR><A=20
  =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR>https://www.ietf.org/m=
ailman/listinfo/ancp<BR></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>

--Boundary_(ID_ZgGJrD8UKnKWn6RfUzrXKw)--

--Boundary_(ID_jGVfE8ggj3mXr9OY9kYZBA)
Content-id: <131585201@25102008-2EFF>
Content-type: image/jpeg; name=outlook_huawei_logo_cn.jpg
Content-transfer-encoding: base64
Content-disposition: attachment; filename=outlook_huawei_logo_cn.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/7QxmUGhvdG9zaG9wIDMuMAA4QklNBCUAAAAAABAAAAAAAAAA
AAAAAAAAAAAAOEJJTQPtAAAAAAAQAEgAAAABAAIASAAAAAEAAjhCSU0EJgAAAAAADgAAAAAAAAAA
AAA/gAAAOEJJTQQNAAAAAAAEAAAAHjhCSU0EGQAAAAAABAAAAB44QklNA/MAAAAAAAkAAAAAAAAA
AAEAOEJJTQQKAAAAAAABAAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgAB
AGxmZgAGAAAAAAABAC9mZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0A
AAAGAAAAAAABOEJJTQP4AAAAAABwAAD/////////////////////////////A+gAAAAA////////
/////////////////////wPoAAAAAP////////////////////////////8D6AAAAAD/////////
////////////////////A+gAADhCSU0EAAAAAAAAAgAAOEJJTQQCAAAAAAACAAA4QklNBDAAAAAA
AAEBADhCSU0ELQAAAAAABgABAAAABjhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBB4A
AAAAAAQAAAAAOEJJTQQaAAAAAAM9AAAABgAAAAAAAAAAAAAAIAAAAGYAAAAEAGwAbwBnAG8AAAAB
AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAGYAAAAgAAAAAAAAAAAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAAAAAAAAAEAAAAAEAAAAAAABudWxsAAAAAgAAAAZib3VuZHNPYmpjAAAAAQAAAAAA
AFJjdDEAAAAEAAAAAFRvcCBsb25nAAAAAAAAAABMZWZ0bG9uZwAAAAAAAAAAQnRvbWxvbmcAAAAg
AAAAAFJnaHRsb25nAAAAZgAAAAZzbGljZXNWbExzAAAAAU9iamMAAAABAAAAAAAFc2xpY2UAAAAS
AAAAB3NsaWNlSURsb25nAAAAAAAAAAdncm91cElEbG9uZwAAAAAAAAAGb3JpZ2luZW51bQAAAAxF
U2xpY2VPcmlnaW4AAAANYXV0b0dlbmVyYXRlZAAAAABUeXBlZW51bQAAAApFU2xpY2VUeXBlAAAA
AEltZyAAAAAGYm91bmRzT2JqYwAAAAEAAAAAAABSY3QxAAAABAAAAABUb3AgbG9uZwAAAAAAAAAA
TGVmdGxvbmcAAAAAAAAAAEJ0b21sb25nAAAAIAAAAABSZ2h0bG9uZwAAAGYAAAADdXJsVEVYVAAA
AAEAAAAAAABudWxsVEVYVAAAAAEAAAAAAABNc2dlVEVYVAAAAAEAAAAAAAZhbHRUYWdURVhUAAAA
AQAAAAAADmNlbGxUZXh0SXNIVE1MYm9vbAEAAAAIY2VsbFRleHRURVhUAAAAAQAAAAAACWhvcnpB
bGlnbmVudW0AAAAPRVNsaWNlSG9yekFsaWduAAAAB2RlZmF1bHQAAAAJdmVydEFsaWduZW51bQAA
AA9FU2xpY2VWZXJ0QWxpZ24AAAAHZGVmYXVsdAAAAAtiZ0NvbG9yVHlwZWVudW0AAAARRVNsaWNl
QkdDb2xvclR5cGUAAAAATm9uZQAAAAl0b3BPdXRzZXRsb25nAAAAAAAAAApsZWZ0T3V0c2V0bG9u
ZwAAAAAAAAAMYm90dG9tT3V0c2V0bG9uZwAAAAAAAAALcmlnaHRPdXRzZXRsb25nAAAAAAA4QklN
BCgAAAAAAAwAAAABP/AAAAAAAAA4QklNBBEAAAAAAAEBADhCSU0EFAAAAAAABAAAAAg4QklNBAwA
AAAABnAAAAABAAAAZgAAACAAAAE0AAAmgAAABlQAGAAB/9j/4AAQSkZJRgABAgAASABIAAD/7QAM
QWRvYmVfQ00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUT
ExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4O
Dg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMB
IgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEB
AAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSR
obFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSF
tJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIR
AyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVV
NnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEA
AhEDEQA/APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC6
6f56f3t30Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUs
VaDHl/dl/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5Vtns
U/qp1vqPUvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9
w9+kqfV+qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVh
fWLCzerW9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX
146P1azqFWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKeh
SWDk/XHpVHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8t
bvSU9Ikucy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uo
JBeNpMtfRc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxb
qtG20uI0PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv
/QXjOu9COI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5F
ztrrn/usXoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4
HX+6yY/jQHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v
6hNyW9Q6jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m
+u1tQc9n0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6
tfRj2YnTgMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJ
JT5b0bpfUrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6r
WuLnfpNjXu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z
OEJJTQQhAAAAAABVAAAAAQEAAAAPAEEAZABvAGIAZQAgAFAAaABvAHQAbwBzAGgAbwBwAAAAEwBB
AGQAbwBiAGUAIABQAGgAbwB0AG8AcwBoAG8AcAAgAEMAUwAyAAAAAQA4QklNBAYAAAAAAAcABQAA
AAEBAP/hB4ZFeGlmAABJSSoACAAAAAcAEgEDAAEAAAABAAAAGgEFAAEAAABiAAAAGwEFAAEAAABq
AAAAKAEDAAEAAAACAAAAMQECABwAAAByAAAAMgECABQAAACOAAAAaYcEAAEAAACiAAAAzAAAAID8
CgAQJwAAgPwKABAnAABBZG9iZSBQaG90b3Nob3AgQ1MyIFdpbmRvd3MAMjAwNzowMjoyNiAxNjox
ODo1MwADAAGgAwABAAAA/////wKgBAABAAAAZgAAAAOgBAABAAAAIAAAAAAAAAAGAAMBAwABAAAA
BgAAABoBBQABAAAAGgEAABsBBQABAAAAIgEAACgBAwABAAAAAgAAAAECBAABAAAAKgEAAAICBAAB
AAAAVAYAAAAAAABIAAAAAQAAAEgAAAABAAAA/9j/4AAQSkZJRgABAgAASABIAAD/7QAMQWRvYmVf
Q00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwM
DAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwM
DAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMBIgACEQED
EQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAA
AAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQV
UsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0
pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRB
UWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKz
hMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/
APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC66f56f3t3
0Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUsVaDHl/dl
/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5VtnsU/qp1vqP
UvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9w9+kqfV+
qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVhfWLCzerW
9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX146P1azq
FWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKehSWDk/XHp
VHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8tbvSU9Iku
cy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uoJBeNpMtf
Rc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxbqtG20uI0
PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv/QXjOu9C
OI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5Fztrrn/us
XoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4HX+6yY/j
QHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v6hNyW9Q6
jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m+u1tQc9n
0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6tfRj2YnT
gMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJJT5b0bpf
UrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6rWuLnfpNj
Xu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z/9sAQwAI
BgYHBgUIBwcHCQkICgwUDQwLCwwZEhMPFB0aHx4dGhwcICQuJyAiLCMcHCg3KSwwMTQ0NB8nOT04
MjwuMzQy/9sAQwEJCQkMCwwYDQ0YMiEcITIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIy/8AAEQgAIABmAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAA
AAABAgMEBQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGh
CCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV
1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkK
C//EALURAAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy
0QoWJDThJfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKD
hIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm
5+jp6vLz9PX29/j5+v/aAAwDAQACEQMRAD8A99LKCASAT0FcOvxDin8XjRre2Bt1l8mS4Zud3Tge
ma5X4j67qukeObG5hdkhto1e3H8L5+9n1z0rnriVIvF9pqdmP9E1CdLiPn7pLDcp9wcj8q8+vimn
yx0sz6zLsihOj7WtrzxbXk/87a/f2PazrqpqL27oBEsnlhwec+4rYyCSM8jtXj0OupJ4hvZbhytr
aSvNOfYHhfqTgVJ4G8R6nrfxAuLklzbTRMZlz8qKPu/THSnSxT5rS1u9Dlr5HNU5VVooxu/8vX/g
dz1+iszX9at/Dug3mr3Su9vax+Y4jGWI9qz9U8ZafpXgtfFE0U7WTQpKEVRvw2McZ967z506Oiuf
03xbY6n4juNDhjmFzBaR3bMw+Xa4BA+vIp2leKrHV9d1nSIElSfSXVJ2cAKdwyMH8KAN6iuM0P4l
6J4hn1eDTkuJJdNRpCpUAzICQWTnkZFK/wASdEj8Ar4wInNiSF8sKPMD7tu3GcZBoA7KiuSu/iDo
9p4NsvE22eW0vWRII41BkZ2OAuM9Rg/lVbUviXptnq82lWem6pql7bgfaUsbfzBCT2Y5xn2oA7ai
uB134q6V4b0nTb7VdM1K3N/v2W7xASJtOPmGeOtFAHnupab4l8P3s+kX+nT6ro/mFoCVLgAngo45
RvUfpWr4a8NnUmFrB5qwxyrcol0hSS3YEZB7MrDjI74r0TxX4MtPFSRNLd3VpcRcLNbyEHHcEdDV
zQPDGn+G7XyrNZHdv9ZPM5d3+p/oK4/q153ex9Is9ccNyrSfktL93/wN+uh5n4m8NNp8ssEvm+Rc
TtcyC2QvJOSTtUDsqjue5NZumaX4h1meLStP06fTNLLgzHaV3Ad3c8sfbp7V7Frnh6w8QWohvEcM
v3JYmKun0P8AjVHwx4PtfDJleO7urueQYMk75wvoB0FTLC+/psa0s/UcLaWtRbXWl++/57dNCp8S
reR/hjrlvBG8shtNqqilmbkdhXmniXwPqEPweS7XW/EFzKbWE/2dI+6MHjK7MZwP6V73RXcfLHj8
V+3g34ivrOq2F9/ZmoaPbwx3MFu0oWRAMqwUZB4rDe/1hIPGWsaXpl/HJ4lu4rPTPMhZXIwQ0hGM
qAO59a98ooA8Fl0Dxb4DvvDmuXNnp8tlpiiwnTTUdpJIHPJcEc4Jzx3pkOgagvj2HwV9gmfw+dY/
thZmQ+X5XllvLPGOuePWvfaKAPBfD2iapL48svB91ZTLpGhalPqKTsp2SKeY1B6cE5/Oqg0u58Le
LfEMes33imwjvLs3FvcaOheKdSSfmwCcjOK+haKAPm34sWlxqvhPwrJpi6zqcY8/M13CxnPzD74x
ke3tRX0lRQB//9k=

--Boundary_(ID_jGVfE8ggj3mXr9OY9kYZBA)--

--===============0143481189==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0143481189==--


From ancp-bounces@ietf.org  Sun Oct 26 08:45:28 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 430BD3A69EE;
	Sun, 26 Oct 2008 08:45:28 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8FC23A69D7
	for <ancp@core3.amsl.com>; Sun, 26 Oct 2008 08:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 0wQfCs4GfKPQ for <ancp@core3.amsl.com>;
	Sun, 26 Oct 2008 08:45:24 -0700 (PDT)
Received: from dtc035.detecon.net (dtc035.detecon.net [194.25.60.135])
	by core3.amsl.com (Postfix) with ESMTP id 348833A68CE
	for <ancp@ietf.org>; Sun, 26 Oct 2008 08:45:23 -0700 (PDT)
Received: from unknown (HELO dc00357.detecon.com) ([172.16.10.107])
	by relay.dtc035.detecon.net with ESMTP; 26 Oct 2008 16:44:01 +0100
Received: from DC00331.detecon.com ([172.16.10.78]) by dc00357.detecon.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Sun, 26 Oct 2008 16:46:39 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 16:46:39 +0100
Message-ID: <D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DOA (was:[ANCP] ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScg=
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com>
	<7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Reith, Lothar" <Lothar.Reith@detecon.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 26 Oct 2008 15:46:39.0943 (UTC)
	FILETIME=[09617D70:01C93782]
Subject: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1013482781=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1013482781==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93782.08F2ED81"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93782.08F2ED81
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,
=20
the ANCP Framework contains the word "delegation", which in my mind is =
key to the whole concept of ANCP.=20
=20
I would like to suggest that the concept of "delegation" should be made =
more extensible.=20
=20
Narrowing it to the term "bandwidth delegation" does not lend itself =
very well to extensibility.
=20
I would rather propose to introduce the more general term of DOA =
(Delegation of Authority), which is a well known concept in the real =
world, when a resource owner delegates control over part or all of his =
resources to someone else - e.g. during a vacation absence.
=20
Today, ANCP does not just support delegation in the form of bandwidth =
delegation, but also in the form of delegation of content access control =
(delegation occurs for whitelist and blacklist content, but not for the =
greylist content).
=20
I think the extensible concept "DOA" is very powerful when harnessed for =
Broadband Access using ANCP.
=20
While updating the framework it may be worth a consideration to add this =
hook for extensibility by following means:
=20
- replace the term "bandwidth delegation" by "DOA for part of access =
circuit bandwidth"
=20
- introduce the first extension of the DOA concept by making clear that =
the concepts of  whitelist and blacklist are DOA for Content Access =
Control.
=20
One more point with respect to the recent discussion about renaming the =
Policy Server.
=20
I like to state that I am fine with the current name "policy server".  =
Historically, I beleive the name was chosen as a compromise between the =
RADIUS camp and the COPS camp.
=20
If - given this background - we still want to change the name of the =
policy server, then perhaps DOA-server may be another alternative to =
consider.=20
=20
An important argument in this case would be, that the concept of =
"delegation of authority" is well aligned with the proxy concept, =
similar to a RADIUS Proxy Server, where the delegation of authority =
happens along a delegation chain which may span multiple RADIUS proxy =
servers and multiple domains. This aspect is missing in the other =
proposed names.
=20
Best Regards,
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20

________________________________

Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
Gesendet: Do 23.10.2008 12:57
An: ancp@ietf.org
Betreff: Re: [ANCP] ANCP Framework update


Hi,
=20
Here's the updated text. I removed any notion of "flags" or how the =
Access Node is told whether or not Bandwidth Delegation applies. I also =
covered Thomas' comments. Actually not that much work: the general ANCP =
requirements as well as the NAS requirements were written in a =
high-level way already. I only had to update the general text and some =
of the Access Node requirements. Below the extracted text, let me know =
your comments.
=20
Regards,
Sven
=20
---
=20
General text
=20
   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.
=20
      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop (as a portion of the Access Loop net data rate),
         and perform video bandwidth accounting for the Access Loop.
         Upon receiving an Admission Request from the AN, the NAS can
         check available "video" bandwidth before admitting or denying
         the multicast flow.  In the process, the NAS may communicate
         with the Policy Server.  For unicast video services such as
         Video on Demand (VoD), the NAS may also be queried (by a Policy
         Server or via on-path CAC signaling), so that it can perform
         admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.
=20
      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List, the AN must perform the
         necessary bandwidth admission control check for the new
         multicast flow, before starting the multicast flow replication.

Access Node requirements
=20
   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.
=20
   o  The AN must accept any join to a multicast flow matching the White
      List and for which no Bandwidth Delegation is required.
=20
   o  Upon receiving a join to a multicast flow which matches the White
      List whose and for which Bandwidth Delegation is required, the AN
      must perform the necessary bandwidth admission control check for
      the new flow before starting the multicast flow replication.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which no Bandwidth Delegation is required, the AN
      must support using ANCP to query the NAS to receive a response
      indicating whether that join is to be honored or denied.  In this
      case, the NAS will perform both the necessary conditional access
      and the admission control checks for the new flow.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which Bandwidth Delegation is required, the AN must
      first perform the necessary bandwidth admission control check for
      the new flow.  If successful, the AN must support using ANCP to
      query the NAS to receive a response indicating whether that join
      is to be honored or denied.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.
=20
Regards,
Sven

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:58
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update




On 20 Oct 2008, at 12:22, OOGHE Sven wrote:


	Francois,
	=20
	Another approach we could take is to let the framework requirements be =
agnostic as to how the Access Node knows whether or not Bandwidth =
Delegation applies. We could describe the notion of Bandwidth Delegation =
and the respective requirements for the Access Node and NAS in this =
case.
	=20
	The details of how the use of Bandwidth Delegation is communicated to =
the Access Node - using a flag, some "on/off" knob or both - would be =
left to the actual protocol specification work.


Good idea. It will avoid these cross dependencies between framework and =
protocol, which indeed reflect that we are probably trying to be too =
precise/prescriptive in the framework.


	=20
	I think following this path would require relatively small edits to the =
document. I'm ok to take a first shot at it.


That would be good.

Thanks

Francois


	=20
	Regards,
	Sven

________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update
=09
=09
	Sven and all,=20
=09
=09

		   o  Upon receiving a join to a multicast flow which matches the Grey =

		      List whose entry is flagged as "no Bandwidth Delegation" for the =

		      relevant Access Port, the AN must support using ANCP to query =
the=20
		      NAS to receive a response indicating whether that join is to be=20
		      honored or denied.  In this case, the NAS will perform both the=20
		      necessary conditional access and the admission control checks =
for=20
		      the new flow.


	Roberta, Tom and myself have started drafting an I-D that will propose =
ANCP protocol extensions supporting some of those requirements (building =
on top of ancp-mc-multicast).
	In doing so, we revisited a point that came up multiple times: do we =
really need to provision a flag in each and every Grey/White List entry =
to activate/deactivate Bandwidth Delegation?
=09
=09
	The current approach (as correctly reflected in the updated Framework) =
is:
	* define a flag in each Grey/White List entry
=09
	* assume that this flag will normally either always be set in all =
entries or never set.
=09
	* setting/no-setting the flag is all entries effectively acts as the =
knob to enable/disable Bandwidth Delegation, therefore we did not need =
to specify a specific knob to enable/disable Bandwidth Delegation.
=09
=09
=09
	Another approach would be:
	* remove flag from White/Grey list entries
=09
	* define a specific knob to enable/disable Bandwidth Delegation at the =
AN granularity
	* in fact, define a generic AN-level provisioning method that could be =
used to enable/disable BAndwidth delegation, but could also be used for =
provisioning the "Service Profiles" that are currently assumed to be =
configured in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles
=09
=09
=09
	Considering that:
	- we got several times the feedback that per-entry BAndwidth Delegation =
flag was confusing since Bandwidth Delegation granularity is more =
AN-level (and may lead to difficulties if it is set on some entries and =
not on others)
	- it is likely that we'll need, anyways, a mechanism to provision =
things at AN level, that could be easily used to convey Bandwidth =
Delegation enable/disable knob.
=09
	we would like to propose to evolve to the newer approach.
=09
=09
	Thoughts?

	Francois

	PS: Sven, if we go for the new approach, we can document in an email =
the deltas that would be needed to reflect that in framework.




------_=_NextPart_001_01C93782.08F2ED81
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">=0A=
<HTML><HEAD>=0A=
=0A=
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>=0A=
<BODY =0A=
style=3D"WORD-WRAP: break-word"  >=0A=
<DIV id=3DidOWAReplyText66978 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Dear =
all,</FONT></DIV>=0A=
<DIV>=0A=
<DIV id=3DidOWAReplyText68228 dir=3Dltr>=0A=
<DIV id=3DidOWAReplyText93369 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>the ANCP Framework contains =
the word =0A=
"delegation", which in my mind is key to the whole concept of ANCP. =0A=
</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I would like to suggest that =
the concept of =0A=
"delegation" should be made more extensible. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Narrowing it to the term =
"bandwidth =0A=
delegation" does not lend itself very well to extensibility.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I would rather propose to =
introduce the =0A=
more general term of DOA (Delegation of Authority), which </FONT><FONT =0A=
face=3DArial size=3D2>is a well known concept in the real world, when a =
resource =0A=
owner delegates control over part or all of his resources to someone =
else - e.g. =0A=
during a vacation absence.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Today, ANCP does not just =
support =0A=
delegation in the form of bandwidth delegation, but also in the form of =0A=
delegation of content access control (delegation occurs for whitelist =
and =0A=
blacklist content, but not for the greylist content).</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think the extensible =
concept =0A=
"DOA"&nbsp;is very powerful when harnessed for Broadband Access using =0A=
ANCP.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>While updating the framework =
it may be =0A=
worth a consideration to add this hook for extensibility by following =0A=
means:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>- replace&nbsp;the term =
"bandwidth =0A=
delegation" by "DOA for part of access circuit bandwidth"</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>- introduce the first =
extension of the DOA =0A=
concept by making clear that the concepts of &nbsp;whitelist and =
blacklist are =0A=
DOA for Content Access Control.</FONT></DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>One more point with respect to the recent discussion =
about renaming =0A=
the Policy Server.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>I like to state that I am fine with the current name =
"policy =0A=
server".&nbsp;&nbsp;Historically,&nbsp;I beleive&nbsp;the name was =
chosen as a =0A=
compromise between the RADIUS camp and the COPS camp.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>If - given this background - we&nbsp;still want to change =
the name =0A=
of the policy server, then perhaps DOA-server may be another alternative =
to =0A=
consider. </DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>An important argument in this case would be, that the =
concept of =0A=
"delegation of authority" is well aligned with the proxy concept, =
similar to a =0A=
RADIUS Proxy Server, where the delegation of authority happens along a =0A=
delegation chain which may span multiple RADIUS proxy servers and =
multiple =0A=
domains. This aspect is missing in the other proposed names.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Lothar Reith</FONT></DIV>=0A=
<DIV dir=3Dltr>Detecon International GmbH (Deutsche Telekom Group)</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>Von:</B> ancp-bounces@ietf.org im =
Auftrag von OOGHE =0A=
Sven<BR><B>Gesendet:</B> Do 23.10.2008 12:57<BR><B>An:</B> =0A=
ancp@ietf.org<BR><B>Betreff:</B> Re: [ANCP] ANCP Framework =0A=
update<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>Here's the updated text. I removed any notion =
of "flags" or =0A=
how the Access Node is told whether or not Bandwidth Delegation applies. =
I also =0A=
covered Thomas' comments. Actually not that much work: the general ANCP =0A=
requirements as well as the NAS requirements were written in a =
high-level =0A=
way&nbsp;already. I only had to update the general text and some of the =
Access =0A=
Node requirements. Below the extracted text, let me know your =0A=
comments.</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>---</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2><STRONG>General =
text</STRONG></FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; One approach is for the AN =
to query =0A=
the NAS so that Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for =
the =0A=
access line is performed by the NAS (possibly =0A=
with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interactions with a Policy =
Server).&nbsp; =0A=
This can be done with or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without =
"bandwidth =0A=
delegation" to the AN.</FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In =
case of =0A=
Admission Control without AN Bandwidth =0A=
Delegation,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
can use =0A=
ANCP to query the NAS, that in turn =0A=
performs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
Admission =0A=
Control check for the new multicast =0A=
flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and responds to =
the AN =0A=
indicating whether the join is to =0A=
be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored (and =
hence =0A=
replication performed by the AN) or =0A=
denied.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may =
locally =0A=
maintain available "video" bandwidth on =0A=
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop (as =
a =0A=
portion of the Access Loop net data =0A=
rate),<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and perform =
video =0A=
bandwidth accounting for the Access =0A=
Loop.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon receiving =
an =0A=
Admission Request from the AN, the NAS =0A=
can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check available =
"video" =0A=
bandwidth before admitting or =0A=
denying<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast =0A=
flow.&nbsp; In the process, the NAS may =0A=
communicate</EM></FONT></SPAN></DIV><SPAN class=3D852244910-23102008>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =0A=
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the =
Policy =0A=
Server.&nbsp; For unicast video services such =0A=
as<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video on Demand =
(VoD), =0A=
the NAS may also be queried (by a =0A=
Policy<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server or via =
on-path =0A=
CAC signaling), so that it can =0A=
perform<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission =
control =0A=
for the unicast flow, and update =0A=
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available video =0A=
bandwidth maintained by the NAS.</EM></FONT></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =0A=
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission =
Control =0A=
with AN Bandwidth Delegation, =0A=
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS (possibly =
with =0A=
interactions with a Policy Server) =0A=
manages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for =0A=
video admission, performs unicast =0A=
admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control =
and uses =0A=
ANCP to delegate a certain amount of =0A=
bandwidth<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast =0A=
flows to the Access Node.&nbsp; In this =0A=
scenario,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =
receiving a =0A=
join to a multicast flow which matches =0A=
an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or =0A=
Grey List, the AN must perform =0A=
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
bandwidth =0A=
admission control check for the =0A=
new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow, =
before =0A=
starting the multicast flow replication.<BR></EM></FONT></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2><STRONG>Access Node =0A=
requirements</STRONG></FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must deny any join =
to a =0A=
multicast flow matching the Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
for the =0A=
relevant Access Port.</FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must accept any =
join to a =0A=
multicast flow matching the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
and for =0A=
which no Bandwidth Delegation is required.</FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a =0A=
multicast flow which matches the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List =0A=
whose and for which Bandwidth Delegation is required, the =0A=
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must perform the necessary =
bandwidth =0A=
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow =0A=
before starting the multicast flow replication.</EM></FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a =0A=
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and =0A=
for which no Bandwidth Delegation is required, the =0A=
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS to =0A=
receive a response<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating whether =
that =0A=
join is to be honored or denied.&nbsp; In =
this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
case, the NAS will perform both the necessary conditional =0A=
access<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the admission control =
checks for =0A=
the new flow.</EM></FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a =0A=
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and =0A=
for which Bandwidth Delegation is required, the AN =0A=
must<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first perform the necessary =
bandwidth =0A=
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =0A=
flow.&nbsp; If successful, the AN must support using ANCP =0A=
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the NAS to receive a response =0A=
indicating whether that join<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored =0A=
or denied.</EM></FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN =0A=
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support =0A=
using ANCP to notify the NAS when the the user =0A=
leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =
flow.</FONT></SPAN></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN =0A=
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support =0A=
using ANCP to query the NAS to request =0A=
additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated multicast =
bandwidth on a =0A=
given Access Port; the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be =
able to =0A=
specify both the minimum and the =
preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
amount of additional multicast bandwidth requested.</FONT></SPAN></DIV>=0A=
<DIV><SPAN class=3D852244910-23102008><FONT face=3DArial color=3D#0000ff =0A=
size=3D2><BR>&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN =
Bandwidth =0A=
Delegation, upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =0A=
Delegation Request from the NAS querying =
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
instructing to decrease the delegated multicast bandwidth on =0A=
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support using =0A=
ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth Delegation =
Response =0A=
indicating the new delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =0A=
bandwidth.</DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV dir=3Dltr align=3Dleft>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with =0A=
AN Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support =0A=
using ANCP to send a Bandwidth Release message to =0A=
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to release unused =
delegated =0A=
multicast bandwidth on a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access =0A=
Port.</DIV>=0A=
<DIV>&nbsp;</DIV></FONT></SPAN></SPAN>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>=0A=
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =0A=
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> maandag 20 oktober 2008 =0A=
12:58<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP; =0A=
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP Framework =0A=
update<BR></FONT><BR></DIV>=0A=
<DIV></DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial =0A=
color=3D#0000ff size=3D2></FONT><BR>=0A=
<DIV>=0A=
<DIV>On 20 Oct 2008, at 12:22, OOGHE Sven wrote:</DIV><BR =0A=
class=3DApple-interchange-newline>=0A=
<BLOCKQUOTE type=3D"cite">=0A=
  <DIV style=3D"WORD-WRAP: break-word">=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2>Another approach we could take is to let the =
framework =0A=
  requirements be agnostic as to how the Access Node knows whether or =
not =0A=
  Bandwidth Delegation applies. We could describe the notion of =
Bandwidth =0A=
  Delegation and the respective requirements for the Access Node and NAS =
in this =0A=
  case.</FONT></SPAN></DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2>The details of how the use of Bandwidth =
Delegation is =0A=
  communicated to the Access Node - using a flag, some "on/off" knob or =
both - =0A=
  would be left to the actual protocol specification =0A=
  work.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>=0A=
<DIV><BR></DIV>=0A=
<DIV>Good idea. It will avoid these cross dependencies between framework =
and =0A=
protocol, which indeed reflect that we are probably trying to be too =0A=
precise/prescriptive in&nbsp;the&nbsp;framework.</DIV><BR>=0A=
<BLOCKQUOTE type=3D"cite">=0A=
  <DIV style=3D"WORD-WRAP: break-word">=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2>I think following this path would require =
relatively =0A=
  small edits to the document. I'm ok to take a first shot at =0A=
  it.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>=0A=
<DIV><BR></DIV>=0A=
<DIV>That would be good.</DIV>=0A=
<DIV><BR></DIV>=0A=
<DIV>Thanks</DIV>=0A=
<DIV><BR></DIV>=0A=
<DIV>Francois</DIV><BR>=0A=
<BLOCKQUOTE type=3D"cite">=0A=
  <DIV style=3D"WORD-WRAP: break-word">=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>=0A=
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>=0A=
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>=0A=
  <HR tabIndex=3D-1>=0A=
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A =0A=
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>] =0A=
  <BR><B>Sent:</B> maandag 20 oktober 2008 12:01<BR><B>To:</B> OOGHE =0A=
  Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP; <A =0A=
  href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> Re: =
[ANCP] =0A=
  ANCP Framework update<BR></FONT><BR></DIV>=0A=
  <DIV></DIV>Sven and all, =0A=
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>=0A=
  <DIV>=0A=
  <DIV>=0A=
  <BLOCKQUOTE type=3D"cite">=0A=
    <DIV>=0A=
    <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to =0A=
    a multicast flow which matches the Grey</FONT></I> <BR><I><FONT =
face=3DArial =0A=
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is flagged =
as "no =0A=
    Bandwidth Delegation" for the</FONT></I> <BR><I><FONT face=3DArial =0A=
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, the AN =
must =0A=
    support using ANCP to query the</FONT></I> <BR><I><FONT face=3DArial =0A=
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a response =
indicating =0A=
    whether that join is to be</FONT></I> <BR><I><FONT face=3DArial =0A=
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; In =
this case, =0A=
    the NAS will perform both the</FONT></I> <BR><I><FONT face=3DArial =0A=
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional access =
and the =0A=
    admission control checks for</FONT></I> <BR><I><FONT face=3DArial =0A=
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =0A=
  flow.</FONT></I></P></DIV></BLOCKQUOTE><BR></DIV>=0A=
  <DIV>=0A=
  <DIV>Roberta, Tom and myself have started drafting an I-D that will =
propose =0A=
  ANCP protocol extensions supporting some of those requirements =
(building on =0A=
  top of ancp-mc-multicast).</DIV>=0A=
  <DIV>In doing so, we revisited a point that came up multiple times: do =
we =0A=
  really need to provision a flag in each and every Grey/White List =
entry =0A=
  to&nbsp;activate/deactivate&nbsp;Bandwidth Delegation?</DIV>=0A=
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial =0A=
  color=3D#0000ff size=3D2></FONT><BR></DIV>=0A=
  <DIV>The current approach (as correctly reflected in the updated =
Framework) =0A=
  is:</DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a =0A=
  flag in each Grey/White List entry<BR></DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
assume that =0A=
  this flag will normally either always be set in all entries or never =0A=
  set.<BR></DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =0A=
  setting/no-setting the flag is all entries effectively acts as the =
knob to =0A=
  enable/disable Bandwidth Delegation, therefore we did not need to =
specify a =0A=
  specific knob to enable/disable Bandwidth Delegation.<BR></DIV>=0A=
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>=0A=
  <DIV>Another approach would be:</DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
remove flag =0A=
  from White/Grey list entries<BR></DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a =0A=
  specific knob to enable/disable Bandwidth Delegation at the AN =0A=
  granularity</DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
in fact, =0A=
  define a generic&nbsp;AN-level provisioning method that could be used =
to =0A=
  enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for =0A=
  provisioning the "Service Profiles" that are currently assumed to be =0A=
  configured in AN, as well as provisioning the Multicast =
White/Grey/Black =0A=
  Profiles<BR></DIV>=0A=
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>=0A=
  <DIV>Considering that:</DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
we got =0A=
  several times the feedback that per-entry BAndwidth Delegation flag =
was =0A=
  confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and =0A=
  may lead to difficulties if it is set on some entries and not on =
others)</DIV>=0A=
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
it is likely =0A=
  that we'll need, anyways, a mechanism to provision things at AN level, =
that =0A=
  could be easily used to convey Bandwidth Delegation enable/disable =0A=
  knob.<BR></DIV>=0A=
  <DIV>we&nbsp;would&nbsp;like to propose =0A=
  to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</DIV>=0A=
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>=0A=
  <DIV>Thoughts?</DIV>=0A=
  <DIV><BR></DIV>=0A=
  <DIV>Francois</DIV>=0A=
  <DIV><BR></DIV>=0A=
  <DIV>PS: Sven, if we go for&nbsp;the&nbsp;new approach, we can =
document in an =0A=
  email the deltas that&nbsp;would&nbsp;be needed to reflect that in =0A=
  framework.</DIV>=0A=
  =
<DIV><BR></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV=
></FONT></DIV></DIV></BODY></HTML>=0A=

------_=_NextPart_001_01C93782.08F2ED81--

--===============1013482781==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1013482781==--


From ancp-bounces@ietf.org  Mon Oct 27 02:21:15 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9ABAE3A6922;
	Mon, 27 Oct 2008 02:21:15 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 964123A6855
	for <ancp@core3.amsl.com>; Mon, 27 Oct 2008 02:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 QqVxuJLbFj1V for <ancp@core3.amsl.com>;
	Mon, 27 Oct 2008 02:21:13 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 19DBF3A689B
	for <ancp@ietf.org>; Mon, 27 Oct 2008 02:21:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,491,1220227200"; d="scan'208,217";a="23780798"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 27 Oct 2008 09:21:11 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9R9LBUh004421
	for <ancp@ietf.org>; Mon, 27 Oct 2008 10:21:11 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9R9LBRj023317
	for <ancp@ietf.org>; Mon, 27 Oct 2008 09:21:11 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 10:21:11 +0100
Received: from ams-flefauch-8713.cisco.com ([10.55.161.196]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 10:21:10 +0100
Message-Id: <9CC19957-D7EF-42C5-A3BC-174ECD82BB93@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: ancp@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 10:21:09 +0100
References: <20081027091501.2D1D53A6969@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 27 Oct 2008 09:21:10.0859 (UTC)
	FILETIME=[59C919B0:01C93815]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6582; t=1225099271;
	x=1225963271; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Fwd=3A=20I-D=20Action=3Adraft-lefaucheur-ancp-m
	c-extensions-00.txt=20 |Sender:=20;
	bh=crWyP30AIqmAlbcdJKTO/IgXxTtN71kEyU71sFGHnMg=;
	b=aatiNH3muUo2qdhkzFAFdX5YPt0kcWXnJGbmWYmA5V4U/SGdhGSFcP7FED
	yZFDMqEFP8Qu2fPLsiF0S2NGTSunNP6xrl8XmvJGVYYhPzXkwPClN59tqOU/
	Lj4eFOzC7N;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: [ANCP] Fwd: I-D Action:draft-lefaucheur-ancp-mc-extensions-00.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1383804109=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--===============1383804109==
Content-Type: multipart/alternative; boundary=Apple-Mail-1--168550089


--Apple-Mail-1--168550089
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

FYI.
Here is the I-D proposing additional ANCP protocol extensions to cover  
the Multicast Admission Control use case.
(It does not yet cover the Bandwidth Delegation mode, but this will be  
added later as WG converges on the basic parts).

Francois, Roberta, Tom

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: 27 October 2008 10:15:01 CEST
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-lefaucheur-ancp-mc-extensions-00.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
> 	Title           : Additional Multicast Control Extensions for ANCP
> 	Author(s)       : F. Le Faucheur, et al.
> 	Filename        : draft-lefaucheur-ancp-mc-extensions-00.txt
> 	Pages           : 35
> 	Date            : 2008-10-27
>
> This memorandum aims at defining additional ANCP protocol extensions
> (beyond those already defined) to support some of the Multicast use
> cases defined in the ANCP Framework document that are not yet
> supported.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-lefaucheur-ancp-mc-extensions-00.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.
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--Apple-Mail-1--168550089
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">FYI.<div>Here is the I-D =
proposing additional ANCP protocol extensions to cover the Multicast =
Admission Control use case.</div><div>(It does not yet cover the =
Bandwidth Delegation mode, but this will be added later as WG converges =
on the basic parts).</div><div><br></div><div>Francois, Roberta, =
Tom</div><div><div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><a =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a></fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" =
color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><b>Date: </b></font><font face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica">27 October 2008 10:15:01 =
CEST</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 18.0px Helvetica; color: =
#000000"><b>To: </b></font><font face=3D"Helvetica" size=3D"5" =
style=3D"font: 18.0px Helvetica"><a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a></font></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><b>Subject: =
</b></font><font face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><b>I-D Action:draft-lefaucheur-ancp-mc-extensions-00.txt<span =
class=3D"Apple-converted-space">&nbsp;</span></b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 18.0px Helvetica; color: #000000"><b>Reply-To: =
</b></font><font face=3D"Helvetica" size=3D"5" style=3D"font: 18.0px =
Helvetica"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><br></div> </div><div>A New =
Internet-Draft is available from the on-line Internet-Drafts =
directories.<br><br><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Additional =
Multicast Control Extensions for ANCP<br><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: F. Le Faucheur, et al.<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-lefaucheur-ancp-mc-extensions-00.txt<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
35<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2008-10-27<br><br>This memorandum aims at defining additional ANCP =
protocol extensions<br>(beyond those already defined) to support some of =
the Multicast use<br>cases defined in the ANCP Framework document that =
are not yet<br>supported.<br><br>A URL for this Internet-Draft is:<br><a =
href=3D"http://www.ietf.org/internet-drafts/draft-lefaucheur-ancp-mc-exten=
sions-00.txt">http://www.ietf.org/internet-drafts/draft-lefaucheur-ancp-mc=
-extensions-00.txt</a><br><br>Internet-Drafts are also available by =
anonymous FTP at:<br>ftp://ftp.ietf.org/internet-drafts/<br><br>Below is =
the data which will enable a MIME compliant mail =
reader<br>implementation to automatically retrieve the ASCII version of =
the<br>Internet-Draft.<br>_______________________________________________<=
br>I-D-Announce mailing =
list<br>I-D-Announce@ietf.org<br>https://www.ietf.org/mailman/listinfo/i-d=
-announce<br>Internet-Draft directories: =
http://www.ietf.org/shadow.html<br>or =
ftp://ftp.ietf.org/ietf/1shadow-sites.txt<br></div></blockquote></div><br>=
</div></body></html>=

--Apple-Mail-1--168550089--

--===============1383804109==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1383804109==--


From ancp-bounces@ietf.org  Mon Oct 27 03:41:30 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB62D3A68BD;
	Mon, 27 Oct 2008 03:41:30 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D71433A67D9
	for <ancp@core3.amsl.com>; Mon, 27 Oct 2008 03:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.135
X-Spam-Level: **
X-Spam-Status: No, score=2.135 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, CN_BODY_35=0.339, EXTRA_MPART_TYPE=1,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,
	MIME_CHARSET_FARAWAY=2.45, MY_CID_AND_ARIAL2=1.46,
	RCVD_IN_DNSWL_MED=-4]
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 SnooyXaMNYT9 for <ancp@core3.amsl.com>;
	Mon, 27 Oct 2008 03:41:23 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 2FD063A6820
	for <ancp@ietf.org>; Mon, 27 Oct 2008 03:41:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,491,1220227200"; 
	d="jpg'145?scan'145,208,217,145";a="23794352"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 27 Oct 2008 10:41:19 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9RAfJ93003675; 
	Mon, 27 Oct 2008 11:41:19 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9RAfIts026102;
	Mon, 27 Oct 2008 10:41:19 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 11:41:18 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 11:41:07 +0100
Message-ID: <D9872168DBD43A41BD71FFC4713274D405E378C6@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <004401c9363a$daeedca0$7b27460a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP Framework update
Thread-Index: AckwOgJsIJe9VJgbRHSt5ybOabbM2wF/v8WAAHl1EoA=
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com>
	<004401c9363a$daeedca0$7b27460a@china.huawei.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Fortune HUANG" <fqhuang@huawei.com>,
	"OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>,
	"Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
	"Tina TSOU" <tena@huawei.com>, "Tom Taylor" <tom.taylor@rogers.com>,
	"Maglione Roberta" <roberta.maglione@telecomitalia.it>,
	"Haag, Thomas" <HaagT@telekom.de>, <stefaan.de_cnodder@alcatel-lucent.be>
X-OriginalArrivalTime: 27 Oct 2008 10:41:18.0452 (UTC)
	FILETIME=[8B559340:01C93820]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=53718; t=1225104079;
	x=1225968079; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20ANCP=20Framework=20update
	|Sender:=20; bh=oA5umxqIhrQoIMx/8lxMwIefpN0iJ2bxWliF4AiFBAU=;
	b=s+UhDZEZvQcLJpVKZ5XW9fjL5A4zfN+7U8D96b5hmzJruvhhMnLkMC54US
	RnX74C3dqeNzHmoaItdNOOttANDdkL0ZvTJ0+SIwlz+DizbKcdpEjDfvwrK2
	udaursnaVl;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1286756725=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1286756725==
Content-class: urn:content-classes:message
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----_=_NextPart_001_01C93820.876413AD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93820.876413AD
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C93820.876413AD"


------_=_NextPart_002_01C93820.876413AD
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

A few remarks inline.


________________________________

	From: Fortune HUANG [mailto:fqhuang@huawei.com]=20
	Sent: 25 October 2008 02:45
	To: 'OOGHE Sven'; Francois Le Faucheur (flefauch); Tina TSOU; Tom =
Taylor; Maglione Roberta; Wojciech Dec (wdec); 'Haag, Thomas'; =
stefaan.de_cnodder@alcatel-lucent.be
	Cc: ancp@ietf.org
	Subject: ??: [ANCP] ANCP Framework update
=09
=09
	Hi all,
	=20
	Please see my three comments below, indicated by [Fortune 1/2/3: ...]
	=20
	Best Regards,
	Fortune
=09
	Huawei Technologies Co., Ltd.  =20

=09


	Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =
518129, P.R. China
	Tel: +86-755-28971871
	Fax: +86-755-28972352
	Mobile: +8615013838060
	Email: fqhuang@huawei.com
	http://www.huawei.com
	=
-------------------------------------------------------------------------=
------------------------------------------------------------
	=
=B1=BE=D3=CA=BC=FE=BC=B0=C6=E4=B8=BD=BC=FE=BA=AC=D3=D0=BB=AA=CE=AA=B9=AB=CB=
=BE=B5=C4=B1=A3=C3=DC=D0=C5=CF=A2=A3=AC=BD=F6=CF=DE=D3=DA=B7=A2=CB=CD=B8=F8=
=C9=CF=C3=E6=B5=D8=D6=B7=D6=D0=C1=D0=B3=F6=B5=C4=B8=F6=C8=CB=BB=F2=C8=BA=D7=
=E9=A1=A3=BD=FB
	=
=D6=B9=C8=CE=BA=CE=C6=E4=CB=FB=C8=CB=D2=D4=C8=CE=BA=CE=D0=CE=CA=BD=CA=B9=D3=
=C3=A3=A8=B0=FC=C0=A8=B5=AB=B2=BB=CF=DE=D3=DA=C8=AB=B2=BF=BB=F2=B2=BF=B7=D6=
=B5=D8=D0=B9=C2=B6=A1=A2=B8=B4=D6=C6=A1=A2=BB=F2=C9=A2=B7=A2=A3=A9=B1=BE=D3=
=CA=BC=FE=D6=D0
	=
=B5=C4=D0=C5=CF=A2=A1=A3=C8=E7=B9=FB=C4=FA=B4=ED=CA=D5=C1=CB=B1=BE=D3=CA=BC=
=FE=A3=AC=C7=EB=C4=FA=C1=A2=BC=B4=B5=E7=BB=B0=BB=F2=D3=CA=BC=FE=CD=A8=D6=AA=
=B7=A2=BC=FE=C8=CB=B2=A2=C9=BE=B3=FD=B1=BE=D3=CA=BC=FE=A3=A1
	This e-mail and its attachments contain confidential information from =
HUAWEI, which=20
	is intended only for the person or entity whose address is listed =
above. Any use of the=20
	information contained herein in any way (including, but not limited to, =
total or partial=20
	disclosure, reproduction, or dissemination) by persons other than the =
intended=20
	recipient(s) is prohibited. If you receive this e-mail in error, please =
notify the sender by=20
	phone or email immediately and delete it!
=09
	=20

________________________________

	=B7=A2=BC=FE=C8=CB: ancp-bounces@ietf.org =
[mailto:ancp-bounces@ietf.org] =B4=FA=B1=ED OOGHE Sven
	=B7=A2=CB=CD=CA=B1=BC=E4: 2008=C4=EA10=D4=C217=C8=D5 17:23
	=CA=D5=BC=FE=C8=CB: ancp@ietf.org
	=D6=F7=CC=E2: [ANCP] ANCP Framework update
=09
=09

	Hi,=20

	I've been updating the ANCP framework draft according to the suggested =
changes from Roberta and Francois. Below I have copy-pasted the sections =
that have undergone changes. Indented text has been changed. I think I =
captured the essence of the notion of "bandwidth delegation". Please =
review and see if this is capturing the agreements.

	Regards,=20
	Sven=20


	3.4.2.  Multicast Admission Control=20

	   The successful delivery of Triple Play Broadband services is quickly =

	   becoming a big capacity planning challenge for most of the Service=20
	   Providers nowadays.  Solely increasing available bandwidth is not=20
	   always practical, cost-economical and/or sufficient to satisfy end=20
	   user experience given not only the strict requirements of unicast=20
	   delay sensitive applications like VoIP and Video, but also the fast=20
	   growth of multicast interactive applications such as=20
	   videoconferencing, digital TV, digital audio, online movies and=20
	   networked gaming.  These applications are typically characterized by =

	   a delay sensitive nature, an extremely loss sensitive nature and=20
	   intensive bandwidth requirements.  They are also typically "non-=20
	   elastic", which means that they operate at a fixed bandwidth, that=20
	   cannot be dynamically adjusted to the currently available bandwidth. =


	   Therefore a Connection Admission Control (CAC) mechanism covering=20
	   admission of multicast traffic over the DSL Broadband access is=20
	   required, in order to avoid oversubscribing the available bandwidth=20
	   and negatively impacting the end user experience.=20

	   Considering specifically admission control over the access line,=20
	   before honoring a user request to join a new multicast flow, the=20
	   combination of AN and NAS MUST ensure admission control is performed =

	   to validate that there is enough "video" bandwidth remaining on the=20
	   access line to carry the new flow (in addition to all other existing =

	   multicast and unicast video traffic).  The solution needs to cope=20
	   with multiple flows per access line and needs to allow access line=20
	   bandwidth to be dynamically shared across multicast and unicast=20
	   traffic (irrespective of whether unicast CAC is performed by NAS or=20
	   by some off-path Policy Server) [Fortune 1: I suggest to replace =
"irrespective of whether unicast CAC is performed by NAS or=20
	   by some off-path Policy Server" by "the unicast CAC is performed =
either by NAS or by some off-path Policy Server", because the latter =
looks clearer to describe the two scenarios

	NOTE: I also suggest we replace "Policy Server/PS" by  other name  as =
specified in my previous email. And this note applies to the whole =
document and all my comments.] . =20

	Woj> The attractiveness of having the current "Policy Server" term is =
that it can be different things to different people (which it actually =
is) without overly affecting ANCP, and it's precise definition as say =
the RACS or other doesn't appear to be quite necessary in my opinion, =
neither is a specification that the PS is the sole place where admission =
control is performed

	   Thus, supporting CAC for the access line requires some form of=20
	   synchronization between the entity performing multicast CAC (e.g. =
the=20
	   NAS or the AN) and the entity performing unicast CAC (e.g. the NAS =
or=20
	   a Policy Server) and the entity actually enforcing the multicast=20
	   replication (i.e. the AN).  This synchronization can be achieved in =
a=20
	   number of ways:=20

	   o  One approach is for the AN to query the NAS so that Admission=20
	      Control for the access line is performed by the NAS (possibly =
with=20
	      interactions with a Policy Server).  This can be done with or=20
	      without "bandwidth delegation" to the AN. =20

	[Fortune 2: The admission control is not actually performed by the NAS =
when there is interactions between NAS and PS. I suggest to replace the =
above paragraph with the following text:=20

	Woj> The admission control can very well be done by the NAS with =
interactions with a Policy Server. That's what the original text states, =
and given that we don't want to open up the discussion of "what is a PS" =
it appears to be fine for now.

	   o  One approach is for the AN to query the NAS so that Admission=20
	      Control for the access line is performed by the NAS  or the =
Policy Server which interacts with the AN via NAS.  This can be done =
with or=20
	      without "bandwidth delegation" to the AN. =20

	]

	      *  In case of Admission Control without AN Bandwidth Delegation,=20
	         the AN can use ANCP to query the NAS, that in turn performs=20
	         multicast Admission Control check for the new multicast flow=20
	         and responds to the AN indicating whether the join is to be=20
	         honored (and hence replication performed by the AN) or denied. =

	         The NAS may locally maintain available "video" bandwidth on =
the=20
	         Access Loop, and perform video bandwidth accounting for the=20
	         Access Loop.  Upon receiving an Admission Request from the AN, =

	         the NAS can check available "video" bandwidth before admitting =

	         or denying the multicast flow.  In the process, the NAS may=20
	         communicate with the Policy Server.  For unicast video =
services=20
	         such as Video on Demand (VoD), the NAS may also be queried (by =

	         a Policy Server or via on-path CAC signaling), so that it can=20
	         perform admission control for the unicast flow, and update the =

	         available video bandwidth maintained by the NAS.=20

	      *  In case of Admission Control with AN Bandwidth Delegation, the =

	         NAS (possibly with interactions with a Policy Server) manages=20
	         total bandwidth for video admission, performs unicast =
admission=20
	         control and uses ANCP to delegate a certain amount of =
bandwidth=20
	         for some multicast flows to the Access Node.  In this =
scenario,=20
	         upon receiving a join to a multicast flow which matches an=20
	         entry in the White or Grey List whose entry is flagged as=20
	         "Bandwidth Delegation", the AN must perform the necessary=20
	         bandwidth admission control check for the new multicast flow,=20
	         before starting the multicast flow replication. =20

	[Fortune 3: This above paragraph is not clear enough for us to =
understand the requirement of the NAS in case the NAS communicates with =
a Policy Server. Actually, the NAS doesn't need to maintain the total =
bandwidth for video admission and doesn't need to perform unicast =
admission control. I strongly suggest we describe the two scenarios with =
or without interaction with a Policy Server in two seperate paragraphs, =
in order to avoid creating unprecise requirements of NAS and misleading =
to the NAS implementation. And the interactions between the AN and the =
NAS/PS are missing here.=20

	Woj> Again, the points you make are valid assuming that the PS is the =
only entity making admission control decisions; it does not capture the =
model where the PS delegates admission control decision to the NAS. =
Personally I'd say that we do not want to iterate through descriptions =
of all the possible scenarios of; Admission control on the AN only; =
Admission control on the NAS only; Admission control coordinated between =
AN and NAS; Admission control coordinated between AN and NAS and PS; =
admission control coordinated between NAS and PS; admission control only =
on the PS, etc.

	Regards,

	Woj.

	=20

	*  In case of Admission Control with AN Bandwidth Delegation, one =
control scenario is that the=20
	         NAS manages total bandwidth for video admission, performs =
unicast admission=20
	         control and uses ANCP to delegate a certain amount of =
bandwidth=20
	         for some multicast flows to the Access Node.  In this =
scenario,=20
	         upon receiving a join to a multicast flow which matches an=20
	         entry in the White or Grey List whose entry is flagged as=20
	         "Bandwidth Delegation", the AN must perform the necessary=20
	         bandwidth admission control check for the new multicast flow,=20
	         before starting the multicast flow replication. =20
	         When the bandwidth for multicast service is insufficient for =
the new multicast request, =20
	         the AN requests the NAS for more bandwidth to meet the new =
multicast request.=20
	         When the bandwidth for unicast service is insufficient for the =
new unicast request,=20
	         the NAS requests the AN for more bandwidth to meet the new =
unicast request.

	*  In case of Admission Control with AN Bandwidth Delegation, another =
control scenario is that the=20
	         Policy Server manages total bandwidth for video admission, =
performs unicast admission=20
	         control, delegate a certain amount of bandwidth for some =
multicast flows to the Access Node via the NAS. =20
	         In this scenario, the NAS interacts with the Access Node with =
the ANCP, =20
	         while the protocol between the NAS and the Policy Server is =
out of scope of this document.=20
	         In this scenario, upon receiving a join to a multicast flow =
which matches an=20
	         entry in the White or Grey List whose entry is flagged as=20
	         "Bandwidth Delegation", the AN must perform the necessary=20
	         bandwidth admission control check for the new multicast flow,=20
	         before starting the multicast flow replication.=20
	         When the bandwidth for multicast service is insufficient for =
the new multicast request, =20
	         the AN requests the Policy Server for more bandwidth to meet =
the new multicast request via the NAS.=20
	         When the bandwidth for unicast service is insufficient for the =
new unicast request,=20
	         the Policy Server requests the AN for more bandwidth to meet =
the new unicast request via the NAS. =20

	]

	      The ANCP requirements to support this approach are specified in=20
	      this document.=20

	   o  In case the subscriber communicates the "join/leave" information=20
	      with the NAS (e.g. by terminating all subscriber IGMP signaling =
on=20
	      the NAS, or by using some form of application level signaling),=20
	      the approach is very similar.  In this case, the NAS may locally=20
	      maintain available "video" bandwidth on the Access Loop, perform=20
	      video bandwidth accounting, and perform CAC for unicast and=20
	      multicast flows.  The NAS can set the replication state on the AN =

	      using ANCP if the flow is admitted.  For unicast video services=20
	      the NAS may be queried (by a policy server or via on-path CAC=20
	      signaling) to perform admission control for the unicast flow, and =

	      update the available video bandwidth maintained by the NAS.  The=20
	      ANCP requirements to support this approach (where the AN queries=20
	      the NAS) are specified in this document;=20

	   o  In a third approach, the Policy Server queries the AN directly so =

	      that both unicast and multicast CAC for the access line are=20
	      performed by the AN.  In this case, a subscriber request for a=20
	      unicast flow (e.g. a Video on Demand session) will trigger a=20
	      resource request message towards a Policy Server; the latter will =

	      then query the AN, that in turn will perform unicast CAC for the=20
	      access line and respond, indicating whether the unicast request =
is=20
	      to be honored or denied.  In this scenario the Policy Server=20
	      queries the AN directly, the approach doesn't require the use of=20
	      ANCP.  It is therefore beyond the scope of this document.=20

	=20


------_=_NextPart_002_01C93820.876413AD
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>ANCP Framework update</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2900.5626" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D392042910-27102008><FONT =
face=3DArial size=3D2>A=20
few remarks inline.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Fortune HUANG=20
  [mailto:fqhuang@huawei.com] <BR><B>Sent:</B> 25 October 2008=20
  02:45<BR><B>To:</B> 'OOGHE Sven'; Francois Le Faucheur (flefauch); =
Tina TSOU;=20
  Tom Taylor; Maglione Roberta; Wojciech Dec (wdec); 'Haag, Thomas';=20
  stefaan.de_cnodder@alcatel-lucent.be<BR><B>Cc:</B>=20
  ancp@ietf.org<BR><B>Subject:</B> ??: [ANCP] ANCP Framework=20
  update<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2><SPAN=20
  class=3D983310803-24102008>Hi all,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2><SPAN=20
  class=3D983310803-24102008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D983310803-24102008><FONT=20
  color=3D#0000ff><FONT size=3D2>Please see my three comments below, =
indicated by=20
  [Fortune 1/2/3: ...]</FONT></FONT></SPAN></DIV>
  <DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D983310803-24102008><FONT color=3D#0000ff =
size=3D2>Best=20
  Regards,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D983310803-24102008><FONT color=3D#0000ff=20
  size=3D2>Fortune</FONT></SPAN></DIV>
  <DIV><SPAN class=3D983310803-24102008></SPAN><FONT =
face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dblack=20
  size=3D2><BR></FONT><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dgray =
size=3D2>Huawei Technologies Co.,=20
  Ltd. </FONT><IMG id=3DridImg alt=3Dhuawei_logo hspace=3D0=20
  src=3D"cid:392042910@27102008-1448" align=3Dleft> </DIV>
  <P></P><BR><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dgray =
size=3D1>Addr: Section F, Huawei=20
  Industrial Base, Bantian Longgang, Shenzhen 518129, P.R. China<BR>Tel: =

  +86-755-28971871<BR>Fax: +86-755-28972352<BR>Mobile: =
+8615013838060<BR>Email:=20
  fqhuang@huawei.com<BR>http://www.huawei.com<BR></FONT><FONT =
face=3D=BB=AA=CE=C4=CF=B8=BA=DA=20
  color=3Dgray=20
  =
size=3D1>----------------------------------------------------------------=
---------------------------------------------------------------------<BR>=
=B1=BE=D3=CA=BC=FE=BC=B0=C6=E4=B8=BD=BC=FE=BA=AC=D3=D0=BB=AA=CE=AA=B9=AB=CB=
=BE=B5=C4=B1=A3=C3=DC=D0=C5=CF=A2=A3=AC=BD=F6=CF=DE=D3=DA=B7=A2=CB=CD=B8=F8=
=C9=CF=C3=E6=B5=D8=D6=B7=D6=D0=C1=D0=B3=F6=B5=C4=B8=F6=C8=CB=BB=F2=C8=BA=D7=
=E9=A1=A3=BD=FB<BR>=D6=B9=C8=CE=BA=CE=C6=E4=CB=FB=C8=CB=D2=D4=C8=CE=BA=CE=
=D0=CE=CA=BD=CA=B9=D3=C3=A3=A8=B0=FC=C0=A8=B5=AB=B2=BB=CF=DE=D3=DA=C8=AB=B2=
=BF=BB=F2=B2=BF=B7=D6=B5=D8=D0=B9=C2=B6=A1=A2=B8=B4=D6=C6=A1=A2=BB=F2=C9=A2=
=B7=A2=A3=A9=B1=BE=D3=CA=BC=FE=D6=D0<BR>=B5=C4=D0=C5=CF=A2=A1=A3=C8=E7=B9=
=FB=C4=FA=B4=ED=CA=D5=C1=CB=B1=BE=D3=CA=BC=FE=A3=AC=C7=EB=C4=FA=C1=A2=BC=B4=
=B5=E7=BB=B0=BB=F2=D3=CA=BC=FE=CD=A8=D6=AA=B7=A2=BC=FE=C8=CB=B2=A2=C9=BE=B3=
=FD=B1=BE=D3=CA=BC=FE=A3=A1<BR></FONT><FONT=20
  face=3DArial color=3Dgray size=3D1>This e-mail and its attachments =
contain=20
  confidential information from HUAWEI, which <BR>is intended only for =
the=20
  person or entity whose address is listed above. Any use of the =
<BR>information=20
  contained herein in any way (including, but not limited to, total or =
partial=20
  <BR>disclosure, reproduction, or dissemination) by persons other than =
the=20
  intended <BR>recipient(s) is prohibited. If you receive this e-mail in =
error,=20
  please notify the sender by <BR>phone or email immediately and delete=20
  it!<BR></FONT>
  <DIV>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Dzh-cn dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3D=CB=CE=CC=E5 size=3D2><B>=B7=A2=BC=FE=C8=CB:</B> =
ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>=B4=FA=B1=ED </B>OOGHE =
Sven<BR><B>=B7=A2=CB=CD=CA=B1=BC=E4:</B>=20
  2008=C4=EA10=D4=C217=C8=D5 17:23<BR><B>=CA=D5=BC=FE=C8=CB:</B> =
ancp@ietf.org<BR><B>=D6=F7=CC=E2:</B> [ANCP] ANCP=20
  Framework update<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial size=3D2>Hi,</FONT> </P>
  <P><FONT face=3DArial size=3D2>I've been updating the ANCP framework =
draft=20
  according to the suggested changes from Roberta and Francois. Below I =
have=20
  copy-pasted the sections that have undergone changes.<I> Indented =
text</I> has=20
  been changed. I think I captured the essence of the notion of =
"bandwidth=20
  delegation". Please review and see if this is capturing the=20
  agreements.</FONT></P>
  <P><FONT face=3DArial size=3D2>Regards,</FONT> <BR><FONT face=3DArial=20
  size=3D2>Sven</FONT> </P><BR>
  <P><B><FONT face=3DArial size=3D2>3.4.2.&nbsp; Multicast Admission=20
  Control</FONT></B> </P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; The successful delivery of =
Triple Play=20
  Broadband services is quickly</FONT> <BR><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;=20
  becoming a big capacity planning challenge for most of the =
Service</FONT>=20
  <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; Providers nowadays.&nbsp; =
Solely=20
  increasing available bandwidth is not</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp; always practical, cost-economical and/or =
sufficient to=20
  satisfy end</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; user =
experience=20
  given not only the strict requirements of unicast</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp; delay sensitive applications like VoIP and =
Video, but also=20
  the fast</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; growth of =
multicast=20
  interactive applications such as</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp; videoconferencing, digital TV, digital audio, =
online=20
  movies and</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
networked=20
  gaming.&nbsp; These applications are typically characterized by</FONT> =

  <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; a delay sensitive nature, =
an=20
  extremely loss sensitive nature and</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp; intensive bandwidth requirements.&nbsp; They are =
also=20
  typically "non-</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
elastic",=20
  which means that they operate at a fixed bandwidth, that</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp; cannot be dynamically adjusted to =
the currently=20
  available bandwidth.</FONT> </P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; Therefore a Connection =
Admission=20
  Control (CAC) mechanism covering</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp; admission of multicast traffic over the DSL =
Broadband=20
  access is</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
required, in order=20
  to avoid oversubscribing the available bandwidth</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp; and negatively impacting the end user =
experience.</FONT>=20
  </P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; Considering specifically =
admission=20
  control over the access line,</FONT> <BR><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;=20
  before honoring a user request to join a new multicast flow, =
the</FONT>=20
  <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; combination of AN and =
NAS<SPAN=20
  class=3D983310803-24102008><FONT face=3D=CB=CE=CC=E5 =
color=3D#0000ff>&nbsp;</FONT></SPAN>MUST=20
  ensure admission control is performed</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp; to validate that there is enough "video" =
bandwidth=20
  remaining on the</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
access line=20
  to carry the new flow (in addition to all other existing</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp; multicast and unicast video =
traffic).&nbsp; The=20
  solution needs to cope</FONT> <BR><FONT face=3DArial =
size=3D2>&nbsp;&nbsp; with=20
  multiple flows per access line and needs to allow access line</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp; bandwidth to be dynamically shared =
across=20
  multicast and unicast</FONT> <BR><FONT face=3DArial =
size=3D2>&nbsp;&nbsp; traffic=20
  (irrespective of whether unicast CAC is performed by NAS or</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp; by some off-path Policy =
Server)<SPAN=20
  class=3D983310803-24102008><FONT face=3D=CB=CE=CC=E5 =
color=3D#0000ff>&nbsp;[Fortune 1: I=20
  suggest to replace "<FONT face=3DArial color=3D#000000>irrespective of =
whether=20
  unicast CAC is performed by NAS or</FONT><FONT color=3D#000000><FONT =
size=3D3>=20
  <BR></FONT><FONT face=3DArial size=3D2>&nbsp;&nbsp; by some off-path =
Policy=20
  Server"<FONT face=3D=CB=CE=CC=E5 color=3D#0000ff>&nbsp;by "the unicast =
CAC is performed=20
  either by NAS or by some off-path Policy Server", because the latter =
looks=20
  clearer&nbsp;to describe the=20
  two&nbsp;scenarios</FONT></FONT></FONT></FONT></SPAN></FONT></P><FONT=20
  face=3DArial><SPAN class=3D983310803-24102008>
  <P><SPAN class=3D983310803-24102008><FONT face=3D=CB=CE=CC=E5 =
size=3D2>NOTE:&nbsp;I also=20
  suggest we replace&nbsp;"Policy Server/PS"&nbsp;by&nbsp;<SPAN=20
  class=3D351223100-25102008>&nbsp;other name&nbsp;</SPAN> as specified =
in my=20
  previous email. And this note applies to the whole document and all my =

  comments.</FONT></SPAN></SPAN></FONT><FONT face=3DArial><FONT =
size=3D2><SPAN=20
  class=3D983310803-24102008><FONT=20
  face=3D=CB=CE=CC=E5>]&nbsp;</FONT></SPAN>.</FONT></FONT><FONT=20
  face=3D"=CB=CE=CC=E5, MS Song">&nbsp;</FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D392042910-27102008>&nbsp;</SPAN></FONT></P>
  <P><FONT face=3DArial size=3D2><SPAN class=3D392042910-27102008><SPAN=20
  class=3D482180508-24102008><FONT face=3DArial size=3D2>Woj&gt; The =
attractiveness of=20
  having the current&nbsp;"Policy Server" term is that it can be =
different=20
  things to different people (which it actually is) without overly =
affecting=20
  ANCP,&nbsp;and it's precise definition as say the RACS or other =
doesn't appear=20
  to be quite&nbsp;necessary in my opinion, neither is a specification =
that the=20
  PS is the sole place where admission control is=20
  performed</FONT></SPAN></SPAN></FONT></P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; Thus, supporting CAC for =
the access=20
  line requires some form of</FONT> <BR><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;=20
  synchronization between the entity performing multicast CAC (e.g. =
the</FONT>=20
  <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; NAS or the AN) and the =
entity=20
  performing unicast CAC (e.g. the NAS or</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp; a Policy Server) and the entity actually =
enforcing the=20
  multicast</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
replication (i.e.=20
  the AN).&nbsp; This synchronization can be achieved in a</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp; number of ways:</FONT> </P>
  <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; One approach is =
for the AN=20
  to query the NAS so that Admission</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the access line is =
performed=20
  by the NAS (possibly with</FONT></I> <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interactions with a Policy=20
  Server).&nbsp; This can be done with or</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth delegation" =
to the=20
  AN.</FONT></I>&nbsp;<SPAN class=3D983310803-24102008><FONT =
color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D983310803-24102008><SPAN =
class=3D983310803-24102008><FONT=20
  color=3D#0000ff size=3D2>[Fortune 2:</FONT></SPAN>&nbsp;<FONT =
color=3D#0000ff><FONT=20
  size=3D2>The admission control is not actually performed by the NAS =
when there=20
  is interactions between NAS and PS. I suggest to replace the above =
paragraph=20
  with the following text:<SPAN class=3D392042910-27102008><FONT =
face=3DArial=20
  color=3D#000000>&nbsp;</FONT></SPAN></FONT></FONT></SPAN></P>
  <P><SPAN class=3D983310803-24102008><FONT color=3D#0000ff><FONT =
size=3D2><SPAN=20
  class=3D392042910-27102008><FONT face=3DArial =
color=3D#000000>Woj&gt;&nbsp;The=20
  admission control can very well be done by the NAS with interactions =
with a=20
  Policy Server. That's what the original text states, and given that we =
don't=20
  want to open up the discussion of "what is a PS" it appears to be fine =
for=20
  now.</FONT></SPAN></FONT></FONT></SPAN></P>
  <P><SPAN class=3D983310803-24102008><EM><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;=20
  o&nbsp; One approach is for the AN to query the NAS so that=20
  Admission</FONT></EM> <BR><FONT face=3DArial=20
  size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the access =
line is=20
  performed by the NAS&nbsp;</EM><FONT color=3D#0000ff>&nbsp;or the =
Policy Server=20
  which interacts with the AN via NAS</FONT></FONT><FONT face=3DArial=20
  size=3D2><EM>.&nbsp; This can be done with or</EM></FONT> <BR><I><FONT =

  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without =
"bandwidth=20
  delegation" to the AN.</FONT></I>&nbsp;<SPAN =
class=3D983310803-24102008><FONT=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></SPAN></P>
  <P><SPAN class=3D983310803-24102008><FONT color=3D#0000ff=20
  size=3D2>]</FONT></SPAN></P>
  <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp; In case=20
  of Admission Control without AN Bandwidth Delegation,</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the AN can=20
  use ANCP to query the NAS, that in turn performs</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast=20
  Admission Control check for the new multicast flow</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and=20
  responds to the AN indicating whether the join is to be</FONT></I>=20
  <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored (and =
hence=20
  replication performed by the AN) or denied.</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may =
locally=20
  maintain available "video" bandwidth on the</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop, =
and=20
  perform video bandwidth accounting for the</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access =
Loop.&nbsp;=20
  Upon receiving an Admission Request from the AN,</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the NAS can=20
  check available "video" bandwidth before admitting</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
or denying=20
  the multicast flow.&nbsp; In the process, the NAS may</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
communicate=20
  with the Policy Server.&nbsp; For unicast video services</FONT></I>=20
  <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; such as =
Video on=20
  Demand (VoD), the NAS may also be queried (by</FONT></I> <BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
a Policy=20
  Server or via on-path CAC signaling), so that it can</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
perform=20
  admission control for the unicast flow, and update the</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
available=20
  video bandwidth maintained by the NAS.</FONT></I> </P>
  <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp; In case=20
  of Admission Control with AN Bandwidth Delegation, the</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
NAS=20
  (possibly with interactions with a Policy Server) manages</FONT></I>=20
  <BR><I><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for=20
  video admission, performs unicast admission</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control and =
uses ANCP=20
  to delegate a certain amount of bandwidth</FONT></I> <BR><I><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast=20
  flows to the Access Node.&nbsp; In this scenario,</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
upon=20
  receiving a join to a multicast flow which matches an</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
entry in=20
  the White or Grey List whose entry is flagged as</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
"Bandwidth=20
  Delegation", the AN must perform the necessary</FONT></I> <BR><I><FONT =

  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
bandwidth=20
  admission control check for the new multicast flow,</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
before=20
  starting the multicast flow replication.</FONT></I>&nbsp;<SPAN=20
  class=3D983310803-24102008><FONT color=3D#0000ff =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P><FONT size=3D2><SPAN class=3D983310803-24102008><FONT =
color=3D#0000ff>[Fortune 3:=20
  This above paragraph is not clear enough for us to understand the =
requirement=20
  of the NAS in case the NAS communicates with a Policy Server. =
Actually, the=20
  NAS doesn't need to maintain the total bandwidth for video admission =
and=20
  doesn't need to perform unicast admission =
control.&nbsp;</FONT></SPAN><SPAN=20
  class=3D983310803-24102008><FONT color=3D#0000ff>I strongly suggest we =
describe=20
  the two scenarios with or without interaction with a Policy Server in =
two=20
  seperate paragraphs, in order to avoid&nbsp;creating unprecise =
requirements of=20
  NAS and misleading to the NAS implementation. And the interactions =
between the=20
  AN and the NAS/PS are missing here.<SPAN =
class=3D392042910-27102008><FONT=20
  face=3DArial =
color=3D#000000>&nbsp;</FONT></SPAN></FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D983310803-24102008><FONT =
color=3D#0000ff><SPAN=20
  class=3D392042910-27102008><FONT face=3DArial color=3D#000000>Woj&gt; =
Again, the=20
  points you make are valid&nbsp;assuming that the PS is the only entity =
making=20
  admission control decisions; it does not capture the model where the =
PS=20
  delegates&nbsp;admission control decision to the NAS.&nbsp;Personally =
I'd say=20
  that&nbsp;we do not&nbsp;want to iterate through descriptions =
of&nbsp;all the=20
  possible scenarios of; Admission control on the AN only; Admission =
control on=20
  the NAS only; Admission control coordinated between AN and NAS; =
Admission=20
  control coordinated between AN and NAS and PS;&nbsp;admission control=20
  coordinated between NAS and PS; admission control only on the PS,=20
  etc.</FONT></SPAN></FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D983310803-24102008><FONT face=3DArial=20
  color=3D#000000><SPAN=20
  class=3D392042910-27102008>Regards,</SPAN></FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D983310803-24102008><FONT face=3DArial=20
  color=3D#000000><SPAN=20
  class=3D392042910-27102008>Woj.</SPAN></FONT></SPAN></FONT></P>
  <P><SPAN class=3D983310803-24102008></SPAN>&nbsp;</P>
  <P><SPAN class=3D983310803-24102008></SPAN><SPAN=20
  class=3D983310803-24102008></SPAN><SPAN =
class=3D983310803-24102008><FONT=20
  color=3D#0000ff size=3D2>*&nbsp; In case of Admission Control with AN =
Bandwidth=20
  Delegation, one control scenario is that the=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =
manages&nbsp;total=20
  bandwidth for video admission, performs unicast admission=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control and uses =
ANCP to=20
  delegate a certain amount of bandwidth=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast flows=20
  to the Access Node.&nbsp; In this scenario,=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon receiving a =
join to=20
  a multicast flow which matches an=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or=20
  Grey List whose entry is flagged as=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Bandwidth =
Delegation",=20
  the AN must perform the necessary=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bandwidth =
admission=20
  control check for the new multicast flow,=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before starting =
the=20
  multicast flow replication.&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When the=20
  bandwidth&nbsp;for multicast service&nbsp;is insufficient for the new=20
  multicast request,&nbsp; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the AN requests the NAS for more bandwidth to meet the new multicast =
request.=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When the =
bandwidth for=20
  unicast service is insufficient for the new unicast=20
  =
request,&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t=
he=20
  NAS requests the AN for more bandwidth to meet the new unicast=20
  request.</FONT></SPAN></P>
  <P><SPAN class=3D983310803-24102008><FONT color=3D#0000ff =
size=3D2><SPAN=20
  class=3D983310803-24102008><FONT color=3D#0000ff size=3D2>*&nbsp; =
</FONT></SPAN>In=20
  case of Admission Control with AN Bandwidth Delegation, another =
control=20
  scenario is that =
the&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Policy Server&nbsp;manages&nbsp;total bandwidth for video admission, =
performs=20
  unicast admission <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  control,&nbsp;delegate a certain amount of bandwidth&nbsp;for some =
multicast=20
  flows to the Access Node via the NAS.&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In this scenario, =
the NAS=20
  interacts with the Access Node with the ANCP,&nbsp;=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; while the =
protocol=20
  between the NAS and the Policy Server is out of scope of this =
document.=20
  <BR></FONT></SPAN><SPAN class=3D983310803-24102008><FONT =
color=3D#0000ff=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In this=20
  scenario,&nbsp;upon receiving a join to a multicast flow which matches =
an=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or=20
  Grey List whose entry is flagged as=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Bandwidth =
Delegation",=20
  the AN must perform the necessary=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bandwidth =
admission=20
  control check for the new multicast flow,=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before starting =
the=20
  multicast flow replication.=20
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When the=20
  bandwidth&nbsp;for multicast service&nbsp;is insufficient for the new=20
  multicast request,&nbsp; =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the AN requests the Policy Server for more bandwidth to meet the new =
multicast=20
  request via the NAS. =
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When=20
  the bandwidth for unicast service is insufficient for the new unicast=20
  =
request,&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;t=
he&nbsp;Policy=20
  Server&nbsp;requests the AN for more bandwidth to meet the new unicast =
request=20
  via the NAS.&nbsp; </FONT></SPAN></P>
  <P><SPAN class=3D983310803-24102008><FONT color=3D#0000ff=20
  size=3D2>]</FONT></SPAN></P>
  <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
ANCP=20
  requirements to support this approach are specified in</FONT></I> =
<BR><I><FONT=20
  face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this =
document.</FONT></I>=20
</P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; In case the =
subscriber=20
  communicates the "join/leave" information</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the NAS (e.g. by =
terminating all=20
  subscriber IGMP signaling on</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS, or by using some form =
of=20
  application level signaling),</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the approach is very =
similar.&nbsp; In=20
  this case, the NAS may locally</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maintain available "video" =
bandwidth on=20
  the Access Loop, perform</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; video bandwidth accounting, =
and perform=20
  CAC for unicast and</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flows.&nbsp; The NAS =
can set=20
  the replication state on the AN</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; using ANCP if the flow is=20
  admitted.&nbsp; For unicast video services</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS may be queried (by a =
policy=20
  server or via on-path CAC</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; signaling) to perform =
admission control=20
  for the unicast flow, and</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; update the available video =
bandwidth=20
  maintained by the NAS.&nbsp; The</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP requirements to support =
this=20
  approach (where the AN queries</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the NAS) are specified in this =

  document;</FONT><I></I> </P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; In a third =
approach, the=20
  Policy Server queries the AN directly so</FONT> <BR><FONT face=3DArial =

  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that both unicast and =
multicast CAC for=20
  the access line are</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; performed by the AN.&nbsp; In =
this case,=20
  a subscriber request for a</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; unicast flow (e.g. a Video on =
Demand=20
  session) will trigger a</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; resource request message =
towards a=20
  Policy Server; the latter will</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then query the AN, that in =
turn will=20
  perform unicast CAC for the</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; access line and respond, =
indicating=20
  whether the unicast request is</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to be honored or denied.&nbsp; =
In this=20
  scenario the Policy Server</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; queries the AN directly, the =
approach=20
  doesn't require the use of</FONT> <BR><FONT face=3DArial=20
  size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ANCP.&nbsp; It is therefore =
beyond the=20
  scope of this document.</FONT><I></I> </P>
  <P><FONT face=3DArial =
size=3D2></FONT>&nbsp;</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_002_01C93820.876413AD--

------_=_NextPart_001_01C93820.876413AD
Content-Type: image/jpeg;
	name="outlook_huawei_logo_cn.jpg"
Content-Transfer-Encoding: base64
Content-ID: <392042910@27102008-1448>
Content-Description: outlook_huawei_logo_cn.jpg
Content-Location: outlook_huawei_logo_cn.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/7QxmUGhvdG9zaG9wIDMuMAA4QklNBCUAAAAAABAAAAAAAAAA
AAAAAAAAAAAAOEJJTQPtAAAAAAAQAEgAAAABAAIASAAAAAEAAjhCSU0EJgAAAAAADgAAAAAAAAAA
AAA/gAAAOEJJTQQNAAAAAAAEAAAAHjhCSU0EGQAAAAAABAAAAB44QklNA/MAAAAAAAkAAAAAAAAA
AAEAOEJJTQQKAAAAAAABAAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgAB
AGxmZgAGAAAAAAABAC9mZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0A
AAAGAAAAAAABOEJJTQP4AAAAAABwAAD/////////////////////////////A+gAAAAA////////
/////////////////////wPoAAAAAP////////////////////////////8D6AAAAAD/////////
////////////////////A+gAADhCSU0EAAAAAAAAAgAAOEJJTQQCAAAAAAACAAA4QklNBDAAAAAA
AAEBADhCSU0ELQAAAAAABgABAAAABjhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBB4A
AAAAAAQAAAAAOEJJTQQaAAAAAAM9AAAABgAAAAAAAAAAAAAAIAAAAGYAAAAEAGwAbwBnAG8AAAAB
AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAGYAAAAgAAAAAAAAAAAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAAAAAAAAAEAAAAAEAAAAAAABudWxsAAAAAgAAAAZib3VuZHNPYmpjAAAAAQAAAAAA
AFJjdDEAAAAEAAAAAFRvcCBsb25nAAAAAAAAAABMZWZ0bG9uZwAAAAAAAAAAQnRvbWxvbmcAAAAg
AAAAAFJnaHRsb25nAAAAZgAAAAZzbGljZXNWbExzAAAAAU9iamMAAAABAAAAAAAFc2xpY2UAAAAS
AAAAB3NsaWNlSURsb25nAAAAAAAAAAdncm91cElEbG9uZwAAAAAAAAAGb3JpZ2luZW51bQAAAAxF
U2xpY2VPcmlnaW4AAAANYXV0b0dlbmVyYXRlZAAAAABUeXBlZW51bQAAAApFU2xpY2VUeXBlAAAA
AEltZyAAAAAGYm91bmRzT2JqYwAAAAEAAAAAAABSY3QxAAAABAAAAABUb3AgbG9uZwAAAAAAAAAA
TGVmdGxvbmcAAAAAAAAAAEJ0b21sb25nAAAAIAAAAABSZ2h0bG9uZwAAAGYAAAADdXJsVEVYVAAA
AAEAAAAAAABudWxsVEVYVAAAAAEAAAAAAABNc2dlVEVYVAAAAAEAAAAAAAZhbHRUYWdURVhUAAAA
AQAAAAAADmNlbGxUZXh0SXNIVE1MYm9vbAEAAAAIY2VsbFRleHRURVhUAAAAAQAAAAAACWhvcnpB
bGlnbmVudW0AAAAPRVNsaWNlSG9yekFsaWduAAAAB2RlZmF1bHQAAAAJdmVydEFsaWduZW51bQAA
AA9FU2xpY2VWZXJ0QWxpZ24AAAAHZGVmYXVsdAAAAAtiZ0NvbG9yVHlwZWVudW0AAAARRVNsaWNl
QkdDb2xvclR5cGUAAAAATm9uZQAAAAl0b3BPdXRzZXRsb25nAAAAAAAAAApsZWZ0T3V0c2V0bG9u
ZwAAAAAAAAAMYm90dG9tT3V0c2V0bG9uZwAAAAAAAAALcmlnaHRPdXRzZXRsb25nAAAAAAA4QklN
BCgAAAAAAAwAAAABP/AAAAAAAAA4QklNBBEAAAAAAAEBADhCSU0EFAAAAAAABAAAAAg4QklNBAwA
AAAABnAAAAABAAAAZgAAACAAAAE0AAAmgAAABlQAGAAB/9j/4AAQSkZJRgABAgAASABIAAD/7QAM
QWRvYmVfQ00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUT
ExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4O
Dg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMB
IgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEB
AAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSR
obFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSF
tJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIR
AyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVV
NnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEA
AhEDEQA/APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC6
6f56f3t30Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUs
VaDHl/dl/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5Vtns
U/qp1vqPUvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9
w9+kqfV+qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVh
fWLCzerW9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX
146P1azqFWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKeh
SWDk/XHpVHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8t
bvSU9Ikucy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uo
JBeNpMtfRc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxb
qtG20uI0PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv
/QXjOu9COI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5F
ztrrn/usXoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4
HX+6yY/jQHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v
6hNyW9Q6jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m
+u1tQc9n0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6
tfRj2YnTgMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJ
JT5b0bpfUrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6r
WuLnfpNjXu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z
OEJJTQQhAAAAAABVAAAAAQEAAAAPAEEAZABvAGIAZQAgAFAAaABvAHQAbwBzAGgAbwBwAAAAEwBB
AGQAbwBiAGUAIABQAGgAbwB0AG8AcwBoAG8AcAAgAEMAUwAyAAAAAQA4QklNBAYAAAAAAAcABQAA
AAEBAP/hB4ZFeGlmAABJSSoACAAAAAcAEgEDAAEAAAABAAAAGgEFAAEAAABiAAAAGwEFAAEAAABq
AAAAKAEDAAEAAAACAAAAMQECABwAAAByAAAAMgECABQAAACOAAAAaYcEAAEAAACiAAAAzAAAAID8
CgAQJwAAgPwKABAnAABBZG9iZSBQaG90b3Nob3AgQ1MyIFdpbmRvd3MAMjAwNzowMjoyNiAxNjox
ODo1MwADAAGgAwABAAAA/////wKgBAABAAAAZgAAAAOgBAABAAAAIAAAAAAAAAAGAAMBAwABAAAA
BgAAABoBBQABAAAAGgEAABsBBQABAAAAIgEAACgBAwABAAAAAgAAAAECBAABAAAAKgEAAAICBAAB
AAAAVAYAAAAAAABIAAAAAQAAAEgAAAABAAAA/9j/4AAQSkZJRgABAgAASABIAAD/7QAMQWRvYmVf
Q00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwM
DAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwM
DAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMBIgACEQED
EQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAA
AAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQV
UsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0
pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRB
UWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKz
hMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/
APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC66f56f3t3
0Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUsVaDHl/dl
/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5VtnsU/qp1vqP
UvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9w9+kqfV+
qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVhfWLCzerW
9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX146P1azq
FWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKehSWDk/XHp
VHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8tbvSU9Iku
cy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uoJBeNpMtf
Rc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxbqtG20uI0
PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv/QXjOu9C
OI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5Fztrrn/us
XoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4HX+6yY/j
QHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v6hNyW9Q6
jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m+u1tQc9n
0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6tfRj2YnT
gMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJJT5b0bpf
UrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6rWuLnfpNj
Xu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z/9sAQwAI
BgYHBgUIBwcHCQkICgwUDQwLCwwZEhMPFB0aHx4dGhwcICQuJyAiLCMcHCg3KSwwMTQ0NB8nOT04
MjwuMzQy/9sAQwEJCQkMCwwYDQ0YMiEcITIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIy/8AAEQgAIABmAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAA
AAABAgMEBQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGh
CCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV
1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkK
C//EALURAAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy
0QoWJDThJfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKD
hIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm
5+jp6vLz9PX29/j5+v/aAAwDAQACEQMRAD8A99LKCASAT0FcOvxDin8XjRre2Bt1l8mS4Zud3Tge
ma5X4j67qukeObG5hdkhto1e3H8L5+9n1z0rnriVIvF9pqdmP9E1CdLiPn7pLDcp9wcj8q8+vimn
yx0sz6zLsihOj7WtrzxbXk/87a/f2PazrqpqL27oBEsnlhwec+4rYyCSM8jtXj0OupJ4hvZbhytr
aSvNOfYHhfqTgVJ4G8R6nrfxAuLklzbTRMZlz8qKPu/THSnSxT5rS1u9Dlr5HNU5VVooxu/8vX/g
dz1+iszX9at/Dug3mr3Su9vax+Y4jGWI9qz9U8ZafpXgtfFE0U7WTQpKEVRvw2McZ967z506Oiuf
03xbY6n4juNDhjmFzBaR3bMw+Xa4BA+vIp2leKrHV9d1nSIElSfSXVJ2cAKdwyMH8KAN6iuM0P4l
6J4hn1eDTkuJJdNRpCpUAzICQWTnkZFK/wASdEj8Ar4wInNiSF8sKPMD7tu3GcZBoA7KiuSu/iDo
9p4NsvE22eW0vWRII41BkZ2OAuM9Rg/lVbUviXptnq82lWem6pql7bgfaUsbfzBCT2Y5xn2oA7ai
uB134q6V4b0nTb7VdM1K3N/v2W7xASJtOPmGeOtFAHnupab4l8P3s+kX+nT6ro/mFoCVLgAngo45
RvUfpWr4a8NnUmFrB5qwxyrcol0hSS3YEZB7MrDjI74r0TxX4MtPFSRNLd3VpcRcLNbyEHHcEdDV
zQPDGn+G7XyrNZHdv9ZPM5d3+p/oK4/q153ex9Is9ccNyrSfktL93/wN+uh5n4m8NNp8ssEvm+Rc
TtcyC2QvJOSTtUDsqjue5NZumaX4h1meLStP06fTNLLgzHaV3Ad3c8sfbp7V7Frnh6w8QWohvEcM
v3JYmKun0P8AjVHwx4PtfDJleO7urueQYMk75wvoB0FTLC+/psa0s/UcLaWtRbXWl++/57dNCp8S
reR/hjrlvBG8shtNqqilmbkdhXmniXwPqEPweS7XW/EFzKbWE/2dI+6MHjK7MZwP6V73RXcfLHj8
V+3g34ivrOq2F9/ZmoaPbwx3MFu0oWRAMqwUZB4rDe/1hIPGWsaXpl/HJ4lu4rPTPMhZXIwQ0hGM
qAO59a98ooA8Fl0Dxb4DvvDmuXNnp8tlpiiwnTTUdpJIHPJcEc4Jzx3pkOgagvj2HwV9gmfw+dY/
thZmQ+X5XllvLPGOuePWvfaKAPBfD2iapL48svB91ZTLpGhalPqKTsp2SKeY1B6cE5/Oqg0u58Le
LfEMes33imwjvLs3FvcaOheKdSSfmwCcjOK+haKAPm34sWlxqvhPwrJpi6zqcY8/M13CxnPzD74x
ke3tRX0lRQB//9k=

------_=_NextPart_001_01C93820.876413AD--

--===============1286756725==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1286756725==--


From ancp-bounces@ietf.org  Mon Oct 27 03:48:53 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DAEE3A6820;
	Mon, 27 Oct 2008 03:48:53 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 899633A67D9
	for <ancp@core3.amsl.com>; Mon, 27 Oct 2008 03:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.048
X-Spam-Level: ***
X-Spam-Status: No, score=3.048 tagged_above=-999 required=5 tests=[AWL=2.696, 
	BAYES_50=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 nZsHFg5C3Foc for <ancp@core3.amsl.com>;
	Mon, 27 Oct 2008 03:48:50 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 9F3BF3A6820
	for <ancp@ietf.org>; Mon, 27 Oct 2008 03:48:49 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com
	[155.132.6.75])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9RAmha3026905; 
	Mon, 27 Oct 2008 11:48:47 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.56]) by
	FRVELSBHS03.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Mon, 27 Oct 2008 11:48:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 11:48:44 +0100
Message-ID: <7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA (was: ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScgAKwVUcA==
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com>
	<D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
From: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>
To: "Reith, Lothar" <Lothar.Reith@detecon.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 10:48:45.0822 (UTC)
	FILETIME=[95FCD1E0:01C93821]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1304953293=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1304953293==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93821.9567B0D7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93821.9567B0D7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Lothar,
=20
I think the term "Delegation of Authority" captures the principle of
what bandwidth delegation is about. I'm fine either way, and would like
to ask other people on this list what they think.
=20
Regards,
Sven

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Reith, Lothar
Sent: zondag 26 oktober 2008 16:47
To: ancp@ietf.org
Subject: [ANCP] DOA (was: ANCP Framework update)


Dear all,
=20
the ANCP Framework contains the word "delegation", which in my mind is
key to the whole concept of ANCP.=20
=20
I would like to suggest that the concept of "delegation" should be made
more extensible.=20
=20
Narrowing it to the term "bandwidth delegation" does not lend itself
very well to extensibility.
=20
I would rather propose to introduce the more general term of DOA
(Delegation of Authority), which is a well known concept in the real
world, when a resource owner delegates control over part or all of his
resources to someone else - e.g. during a vacation absence.
=20
Today, ANCP does not just support delegation in the form of bandwidth
delegation, but also in the form of delegation of content access control
(delegation occurs for whitelist and blacklist content, but not for the
greylist content).
=20
I think the extensible concept "DOA" is very powerful when harnessed for
Broadband Access using ANCP.
=20
While updating the framework it may be worth a consideration to add this
hook for extensibility by following means:
=20
- replace the term "bandwidth delegation" by "DOA for part of access
circuit bandwidth"
=20
- introduce the first extension of the DOA concept by making clear that
the concepts of  whitelist and blacklist are DOA for Content Access
Control.
=20
One more point with respect to the recent discussion about renaming the
Policy Server.
=20
I like to state that I am fine with the current name "policy server".
Historically, I beleive the name was chosen as a compromise between the
RADIUS camp and the COPS camp.
=20
If - given this background - we still want to change the name of the
policy server, then perhaps DOA-server may be another alternative to
consider.=20
=20
An important argument in this case would be, that the concept of
"delegation of authority" is well aligned with the proxy concept,
similar to a RADIUS Proxy Server, where the delegation of authority
happens along a delegation chain which may span multiple RADIUS proxy
servers and multiple domains. This aspect is missing in the other
proposed names.
=20
Best Regards,
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20

________________________________

Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
Gesendet: Do 23.10.2008 12:57
An: ancp@ietf.org
Betreff: Re: [ANCP] ANCP Framework update


Hi,
=20
Here's the updated text. I removed any notion of "flags" or how the
Access Node is told whether or not Bandwidth Delegation applies. I also
covered Thomas' comments. Actually not that much work: the general ANCP
requirements as well as the NAS requirements were written in a
high-level way already. I only had to update the general text and some
of the Access Node requirements. Below the extracted text, let me know
your comments.
=20
Regards,
Sven
=20
---
=20
General text
=20
   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.
=20
      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop (as a portion of the Access Loop net data rate),
         and perform video bandwidth accounting for the Access Loop.
         Upon receiving an Admission Request from the AN, the NAS can
         check available "video" bandwidth before admitting or denying
         the multicast flow.  In the process, the NAS may communicate
         with the Policy Server.  For unicast video services such as
         Video on Demand (VoD), the NAS may also be queried (by a Policy
         Server or via on-path CAC signaling), so that it can perform
         admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.
=20
      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List, the AN must perform the
         necessary bandwidth admission control check for the new
         multicast flow, before starting the multicast flow replication.

Access Node requirements
=20
   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.
=20
   o  The AN must accept any join to a multicast flow matching the White
      List and for which no Bandwidth Delegation is required.
=20
   o  Upon receiving a join to a multicast flow which matches the White
      List whose and for which Bandwidth Delegation is required, the AN
      must perform the necessary bandwidth admission control check for
      the new flow before starting the multicast flow replication.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which no Bandwidth Delegation is required, the AN
      must support using ANCP to query the NAS to receive a response
      indicating whether that join is to be honored or denied.  In this
      case, the NAS will perform both the necessary conditional access
      and the admission control checks for the new flow.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which Bandwidth Delegation is required, the AN must
      first perform the necessary bandwidth admission control check for
      the new flow.  If successful, the AN must support using ANCP to
      query the NAS to receive a response indicating whether that join
      is to be honored or denied.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.
=20
Regards,
Sven

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:58
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update




On 20 Oct 2008, at 12:22, OOGHE Sven wrote:


	Francois,
	=20
	Another approach we could take is to let the framework
requirements be agnostic as to how the Access Node knows whether or not
Bandwidth Delegation applies. We could describe the notion of Bandwidth
Delegation and the respective requirements for the Access Node and NAS
in this case.
	=20
	The details of how the use of Bandwidth Delegation is
communicated to the Access Node - using a flag, some "on/off" knob or
both - would be left to the actual protocol specification work.


Good idea. It will avoid these cross dependencies between framework and
protocol, which indeed reflect that we are probably trying to be too
precise/prescriptive in the framework.


	=20
	I think following this path would require relatively small edits
to the document. I'm ok to take a first shot at it.


That would be good.

Thanks

Francois


	=20
	Regards,
	Sven

________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update
=09
=09
	Sven and all,=20
=09
=09

		   o  Upon receiving a join to a multicast flow which
matches the Grey=20
		      List whose entry is flagged as "no Bandwidth
Delegation" for the=20
		      relevant Access Port, the AN must support using
ANCP to query the=20
		      NAS to receive a response indicating whether that
join is to be=20
		      honored or denied.  In this case, the NAS will
perform both the=20
		      necessary conditional access and the admission
control checks for=20
		      the new flow.


	Roberta, Tom and myself have started drafting an I-D that will
propose ANCP protocol extensions supporting some of those requirements
(building on top of ancp-mc-multicast).
	In doing so, we revisited a point that came up multiple times:
do we really need to provision a flag in each and every Grey/White List
entry to activate/deactivate Bandwidth Delegation?
=09
=09
	The current approach (as correctly reflected in the updated
Framework) is:
	* define a flag in each Grey/White List entry
=09
	* assume that this flag will normally either always be set in
all entries or never set.
=09
	* setting/no-setting the flag is all entries effectively acts as
the knob to enable/disable Bandwidth Delegation, therefore we did not
need to specify a specific knob to enable/disable Bandwidth Delegation.
=09
=09
=09
	Another approach would be:
	* remove flag from White/Grey list entries
=09
	* define a specific knob to enable/disable Bandwidth Delegation
at the AN granularity
	* in fact, define a generic AN-level provisioning method that
could be used to enable/disable BAndwidth delegation, but could also be
used for provisioning the "Service Profiles" that are currently assumed
to be configured in AN, as well as provisioning the Multicast
White/Grey/Black Profiles
=09
=09
=09
	Considering that:
	- we got several times the feedback that per-entry BAndwidth
Delegation flag was confusing since Bandwidth Delegation granularity is
more AN-level (and may lead to difficulties if it is set on some entries
and not on others)
	- it is likely that we'll need, anyways, a mechanism to
provision things at AN level, that could be easily used to convey
Bandwidth Delegation enable/disable knob.
=09
	we would like to propose to evolve to the newer approach.
=09
=09
	Thoughts?

	Francois

	PS: Sven, if we go for the new approach, we can document in an
email the deltas that would be needed to reflect that in framework.




------_=_NextPart_001_01C93821.9567B0D7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY style=3D"WORD-WRAP: break-word">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Lothar,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think the term "Delegation of Authority" =
captures the=20
principle of what bandwidth delegation is about. I'm fine either way, =
and would=20
like to ask other people on this list what they =
think.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Reith, =
Lothar<BR><B>Sent:</B>=20
zondag 26 oktober 2008 16:47<BR><B>To:</B> =
ancp@ietf.org<BR><B>Subject:</B>=20
[ANCP] DOA (was: ANCP Framework update)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=3DidOWAReplyText66978 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Dear =
all,</FONT></DIV>
<DIV>
<DIV id=3DidOWAReplyText68228 dir=3Dltr>
<DIV id=3DidOWAReplyText93369 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>the ANCP Framework contains =
the word=20
"delegation", which in my mind is key to the whole concept of ANCP.=20
</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I would like to suggest that =
the concept of=20
"delegation" should be made more extensible. </FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Narrowing it to the term =
"bandwidth=20
delegation" does not lend itself very well to =
extensibility.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I would rather propose to =
introduce the=20
more general term of DOA (Delegation of Authority), which </FONT><FONT=20
face=3DArial size=3D2>is a well known concept in the real world, when a =
resource=20
owner delegates control over part or all of his resources to someone =
else - e.g.=20
during a vacation absence.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Today, ANCP does not just =
support=20
delegation in the form of bandwidth delegation, but also in the form of=20
delegation of content access control (delegation occurs for whitelist =
and=20
blacklist content, but not for the greylist content).</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think the extensible =
concept=20
"DOA"&nbsp;is very powerful when harnessed for Broadband Access using=20
ANCP.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>While updating the framework =
it may be=20
worth a consideration to add this hook for extensibility by following=20
means:</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>- replace&nbsp;the term =
"bandwidth=20
delegation" by "DOA for part of access circuit bandwidth"</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>- introduce the first =
extension of the DOA=20
concept by making clear that the concepts of &nbsp;whitelist and =
blacklist are=20
DOA for Content Access Control.</FONT></DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>One more point with respect to the recent discussion =
about renaming=20
the Policy Server.</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>I like to state that I am fine with the current name =
"policy=20
server".&nbsp;&nbsp;Historically,&nbsp;I beleive&nbsp;the name was =
chosen as a=20
compromise between the RADIUS camp and the COPS camp.</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>If - given this background - we&nbsp;still want to change =
the name=20
of the policy server, then perhaps DOA-server may be another alternative =
to=20
consider. </DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>An important argument in this case would be, that the =
concept of=20
"delegation of authority" is well aligned with the proxy concept, =
similar to a=20
RADIUS Proxy Server, where the delegation of authority happens along a=20
delegation chain which may span multiple RADIUS proxy servers and =
multiple=20
domains. This aspect is missing in the other proposed names.</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Lothar Reith</FONT></DIV>
<DIV dir=3Dltr>Detecon International GmbH (Deutsche Telekom Group)</DIV>
<DIV dir=3Dltr>&nbsp;</DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>Von:</B> ancp-bounces@ietf.org im =
Auftrag von OOGHE=20
Sven<BR><B>Gesendet:</B> Do 23.10.2008 12:57<BR><B>An:</B>=20
ancp@ietf.org<BR><B>Betreff:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Here's the updated text. I removed any notion =
of "flags" or=20
how the Access Node is told whether or not Bandwidth Delegation applies. =
I also=20
covered Thomas' comments. Actually not that much work: the general ANCP=20
requirements as well as the NAS requirements were written in a =
high-level=20
way&nbsp;already. I only had to update the general text and some of the =
Access=20
Node requirements. Below the extracted text, let me know your=20
comments.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>---</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><STRONG>General =
text</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; One approach is for the AN =
to query=20
the NAS so that Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for =
the=20
access line is performed by the NAS (possibly=20
with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interactions with a Policy =
Server).&nbsp;=20
This can be done with or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without =
"bandwidth=20
delegation" to the AN.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In =
case of=20
Admission Control without AN Bandwidth=20
Delegation,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
can use=20
ANCP to query the NAS, that in turn=20
performs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
Admission=20
Control check for the new multicast=20
flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and responds to =
the AN=20
indicating whether the join is to=20
be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored (and =
hence=20
replication performed by the AN) or=20
denied.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may =
locally=20
maintain available "video" bandwidth on=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop (as =
a=20
portion of the Access Loop net data=20
rate),<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and perform =
video=20
bandwidth accounting for the Access=20
Loop.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon receiving =
an=20
Admission Request from the AN, the NAS=20
can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check available =
"video"=20
bandwidth before admitting or=20
denying<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast=20
flow.&nbsp; In the process, the NAS may=20
communicate</EM></FONT></SPAN></DIV><SPAN class=3D852244910-23102008>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the =
Policy=20
Server.&nbsp; For unicast video services such=20
as<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video on Demand =
(VoD),=20
the NAS may also be queried (by a=20
Policy<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server or via =
on-path=20
CAC signaling), so that it can=20
perform<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission =
control=20
for the unicast flow, and update=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available video=20
bandwidth maintained by the NAS.</EM></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission =
Control=20
with AN Bandwidth Delegation,=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS (possibly =
with=20
interactions with a Policy Server)=20
manages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for=20
video admission, performs unicast=20
admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control =
and uses=20
ANCP to delegate a certain amount of=20
bandwidth<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast=20
flows to the Access Node.&nbsp; In this=20
scenario,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =
receiving a=20
join to a multicast flow which matches=20
an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or=20
Grey List, the AN must perform=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
bandwidth=20
admission control check for the=20
new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow, =
before=20
starting the multicast flow replication.<BR></EM></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><STRONG>Access Node=20
requirements</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must deny any join =
to a=20
multicast flow matching the Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
for the=20
relevant Access Port.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must accept any =
join to a=20
multicast flow matching the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
and for=20
which no Bandwidth Delegation is required.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List=20
whose and for which Bandwidth Delegation is required, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must perform the necessary =
bandwidth=20
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow=20
before starting the multicast flow replication.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and=20
for which no Bandwidth Delegation is required, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS to=20
receive a response<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating whether =
that=20
join is to be honored or denied.&nbsp; In =
this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
case, the NAS will perform both the necessary conditional=20
access<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the admission control =
checks for=20
the new flow.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and=20
for which Bandwidth Delegation is required, the AN=20
must<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first perform the necessary =
bandwidth=20
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
flow.&nbsp; If successful, the AN must support using ANCP=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the NAS to receive a response =

indicating whether that join<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored=20
or denied.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN=20
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to notify the NAS when the the user=20
leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =
flow.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN=20
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to query the NAS to request=20
additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated multicast =
bandwidth on a=20
given Access Port; the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be =
able to=20
specify both the minimum and the =
preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
amount of additional multicast bandwidth requested.</FONT></SPAN></DIV>
<DIV><SPAN class=3D852244910-23102008><FONT face=3DArial color=3D#0000ff =

size=3D2><BR>&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN =
Bandwidth=20
Delegation, upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =

Delegation Request from the NAS querying =
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
instructing to decrease the delegated multicast bandwidth on=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support using=20
ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth Delegation =
Response=20
indicating the new delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =

bandwidth.</DIV>
<DIV>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with=20
AN Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to send a Bandwidth Release message to=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to release unused =
delegated=20
multicast bandwidth on a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access=20
Port.</DIV>
<DIV>&nbsp;</DIV></FONT></SPAN></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> maandag 20 oktober 2008=20
12:58<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT><BR>
<DIV>
<DIV>On 20 Oct 2008, at 12:22, OOGHE Sven wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Another approach we could take is to let the =
framework=20
  requirements be agnostic as to how the Access Node knows whether or =
not=20
  Bandwidth Delegation applies. We could describe the notion of =
Bandwidth=20
  Delegation and the respective requirements for the Access Node and NAS =
in this=20
  case.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The details of how the use of Bandwidth =
Delegation is=20
  communicated to the Access Node - using a flag, some "on/off" knob or =
both -=20
  would be left to the actual protocol specification=20
  work.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Good idea. It will avoid these cross dependencies between framework =
and=20
protocol, which indeed reflect that we are probably trying to be too=20
precise/prescriptive in&nbsp;the&nbsp;framework.</DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I think following this path would require =
relatively=20
  small edits to the document. I'm ok to take a first shot at=20
  it.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>That would be good.</DIV>
<DIV><BR></DIV>
<DIV>Thanks</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A=20
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
  <BR><B>Sent:</B> maandag 20 oktober 2008 12:01<BR><B>To:</B> OOGHE=20
  Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP; <A=20
  href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> Re: =
[ANCP]=20
  ANCP Framework update<BR></FONT><BR></DIV>
  <DIV></DIV>Sven and all,=20
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>
  <DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to=20
    a multicast flow which matches the Grey</FONT></I> <BR><I><FONT =
face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is flagged =
as "no=20
    Bandwidth Delegation" for the</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, the AN =
must=20
    support using ANCP to query the</FONT></I> <BR><I><FONT face=3DArial =

    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a response =
indicating=20
    whether that join is to be</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; In =
this case,=20
    the NAS will perform both the</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional access =
and the=20
    admission control checks for</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
  flow.</FONT></I></P></DIV></BLOCKQUOTE><BR></DIV>
  <DIV>
  <DIV>Roberta, Tom and myself have started drafting an I-D that will =
propose=20
  ANCP protocol extensions supporting some of those requirements =
(building on=20
  top of ancp-mc-multicast).</DIV>
  <DIV>In doing so, we revisited a point that came up multiple times: do =
we=20
  really need to provision a flag in each and every Grey/White List =
entry=20
  to&nbsp;activate/deactivate&nbsp;Bandwidth Delegation?</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>The current approach (as correctly reflected in the updated =
Framework)=20
  is:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
  flag in each Grey/White List entry<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
assume that=20
  this flag will normally either always be set in all entries or never=20
  set.<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>*=20
  setting/no-setting the flag is all entries effectively acts as the =
knob to=20
  enable/disable Bandwidth Delegation, therefore we did not need to =
specify a=20
  specific knob to enable/disable Bandwidth Delegation.<BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Another approach would be:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
remove flag=20
  from White/Grey list entries<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
  specific knob to enable/disable Bandwidth Delegation at the AN=20
  granularity</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
in fact,=20
  define a generic&nbsp;AN-level provisioning method that could be used =
to=20
  enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for=20
  provisioning the "Service Profiles" that are currently assumed to be=20
  configured in AN, as well as provisioning the Multicast =
White/Grey/Black=20
  Profiles<BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Considering that:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
we got=20
  several times the feedback that per-entry BAndwidth Delegation flag =
was=20
  confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and=20
  may lead to difficulties if it is set on some entries and not on =
others)</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
it is likely=20
  that we'll need, anyways, a mechanism to provision things at AN level, =
that=20
  could be easily used to convey Bandwidth Delegation enable/disable=20
  knob.<BR></DIV>
  <DIV>we&nbsp;would&nbsp;like to propose=20
  to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Thoughts?</DIV>
  <DIV><BR></DIV>
  <DIV>Francois</DIV>
  <DIV><BR></DIV>
  <DIV>PS: Sven, if we go for&nbsp;the&nbsp;new approach, we can =
document in an=20
  email the deltas that&nbsp;would&nbsp;be needed to reflect that in=20
  framework.</DIV>
  =
<DIV><BR></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV=
></FONT></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C93821.9567B0D7--

--===============1304953293==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1304953293==--


From ancp-bounces@ietf.org  Tue Oct 28 02:00:47 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D1C93A6968;
	Tue, 28 Oct 2008 02:00:47 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFA923A683A
	for <ancp@core3.amsl.com>; Tue, 28 Oct 2008 02:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_LOW=-1]
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 Hg5hHzrdmFe1 for <ancp@core3.amsl.com>;
	Tue, 28 Oct 2008 02:00:44 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [217.6.95.237])
	by core3.amsl.com (Postfix) with ESMTP id 12DAE3A682A
	for <ancp@ietf.org>; Tue, 28 Oct 2008 02:00:43 -0700 (PDT)
Received: from S4DE8PSAANQ.mitte.t-com.de (S4DE8PSAANQ.mitte.t-com.de
	[10.151.180.166]) by tcmail21.telekom.de with ESMTP;
	Tue, 28 Oct 2008 09:34:44 +0100
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by
	S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Oct 2008 09:34:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 09:34:42 +0100
Message-Id: <5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA (was: ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScgAKwVUcAAte4Tg
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com><D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
	<7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Haag, Thomas" <HaagT@telekom.de>
To: <Sven.Ooghe@alcatel-lucent.be>
X-OriginalArrivalTime: 28 Oct 2008 08:34:44.0183 (UTC)
	FILETIME=[0735D670:01C938D8]
Cc: ancp@ietf.org
Subject: Re: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1318279124=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1318279124==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C938D8.06F3A910"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C938D8.06F3A910
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Sven,
=20
I also agree on DOA.=20
This covers the issue in a better way.
=20
Regards
Thomas

________________________________

Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von
OOGHE Sven
Gesendet: Montag, 27. Oktober 2008 11:49
An: Reith, Lothar; ancp@ietf.org
Betreff: Re: [ANCP] DOA (was: ANCP Framework update)


Hi Lothar,
=20
I think the term "Delegation of Authority" captures the principle of
what bandwidth delegation is about. I'm fine either way, and would like
to ask other people on this list what they think.
=20
Regards,
Sven

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Reith, Lothar
Sent: zondag 26 oktober 2008 16:47
To: ancp@ietf.org
Subject: [ANCP] DOA (was: ANCP Framework update)


Dear all,
=20
the ANCP Framework contains the word "delegation", which in my mind is
key to the whole concept of ANCP.=20
=20
I would like to suggest that the concept of "delegation" should be made
more extensible.=20
=20
Narrowing it to the term "bandwidth delegation" does not lend itself
very well to extensibility.
=20
I would rather propose to introduce the more general term of DOA
(Delegation of Authority), which is a well known concept in the real
world, when a resource owner delegates control over part or all of his
resources to someone else - e.g. during a vacation absence.
=20
Today, ANCP does not just support delegation in the form of bandwidth
delegation, but also in the form of delegation of content access control
(delegation occurs for whitelist and blacklist content, but not for the
greylist content).
=20
I think the extensible concept "DOA" is very powerful when harnessed for
Broadband Access using ANCP.
=20
While updating the framework it may be worth a consideration to add this
hook for extensibility by following means:
=20
- replace the term "bandwidth delegation" by "DOA for part of access
circuit bandwidth"
=20
- introduce the first extension of the DOA concept by making clear that
the concepts of  whitelist and blacklist are DOA for Content Access
Control.
=20
One more point with respect to the recent discussion about renaming the
Policy Server.
=20
I like to state that I am fine with the current name "policy server".
Historically, I beleive the name was chosen as a compromise between the
RADIUS camp and the COPS camp.
=20
If - given this background - we still want to change the name of the
policy server, then perhaps DOA-server may be another alternative to
consider.=20
=20
An important argument in this case would be, that the concept of
"delegation of authority" is well aligned with the proxy concept,
similar to a RADIUS Proxy Server, where the delegation of authority
happens along a delegation chain which may span multiple RADIUS proxy
servers and multiple domains. This aspect is missing in the other
proposed names.
=20
Best Regards,
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20

________________________________

Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
Gesendet: Do 23.10.2008 12:57
An: ancp@ietf.org
Betreff: Re: [ANCP] ANCP Framework update


Hi,
=20
Here's the updated text. I removed any notion of "flags" or how the
Access Node is told whether or not Bandwidth Delegation applies. I also
covered Thomas' comments. Actually not that much work: the general ANCP
requirements as well as the NAS requirements were written in a
high-level way already. I only had to update the general text and some
of the Access Node requirements. Below the extracted text, let me know
your comments.
=20
Regards,
Sven
=20
---
=20
General text
=20
   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.
=20
      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop (as a portion of the Access Loop net data rate),
         and perform video bandwidth accounting for the Access Loop.
         Upon receiving an Admission Request from the AN, the NAS can
         check available "video" bandwidth before admitting or denying
         the multicast flow.  In the process, the NAS may communicate
         with the Policy Server.  For unicast video services such as
         Video on Demand (VoD), the NAS may also be queried (by a Policy
         Server or via on-path CAC signaling), so that it can perform
         admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.
=20
      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List, the AN must perform the
         necessary bandwidth admission control check for the new
         multicast flow, before starting the multicast flow replication.

Access Node requirements
=20
   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.
=20
   o  The AN must accept any join to a multicast flow matching the White
      List and for which no Bandwidth Delegation is required.
=20
   o  Upon receiving a join to a multicast flow which matches the White
      List whose and for which Bandwidth Delegation is required, the AN
      must perform the necessary bandwidth admission control check for
      the new flow before starting the multicast flow replication.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which no Bandwidth Delegation is required, the AN
      must support using ANCP to query the NAS to receive a response
      indicating whether that join is to be honored or denied.  In this
      case, the NAS will perform both the necessary conditional access
      and the admission control checks for the new flow.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which Bandwidth Delegation is required, the AN must
      first perform the necessary bandwidth admission control check for
      the new flow.  If successful, the AN must support using ANCP to
      query the NAS to receive a response indicating whether that join
      is to be honored or denied.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.
=20
Regards,
Sven

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:58
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update




On 20 Oct 2008, at 12:22, OOGHE Sven wrote:


	Francois,
	=20
	Another approach we could take is to let the framework
requirements be agnostic as to how the Access Node knows whether or not
Bandwidth Delegation applies. We could describe the notion of Bandwidth
Delegation and the respective requirements for the Access Node and NAS
in this case.
	=20
	The details of how the use of Bandwidth Delegation is
communicated to the Access Node - using a flag, some "on/off" knob or
both - would be left to the actual protocol specification work.


Good idea. It will avoid these cross dependencies between framework and
protocol, which indeed reflect that we are probably trying to be too
precise/prescriptive in the framework.


	=20
	I think following this path would require relatively small edits
to the document. I'm ok to take a first shot at it.


That would be good.

Thanks

Francois


	=20
	Regards,
	Sven

________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update
=09
=09
	Sven and all,=20
=09
=09

		   o  Upon receiving a join to a multicast flow which
matches the Grey=20
		      List whose entry is flagged as "no Bandwidth
Delegation" for the=20
		      relevant Access Port, the AN must support using
ANCP to query the=20
		      NAS to receive a response indicating whether that
join is to be=20
		      honored or denied.  In this case, the NAS will
perform both the=20
		      necessary conditional access and the admission
control checks for=20
		      the new flow.


	Roberta, Tom and myself have started drafting an I-D that will
propose ANCP protocol extensions supporting some of those requirements
(building on top of ancp-mc-multicast).
	In doing so, we revisited a point that came up multiple times:
do we really need to provision a flag in each and every Grey/White List
entry to activate/deactivate Bandwidth Delegation?
=09
=09
	The current approach (as correctly reflected in the updated
Framework) is:
	* define a flag in each Grey/White List entry
=09
	* assume that this flag will normally either always be set in
all entries or never set.
=09
	* setting/no-setting the flag is all entries effectively acts as
the knob to enable/disable Bandwidth Delegation, therefore we did not
need to specify a specific knob to enable/disable Bandwidth Delegation.
=09
=09
=09
	Another approach would be:
	* remove flag from White/Grey list entries
=09
	* define a specific knob to enable/disable Bandwidth Delegation
at the AN granularity
	* in fact, define a generic AN-level provisioning method that
could be used to enable/disable BAndwidth delegation, but could also be
used for provisioning the "Service Profiles" that are currently assumed
to be configured in AN, as well as provisioning the Multicast
White/Grey/Black Profiles
=09
=09
=09
	Considering that:
	- we got several times the feedback that per-entry BAndwidth
Delegation flag was confusing since Bandwidth Delegation granularity is
more AN-level (and may lead to difficulties if it is set on some entries
and not on others)
	- it is likely that we'll need, anyways, a mechanism to
provision things at AN level, that could be easily used to convey
Bandwidth Delegation enable/disable knob.
=09
	we would like to propose to evolve to the newer approach.
=09
=09
	Thoughts?

	Francois

	PS: Sven, if we go for the new approach, we can document in an
email the deltas that would be needed to reflect that in framework.




------_=_NextPart_001_01C938D8.06F3A910
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>

<META content=3D"MSHTML 6.00.2900.3354" name=3DGENERATOR></HEAD>
<BODY style=3D"WORD-WRAP: break-word">
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008>Hi Sven,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008>I also agree on DOA. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008>This covers the issue in a better=20
way.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008>Regards</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D109113008-28102008>Thomas</SPAN></FONT></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>Von:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>Im Auftrag von </B>OOGHE=20
Sven<BR><B>Gesendet:</B> Montag, 27. Oktober 2008 11:49<BR><B>An:</B> =
Reith,=20
Lothar; ancp@ietf.org<BR><B>Betreff:</B> Re: [ANCP] DOA (was: ANCP =
Framework=20
update)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Lothar,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think the term "Delegation of Authority" =
captures the=20
principle of what bandwidth delegation is about. I'm fine either way, =
and would=20
like to ask other people on this list what they =
think.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D114524710-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Reith, =
Lothar<BR><B>Sent:</B>=20
zondag 26 oktober 2008 16:47<BR><B>To:</B> =
ancp@ietf.org<BR><B>Subject:</B>=20
[ANCP] DOA (was: ANCP Framework update)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=3DidOWAReplyText66978 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Dear =
all,</FONT></DIV>
<DIV>
<DIV id=3DidOWAReplyText68228 dir=3Dltr>
<DIV id=3DidOWAReplyText93369 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>the ANCP Framework contains =
the word=20
"delegation", which in my mind is key to the whole concept of ANCP.=20
</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I would like to suggest that =
the concept of=20
"delegation" should be made more extensible. </FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Narrowing it to the term =
"bandwidth=20
delegation" does not lend itself very well to =
extensibility.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I would rather propose to =
introduce the=20
more general term of DOA (Delegation of Authority), which </FONT><FONT=20
face=3DArial size=3D2>is a well known concept in the real world, when a =
resource=20
owner delegates control over part or all of his resources to someone =
else - e.g.=20
during a vacation absence.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Today, ANCP does not just =
support=20
delegation in the form of bandwidth delegation, but also in the form of=20
delegation of content access control (delegation occurs for whitelist =
and=20
blacklist content, but not for the greylist content).</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I think the extensible =
concept=20
"DOA"&nbsp;is very powerful when harnessed for Broadband Access using=20
ANCP.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>While updating the framework =
it may be=20
worth a consideration to add this hook for extensibility by following=20
means:</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>- replace&nbsp;the term =
"bandwidth=20
delegation" by "DOA for part of access circuit bandwidth"</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>- introduce the first =
extension of the DOA=20
concept by making clear that the concepts of &nbsp;whitelist and =
blacklist are=20
DOA for Content Access Control.</FONT></DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>One more point with respect to the recent discussion =
about renaming=20
the Policy Server.</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>I like to state that I am fine with the current name =
"policy=20
server".&nbsp;&nbsp;Historically,&nbsp;I beleive&nbsp;the name was =
chosen as a=20
compromise between the RADIUS camp and the COPS camp.</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>If - given this background - we&nbsp;still want to change =
the name=20
of the policy server, then perhaps DOA-server may be another alternative =
to=20
consider. </DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr>An important argument in this case would be, that the =
concept of=20
"delegation of authority" is well aligned with the proxy concept, =
similar to a=20
RADIUS Proxy Server, where the delegation of authority happens along a=20
delegation chain which may span multiple RADIUS proxy servers and =
multiple=20
domains. This aspect is missing in the other proposed names.</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Lothar Reith</FONT></DIV>
<DIV dir=3Dltr>Detecon International GmbH (Deutsche Telekom Group)</DIV>
<DIV dir=3Dltr>&nbsp;</DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>Von:</B> ancp-bounces@ietf.org im =
Auftrag von OOGHE=20
Sven<BR><B>Gesendet:</B> Do 23.10.2008 12:57<BR><B>An:</B>=20
ancp@ietf.org<BR><B>Betreff:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Here's the updated text. I removed any notion =
of "flags" or=20
how the Access Node is told whether or not Bandwidth Delegation applies. =
I also=20
covered Thomas' comments. Actually not that much work: the general ANCP=20
requirements as well as the NAS requirements were written in a =
high-level=20
way&nbsp;already. I only had to update the general text and some of the =
Access=20
Node requirements. Below the extracted text, let me know your=20
comments.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>---</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><STRONG>General =
text</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; One approach is for the AN =
to query=20
the NAS so that Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for =
the=20
access line is performed by the NAS (possibly=20
with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interactions with a Policy =
Server).&nbsp;=20
This can be done with or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without =
"bandwidth=20
delegation" to the AN.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In =
case of=20
Admission Control without AN Bandwidth=20
Delegation,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
can use=20
ANCP to query the NAS, that in turn=20
performs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
Admission=20
Control check for the new multicast=20
flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and responds to =
the AN=20
indicating whether the join is to=20
be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored (and =
hence=20
replication performed by the AN) or=20
denied.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may =
locally=20
maintain available "video" bandwidth on=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop (as =
a=20
portion of the Access Loop net data=20
rate),<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and perform =
video=20
bandwidth accounting for the Access=20
Loop.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon receiving =
an=20
Admission Request from the AN, the NAS=20
can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check available =
"video"=20
bandwidth before admitting or=20
denying<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast=20
flow.&nbsp; In the process, the NAS may=20
communicate</EM></FONT></SPAN></DIV><SPAN class=3D852244910-23102008>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the =
Policy=20
Server.&nbsp; For unicast video services such=20
as<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video on Demand =
(VoD),=20
the NAS may also be queried (by a=20
Policy<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server or via =
on-path=20
CAC signaling), so that it can=20
perform<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission =
control=20
for the unicast flow, and update=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available video=20
bandwidth maintained by the NAS.</EM></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission =
Control=20
with AN Bandwidth Delegation,=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS (possibly =
with=20
interactions with a Policy Server)=20
manages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for=20
video admission, performs unicast=20
admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control =
and uses=20
ANCP to delegate a certain amount of=20
bandwidth<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast=20
flows to the Access Node.&nbsp; In this=20
scenario,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =
receiving a=20
join to a multicast flow which matches=20
an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or=20
Grey List, the AN must perform=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
bandwidth=20
admission control check for the=20
new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow, =
before=20
starting the multicast flow replication.<BR></EM></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><STRONG>Access Node=20
requirements</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must deny any join =
to a=20
multicast flow matching the Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
for the=20
relevant Access Port.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; The AN must accept any =
join to a=20
multicast flow matching the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
and for=20
which no Bandwidth Delegation is required.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List=20
whose and for which Bandwidth Delegation is required, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must perform the necessary =
bandwidth=20
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow=20
before starting the multicast flow replication.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and=20
for which no Bandwidth Delegation is required, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS to=20
receive a response<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating whether =
that=20
join is to be honored or denied.&nbsp; In =
this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
case, the NAS will perform both the necessary conditional=20
access<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the admission control =
checks for=20
the new flow.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join =
to a=20
multicast flow which matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
List and=20
for which Bandwidth Delegation is required, the AN=20
must<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first perform the necessary =
bandwidth=20
admission control check for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
flow.&nbsp; If successful, the AN must support using ANCP=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the NAS to receive a response =

indicating whether that join<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored=20
or denied.</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN=20
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to notify the NAS when the the user=20
leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =
flow.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with AN=20
Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to query the NAS to request=20
additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated multicast =
bandwidth on a=20
given Access Port; the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be =
able to=20
specify both the minimum and the =
preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
amount of additional multicast bandwidth requested.</FONT></SPAN></DIV>
<DIV><SPAN class=3D852244910-23102008><FONT face=3DArial color=3D#0000ff =

size=3D2><BR>&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN =
Bandwidth=20
Delegation, upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =

Delegation Request from the NAS querying =
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
instructing to decrease the delegated multicast bandwidth on=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support using=20
ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth Delegation =
Response=20
indicating the new delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =

bandwidth.</DIV>
<DIV>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>&nbsp;&nbsp; o&nbsp; In case of Admission =
Control with=20
AN Bandwidth Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support=20
using ANCP to send a Bandwidth Release message to=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to release unused =
delegated=20
multicast bandwidth on a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access=20
Port.</DIV>
<DIV>&nbsp;</DIV></FONT></SPAN></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> maandag 20 oktober 2008=20
12:58<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT><BR>
<DIV>
<DIV>On 20 Oct 2008, at 12:22, OOGHE Sven wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Another approach we could take is to let the =
framework=20
  requirements be agnostic as to how the Access Node knows whether or =
not=20
  Bandwidth Delegation applies. We could describe the notion of =
Bandwidth=20
  Delegation and the respective requirements for the Access Node and NAS =
in this=20
  case.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The details of how the use of Bandwidth =
Delegation is=20
  communicated to the Access Node - using a flag, some "on/off" knob or =
both -=20
  would be left to the actual protocol specification=20
  work.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Good idea. It will avoid these cross dependencies between framework =
and=20
protocol, which indeed reflect that we are probably trying to be too=20
precise/prescriptive in&nbsp;the&nbsp;framework.</DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I think following this path would require =
relatively=20
  small edits to the document. I'm ok to take a first shot at=20
  it.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>That would be good.</DIV>
<DIV><BR></DIV>
<DIV>Thanks</DIV>
<DIV><BR></DIV>
<DIV>Francois</DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP =
[<A=20
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]=20
  <BR><B>Sent:</B> maandag 20 oktober 2008 12:01<BR><B>To:</B> OOGHE=20
  Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP; <A=20
  href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B>Subject:</B> Re: =
[ANCP]=20
  ANCP Framework update<BR></FONT><BR></DIV>
  <DIV></DIV>Sven and all,=20
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>
  <DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <P><I><FONT face=3DArial size=3D2>&nbsp;&nbsp; o&nbsp; Upon =
receiving a join to=20
    a multicast flow which matches the Grey</FONT></I> <BR><I><FONT =
face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is flagged =
as "no=20
    Bandwidth Delegation" for the</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, the AN =
must=20
    support using ANCP to query the</FONT></I> <BR><I><FONT face=3DArial =

    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a response =
indicating=20
    whether that join is to be</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; In =
this case,=20
    the NAS will perform both the</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional access =
and the=20
    admission control checks for</FONT></I> <BR><I><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
  flow.</FONT></I></P></DIV></BLOCKQUOTE><BR></DIV>
  <DIV>
  <DIV>Roberta, Tom and myself have started drafting an I-D that will =
propose=20
  ANCP protocol extensions supporting some of those requirements =
(building on=20
  top of ancp-mc-multicast).</DIV>
  <DIV>In doing so, we revisited a point that came up multiple times: do =
we=20
  really need to provision a flag in each and every Grey/White List =
entry=20
  to&nbsp;activate/deactivate&nbsp;Bandwidth Delegation?</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>The current approach (as correctly reflected in the updated =
Framework)=20
  is:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
  flag in each Grey/White List entry<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
assume that=20
  this flag will normally either always be set in all entries or never=20
  set.<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>*=20
  setting/no-setting the flag is all entries effectively acts as the =
knob to=20
  enable/disable Bandwidth Delegation, therefore we did not need to =
specify a=20
  specific knob to enable/disable Bandwidth Delegation.<BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Another approach would be:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
remove flag=20
  from White/Grey list entries<BR></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
define a=20
  specific knob to enable/disable Bandwidth Delegation at the AN=20
  granularity</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
in fact,=20
  define a generic&nbsp;AN-level provisioning method that could be used =
to=20
  enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be used =
for=20
  provisioning the "Service Profiles" that are currently assumed to be=20
  configured in AN, as well as provisioning the Multicast =
White/Grey/Black=20
  Profiles<BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Considering that:</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
we got=20
  several times the feedback that per-entry BAndwidth Delegation flag =
was=20
  confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and=20
  may lead to difficulties if it is set on some entries and not on =
others)</DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>- =
it is likely=20
  that we'll need, anyways, a mechanism to provision things at AN level, =
that=20
  could be easily used to convey Bandwidth Delegation enable/disable=20
  knob.<BR></DIV>
  <DIV>we&nbsp;would&nbsp;like to propose=20
  to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><BR></DIV>
  <DIV>Thoughts?</DIV>
  <DIV><BR></DIV>
  <DIV>Francois</DIV>
  <DIV><BR></DIV>
  <DIV>PS: Sven, if we go for&nbsp;the&nbsp;new approach, we can =
document in an=20
  email the deltas that&nbsp;would&nbsp;be needed to reflect that in=20
  framework.</DIV>
  =
<DIV><BR></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV=
></FONT></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C938D8.06F3A910--

--===============1318279124==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1318279124==--


From ancp-bounces@ietf.org  Tue Oct 28 06:02:26 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D319A3A6C35;
	Tue, 28 Oct 2008 06:02:26 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BACFD3A6C35
	for <ancp@core3.amsl.com>; Tue, 28 Oct 2008 06:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599]
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 fXxaoAG6GESd for <ancp@core3.amsl.com>;
	Tue, 28 Oct 2008 06:02:24 -0700 (PDT)
Received: from smtp106.rog.mail.re2.yahoo.com (smtp106.rog.mail.re2.yahoo.com
	[68.142.225.204])
	by core3.amsl.com (Postfix) with SMTP id D365A3A6C34
	for <ancp@ietf.org>; Tue, 28 Oct 2008 06:02:23 -0700 (PDT)
Received: (qmail 39978 invoked from network); 28 Oct 2008 13:02:22 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com;
	h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=ON9GvtVUvXpKF8VdOfDHiTH+r9BofGqs2nvHSMKj1hZmmmBLIzNF5QrEkHJ7VzIDRFAWC2i1bC1ULKw/ENsXJIDp3lLyMmWUC26MJ936U+1bZc6ewuro+mM5Tcqv5YYFZqLpphZdpYhYKZ+hnp0g0Ai6eSbLxgCuGN3iZnVqEMM=
	; 
Received: from unknown (HELO ?192.168.0.100?) (tom.taylor@72.140.46.24 with
	plain)
	by smtp106.rog.mail.re2.yahoo.com with SMTP; 28 Oct 2008 13:02:22 -0000
X-YMail-OSG: Kbvp2mQVM1nAZPh6Z79VUD.D.7bF4s3udblfTspzJe1RA0ZFb.VWkXgVJOPa1MMigA--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <49070D5D.2020604@rogers.com>
Date: Tue, 28 Oct 2008 09:02:21 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Haag, Thomas" <HaagT@telekom.de>
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com><D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>	<7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com>
	<5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de>
Cc: Sven.Ooghe@alcatel-lucent.be, ancp@ietf.org
Subject: Re: [ANCP] DOA
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

I don't mind. I coined the phrase "bandwidth delegation" to express what was 
happening. The only thing is, "DOA" has unfortunate connotations -- it's a 
notation that appears on ambulance drivers' reports (Dead on Arrival) when their 
patient dies before reaching the hospital. So I'd prefer that "Delegation of 
Authority" be spelled out.

Haag, Thomas wrote:
> Hi Sven,
>  
> I also agree on DOA. 
> This covers the issue in a better way.
>  
> Regards
> Thomas
> 
> ________________________________
> 
> Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von
> OOGHE Sven
> Gesendet: Montag, 27. Oktober 2008 11:49
> An: Reith, Lothar; ancp@ietf.org
> Betreff: Re: [ANCP] DOA (was: ANCP Framework update)
> 
> 
> Hi Lothar,
>  
> I think the term "Delegation of Authority" captures the principle of
> what bandwidth delegation is about. I'm fine either way, and would like
> to ask other people on this list what they think.
>  
> Regards,
> Sven
> 
> ________________________________
> 
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
> Reith, Lothar
> Sent: zondag 26 oktober 2008 16:47
> To: ancp@ietf.org
> Subject: [ANCP] DOA (was: ANCP Framework update)
> 
> 
> Dear all,
>  
> the ANCP Framework contains the word "delegation", which in my mind is
> key to the whole concept of ANCP. 
>  
> I would like to suggest that the concept of "delegation" should be made
> more extensible. 
>  
> Narrowing it to the term "bandwidth delegation" does not lend itself
> very well to extensibility.
>  
> I would rather propose to introduce the more general term of DOA
> (Delegation of Authority), which is a well known concept in the real
> world, when a resource owner delegates control over part or all of his
> resources to someone else - e.g. during a vacation absence.
>  
> Today, ANCP does not just support delegation in the form of bandwidth
> delegation, but also in the form of delegation of content access control
> (delegation occurs for whitelist and blacklist content, but not for the
> greylist content).
>  
> I think the extensible concept "DOA" is very powerful when harnessed for
> Broadband Access using ANCP.
>  
> While updating the framework it may be worth a consideration to add this
> hook for extensibility by following means:
>  
> - replace the term "bandwidth delegation" by "DOA for part of access
> circuit bandwidth"
>  
> - introduce the first extension of the DOA concept by making clear that
> the concepts of  whitelist and blacklist are DOA for Content Access
> Control.
>  
> One more point with respect to the recent discussion about renaming the
> Policy Server.
>  
> I like to state that I am fine with the current name "policy server".
> Historically, I beleive the name was chosen as a compromise between the
> RADIUS camp and the COPS camp.
>  
> If - given this background - we still want to change the name of the
> policy server, then perhaps DOA-server may be another alternative to
> consider. 
>  
> An important argument in this case would be, that the concept of
> "delegation of authority" is well aligned with the proxy concept,
> similar to a RADIUS Proxy Server, where the delegation of authority
> happens along a delegation chain which may span multiple RADIUS proxy
> servers and multiple domains. This aspect is missing in the other
> proposed names.
>  
> Best Regards,
>  
> Lothar Reith
> Detecon International GmbH (Deutsche Telekom Group)
>  
> 
> ________________________________
> 
> Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
> Gesendet: Do 23.10.2008 12:57
> An: ancp@ietf.org
> Betreff: Re: [ANCP] ANCP Framework update
> 
> 
> Hi,
>  
> Here's the updated text. I removed any notion of "flags" or how the
> Access Node is told whether or not Bandwidth Delegation applies. I also
> covered Thomas' comments. Actually not that much work: the general ANCP
> requirements as well as the NAS requirements were written in a
> high-level way already. I only had to update the general text and some
> of the Access Node requirements. Below the extracted text, let me know
> your comments.
>  
> Regards,
> Sven
>  
> ---
>  
> General text
>  
>    o  One approach is for the AN to query the NAS so that Admission
>       Control for the access line is performed by the NAS (possibly with
>       interactions with a Policy Server).  This can be done with or
>       without "bandwidth delegation" to the AN.
>  
>       *  In case of Admission Control without AN Bandwidth Delegation,
>          the AN can use ANCP to query the NAS, that in turn performs
>          multicast Admission Control check for the new multicast flow
>          and responds to the AN indicating whether the join is to be
>          honored (and hence replication performed by the AN) or denied.
>          The NAS may locally maintain available "video" bandwidth on the
>          Access Loop (as a portion of the Access Loop net data rate),
>          and perform video bandwidth accounting for the Access Loop.
>          Upon receiving an Admission Request from the AN, the NAS can
>          check available "video" bandwidth before admitting or denying
>          the multicast flow.  In the process, the NAS may communicate
>          with the Policy Server.  For unicast video services such as
>          Video on Demand (VoD), the NAS may also be queried (by a Policy
>          Server or via on-path CAC signaling), so that it can perform
>          admission control for the unicast flow, and update the
>          available video bandwidth maintained by the NAS.
>  
>       *  In case of Admission Control with AN Bandwidth Delegation, the
>          NAS (possibly with interactions with a Policy Server) manages
>          total bandwidth for video admission, performs unicast admission
>          control and uses ANCP to delegate a certain amount of bandwidth
>          for some multicast flows to the Access Node.  In this scenario,
>          upon receiving a join to a multicast flow which matches an
>          entry in the White or Grey List, the AN must perform the
>          necessary bandwidth admission control check for the new
>          multicast flow, before starting the multicast flow replication.
> 
> Access Node requirements
>  
>    o  The AN must deny any join to a multicast flow matching the Black
>       List for the relevant Access Port.
>  
>    o  The AN must accept any join to a multicast flow matching the White
>       List and for which no Bandwidth Delegation is required.
>  
>    o  Upon receiving a join to a multicast flow which matches the White
>       List whose and for which Bandwidth Delegation is required, the AN
>       must perform the necessary bandwidth admission control check for
>       the new flow before starting the multicast flow replication.
>  
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which no Bandwidth Delegation is required, the AN
>       must support using ANCP to query the NAS to receive a response
>       indicating whether that join is to be honored or denied.  In this
>       case, the NAS will perform both the necessary conditional access
>       and the admission control checks for the new flow.
>  
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which Bandwidth Delegation is required, the AN must
>       first perform the necessary bandwidth admission control check for
>       the new flow.  If successful, the AN must support using ANCP to
>       query the NAS to receive a response indicating whether that join
>       is to be honored or denied.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the AN
>       must support using ANCP to notify the NAS when the the user leaves
>       the multicast flow.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the AN
>       must support using ANCP to query the NAS to request additional
>       delegated multicast bandwidth on a given Access Port; the AN
>       should be able to specify both the minimum and the preferred
>       amount of additional multicast bandwidth requested.
> 
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving a Bandwidth Delegation Request from the NAS querying or
>       instructing to decrease the delegated multicast bandwidth on a
>       given Access Port, the AN must support using ANCP to send a
>       Bandwidth Delegation Response indicating the new delegated
>       multicast bandwidth.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the AN
>       must support using ANCP to send a Bandwidth Release message to the
>       NAS in order to release unused delegated multicast bandwidth on a
>       given Access Port.
>  
> Regards,
> Sven
> 
> ________________________________
> 
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] 
> Sent: maandag 20 oktober 2008 12:58
> To: OOGHE Sven
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> Subject: Re: [ANCP] ANCP Framework update
> 
> 
> 
> 
> On 20 Oct 2008, at 12:22, OOGHE Sven wrote:
> 
> 
> 	Francois,
> 	 
> 	Another approach we could take is to let the framework
> requirements be agnostic as to how the Access Node knows whether or not
> Bandwidth Delegation applies. We could describe the notion of Bandwidth
> Delegation and the respective requirements for the Access Node and NAS
> in this case.
> 	 
> 	The details of how the use of Bandwidth Delegation is
> communicated to the Access Node - using a flag, some "on/off" knob or
> both - would be left to the actual protocol specification work.
> 
> 
> Good idea. It will avoid these cross dependencies between framework and
> protocol, which indeed reflect that we are probably trying to be too
> precise/prescriptive in the framework.
> 
> 
> 	 
> 	I think following this path would require relatively small edits
> to the document. I'm ok to take a first shot at it.
> 
> 
> That would be good.
> 
> Thanks
> 
> Francois
> 
> 
> 	 
> 	Regards,
> 	Sven
> 
> ________________________________
> 
> 	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] 
> 	Sent: maandag 20 oktober 2008 12:01
> 	To: OOGHE Sven
> 	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> 	Subject: Re: [ANCP] ANCP Framework update
> 	
> 	
> 	Sven and all, 
> 	
> 	
> 
> 		   o  Upon receiving a join to a multicast flow which
> matches the Grey 
> 		      List whose entry is flagged as "no Bandwidth
> Delegation" for the 
> 		      relevant Access Port, the AN must support using
> ANCP to query the 
> 		      NAS to receive a response indicating whether that
> join is to be 
> 		      honored or denied.  In this case, the NAS will
> perform both the 
> 		      necessary conditional access and the admission
> control checks for 
> 		      the new flow.
> 
> 
> 	Roberta, Tom and myself have started drafting an I-D that will
> propose ANCP protocol extensions supporting some of those requirements
> (building on top of ancp-mc-multicast).
> 	In doing so, we revisited a point that came up multiple times:
> do we really need to provision a flag in each and every Grey/White List
> entry to activate/deactivate Bandwidth Delegation?
> 	
> 	
> 	The current approach (as correctly reflected in the updated
> Framework) is:
> 	* define a flag in each Grey/White List entry
> 	
> 	* assume that this flag will normally either always be set in
> all entries or never set.
> 	
> 	* setting/no-setting the flag is all entries effectively acts as
> the knob to enable/disable Bandwidth Delegation, therefore we did not
> need to specify a specific knob to enable/disable Bandwidth Delegation.
> 	
> 	
> 	
> 	Another approach would be:
> 	* remove flag from White/Grey list entries
> 	
> 	* define a specific knob to enable/disable Bandwidth Delegation
> at the AN granularity
> 	* in fact, define a generic AN-level provisioning method that
> could be used to enable/disable BAndwidth delegation, but could also be
> used for provisioning the "Service Profiles" that are currently assumed
> to be configured in AN, as well as provisioning the Multicast
> White/Grey/Black Profiles
> 	
> 	
> 	
> 	Considering that:
> 	- we got several times the feedback that per-entry BAndwidth
> Delegation flag was confusing since Bandwidth Delegation granularity is
> more AN-level (and may lead to difficulties if it is set on some entries
> and not on others)
> 	- it is likely that we'll need, anyways, a mechanism to
> provision things at AN level, that could be easily used to convey
> Bandwidth Delegation enable/disable knob.
> 	
> 	we would like to propose to evolve to the newer approach.
> 	
> 	
> 	Thoughts?
> 
> 	Francois
> 
> 	PS: Sven, if we go for the new approach, we can document in an
> email the deltas that would be needed to reflect that in framework.
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 28 08:12:11 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0E8528C2DB;
	Tue, 28 Oct 2008 08:12:11 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BC1828C2DB
	for <ancp@core3.amsl.com>; Tue, 28 Oct 2008 08:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.522
X-Spam-Level: 
X-Spam-Status: No, score=-4.522 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077]
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 6xJFsPmTiAul for <ancp@core3.amsl.com>;
	Tue, 28 Oct 2008 08:12:09 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171])
	by core3.amsl.com (Postfix) with ESMTP id B6EAE28C2D8
	for <ancp@ietf.org>; Tue, 28 Oct 2008 08:12:05 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob109.postini.com
	([64.18.6.12]) with SMTP; Tue, 28 Oct 2008 08:11:56 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp01.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Oct 2008 08:11:11 -0700
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Oct 2008 08:11:11 -0700
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 11:11:08 -0400
Message-ID: <3525C9833C09ED418C6FD6CD9514668C04F70C13@emailwf1.jnpr.net>
In-Reply-To: <49070D5D.2020604@rogers.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA
Thread-Index: Ack4/XL8dDL57Sh4Rp2O9SGfurF1GwAEP36g
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com><D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>	<7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com><5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de>
	<49070D5D.2020604@rogers.com>
From: "Jerome Moisand" <jmoisand@juniper.net>
To: "Tom Taylor" <tom.taylor@rogers.com>,
	"Haag, Thomas" <HaagT@telekom.de>
X-OriginalArrivalTime: 28 Oct 2008 15:11:11.0066 (UTC)
	FILETIME=[694C23A0:01C9390F]
Cc: Sven.Ooghe@alcatel-lucent.be, ancp@ietf.org
Subject: Re: [ANCP] DOA
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Folks,

Actually, in the very early days of L2CP (wasn't called ANCP by then)
discussions in the DSL-Forum, we did come up with the term "Delegation
of Authorization" terminology to describe the essence of the concept.

"Authorization" is a direct reference to AAA concepts, whether this is
an initial authorization (at user session establishment time), or
dynamic change of authorization (i.e. in-session).

We certainly didn't notice the unfortunate side-effect with ambulance
driver reports... But still, I always liked this "Delegation of
Authorization" terminology. A BRAS/BNG is essentially an authorization
enforcer for subscriber/service management. And ANCP is a mechanism to
delegate some of that enforcement to the access node.

Cheers,
Jerome - the ghost

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Tom Taylor
Sent: Tuesday, October 28, 2008 9:02 AM
To: Haag, Thomas
Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org
Subject: Re: [ANCP] DOA

I don't mind. I coined the phrase "bandwidth delegation" to express what
was 
happening. The only thing is, "DOA" has unfortunate connotations -- it's
a 
notation that appears on ambulance drivers' reports (Dead on Arrival)
when their 
patient dies before reaching the hospital. So I'd prefer that
"Delegation of 
Authority" be spelled out.

Haag, Thomas wrote:
> Hi Sven,
>  
> I also agree on DOA. 
> This covers the issue in a better way.
>  
> Regards
> Thomas
> 
> ________________________________
> 
> Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag
von
> OOGHE Sven
> Gesendet: Montag, 27. Oktober 2008 11:49
> An: Reith, Lothar; ancp@ietf.org
> Betreff: Re: [ANCP] DOA (was: ANCP Framework update)
> 
> 
> Hi Lothar,
>  
> I think the term "Delegation of Authority" captures the principle of
> what bandwidth delegation is about. I'm fine either way, and would
like
> to ask other people on this list what they think.
>  
> Regards,
> Sven
> 
> ________________________________
> 
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf
Of
> Reith, Lothar
> Sent: zondag 26 oktober 2008 16:47
> To: ancp@ietf.org
> Subject: [ANCP] DOA (was: ANCP Framework update)
> 
> 
> Dear all,
>  
> the ANCP Framework contains the word "delegation", which in my mind is
> key to the whole concept of ANCP. 
>  
> I would like to suggest that the concept of "delegation" should be
made
> more extensible. 
>  
> Narrowing it to the term "bandwidth delegation" does not lend itself
> very well to extensibility.
>  
> I would rather propose to introduce the more general term of DOA
> (Delegation of Authority), which is a well known concept in the real
> world, when a resource owner delegates control over part or all of his
> resources to someone else - e.g. during a vacation absence.
>  
> Today, ANCP does not just support delegation in the form of bandwidth
> delegation, but also in the form of delegation of content access
control
> (delegation occurs for whitelist and blacklist content, but not for
the
> greylist content).
>  
> I think the extensible concept "DOA" is very powerful when harnessed
for
> Broadband Access using ANCP.
>  
> While updating the framework it may be worth a consideration to add
this
> hook for extensibility by following means:
>  
> - replace the term "bandwidth delegation" by "DOA for part of access
> circuit bandwidth"
>  
> - introduce the first extension of the DOA concept by making clear
that
> the concepts of  whitelist and blacklist are DOA for Content Access
> Control.
>  
> One more point with respect to the recent discussion about renaming
the
> Policy Server.
>  
> I like to state that I am fine with the current name "policy server".
> Historically, I beleive the name was chosen as a compromise between
the
> RADIUS camp and the COPS camp.
>  
> If - given this background - we still want to change the name of the
> policy server, then perhaps DOA-server may be another alternative to
> consider. 
>  
> An important argument in this case would be, that the concept of
> "delegation of authority" is well aligned with the proxy concept,
> similar to a RADIUS Proxy Server, where the delegation of authority
> happens along a delegation chain which may span multiple RADIUS proxy
> servers and multiple domains. This aspect is missing in the other
> proposed names.
>  
> Best Regards,
>  
> Lothar Reith
> Detecon International GmbH (Deutsche Telekom Group)
>  
> 
> ________________________________
> 
> Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
> Gesendet: Do 23.10.2008 12:57
> An: ancp@ietf.org
> Betreff: Re: [ANCP] ANCP Framework update
> 
> 
> Hi,
>  
> Here's the updated text. I removed any notion of "flags" or how the
> Access Node is told whether or not Bandwidth Delegation applies. I
also
> covered Thomas' comments. Actually not that much work: the general
ANCP
> requirements as well as the NAS requirements were written in a
> high-level way already. I only had to update the general text and some
> of the Access Node requirements. Below the extracted text, let me know
> your comments.
>  
> Regards,
> Sven
>  
> ---
>  
> General text
>  
>    o  One approach is for the AN to query the NAS so that Admission
>       Control for the access line is performed by the NAS (possibly
with
>       interactions with a Policy Server).  This can be done with or
>       without "bandwidth delegation" to the AN.
>  
>       *  In case of Admission Control without AN Bandwidth Delegation,
>          the AN can use ANCP to query the NAS, that in turn performs
>          multicast Admission Control check for the new multicast flow
>          and responds to the AN indicating whether the join is to be
>          honored (and hence replication performed by the AN) or
denied.
>          The NAS may locally maintain available "video" bandwidth on
the
>          Access Loop (as a portion of the Access Loop net data rate),
>          and perform video bandwidth accounting for the Access Loop.
>          Upon receiving an Admission Request from the AN, the NAS can
>          check available "video" bandwidth before admitting or denying
>          the multicast flow.  In the process, the NAS may communicate
>          with the Policy Server.  For unicast video services such as
>          Video on Demand (VoD), the NAS may also be queried (by a
Policy
>          Server or via on-path CAC signaling), so that it can perform
>          admission control for the unicast flow, and update the
>          available video bandwidth maintained by the NAS.
>  
>       *  In case of Admission Control with AN Bandwidth Delegation,
the
>          NAS (possibly with interactions with a Policy Server) manages
>          total bandwidth for video admission, performs unicast
admission
>          control and uses ANCP to delegate a certain amount of
bandwidth
>          for some multicast flows to the Access Node.  In this
scenario,
>          upon receiving a join to a multicast flow which matches an
>          entry in the White or Grey List, the AN must perform the
>          necessary bandwidth admission control check for the new
>          multicast flow, before starting the multicast flow
replication.
> 
> Access Node requirements
>  
>    o  The AN must deny any join to a multicast flow matching the Black
>       List for the relevant Access Port.
>  
>    o  The AN must accept any join to a multicast flow matching the
White
>       List and for which no Bandwidth Delegation is required.
>  
>    o  Upon receiving a join to a multicast flow which matches the
White
>       List whose and for which Bandwidth Delegation is required, the
AN
>       must perform the necessary bandwidth admission control check for
>       the new flow before starting the multicast flow replication.
>  
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which no Bandwidth Delegation is required, the AN
>       must support using ANCP to query the NAS to receive a response
>       indicating whether that join is to be honored or denied.  In
this
>       case, the NAS will perform both the necessary conditional access
>       and the admission control checks for the new flow.
>  
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which Bandwidth Delegation is required, the AN must
>       first perform the necessary bandwidth admission control check
for
>       the new flow.  If successful, the AN must support using ANCP to
>       query the NAS to receive a response indicating whether that join
>       is to be honored or denied.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to notify the NAS when the the user
leaves
>       the multicast flow.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to query the NAS to request additional
>       delegated multicast bandwidth on a given Access Port; the AN
>       should be able to specify both the minimum and the preferred
>       amount of additional multicast bandwidth requested.
> 
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving a Bandwidth Delegation Request from the NAS querying
or
>       instructing to decrease the delegated multicast bandwidth on a
>       given Access Port, the AN must support using ANCP to send a
>       Bandwidth Delegation Response indicating the new delegated
>       multicast bandwidth.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to send a Bandwidth Release message to
the
>       NAS in order to release unused delegated multicast bandwidth on
a
>       given Access Port.
>  
> Regards,
> Sven
> 
> ________________________________
> 
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] 
> Sent: maandag 20 oktober 2008 12:58
> To: OOGHE Sven
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> Subject: Re: [ANCP] ANCP Framework update
> 
> 
> 
> 
> On 20 Oct 2008, at 12:22, OOGHE Sven wrote:
> 
> 
> 	Francois,
> 	 
> 	Another approach we could take is to let the framework
> requirements be agnostic as to how the Access Node knows whether or
not
> Bandwidth Delegation applies. We could describe the notion of
Bandwidth
> Delegation and the respective requirements for the Access Node and NAS
> in this case.
> 	 
> 	The details of how the use of Bandwidth Delegation is
> communicated to the Access Node - using a flag, some "on/off" knob or
> both - would be left to the actual protocol specification work.
> 
> 
> Good idea. It will avoid these cross dependencies between framework
and
> protocol, which indeed reflect that we are probably trying to be too
> precise/prescriptive in the framework.
> 
> 
> 	 
> 	I think following this path would require relatively small edits
> to the document. I'm ok to take a first shot at it.
> 
> 
> That would be good.
> 
> Thanks
> 
> Francois
> 
> 
> 	 
> 	Regards,
> 	Sven
> 
> ________________________________
> 
> 	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] 
> 	Sent: maandag 20 oktober 2008 12:01
> 	To: OOGHE Sven
> 	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> 	Subject: Re: [ANCP] ANCP Framework update
> 	
> 	
> 	Sven and all, 
> 	
> 	
> 
> 		   o  Upon receiving a join to a multicast flow which
> matches the Grey 
> 		      List whose entry is flagged as "no Bandwidth
> Delegation" for the 
> 		      relevant Access Port, the AN must support using
> ANCP to query the 
> 		      NAS to receive a response indicating whether that
> join is to be 
> 		      honored or denied.  In this case, the NAS will
> perform both the 
> 		      necessary conditional access and the admission
> control checks for 
> 		      the new flow.
> 
> 
> 	Roberta, Tom and myself have started drafting an I-D that will
> propose ANCP protocol extensions supporting some of those requirements
> (building on top of ancp-mc-multicast).
> 	In doing so, we revisited a point that came up multiple times:
> do we really need to provision a flag in each and every Grey/White
List
> entry to activate/deactivate Bandwidth Delegation?
> 	
> 	
> 	The current approach (as correctly reflected in the updated
> Framework) is:
> 	* define a flag in each Grey/White List entry
> 	
> 	* assume that this flag will normally either always be set in
> all entries or never set.
> 	
> 	* setting/no-setting the flag is all entries effectively acts as
> the knob to enable/disable Bandwidth Delegation, therefore we did not
> need to specify a specific knob to enable/disable Bandwidth
Delegation.
> 	
> 	
> 	
> 	Another approach would be:
> 	* remove flag from White/Grey list entries
> 	
> 	* define a specific knob to enable/disable Bandwidth Delegation
> at the AN granularity
> 	* in fact, define a generic AN-level provisioning method that
> could be used to enable/disable BAndwidth delegation, but could also
be
> used for provisioning the "Service Profiles" that are currently
assumed
> to be configured in AN, as well as provisioning the Multicast
> White/Grey/Black Profiles
> 	
> 	
> 	
> 	Considering that:
> 	- we got several times the feedback that per-entry BAndwidth
> Delegation flag was confusing since Bandwidth Delegation granularity
is
> more AN-level (and may lead to difficulties if it is set on some
entries
> and not on others)
> 	- it is likely that we'll need, anyways, a mechanism to
> provision things at AN level, that could be easily used to convey
> Bandwidth Delegation enable/disable knob.
> 	
> 	we would like to propose to evolve to the newer approach.
> 	
> 	
> 	Thoughts?
> 
> 	Francois
> 
> 	PS: Sven, if we go for the new approach, we can document in an
> email the deltas that would be needed to reflect that in framework.
> 
> 
> 
> 
> 
> 
>
------------------------------------------------------------------------
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 28 08:51:36 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD5F33A6C31;
	Tue, 28 Oct 2008 08:51:36 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38CFD3A695A
	for <ancp@core3.amsl.com>; Tue, 28 Oct 2008 08:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.522
X-Spam-Level: 
X-Spam-Status: No, score=-0.522 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SUBJ_ALL_CAPS=2.077]
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 5-jS0SMtDNZI for <ancp@core3.amsl.com>;
	Tue, 28 Oct 2008 08:51:34 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id B0F0F3A6C31
	for <ancp@ietf.org>; Tue, 28 Oct 2008 08:51:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 51F627F8150;
	Tue, 28 Oct 2008 08:51:34 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 15144-04; Tue, 28 Oct 2008 08:51:34 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh2.redback.com [155.53.14.106])
	by prattle.redback.com (Postfix) with ESMTP id F20C37F814D;
	Tue, 28 Oct 2008 08:51:33 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh2.ad.redback.com ([155.53.14.106]) with mapi;
	Tue, 28 Oct 2008 08:51:33 -0700
From: Peter Arberg <parberg@redback.com>
To: Tom Taylor <tom.taylor@rogers.com>,
	"Sven.Ooghe@alcatel-lucent.be" <Sven.Ooghe@alcatel-lucent.be>
Date: Tue, 28 Oct 2008 08:51:32 -0700
Thread-Topic: [ANCP] DOA
Thread-Index: Ack4/XQnvQtzAUqcTPaWg99QV/vhoQAFyDYQ
Message-ID: <48C276B536524E478C659685995F6AA5904328C9D5@RBSJX.ad.redback.com>
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com><D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
	<7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com>
	<5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de>
	<49070D5D.2020604@rogers.com>
In-Reply-To: <49070D5D.2020604@rogers.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] DOA
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

I agree on the term Delegation of Authority.  Like Tom I will
like us to spell it out instead of creating a new acronym.

cheers,
peter

> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
> Behalf Of Tom Taylor
> Sent: 28. oktober 2008 06:02
> To: Haag, Thomas
> Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org
> Subject: Re: [ANCP] DOA
>
> I don't mind. I coined the phrase "bandwidth delegation" to
> express what was
> happening. The only thing is, "DOA" has unfortunate
> connotations -- it's a
> notation that appears on ambulance drivers' reports (Dead on
> Arrival) when their
> patient dies before reaching the hospital. So I'd prefer that
> "Delegation of
> Authority" be spelled out.
>
> Haag, Thomas wrote:
> > Hi Sven,
> >
> > I also agree on DOA.
> > This covers the issue in a better way.
> >
> > Regards
> > Thomas
> >
> > ________________________________
> >
> > Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]
> Im Auftrag von
> > OOGHE Sven
> > Gesendet: Montag, 27. Oktober 2008 11:49
> > An: Reith, Lothar; ancp@ietf.org
> > Betreff: Re: [ANCP] DOA (was: ANCP Framework update)
> >
> >
> > Hi Lothar,
> >
> > I think the term "Delegation of Authority" captures the principle of
> > what bandwidth delegation is about. I'm fine either way,
> and would like
> > to ask other people on this list what they think.
> >
> > Regards,
> > Sven
> >
> > ________________________________
> >
> > From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]
> On Behalf Of
> > Reith, Lothar
> > Sent: zondag 26 oktober 2008 16:47
> > To: ancp@ietf.org
> > Subject: [ANCP] DOA (was: ANCP Framework update)
> >
> >
> > Dear all,
> >
> > the ANCP Framework contains the word "delegation", which in
> my mind is
> > key to the whole concept of ANCP.
> >
> > I would like to suggest that the concept of "delegation"
> should be made
> > more extensible.
> >
> > Narrowing it to the term "bandwidth delegation" does not lend itself
> > very well to extensibility.
> >
> > I would rather propose to introduce the more general term of DOA
> > (Delegation of Authority), which is a well known concept in the real
> > world, when a resource owner delegates control over part or
> all of his
> > resources to someone else - e.g. during a vacation absence.
> >
> > Today, ANCP does not just support delegation in the form of
> bandwidth
> > delegation, but also in the form of delegation of content
> access control
> > (delegation occurs for whitelist and blacklist content, but
> not for the
> > greylist content).
> >
> > I think the extensible concept "DOA" is very powerful when
> harnessed for
> > Broadband Access using ANCP.
> >
> > While updating the framework it may be worth a
> consideration to add this
> > hook for extensibility by following means:
> >
> > - replace the term "bandwidth delegation" by "DOA for part of access
> > circuit bandwidth"
> >
> > - introduce the first extension of the DOA concept by
> making clear that
> > the concepts of  whitelist and blacklist are DOA for Content Access
> > Control.
> >
> > One more point with respect to the recent discussion about
> renaming the
> > Policy Server.
> >
> > I like to state that I am fine with the current name
> "policy server".
> > Historically, I beleive the name was chosen as a compromise
> between the
> > RADIUS camp and the COPS camp.
> >
> > If - given this background - we still want to change the name of the
> > policy server, then perhaps DOA-server may be another alternative to
> > consider.
> >
> > An important argument in this case would be, that the concept of
> > "delegation of authority" is well aligned with the proxy concept,
> > similar to a RADIUS Proxy Server, where the delegation of authority
> > happens along a delegation chain which may span multiple
> RADIUS proxy
> > servers and multiple domains. This aspect is missing in the other
> > proposed names.
> >
> > Best Regards,
> >
> > Lothar Reith
> > Detecon International GmbH (Deutsche Telekom Group)
> >
> >
> > ________________________________
> >
> > Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
> > Gesendet: Do 23.10.2008 12:57
> > An: ancp@ietf.org
> > Betreff: Re: [ANCP] ANCP Framework update
> >
> >
> > Hi,
> >
> > Here's the updated text. I removed any notion of "flags" or how the
> > Access Node is told whether or not Bandwidth Delegation
> applies. I also
> > covered Thomas' comments. Actually not that much work: the
> general ANCP
> > requirements as well as the NAS requirements were written in a
> > high-level way already. I only had to update the general
> text and some
> > of the Access Node requirements. Below the extracted text,
> let me know
> > your comments.
> >
> > Regards,
> > Sven
> >
> > ---
> >
> > General text
> >
> >    o  One approach is for the AN to query the NAS so that Admission
> >       Control for the access line is performed by the NAS
> (possibly with
> >       interactions with a Policy Server).  This can be done with or
> >       without "bandwidth delegation" to the AN.
> >
> >       *  In case of Admission Control without AN Bandwidth
> Delegation,
> >          the AN can use ANCP to query the NAS, that in turn performs
> >          multicast Admission Control check for the new
> multicast flow
> >          and responds to the AN indicating whether the join is to be
> >          honored (and hence replication performed by the
> AN) or denied.
> >          The NAS may locally maintain available "video"
> bandwidth on the
> >          Access Loop (as a portion of the Access Loop net
> data rate),
> >          and perform video bandwidth accounting for the Access Loop.
> >          Upon receiving an Admission Request from the AN,
> the NAS can
> >          check available "video" bandwidth before admitting
> or denying
> >          the multicast flow.  In the process, the NAS may
> communicate
> >          with the Policy Server.  For unicast video services such as
> >          Video on Demand (VoD), the NAS may also be queried
> (by a Policy
> >          Server or via on-path CAC signaling), so that it
> can perform
> >          admission control for the unicast flow, and update the
> >          available video bandwidth maintained by the NAS.
> >
> >       *  In case of Admission Control with AN Bandwidth
> Delegation, the
> >          NAS (possibly with interactions with a Policy
> Server) manages
> >          total bandwidth for video admission, performs
> unicast admission
> >          control and uses ANCP to delegate a certain amount
> of bandwidth
> >          for some multicast flows to the Access Node.  In
> this scenario,
> >          upon receiving a join to a multicast flow which matches an
> >          entry in the White or Grey List, the AN must perform the
> >          necessary bandwidth admission control check for the new
> >          multicast flow, before starting the multicast flow
> replication.
> >
> > Access Node requirements
> >
> >    o  The AN must deny any join to a multicast flow
> matching the Black
> >       List for the relevant Access Port.
> >
> >    o  The AN must accept any join to a multicast flow
> matching the White
> >       List and for which no Bandwidth Delegation is required.
> >
> >    o  Upon receiving a join to a multicast flow which
> matches the White
> >       List whose and for which Bandwidth Delegation is
> required, the AN
> >       must perform the necessary bandwidth admission
> control check for
> >       the new flow before starting the multicast flow replication.
> >
> >    o  Upon receiving a join to a multicast flow which
> matches the Grey
> >       List and for which no Bandwidth Delegation is required, the AN
> >       must support using ANCP to query the NAS to receive a response
> >       indicating whether that join is to be honored or
> denied.  In this
> >       case, the NAS will perform both the necessary
> conditional access
> >       and the admission control checks for the new flow.
> >
> >    o  Upon receiving a join to a multicast flow which
> matches the Grey
> >       List and for which Bandwidth Delegation is required,
> the AN must
> >       first perform the necessary bandwidth admission
> control check for
> >       the new flow.  If successful, the AN must support
> using ANCP to
> >       query the NAS to receive a response indicating
> whether that join
> >       is to be honored or denied.
> >
> >    o  In case of Admission Control with AN Bandwidth
> Delegation, the AN
> >       must support using ANCP to notify the NAS when the
> the user leaves
> >       the multicast flow.
> >
> >    o  In case of Admission Control with AN Bandwidth
> Delegation, the AN
> >       must support using ANCP to query the NAS to request additional
> >       delegated multicast bandwidth on a given Access Port; the AN
> >       should be able to specify both the minimum and the preferred
> >       amount of additional multicast bandwidth requested.
> >
> >    o  In case of Admission Control with AN Bandwidth
> Delegation, upon
> >       receiving a Bandwidth Delegation Request from the NAS
> querying or
> >       instructing to decrease the delegated multicast bandwidth on a
> >       given Access Port, the AN must support using ANCP to send a
> >       Bandwidth Delegation Response indicating the new delegated
> >       multicast bandwidth.
> >
> >    o  In case of Admission Control with AN Bandwidth
> Delegation, the AN
> >       must support using ANCP to send a Bandwidth Release
> message to the
> >       NAS in order to release unused delegated multicast
> bandwidth on a
> >       given Access Port.
> >
> > Regards,
> > Sven
> >
> > ________________________________
> >
> > From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> > Sent: maandag 20 oktober 2008 12:58
> > To: OOGHE Sven
> > Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> > Subject: Re: [ANCP] ANCP Framework update
> >
> >
> >
> >
> > On 20 Oct 2008, at 12:22, OOGHE Sven wrote:
> >
> >
> >       Francois,
> >
> >       Another approach we could take is to let the framework
> > requirements be agnostic as to how the Access Node knows
> whether or not
> > Bandwidth Delegation applies. We could describe the notion
> of Bandwidth
> > Delegation and the respective requirements for the Access
> Node and NAS
> > in this case.
> >
> >       The details of how the use of Bandwidth Delegation is
> > communicated to the Access Node - using a flag, some
> "on/off" knob or
> > both - would be left to the actual protocol specification work.
> >
> >
> > Good idea. It will avoid these cross dependencies between
> framework and
> > protocol, which indeed reflect that we are probably trying to be too
> > precise/prescriptive in the framework.
> >
> >
> >
> >       I think following this path would require relatively
> small edits
> > to the document. I'm ok to take a first shot at it.
> >
> >
> > That would be good.
> >
> > Thanks
> >
> > Francois
> >
> >
> >
> >       Regards,
> >       Sven
> >
> > ________________________________
> >
> >       From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> >       Sent: maandag 20 oktober 2008 12:01
> >       To: OOGHE Sven
> >       Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> >       Subject: Re: [ANCP] ANCP Framework update
> >
> >
> >       Sven and all,
> >
> >
> >
> >                  o  Upon receiving a join to a multicast flow which
> > matches the Grey
> >                     List whose entry is flagged as "no Bandwidth
> > Delegation" for the
> >                     relevant Access Port, the AN must support using
> > ANCP to query the
> >                     NAS to receive a response indicating
> whether that
> > join is to be
> >                     honored or denied.  In this case, the NAS will
> > perform both the
> >                     necessary conditional access and the admission
> > control checks for
> >                     the new flow.
> >
> >
> >       Roberta, Tom and myself have started drafting an I-D that will
> > propose ANCP protocol extensions supporting some of those
> requirements
> > (building on top of ancp-mc-multicast).
> >       In doing so, we revisited a point that came up multiple times:
> > do we really need to provision a flag in each and every
> Grey/White List
> > entry to activate/deactivate Bandwidth Delegation?
> >
> >
> >       The current approach (as correctly reflected in the updated
> > Framework) is:
> >       * define a flag in each Grey/White List entry
> >
> >       * assume that this flag will normally either always be set in
> > all entries or never set.
> >
> >       * setting/no-setting the flag is all entries
> effectively acts as
> > the knob to enable/disable Bandwidth Delegation, therefore
> we did not
> > need to specify a specific knob to enable/disable Bandwidth
> Delegation.
> >
> >
> >
> >       Another approach would be:
> >       * remove flag from White/Grey list entries
> >
> >       * define a specific knob to enable/disable Bandwidth
> Delegation
> > at the AN granularity
> >       * in fact, define a generic AN-level provisioning method that
> > could be used to enable/disable BAndwidth delegation, but
> could also be
> > used for provisioning the "Service Profiles" that are
> currently assumed
> > to be configured in AN, as well as provisioning the Multicast
> > White/Grey/Black Profiles
> >
> >
> >
> >       Considering that:
> >       - we got several times the feedback that per-entry BAndwidth
> > Delegation flag was confusing since Bandwidth Delegation
> granularity is
> > more AN-level (and may lead to difficulties if it is set on
> some entries
> > and not on others)
> >       - it is likely that we'll need, anyways, a mechanism to
> > provision things at AN level, that could be easily used to convey
> > Bandwidth Delegation enable/disable knob.
> >
> >       we would like to propose to evolve to the newer approach.
> >
> >
> >       Thoughts?
> >
> >       Francois
> >
> >       PS: Sven, if we go for the new approach, we can document in an
> > email the deltas that would be needed to reflect that in framework.
> >
> >
> >
> >
> >
> >
> >
> --------------------------------------------------------------
> ----------
> >
> > _______________________________________________
> > ANCP mailing list
> > ANCP@ietf.org
> > https://www.ietf.org/mailman/listinfo/ancp
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Tue Oct 28 10:09:28 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF4E728C1AB;
	Tue, 28 Oct 2008 10:09:28 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 622D83A6C8A
	for <ancp@core3.amsl.com>; Tue, 28 Oct 2008 10:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.318
X-Spam-Level: 
X-Spam-Status: No, score=-0.318 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,
	MIME_QP_LONG_LINE=1.396]
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 RX2k0aVHBBju for <ancp@core3.amsl.com>;
	Tue, 28 Oct 2008 10:09:09 -0700 (PDT)
Received: from dtc035.detecon.net (dtc035.detecon.net [194.25.60.135])
	by core3.amsl.com (Postfix) with ESMTP id 2AEA728C21D
	for <ancp@ietf.org>; Tue, 28 Oct 2008 10:09:07 -0700 (PDT)
Received: from unknown (HELO dc00357.detecon.com) ([172.16.10.107])
	by relay.dtc035.detecon.net with ESMTP; 28 Oct 2008 18:09:04 +0100
Received: from DC00331.detecon.com ([172.16.10.78]) by dc00357.detecon.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Oct 2008 18:09:04 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 18:09:03 +0100
Message-ID: <D4ECB93FEDE50045B2657B56894BADF204FA8399@DC00331.detecon.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA (was: ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScgAKwVUcAA5YynwAAUSsJA=
References: <007b01c9390b$3acbad60$9001a8c0@xxxx87e842e29b>
From: "Reith, Lothar" <Lothar.Reith@detecon.com>
To: "Fortune HUANG" <fqhuang@huawei.com>,
	<ancp@ietf.org>
X-OriginalArrivalTime: 28 Oct 2008 17:09:04.0552 (UTC)
	FILETIME=[E16C7280:01C9391F]
Subject: Re: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1854670696=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1854670696==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9391F.E10F304C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9391F.E10F304C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Fortune,
=20
regarding your statement:
=20
The bandwidth can be negotiated dynamically in quantity. When the =
bandwidth on AN is insufficient, AN can ask for more from NAS/PS; when =
the bandwidth is insufficient, NAS/PS can ask for more from AN.
=20
I would like to comment as follows:
=20
Like in the real world, there is a hierarchy with the root being the =
legal owner of the resource, who is also the owner of the authority to =
control the resource. He delegates this authority  downwards through a =
chain of "Delegation of Authority" actions towards some enforcement =
point - in this case the AN. You may well imagine, that the root =
authority over all resource of a telco is with the shareholder annual =
assembly, which delegates it to the Management board, those to the CTO, =
and further to some line managers who delegate the control to some =
Policy Server, where our scope begins.
=20
What you refer to as negotiation, is rather a delegation of authority =
which is quantized with a certain amount of bandwidth. Note that the PS =
may have delegated authority to control the full bandwidth to the NAS, =
but the NAS delegates only part of that bandwidth onwards to the AN.=20
=20
 And yes, the AN may ask for that Delegation of Authority specifying the =
amount desired, and the NAS may grant it. However, if the NAS needs some =
of the delegated authority back for his own purposes, he withdraws part =
of the quantized authority by claiming back part of the previously =
delegated authority over access circuit bandwidth.
=20
The point is:  There is no real negotiation, because the AN and the =
NAS/PS are not peers.=20
=20
The AN has to obey to whatever the NAS grants, and is not allowed to =
exceed the delegated quantity of authority.  Note that the authority =
could be quantized in many ways, e.g. a time limited delegation of =
authority is just one example. Or a volume limited delegation of =
authority. This is still in line with the concept of "delegation of =
authority" in real life, and shows that this extensibility is very =
powerful indeed.=20
=20
=20
Best Regards, Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20
=20
=20
________________________________

Von: Fortune HUANG [mailto:fqhuang@huawei.com]
Gesendet: Di 28.10.2008 15:41
An: 'OOGHE Sven'; Reith, Lothar; ancp@ietf.org
Betreff: ??: [ANCP] DOA (was: ANCP Framework update)



Hi Sven, Lothar et al,

=20

Yes, the "Delegation of Authority" is more generic than "Bandwidth =
Delegation" and I fully agree with the example from Lothar was that not =
only the bandwidth can be delegated but also the content access control =
can be delegated.

=20

However, we have to pay attention to the difference of the delegation of =
bandwidth and the delegation of content access control.

The bandwidth can be negotiated dynamically in quantity. When the =
bandwidth on AN is insufficient, AN can ask for more from NAS/PS; when =
the bandwidth is insufficient, NAS/PS can ask for more from AN.

But this negotiation can not be applied for the content access control =
properly.

=20

That is to say, if we extend the "bandwidth delegation" to "delegation =
of authority", the negotiation still needs to be specified specially for =
the bandwidth.

=20

Best Regards,

Fortune

=20

=20

=20

________________________________

???: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] ?? OOGHE Sven
????: 2008?10?27? 18:49
???: Reith, Lothar; ancp@ietf.org
??: Re: [ANCP] DOA (was: ANCP Framework update)

=20

Hi Lothar,

=20

I think the term "Delegation of Authority" captures the principle of =
what bandwidth delegation is about. I'm fine either way, and would like =
to ask other people on this list what they think.

=20

Regards,

Sven

=20

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Reith, Lothar
Sent: zondag 26 oktober 2008 16:47
To: ancp@ietf.org
Subject: [ANCP] DOA (was: ANCP Framework update)

Dear all,

=20

the ANCP Framework contains the word "delegation", which in my mind is =
key to the whole concept of ANCP.=20

=20

I would like to suggest that the concept of "delegation" should be made =
more extensible.=20

=20

Narrowing it to the term "bandwidth delegation" does not lend itself =
very well to extensibility.

=20

I would rather propose to introduce the more general term of DOA =
(Delegation of Authority), which is a well known concept in the real =
world, when a resource owner delegates control over part or all of his =
resources to someone else - e.g. during a vacation absence.

=20

Today, ANCP does not just support delegation in the form of bandwidth =
delegation, but also in the form of delegation of content access control =
(delegation occurs for whitelist and blacklist content, but not for the =
greylist content).

=20

I think the extensible concept "DOA" is very powerful when harnessed for =
Broadband Access using ANCP.

=20

While updating the framework it may be worth a consideration to add this =
hook for extensibility by following means:

=20

- replace the term "bandwidth delegation" by "DOA for part of access =
circuit bandwidth"

=20

- introduce the first extension of the DOA concept by making clear that =
the concepts of  whitelist and blacklist are DOA for Content Access =
Control.

=20

One more point with respect to the recent discussion about renaming the =
Policy Server.

=20

I like to state that I am fine with the current name "policy server".  =
Historically, I beleive the name was chosen as a compromise between the =
RADIUS camp and the COPS camp.

=20

If - given this background - we still want to change the name of the =
policy server, then perhaps DOA-server may be another alternative to =
consider.=20

=20

An important argument in this case would be, that the concept of =
"delegation of authority" is well aligned with the proxy concept, =
similar to a RADIUS Proxy Server, where the delegation of authority =
happens along a delegation chain which may span multiple RADIUS proxy =
servers and multiple domains. This aspect is missing in the other =
proposed names.

=20

Best Regards,

=20

Lothar Reith

Detecon International GmbH (Deutsche Telekom Group)

=20

=20

________________________________

Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
Gesendet: Do 23.10.2008 12:57
An: ancp@ietf.org
Betreff: Re: [ANCP] ANCP Framework update

Hi,

=20

Here's the updated text. I removed any notion of "flags" or how the =
Access Node is told whether or not Bandwidth Delegation applies. I also =
covered Thomas' comments. Actually not that much work: the general ANCP =
requirements as well as the NAS requirements were written in a =
high-level way already. I only had to update the general text and some =
of the Access Node requirements. Below the extracted text, let me know =
your comments.

=20

Regards,

Sven

=20

---

=20

General text

=20

   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.

=20

      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop (as a portion of the Access Loop net data rate),
         and perform video bandwidth accounting for the Access Loop.
         Upon receiving an Admission Request from the AN, the NAS can
         check available "video" bandwidth before admitting or denying
         the multicast flow.  In the process, the NAS may communicate

         with the Policy Server.  For unicast video services such as
         Video on Demand (VoD), the NAS may also be queried (by a Policy
         Server or via on-path CAC signaling), so that it can perform
         admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.

=20

      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List, the AN must perform the
         necessary bandwidth admission control check for the new
         multicast flow, before starting the multicast flow replication.

Access Node requirements

=20

   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.

=20

   o  The AN must accept any join to a multicast flow matching the White
      List and for which no Bandwidth Delegation is required.

=20

   o  Upon receiving a join to a multicast flow which matches the White
      List whose and for which Bandwidth Delegation is required, the AN
      must perform the necessary bandwidth admission control check for
      the new flow before starting the multicast flow replication.

=20

   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which no Bandwidth Delegation is required, the AN
      must support using ANCP to query the NAS to receive a response
      indicating whether that join is to be honored or denied.  In this
      case, the NAS will perform both the necessary conditional access
      and the admission control checks for the new flow.

=20

   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which Bandwidth Delegation is required, the AN must
      first perform the necessary bandwidth admission control check for
      the new flow.  If successful, the AN must support using ANCP to
      query the NAS to receive a response indicating whether that join
      is to be honored or denied.

=20

   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.

=20

   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.


   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.

=20

   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.

=20

Regards,

Sven

=20

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:58
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update

=20

On 20 Oct 2008, at 12:22, OOGHE Sven wrote:





Francois,

=20

Another approach we could take is to let the framework requirements be =
agnostic as to how the Access Node knows whether or not Bandwidth =
Delegation applies. We could describe the notion of Bandwidth Delegation =
and the respective requirements for the Access Node and NAS in this =
case.

=20

The details of how the use of Bandwidth Delegation is communicated to =
the Access Node - using a flag, some "on/off" knob or both - would be =
left to the actual protocol specification work.

=20

Good idea. It will avoid these cross dependencies between framework and =
protocol, which indeed reflect that we are probably trying to be too =
precise/prescriptive in the framework.





=20

I think following this path would require relatively small edits to the =
document. I'm ok to take a first shot at it.

=20

That would be good.

=20

Thanks

=20

Francois





=20

Regards,

Sven

=20

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:01
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update

Sven and all,=20

=20

	   o  Upon receiving a join to a multicast flow which matches the Grey=20
	      List whose entry is flagged as "no Bandwidth Delegation" for the=20
	      relevant Access Port, the AN must support using ANCP to query the =

	      NAS to receive a response indicating whether that join is to be=20
	      honored or denied.  In this case, the NAS will perform both the=20
	      necessary conditional access and the admission control checks for =

	      the new flow.

=20

Roberta, Tom and myself have started drafting an I-D that will propose =
ANCP protocol extensions supporting some of those requirements (building =
on top of ancp-mc-multicast).

In doing so, we revisited a point that came up multiple times: do we =
really need to provision a flag in each and every Grey/White List entry =
to activate/deactivate Bandwidth Delegation?

=20

The current approach (as correctly reflected in the updated Framework) =
is:

* define a flag in each Grey/White List entry

* assume that this flag will normally either always be set in all =
entries or never set.

* setting/no-setting the flag is all entries effectively acts as the =
knob to enable/disable Bandwidth Delegation, therefore we did not need =
to specify a specific knob to enable/disable Bandwidth Delegation.

=20

Another approach would be:

* remove flag from White/Grey list entries

* define a specific knob to enable/disable Bandwidth Delegation at the =
AN granularity

* in fact, define a generic AN-level provisioning method that could be =
used to enable/disable BAndwidth delegation, but could also be used for =
provisioning the "Service Profiles" that are currently assumed to be =
configured in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles

=20

Considering that:

- we got several times the feedback that per-entry BAndwidth Delegation =
flag was confusing since Bandwidth Delegation granularity is more =
AN-level (and may lead to difficulties if it is set on some entries and =
not on others)

- it is likely that we'll need, anyways, a mechanism to provision things =
at AN level, that could be easily used to convey Bandwidth Delegation =
enable/disable knob.

we would like to propose to evolve to the newer approach.

=20

Thoughts?

=20

Francois

=20

PS: Sven, if we go for the new approach, we can document in an email the =
deltas that would be needed to reflect that in framework.

=20

=20


------_=_NextPart_001_01C9391F.E10F304C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<html                                                                    =
                                                                         =
                                                                         =
                   >=0A=
=0A=
<head>=0A=
=0A=
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<style>=0A=
<!--=0A=
                       =0A=
 font-face=0A=
	{font-family:&#23435;&#20307;;}=0A=
font-face=0A=
	{font-family:Tahoma;}=0A=
font-face=0A=
	{font-family:"\@&#23435;&#20307;";}=0A=
                        =0A=
 p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0cm;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman";}=0A=
a:link, span.MsoHyperlink=0A=
	{color:blue;=0A=
	text-decoration:underline;}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{color:blue;=0A=
	text-decoration:underline;}=0A=
p=0A=
	{=0A=
	margin-right:0cm;=0A=
	margin-left:0cm;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman";}=0A=
span.EmailStyle21=0A=
	{=0A=
	font-family:Arial;=0A=
	color:navy;}=0A=
=0A=
div.Section1=0A=
	{page:Section1;}=0A=
-->=0A=
</style>=0A=
=0A=
</head>=0A=
=0A=
<body lang=3DZH-CN link=3Dblue vlink=3Dblue style=3D"WORD-WRAP: =
break-word">=0A=
<DIV id=3DidOWAReplyText70064 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Hi =
Fortune,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>regarding your =
statement:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">The bandwidth =
can be =0A=
negotiated dynamically in quantity. When the bandwidth on AN is =
insufficient, AN =0A=
can ask for more from NAS/PS; when the bandwidth is insufficient, NAS/PS =
can ask =0A=
for more from AN.</SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>I would like to comment as follows:</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>Like in the real world, there is a hierarchy with the root =
being the =0A=
legal owner of the resource, who is also the owner of the authority to =0A=
control&nbsp;the resource. He delegates this authority &nbsp;downwards =
through a =0A=
chain of "Delegation of Authority" actions towards some enforcement =
point - in =0A=
this case the AN. You may well imagine, that the root authority over all =0A=
resource of a telco is with the shareholder annual assembly, which =
delegates it =0A=
to the Management board, those to the CTO, and further to some line =
managers who =0A=
delegate the control to some Policy Server, where our scope =0A=
begins.</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>What you refer to as negotiation, is rather a delegation of =
authority =0A=
which is quantized with a certain amount of bandwidth. Note =
that&nbsp;the PS may =0A=
have delegated authority to control&nbsp;the full bandwidth to the NAS, =0A=
but&nbsp;the NAS delegates only part of that bandwidth onwards to the =0A=
AN.&nbsp;</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>&nbsp;And yes, the AN may ask for that Delegation of Authority =
specifying =0A=
the amount desired, and the NAS may grant it. However, if the NAS needs =
some of =0A=
the delegated authority back for his own purposes, he withdraws part of =
the =0A=
quantized authority by claiming back part of the previously delegated =
authority =0A=
over access circuit bandwidth.</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>The point is:&nbsp; There is no real negotiation, because the =
AN and the =0A=
NAS/PS are not peers. </FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>The AN has to obey to whatever the NAS grants, and is not =
allowed to =0A=
exceed the delegated quantity of authority.&nbsp; Note that the =
authority could =0A=
be quantized in many ways, e.g. a time limited delegation of authority =
is just =0A=
one example. Or a volume limited delegation of authority. This is still =
in line =0A=
with the concept of "delegation of authority" in real life, and shows =
that this =0A=
extensibility is very powerful indeed. </FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2>Best Regards, Lothar Reith</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon =
International =0A=
GmbH (Deutsche Telekom Group)</SPAN></SPAN></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000 =0A=
size=3D2></FONT></SPAN>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>Von:</B> Fortune HUANG =0A=
[mailto:fqhuang@huawei.com]<BR><B>Gesendet:</B> Di 28.10.2008 =0A=
15:41<BR><B>An:</B> 'OOGHE Sven'; Reith, Lothar; =0A=
ancp@ietf.org<BR><B>Betreff:</B> &#31572;&#22797;: [ANCP] DOA (was: ANCP =
Framework =0A=
update)<BR></FONT><BR></DIV></DIV>=0A=
<DIV>=0A=
<DIV class=3DSection1>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DSV =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Hi Sven, =
Lothar et =0A=
al,</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DSV =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Yes, the =
&#8220;Delegation of =0A=
Authority&#8221; is more generic than &#8220;Bandwidth Delegation&#8221; =
and I fully agree with =0A=
the example from Lothar was that not only the bandwidth can be delegated =
but =0A=
also the content access control can be delegated.</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">However, we =
have to pay =0A=
attention to the difference of the delegation of bandwidth and the =
delegation of =0A=
content access control.</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">The bandwidth =
can be =0A=
negotiated dynamically in quantity. When the bandwidth on AN is =
insufficient, AN =0A=
can ask for more from NAS/PS; when the bandwidth is insufficient, NAS/PS =
can ask =0A=
for more from AN.</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">But this =
negotiation can =0A=
not be applied for the content access control properly.</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">That is to =
say, if we =0A=
extend the &#8220;bandwidth delegation&#8221; to &#8220;delegation of =
authority&#8221;, the negotiation =0A=
still needs to be specified specially for the =
bandwidth.</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Best =0A=
Regards,</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial">Fortune</SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<DIV>=0A=
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =0A=
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US style=3D"FONT-SIZE: =
12pt">=0A=
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>=0A=
</SPAN></FONT></DIV>=0A=
<P class=3DMsoNormal><B><FONT face=3D&#23435;&#20307; size=3D2><SPAN =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
&#23435;&#20307;">&#21457;&#20214;&#20154;<SPAN =0A=
lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D&#23435;&#20307; =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: &#23435;&#20307;"> =
ancp-bounces@ietf.org =0A=
[mailto:ancp-bounces@ietf.org] </SPAN></FONT><B><FONT =
face=3D&#23435;&#20307; size=3D2><SPAN =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
&#23435;&#20307;">&#20195;&#34920; =0A=
</SPAN></FONT></B><FONT face=3D&#23435;&#20307; size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: &#23435;&#20307;">OOGHE =
Sven<BR></SPAN></FONT><B><FONT =0A=
face=3D&#23435;&#20307; size=3D2><SPAN =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
&#23435;&#20307;">&#21457;&#36865;&#26102;&#38388;<SPAN =0A=
lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D&#23435;&#20307; =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: &#23435;&#20307;"> 2008<SPAN =
lang=3DEN-US><SPAN =0A=
lang=3DEN-US>&#24180;10</SPAN></SPAN><SPAN lang=3DEN-US><SPAN =0A=
lang=3DEN-US>&#26376;27</SPAN></SPAN><SPAN lang=3DEN-US><SPAN =
lang=3DEN-US>&#26085;</SPAN></SPAN> =0A=
18:49<BR></SPAN></FONT><B><FONT face=3D&#23435;&#20307; size=3D2><SPAN =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
&#23435;&#20307;">&#25910;&#20214;&#20154;<SPAN =0A=
lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D&#23435;&#20307; =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: &#23435;&#20307;"> Reith, Lothar; =0A=
ancp@ietf.org<BR></SPAN></FONT><B><FONT face=3D&#23435;&#20307; =
size=3D2><SPAN =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
&#23435;&#20307;">&#20027;&#39064;<SPAN =0A=
lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D&#23435;&#20307; =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: &#23435;&#20307;"> Re: [ANCP] DOA =
(was: ANCP Framework =0A=
update)</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi =0A=
Lothar,</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>=0A=
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think the =
term =0A=
"Delegation of Authority" captures the principle of what bandwidth =
delegation is =0A=
about. I'm fine either way, and would like to ask other people on this =
list what =0A=
they think.</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>=0A=
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN =0A=
lang=3DEN-US></SPAN></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><SPAN =0A=
lang=3DEN-US></SPAN></P>=0A=
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>=0A=
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =0A=
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US style=3D"FONT-SIZE: =
12pt">=0A=
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>=0A=
</SPAN></FONT></DIV>=0A=
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT =0A=
face=3DTahoma size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> ancp-bounces@ietf.org =0A=
[mailto:ancp-bounces@ietf.org] <B><SPAN style=3D"FONT-WEIGHT: bold">On =
Behalf Of =0A=
</SPAN></B>Reith, Lothar<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> =0A=
zondag 26 oktober 2008 16:47<BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> ancp@ietf.org<BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [ANCP] DOA (was: ANCP =
Framework =0A=
update)</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>=0A=
<DIV id=3DidOWAReplyText66978>=0A=
<DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Dear =0A=
all,</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<DIV id=3DidOWAReplyText68228>=0A=
<DIV id=3DidOWAReplyText93369>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">the ANCP =
Framework =0A=
contains the word "delegation", which in my mind is key to the whole =
concept of =0A=
ANCP. </SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I would like =
to =0A=
suggest that the concept of "delegation" should be made more extensible. =0A=
</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Narrowing it =
to the =0A=
term "bandwidth delegation" does not lend itself very well to =0A=
extensibility.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I would =
rather propose =0A=
to introduce the more general term of DOA (Delegation of Authority), =
which is a =0A=
well known concept in the real world, when a resource owner delegates =
control =0A=
over part or all of his resources to someone else - e.g. during a =
vacation =0A=
absence.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Today, ANCP =
does not =0A=
just support delegation in the form of bandwidth delegation, but also in =
the =0A=
form of delegation of content access control (delegation occurs for =
whitelist =0A=
and blacklist content, but not for the greylist =0A=
content).</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I think the =
extensible =0A=
concept "DOA"&nbsp;is very powerful when harnessed for Broadband Access =
using =0A=
ANCP.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">While =
updating the =0A=
framework it may be worth a consideration to add this hook for =
extensibility by =0A=
following means:</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- =
replace&nbsp;the =0A=
term "bandwidth delegation" by "DOA for part of access circuit =0A=
bandwidth"</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- introduce =
the first =0A=
extension of the DOA concept by making clear that the concepts of =0A=
&nbsp;whitelist and blacklist are DOA for Content Access =0A=
Control.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">One more =
point with =0A=
respect to the recent discussion about renaming the Policy =0A=
Server.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I like to =
state that I =0A=
am fine with the current name "policy =
server".&nbsp;&nbsp;Historically,&nbsp;I =0A=
beleive&nbsp;the name was chosen as a compromise between the RADIUS camp =
and the =0A=
COPS camp.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">If - given =
this =0A=
background - we&nbsp;still want to change the name of the policy server, =
then =0A=
perhaps DOA-server may be another alternative to consider. =0A=
</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">An important =
argument =0A=
in this case would be, that the concept of "delegation of authority" is =
well =0A=
aligned with the proxy concept, similar to a RADIUS Proxy Server, where =
the =0A=
delegation of authority happens along a delegation chain which may span =
multiple =0A=
RADIUS proxy servers and multiple domains. This aspect is missing in the =
other =0A=
proposed names.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Best =0A=
Regards,</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Lothar =0A=
Reith</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon =
International =0A=
GmbH (Deutsche Telekom Group)</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =
face=3DArial =0A=
color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">=0A=
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>=0A=
</SPAN></FONT></DIV>=0A=
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">Von:</SPAN></FONT></B><FONT =0A=
face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> =0A=
ancp-bounces@ietf.org im Auftrag von OOGHE Sven<BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B> Do 23.10.2008 =
12:57<BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">An:</SPAN></B> ancp@ietf.org<BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B> Re: [ANCP] ANCP =
Framework =0A=
update</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Here's the =
updated =0A=
text. I removed any notion of "flags" or how the Access Node is told =
whether or =0A=
not Bandwidth Delegation applies. I also covered Thomas' comments. =
Actually not =0A=
that much work: the general ANCP requirements as well as the NAS =
requirements =0A=
were written in a high-level way&nbsp;already. I only had to update the =
general =0A=
text and some of the Access Node requirements. Below the extracted text, =
let me =0A=
know your comments.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">---</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><STRONG><B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN =0A=
lang=3DEN-US style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">General =0A=
text</SPAN></FONT></B></STRONG><FONT face=3DArial color=3Dblack =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; =0A=
One approach is for the AN to query the NAS so that =0A=
Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the access line =
is =0A=
performed by the NAS (possibly with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
interactions with a Policy Server).&nbsp; This can be done with =0A=
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth delegation" to =
the =0A=
AN.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
*&nbsp; In case of Admission Control without AN Bandwidth =0A=
Delegation,</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: =
Arial"><BR><EM><I><FONT =0A=
face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =0A=
AN can use ANCP to query the NAS, that in turn =0A=
performs</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
multicast Admission Control check for the new multicast =0A=
flow</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =0A=
responds to the AN indicating whether the join is to =0A=
be</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
honored (and hence replication performed by the AN) or =0A=
denied.</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =0A=
NAS may locally maintain available "video" bandwidth on =0A=
the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Access Loop (as a portion of the Access Loop net data =0A=
rate),</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =0A=
perform video bandwidth accounting for the Access =0A=
Loop.</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon =0A=
receiving an Admission Request from the AN, the NAS =0A=
can</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
check available "video" bandwidth before admitting or =0A=
denying</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =0A=
multicast flow.&nbsp; In the process, the NAS may =0A=
communicate</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
with the Policy Server.&nbsp; For unicast video services such =0A=
as</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: =
Arial"><BR><EM><I><FONT =0A=
face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Video on Demand (VoD), the NAS may also be queried (by a =0A=
Policy</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Server or via on-path CAC signaling), so that it can =0A=
perform</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
admission control for the unicast flow, and update =0A=
the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
available video bandwidth maintained by the =0A=
NAS.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
*&nbsp; In case of Admission Control with AN Bandwidth Delegation, =0A=
the</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: =
Arial"><BR><EM><I><FONT =0A=
face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =0A=
(possibly with interactions with a Policy Server) =0A=
manages</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
total bandwidth for video admission, performs unicast =0A=
admission</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
control and uses ANCP to delegate a certain amount of =0A=
bandwidth</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for =0A=
some multicast flows to the Access Node.&nbsp; In this =0A=
scenario,</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =0A=
receiving a join to a multicast flow which matches =0A=
an</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
entry in the White or Grey List, the AN must perform =0A=
the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
necessary bandwidth admission control check for the =0A=
new</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
multicast flow, before starting the multicast flow =0A=
replication.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =0A=
color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><STRONG><B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN =0A=
lang=3DEN-US style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Access Node =0A=
requirements</SPAN></FONT></B></STRONG><FONT face=3DArial color=3Dblack =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; =0A=
The AN must deny any join to a multicast flow matching the =0A=
Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List for the relevant Access =0A=
Port.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; =0A=
The AN must accept any join to a multicast flow matching the =0A=
White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which no Bandwidth =0A=
Delegation is required.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; =0A=
Upon receiving a join to a multicast flow which matches the =0A=
White</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: =
Arial"><BR><EM><I><FONT =0A=
face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =0A=
whose and for which Bandwidth Delegation is required, the =0A=
AN</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must perform =
the =0A=
necessary bandwidth admission control check =0A=
for</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new flow =
before =0A=
starting the multicast flow =0A=
replication.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =0A=
color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; =0A=
Upon receiving a join to a multicast flow which matches the =0A=
Grey</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: =
Arial"><BR><EM><I><FONT =0A=
face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =0A=
and for which no Bandwidth Delegation is required, the =0A=
AN</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support =
using =0A=
ANCP to query the NAS to receive a =0A=
response</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating =
whether =0A=
that join is to be honored or denied.&nbsp; In =0A=
this</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case, the =
NAS will =0A=
perform both the necessary conditional =0A=
access</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the =
admission =0A=
control checks for the new =
flow.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; =0A=
Upon receiving a join to a multicast flow which matches the =0A=
Grey</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; FONT-FAMILY: =
Arial"><BR><EM><I><FONT =0A=
face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =0A=
and for which Bandwidth Delegation is required, the AN =0A=
must</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first =
perform the =0A=
necessary bandwidth admission control check =0A=
for</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow.&nbsp; If =0A=
successful, the AN must support using ANCP =0A=
to</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the =
NAS to =0A=
receive a response indicating whether that =0A=
join</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN =0A=
style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored or =0A=
denied.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; In =0A=
case of Admission Control with AN Bandwidth Delegation, the =0A=
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to notify =
the NAS =0A=
when the the user leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =0A=
flow.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; In =0A=
case of Admission Control with AN Bandwidth Delegation, the =0A=
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS to =0A=
request additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated multicast =0A=
bandwidth on a given Access Port; the =
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
should be able to specify both the minimum and the =0A=
preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount of additional =
multicast =0A=
bandwidth requested.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><BR>&nbsp;&nbsp; =0A=
o&nbsp; In case of Admission Control with AN Bandwidth Delegation, =0A=
upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth Delegation =
Request =0A=
from the NAS querying or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instructing =
to =0A=
decrease the delegated multicast bandwidth on =0A=
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support using =0A=
ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth Delegation =
Response =0A=
indicating the new delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =0A=
bandwidth.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; =
o&nbsp; In =0A=
case of Admission Control with AN Bandwidth Delegation, the =0A=
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to send a =
Bandwidth =0A=
Release message to the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to =
release =0A=
unused delegated multicast bandwidth on =
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
given Access Port.</SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =
face=3DArial =0A=
color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">=0A=
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>=0A=
</SPAN></FONT></DIV>=0A=
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT =0A=
face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> Francois =
Le Faucheur =0A=
IMAP [mailto:flefauch@cisco.com] <BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 20 oktober 2008 =0A=
12:58<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> OOGHE =0A=
Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Francois Le =
Faucheur =0A=
IMAP; ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> =0A=
Re: [ANCP] ANCP Framework update</SPAN></FONT><FONT face=3DArial =
color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">On 20 Oct =
2008, at =0A=
12:22, OOGHE Sven wrote:</SPAN></FONT></P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>=0A=
<DIV style=3D"WORD-WRAP: break-word">=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Francois,</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Another =
approach we =0A=
could take is to let the framework requirements be agnostic as to how =
the Access =0A=
Node knows whether or not Bandwidth Delegation applies. We could =
describe the =0A=
notion of Bandwidth Delegation and the respective requirements for the =
Access =0A=
Node and NAS in this case.</SPAN></FONT><FONT face=3DArial color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The details =
of how the =0A=
use of Bandwidth Delegation is communicated to the Access Node - using a =
flag, =0A=
some "on/off" knob or both - would be left to the actual protocol =
specification =0A=
work.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Good idea. =
It will =0A=
avoid these cross dependencies between framework and protocol, which =
indeed =0A=
reflect that we are probably trying to be too precise/prescriptive =0A=
in&nbsp;the&nbsp;framework.</SPAN></FONT></P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>=0A=
<DIV style=3D"WORD-WRAP: break-word">=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think =
following this =0A=
path would require relatively small edits to the document. I'm ok to =
take a =0A=
first shot at it.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN =0A=
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">That would =
be =0A=
good.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Thanks</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Francois</SPAN></FONT></P></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>=0A=
<DIV style=3D"WORD-WRAP: break-word">=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT =0A=
face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>=0A=
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =
face=3DArial =0A=
color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">=0A=
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>=0A=
</SPAN></FONT></DIV>=0A=
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma color=3Dblack =0A=
size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT =0A=
face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> Francois =
Le Faucheur =0A=
IMAP [<A =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>] =0A=
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 20 =
oktober 2008 =0A=
12:01<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> OOGHE =0A=
Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Francois Le =
Faucheur =0A=
IMAP; <A href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B><SPAN =0A=
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] ANCP =
Framework =0A=
update</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Sven and =
all, =0A=
</SPAN></FONT></P>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<DIV>=0A=
<BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt" type=3D"cite">=0A=
  <DIV>=0A=
  <P><I><FONT face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US =0A=
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp; =0A=
  o&nbsp; Upon receiving a join to a multicast flow which matches the =0A=
  Grey</SPAN></FONT></I><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"> =
<BR><I><SPAN =0A=
  style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose =
entry is =0A=
  flagged as "no Bandwidth Delegation" for the</SPAN></I> <BR><I><SPAN =0A=
  style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant =
Access =0A=
  Port, the AN must support using ANCP to query the</SPAN></I> =
<BR><I><SPAN =0A=
  style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to =
receive a =0A=
  response indicating whether that join is to be</SPAN></I> <BR><I><SPAN =0A=
  style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or =0A=
  denied.&nbsp; In this case, the NAS will perform both the</SPAN></I> =0A=
  <BR><I><SPAN style=3D"FONT-STYLE: =
italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
  necessary conditional access and the admission control checks =
for</SPAN></I> =0A=
  <BR><I><SPAN style=3D"FONT-STYLE: =
italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =0A=
  flow.</SPAN></I></SPAN></FONT></P></DIV></BLOCKQUOTE>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Roberta, Tom =
and =0A=
myself have started drafting an I-D that will propose ANCP protocol =
extensions =0A=
supporting some of those requirements (building on top of =0A=
ancp-mc-multicast).</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">In doing so, =
we =0A=
revisited a point that came up multiple times: do we really need to =
provision a =0A=
flag in each and every Grey/White List entry =0A=
to&nbsp;activate/deactivate&nbsp;Bandwidth =
Delegation?</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">The current =
approach =0A=
(as correctly reflected in the updated Framework) =
is:</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* define a =
flag in =0A=
each Grey/White List entry</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* assume =
that this =0A=
flag will normally either always be set in all entries or never =0A=
set.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* =
setting/no-setting =0A=
the flag is all entries effectively acts as the knob to enable/disable =
Bandwidth =0A=
Delegation, therefore we did not need to specify a specific knob to =0A=
enable/disable Bandwidth Delegation.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Another =
approach would =0A=
be:</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* remove =
flag from =0A=
White/Grey list entries</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* define a =
specific =0A=
knob to enable/disable Bandwidth Delegation at the AN =0A=
granularity</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* in fact, =
define a =0A=
generic&nbsp;AN-level provisioning method that could be used to =
enable/disable =0A=
BAndwidth delegation, but&nbsp;could&nbsp;also be used for provisioning =
the =0A=
"Service Profiles" that are currently assumed to be configured in AN, as =
well as =0A=
provisioning the Multicast White/Grey/Black =
Profiles</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Considering =0A=
that:</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- we got =
several times =0A=
the feedback that per-entry BAndwidth Delegation flag was confusing =0A=
since&nbsp;Bandwidth Delegation granularity is more AN-level (and may =
lead to =0A=
difficulties if it is set on some entries and not on =0A=
others)</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- it is =
likely that =0A=
we'll need, anyways, a mechanism to provision things at AN level, that =
could be =0A=
easily used to convey Bandwidth Delegation enable/disable =0A=
knob.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">we&nbsp;would&nbsp;like =0A=
to propose to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer =0A=
approach.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Thoughts?</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Francois</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">PS: Sven, if =
we go =0A=
for&nbsp;the&nbsp;new approach, we can document in an email the deltas =0A=
that&nbsp;would&nbsp;be needed to reflect that in =0A=
framework.</SPAN></FONT></P></DIV>=0A=
<DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></DIV>=0A=
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></DIV></DIV></DIV>=0A=
=0A=
</body>=0A=
=0A=
</html>=0A=

------_=_NextPart_001_01C9391F.E10F304C--

--===============1854670696==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1854670696==--


From ancp-bounces@ietf.org  Tue Oct 28 10:22:09 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E8ED128C2D4;
	Tue, 28 Oct 2008 10:22:09 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F0B728C32C
	for <ancp@core3.amsl.com>; Tue, 28 Oct 2008 10:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.278
X-Spam-Level: 
X-Spam-Status: No, score=0.278 tagged_above=-999 required=5 tests=[AWL=-0.597, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	SUBJ_ALL_CAPS=2.077]
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 scR9Qf4wQSig for <ancp@core3.amsl.com>;
	Tue, 28 Oct 2008 10:22:06 -0700 (PDT)
Received: from dtc035.detecon.net (dtc035.detecon.net [194.25.60.135])
	by core3.amsl.com (Postfix) with ESMTP id B7B1428C34B
	for <ancp@ietf.org>; Tue, 28 Oct 2008 10:21:55 -0700 (PDT)
Received: from unknown (HELO dc00357.detecon.com) ([172.16.10.107])
	by relay.dtc035.detecon.net with ESMTP; 28 Oct 2008 18:21:53 +0100
Received: from DC00331.detecon.com ([172.16.10.78]) by dc00357.detecon.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Oct 2008 18:21:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 28 Oct 2008 18:21:53 +0100
Message-ID: <D4ECB93FEDE50045B2657B56894BADF204FA839A@DC00331.detecon.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA
Thread-Index: Ack4/XL8dDL57Sh4Rp2O9SGfurF1GwAEP36gAAR57K8=
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com><D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>	<7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com><5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de>
	<49070D5D.2020604@rogers.com>
	<3525C9833C09ED418C6FD6CD9514668C04F70C13@emailwf1.jnpr.net>
From: "Reith, Lothar" <Lothar.Reith@detecon.com>
To: "Jerome Moisand" <jmoisand@juniper.net>
X-OriginalArrivalTime: 28 Oct 2008 17:21:53.0439 (UTC)
	FILETIME=[ABB74AF0:01C93921]
Cc: ancp@ietf.org
Subject: Re: [ANCP] DOA
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0720411633=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0720411633==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93921.AB89B14D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93921.AB89B14D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Jerome,
=20
yes, that was probably in 2004 and maybe you also remember that it was =
my verbal contribution in my first L2CP telco when I joined the =
discussions on L2CP. At the time I was working for a vendor in a BRAS =
business development context.
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)

________________________________

Von: ancp-bounces@ietf.org im Auftrag von Jerome Moisand
Gesendet: Di 28.10.2008 16:11
An: Tom Taylor; Haag, Thomas
Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org
Betreff: Re: [ANCP] DOA



Folks,

Actually, in the very early days of L2CP (wasn't called ANCP by then)
discussions in the DSL-Forum, we did come up with the term "Delegation
of Authorization" terminology to describe the essence of the concept.

"Authorization" is a direct reference to AAA concepts, whether this is
an initial authorization (at user session establishment time), or
dynamic change of authorization (i.e. in-session).

We certainly didn't notice the unfortunate side-effect with ambulance
driver reports... But still, I always liked this "Delegation of
Authorization" terminology. A BRAS/BNG is essentially an authorization
enforcer for subscriber/service management. And ANCP is a mechanism to
delegate some of that enforcement to the access node.

Cheers,
Jerome - the ghost

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Tom Taylor
Sent: Tuesday, October 28, 2008 9:02 AM
To: Haag, Thomas
Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org
Subject: Re: [ANCP] DOA

I don't mind. I coined the phrase "bandwidth delegation" to express what
was
happening. The only thing is, "DOA" has unfortunate connotations -- it's
a
notation that appears on ambulance drivers' reports (Dead on Arrival)
when their
patient dies before reaching the hospital. So I'd prefer that
"Delegation of
Authority" be spelled out.

Haag, Thomas wrote:
> Hi Sven,
>=20
> I also agree on DOA.
> This covers the issue in a better way.
>=20
> Regards
> Thomas
>
> ________________________________
>
> Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag
von
> OOGHE Sven
> Gesendet: Montag, 27. Oktober 2008 11:49
> An: Reith, Lothar; ancp@ietf.org
> Betreff: Re: [ANCP] DOA (was: ANCP Framework update)
>
>
> Hi Lothar,
>=20
> I think the term "Delegation of Authority" captures the principle of
> what bandwidth delegation is about. I'm fine either way, and would
like
> to ask other people on this list what they think.
>=20
> Regards,
> Sven
>
> ________________________________
>
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf
Of
> Reith, Lothar
> Sent: zondag 26 oktober 2008 16:47
> To: ancp@ietf.org
> Subject: [ANCP] DOA (was: ANCP Framework update)
>
>
> Dear all,
>=20
> the ANCP Framework contains the word "delegation", which in my mind is
> key to the whole concept of ANCP.
>=20
> I would like to suggest that the concept of "delegation" should be
made
> more extensible.
>=20
> Narrowing it to the term "bandwidth delegation" does not lend itself
> very well to extensibility.
>=20
> I would rather propose to introduce the more general term of DOA
> (Delegation of Authority), which is a well known concept in the real
> world, when a resource owner delegates control over part or all of his
> resources to someone else - e.g. during a vacation absence.
>=20
> Today, ANCP does not just support delegation in the form of bandwidth
> delegation, but also in the form of delegation of content access
control
> (delegation occurs for whitelist and blacklist content, but not for
the
> greylist content).
>=20
> I think the extensible concept "DOA" is very powerful when harnessed
for
> Broadband Access using ANCP.
>=20
> While updating the framework it may be worth a consideration to add
this
> hook for extensibility by following means:
>=20
> - replace the term "bandwidth delegation" by "DOA for part of access
> circuit bandwidth"
>=20
> - introduce the first extension of the DOA concept by making clear
that
> the concepts of  whitelist and blacklist are DOA for Content Access
> Control.
>=20
> One more point with respect to the recent discussion about renaming
the
> Policy Server.
>=20
> I like to state that I am fine with the current name "policy server".
> Historically, I beleive the name was chosen as a compromise between
the
> RADIUS camp and the COPS camp.
>=20
> If - given this background - we still want to change the name of the
> policy server, then perhaps DOA-server may be another alternative to
> consider.
>=20
> An important argument in this case would be, that the concept of
> "delegation of authority" is well aligned with the proxy concept,
> similar to a RADIUS Proxy Server, where the delegation of authority
> happens along a delegation chain which may span multiple RADIUS proxy
> servers and multiple domains. This aspect is missing in the other
> proposed names.
>=20
> Best Regards,
>=20
> Lothar Reith
> Detecon International GmbH (Deutsche Telekom Group)
>=20
>
> ________________________________
>
> Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
> Gesendet: Do 23.10.2008 12:57
> An: ancp@ietf.org
> Betreff: Re: [ANCP] ANCP Framework update
>
>
> Hi,
>=20
> Here's the updated text. I removed any notion of "flags" or how the
> Access Node is told whether or not Bandwidth Delegation applies. I
also
> covered Thomas' comments. Actually not that much work: the general
ANCP
> requirements as well as the NAS requirements were written in a
> high-level way already. I only had to update the general text and some
> of the Access Node requirements. Below the extracted text, let me know
> your comments.
>=20
> Regards,
> Sven
>=20
> ---
>=20
> General text
>=20
>    o  One approach is for the AN to query the NAS so that Admission
>       Control for the access line is performed by the NAS (possibly
with
>       interactions with a Policy Server).  This can be done with or
>       without "bandwidth delegation" to the AN.
>=20
>       *  In case of Admission Control without AN Bandwidth Delegation,
>          the AN can use ANCP to query the NAS, that in turn performs
>          multicast Admission Control check for the new multicast flow
>          and responds to the AN indicating whether the join is to be
>          honored (and hence replication performed by the AN) or
denied.
>          The NAS may locally maintain available "video" bandwidth on
the
>          Access Loop (as a portion of the Access Loop net data rate),
>          and perform video bandwidth accounting for the Access Loop.
>          Upon receiving an Admission Request from the AN, the NAS can
>          check available "video" bandwidth before admitting or denying
>          the multicast flow.  In the process, the NAS may communicate
>          with the Policy Server.  For unicast video services such as
>          Video on Demand (VoD), the NAS may also be queried (by a
Policy
>          Server or via on-path CAC signaling), so that it can perform
>          admission control for the unicast flow, and update the
>          available video bandwidth maintained by the NAS.
>=20
>       *  In case of Admission Control with AN Bandwidth Delegation,
the
>          NAS (possibly with interactions with a Policy Server) manages
>          total bandwidth for video admission, performs unicast
admission
>          control and uses ANCP to delegate a certain amount of
bandwidth
>          for some multicast flows to the Access Node.  In this
scenario,
>          upon receiving a join to a multicast flow which matches an
>          entry in the White or Grey List, the AN must perform the
>          necessary bandwidth admission control check for the new
>          multicast flow, before starting the multicast flow
replication.
>
> Access Node requirements
>=20
>    o  The AN must deny any join to a multicast flow matching the Black
>       List for the relevant Access Port.
>=20
>    o  The AN must accept any join to a multicast flow matching the
White
>       List and for which no Bandwidth Delegation is required.
>=20
>    o  Upon receiving a join to a multicast flow which matches the
White
>       List whose and for which Bandwidth Delegation is required, the
AN
>       must perform the necessary bandwidth admission control check for
>       the new flow before starting the multicast flow replication.
>=20
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which no Bandwidth Delegation is required, the AN
>       must support using ANCP to query the NAS to receive a response
>       indicating whether that join is to be honored or denied.  In
this
>       case, the NAS will perform both the necessary conditional access
>       and the admission control checks for the new flow.
>=20
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which Bandwidth Delegation is required, the AN must
>       first perform the necessary bandwidth admission control check
for
>       the new flow.  If successful, the AN must support using ANCP to
>       query the NAS to receive a response indicating whether that join
>       is to be honored or denied.
>=20
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to notify the NAS when the the user
leaves
>       the multicast flow.
>=20
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to query the NAS to request additional
>       delegated multicast bandwidth on a given Access Port; the AN
>       should be able to specify both the minimum and the preferred
>       amount of additional multicast bandwidth requested.
>
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving a Bandwidth Delegation Request from the NAS querying
or
>       instructing to decrease the delegated multicast bandwidth on a
>       given Access Port, the AN must support using ANCP to send a
>       Bandwidth Delegation Response indicating the new delegated
>       multicast bandwidth.
>=20
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to send a Bandwidth Release message to
the
>       NAS in order to release unused delegated multicast bandwidth on
a
>       given Access Port.
>=20
> Regards,
> Sven
>
> ________________________________
>
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: maandag 20 oktober 2008 12:58
> To: OOGHE Sven
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> Subject: Re: [ANCP] ANCP Framework update
>
>
>
>
> On 20 Oct 2008, at 12:22, OOGHE Sven wrote:
>
>
>       Francois,
>      =20
>       Another approach we could take is to let the framework
> requirements be agnostic as to how the Access Node knows whether or
not
> Bandwidth Delegation applies. We could describe the notion of
Bandwidth
> Delegation and the respective requirements for the Access Node and NAS
> in this case.
>      =20
>       The details of how the use of Bandwidth Delegation is
> communicated to the Access Node - using a flag, some "on/off" knob or
> both - would be left to the actual protocol specification work.
>
>
> Good idea. It will avoid these cross dependencies between framework
and
> protocol, which indeed reflect that we are probably trying to be too
> precise/prescriptive in the framework.
>
>
>      =20
>       I think following this path would require relatively small edits
> to the document. I'm ok to take a first shot at it.
>
>
> That would be good.
>
> Thanks
>
> Francois
>
>
>      =20
>       Regards,
>       Sven
>
> ________________________________
>
>       From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
>       Sent: maandag 20 oktober 2008 12:01
>       To: OOGHE Sven
>       Cc: Francois Le Faucheur IMAP; ancp@ietf.org
>       Subject: Re: [ANCP] ANCP Framework update
>     =20
>     =20
>       Sven and all,
>     =20
>     =20
>
>                  o  Upon receiving a join to a multicast flow which
> matches the Grey
>                     List whose entry is flagged as "no Bandwidth
> Delegation" for the
>                     relevant Access Port, the AN must support using
> ANCP to query the
>                     NAS to receive a response indicating whether that
> join is to be
>                     honored or denied.  In this case, the NAS will
> perform both the
>                     necessary conditional access and the admission
> control checks for
>                     the new flow.
>
>
>       Roberta, Tom and myself have started drafting an I-D that will
> propose ANCP protocol extensions supporting some of those requirements
> (building on top of ancp-mc-multicast).
>       In doing so, we revisited a point that came up multiple times:
> do we really need to provision a flag in each and every Grey/White
List
> entry to activate/deactivate Bandwidth Delegation?
>     =20
>     =20
>       The current approach (as correctly reflected in the updated
> Framework) is:
>       * define a flag in each Grey/White List entry
>     =20
>       * assume that this flag will normally either always be set in
> all entries or never set.
>     =20
>       * setting/no-setting the flag is all entries effectively acts as
> the knob to enable/disable Bandwidth Delegation, therefore we did not
> need to specify a specific knob to enable/disable Bandwidth
Delegation.
>     =20
>     =20
>     =20
>       Another approach would be:
>       * remove flag from White/Grey list entries
>     =20
>       * define a specific knob to enable/disable Bandwidth Delegation
> at the AN granularity
>       * in fact, define a generic AN-level provisioning method that
> could be used to enable/disable BAndwidth delegation, but could also
be
> used for provisioning the "Service Profiles" that are currently
assumed
> to be configured in AN, as well as provisioning the Multicast
> White/Grey/Black Profiles
>     =20
>     =20
>     =20
>       Considering that:
>       - we got several times the feedback that per-entry BAndwidth
> Delegation flag was confusing since Bandwidth Delegation granularity
is
> more AN-level (and may lead to difficulties if it is set on some
entries
> and not on others)
>       - it is likely that we'll need, anyways, a mechanism to
> provision things at AN level, that could be easily used to convey
> Bandwidth Delegation enable/disable knob.
>     =20
>       we would like to propose to evolve to the newer approach.
>     =20
>     =20
>       Thoughts?
>
>       Francois
>
>       PS: Sven, if we go for the new approach, we can document in an
> email the deltas that would be needed to reflect that in framework.
>
>
>
>
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp



------_=_NextPart_001_01C93921.AB89B14D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.5">=0A=
<TITLE>Re: [ANCP] DOA</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText89908 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Hi =
Jerome,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>yes, that was probably in =
2004 and maybe =0A=
you also remember that it was my verbal contribution in my first L2CP =
telco when =0A=
I joined the discussions on L2CP. At&nbsp;the time I was&nbsp;working =
for a =0A=
vendor in a BRAS business development context.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Lothar Reith</FONT></DIV>=0A=
<DIV dir=3Dltr><SPAN lang=3DEN-US =0A=
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon =
International =0A=
GmbH (Deutsche Telekom Group)</SPAN></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>Von:</B> ancp-bounces@ietf.org im =
Auftrag von Jerome =0A=
Moisand<BR><B>Gesendet:</B> Di 28.10.2008 16:11<BR><B>An:</B> Tom =
Taylor; Haag, =0A=
Thomas<BR><B>Cc:</B> Sven.Ooghe@alcatel-lucent.be; =0A=
ancp@ietf.org<BR><B>Betreff:</B> Re: [ANCP] DOA<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Folks,<BR><BR>Actually, in the very early days of L2CP =
(wasn't =0A=
called ANCP by then)<BR>discussions in the DSL-Forum, we did come up =
with the =0A=
term "Delegation<BR>of Authorization" terminology to describe the =
essence of the =0A=
concept.<BR><BR>"Authorization" is a direct reference to AAA concepts, =
whether =0A=
this is<BR>an initial authorization (at user session establishment =
time), =0A=
or<BR>dynamic change of authorization (i.e. in-session).<BR><BR>We =
certainly =0A=
didn't notice the unfortunate side-effect with ambulance<BR>driver =
reports... =0A=
But still, I always liked this "Delegation of<BR>Authorization" =
terminology. A =0A=
BRAS/BNG is essentially an authorization<BR>enforcer for =
subscriber/service =0A=
management. And ANCP is a mechanism to<BR>delegate some of that =
enforcement to =0A=
the access node.<BR><BR>Cheers,<BR>Jerome - the =
ghost<BR><BR>-----Original =0A=
Message-----<BR>From: ancp-bounces@ietf.org [<A =0A=
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>] =
On Behalf =0A=
Of<BR>Tom Taylor<BR>Sent: Tuesday, October 28, 2008 9:02 AM<BR>To: Haag, =0A=
Thomas<BR>Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org<BR>Subject: =
Re: [ANCP] =0A=
DOA<BR><BR>I don't mind. I coined the phrase "bandwidth delegation" to =
express =0A=
what<BR>was<BR>happening. The only thing is, "DOA" has unfortunate =
connotations =0A=
-- it's<BR>a<BR>notation that appears on ambulance drivers' reports =
(Dead on =0A=
Arrival)<BR>when their<BR>patient dies before reaching the hospital. So =
I'd =0A=
prefer that<BR>"Delegation of<BR>Authority" be spelled out.<BR><BR>Haag, =
Thomas =0A=
wrote:<BR>&gt; Hi Sven,<BR>&gt;&nbsp;<BR>&gt; I also agree on =
DOA.<BR>&gt; This =0A=
covers the issue in a better way.<BR>&gt;&nbsp;<BR>&gt; Regards<BR>&gt; =0A=
Thomas<BR>&gt;<BR>&gt; ________________________________<BR>&gt;<BR>&gt; =
Von: =0A=
ancp-bounces@ietf.org [<A =0A=
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>] =
Im =0A=
Auftrag<BR>von<BR>&gt; OOGHE Sven<BR>&gt; Gesendet: Montag, 27. Oktober =
2008 =0A=
11:49<BR>&gt; An: Reith, Lothar; ancp@ietf.org<BR>&gt; Betreff: Re: =
[ANCP] DOA =0A=
(was: ANCP Framework update)<BR>&gt;<BR>&gt;<BR>&gt; Hi =0A=
Lothar,<BR>&gt;&nbsp;<BR>&gt; I think the term "Delegation of Authority" =0A=
captures the principle of<BR>&gt; what bandwidth delegation is about. =
I'm fine =0A=
either way, and would<BR>like<BR>&gt; to ask other people on this list =
what they =0A=
think.<BR>&gt;&nbsp;<BR>&gt; Regards,<BR>&gt; Sven<BR>&gt;<BR>&gt; =0A=
________________________________<BR>&gt;<BR>&gt; From: =
ancp-bounces@ietf.org [<A =0A=
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>] =
On =0A=
Behalf<BR>Of<BR>&gt; Reith, Lothar<BR>&gt; Sent: zondag 26 oktober 2008 =0A=
16:47<BR>&gt; To: ancp@ietf.org<BR>&gt; Subject: [ANCP] DOA (was: ANCP =
Framework =0A=
update)<BR>&gt;<BR>&gt;<BR>&gt; Dear all,<BR>&gt;&nbsp;<BR>&gt; the ANCP =0A=
Framework contains the word "delegation", which in my mind is<BR>&gt; =
key to the =0A=
whole concept of ANCP.<BR>&gt;&nbsp;<BR>&gt; I would like to suggest =
that the =0A=
concept of "delegation" should be<BR>made<BR>&gt; more =0A=
extensible.<BR>&gt;&nbsp;<BR>&gt; Narrowing it to the term "bandwidth =0A=
delegation" does not lend itself<BR>&gt; very well to =0A=
extensibility.<BR>&gt;&nbsp;<BR>&gt; I would rather propose to introduce =
the =0A=
more general term of DOA<BR>&gt; (Delegation of Authority), which is a =
well =0A=
known concept in the real<BR>&gt; world, when a resource owner delegates =
control =0A=
over part or all of his<BR>&gt; resources to someone else - e.g. during =
a =0A=
vacation absence.<BR>&gt;&nbsp;<BR>&gt; Today, ANCP does not just =
support =0A=
delegation in the form of bandwidth<BR>&gt; delegation, but also in the =
form of =0A=
delegation of content access<BR>control<BR>&gt; (delegation occurs for =
whitelist =0A=
and blacklist content, but not for<BR>the<BR>&gt; greylist =0A=
content).<BR>&gt;&nbsp;<BR>&gt; I think the extensible concept "DOA" is =
very =0A=
powerful when harnessed<BR>for<BR>&gt; Broadband Access using =0A=
ANCP.<BR>&gt;&nbsp;<BR>&gt; While updating the framework it may be worth =
a =0A=
consideration to add<BR>this<BR>&gt; hook for extensibility by following =0A=
means:<BR>&gt;&nbsp;<BR>&gt; - replace the term "bandwidth delegation" =
by "DOA =0A=
for part of access<BR>&gt; circuit bandwidth"<BR>&gt;&nbsp;<BR>&gt; - =
introduce =0A=
the first extension of the DOA concept by making clear<BR>that<BR>&gt; =
the =0A=
concepts of&nbsp; whitelist and blacklist are DOA for Content =
Access<BR>&gt; =0A=
Control.<BR>&gt;&nbsp;<BR>&gt; One more point with respect to the recent =0A=
discussion about renaming<BR>the<BR>&gt; Policy =
Server.<BR>&gt;&nbsp;<BR>&gt; I =0A=
like to state that I am fine with the current name "policy =
server".<BR>&gt; =0A=
Historically, I beleive the name was chosen as a compromise =0A=
between<BR>the<BR>&gt; RADIUS camp and the COPS =
camp.<BR>&gt;&nbsp;<BR>&gt; If - =0A=
given this background - we still want to change the name of the<BR>&gt; =
policy =0A=
server, then perhaps DOA-server may be another alternative to<BR>&gt; =0A=
consider.<BR>&gt;&nbsp;<BR>&gt; An important argument in this case would =
be, =0A=
that the concept of<BR>&gt; "delegation of authority" is well aligned =
with the =0A=
proxy concept,<BR>&gt; similar to a RADIUS Proxy Server, where the =
delegation of =0A=
authority<BR>&gt; happens along a delegation chain which may span =
multiple =0A=
RADIUS proxy<BR>&gt; servers and multiple domains. This aspect is =
missing in the =0A=
other<BR>&gt; proposed names.<BR>&gt;&nbsp;<BR>&gt; Best =0A=
Regards,<BR>&gt;&nbsp;<BR>&gt; Lothar Reith<BR>&gt; Detecon =
International GmbH =0A=
(Deutsche Telekom Group)<BR>&gt;&nbsp;<BR>&gt;<BR>&gt; =0A=
________________________________<BR>&gt;<BR>&gt; Von: =
ancp-bounces@ietf.org im =0A=
Auftrag von OOGHE Sven<BR>&gt; Gesendet: Do 23.10.2008 12:57<BR>&gt; An: =0A=
ancp@ietf.org<BR>&gt; Betreff: Re: [ANCP] ANCP Framework =0A=
update<BR>&gt;<BR>&gt;<BR>&gt; Hi,<BR>&gt;&nbsp;<BR>&gt; Here's the =
updated =0A=
text. I removed any notion of "flags" or how the<BR>&gt; Access Node is =
told =0A=
whether or not Bandwidth Delegation applies. I<BR>also<BR>&gt; covered =
Thomas' =0A=
comments. Actually not that much work: the general<BR>ANCP<BR>&gt; =
requirements =0A=
as well as the NAS requirements were written in a<BR>&gt; high-level way =0A=
already. I only had to update the general text and some<BR>&gt; of the =
Access =0A=
Node requirements. Below the extracted text, let me know<BR>&gt; your =0A=
comments.<BR>&gt;&nbsp;<BR>&gt; Regards,<BR>&gt; =
Sven<BR>&gt;&nbsp;<BR>&gt; =0A=
---<BR>&gt;&nbsp;<BR>&gt; General =
text<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; =0A=
o&nbsp; One approach is for the AN to query the NAS so that =0A=
Admission<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the =
access =0A=
line is performed by the NAS =0A=
(possibly<BR>with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
interactions with =0A=
a Policy Server).&nbsp; This can be done with =0A=
or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth =
delegation" to =0A=
the AN.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*&nbsp; In =0A=
case of Admission Control without AN Bandwidth =0A=
Delegation,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 the AN =0A=
can use ANCP to query the NAS, that in turn =0A=
performs<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast =0A=
Admission Control check for the new multicast =0A=
flow<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =
responds =0A=
to the AN indicating whether the join is to =0A=
be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored =
(and =0A=
hence replication performed by the AN) =0A=
or<BR>denied.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; The =0A=
NAS may locally maintain available "video" bandwidth =0A=
on<BR>the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Access =0A=
Loop (as a portion of the Access Loop net data =0A=
rate),<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and =
perform =0A=
video bandwidth accounting for the Access =0A=
Loop.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon =0A=
receiving an Admission Request from the AN, the NAS =0A=
can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check =0A=
available "video" bandwidth before admitting or =0A=
denying<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the =0A=
multicast flow.&nbsp; In the process, the NAS may =0A=
communicate<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 with =0A=
the Policy Server.&nbsp; For unicast video services such =0A=
as<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video =
on Demand =0A=
(VoD), the NAS may also be queried (by =0A=
a<BR>Policy<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Server =0A=
or via on-path CAC signaling), so that it can =0A=
perform<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
admission =0A=
control for the unicast flow, and update =0A=
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
available =0A=
video bandwidth maintained by the =0A=
NAS.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; =
In case =0A=
of Admission Control with AN Bandwidth =0A=
Delegation,<BR>the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =0A=
NAS (possibly with interactions with a Policy Server) =0A=
manages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
total =0A=
bandwidth for video admission, performs =0A=
unicast<BR>admission<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; =0A=
control and uses ANCP to delegate a certain amount =0A=
of<BR>bandwidth<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; =0A=
for some multicast flows to the Access Node.&nbsp; In =0A=
this<BR>scenario,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; =0A=
upon receiving a join to a multicast flow which matches =0A=
an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry =
in the =0A=
White or Grey List, the AN must perform =0A=
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
necessary =0A=
bandwidth admission control check for the =0A=
new<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
multicast =0A=
flow, before starting the multicast flow<BR>replication.<BR>&gt;<BR>&gt; =
Access =0A=
Node requirements<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; The AN =
must =0A=
deny any join to a multicast flow matching the =0A=
Black<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List for the relevant =
Access =0A=
Port.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; The AN must accept =
any =0A=
join to a multicast flow matching =0A=
the<BR>White<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for =
which no =0A=
Bandwidth Delegation is =
required.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; =0A=
o&nbsp; Upon receiving a join to a multicast flow which matches =0A=
the<BR>White<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose and =
for =0A=
which Bandwidth Delegation is required, =0A=
the<BR>AN<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must perform the =
necessary =0A=
bandwidth admission control check =0A=
for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new flow before =
starting the =0A=
multicast flow replication.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; =
o&nbsp; Upon =0A=
receiving a join to a multicast flow which matches the =0A=
Grey<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which no =
Bandwidth =0A=
Delegation is required, the =
AN<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =0A=
support using ANCP to query the NAS to receive a =0A=
response<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating whether =
that =0A=
join is to be honored or denied.&nbsp; =0A=
In<BR>this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case, the NAS =
will =0A=
perform both the necessary conditional =0A=
access<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the admission =
control =0A=
checks for the new flow.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; =
Upon =0A=
receiving a join to a multicast flow which matches the =0A=
Grey<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which =
Bandwidth =0A=
Delegation is required, the AN =
must<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
first perform the necessary bandwidth admission control =0A=
check<BR>for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow.&nbsp; If =0A=
successful, the AN must support using ANCP =0A=
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the NAS to receive =
a =0A=
response indicating whether that =0A=
join<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be honored or =0A=
denied.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; In case of =
Admission =0A=
Control with AN Bandwidth Delegation, =0A=
the<BR>AN<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to =0A=
notify the NAS when the the =0A=
user<BR>leaves<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the multicast =0A=
flow.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; In case of =
Admission =0A=
Control with AN Bandwidth Delegation, =0A=
the<BR>AN<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to =0A=
query the NAS to request =
additional<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
delegated multicast bandwidth on a given Access Port; the =0A=
AN<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be able to specify =
both =0A=
the minimum and the =
preferred<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount =0A=
of additional multicast bandwidth =
requested.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp; =0A=
o&nbsp; In case of Admission Control with AN Bandwidth Delegation, =0A=
upon<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =0A=
Delegation Request from the NAS =0A=
querying<BR>or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instructing =
to =0A=
decrease the delegated multicast bandwidth on =0A=
a<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN =
must =0A=
support using ANCP to send a<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Bandwidth Delegation Response indicating the new =0A=
delegated<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =0A=
bandwidth.<BR>&gt;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp; o&nbsp; In case of =
Admission =0A=
Control with AN Bandwidth Delegation, =0A=
the<BR>AN<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to =0A=
send a Bandwidth Release message =0A=
to<BR>the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to =
release =0A=
unused delegated multicast bandwidth =0A=
on<BR>a<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access =0A=
Port.<BR>&gt;&nbsp;<BR>&gt; Regards,<BR>&gt; Sven<BR>&gt;<BR>&gt; =0A=
________________________________<BR>&gt;<BR>&gt; From: Francois Le =
Faucheur IMAP =0A=
[<A =
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]<BR>&gt;=
 =0A=
Sent: maandag 20 oktober 2008 12:58<BR>&gt; To: OOGHE Sven<BR>&gt; Cc: =
Francois =0A=
Le Faucheur IMAP; ancp@ietf.org<BR>&gt; Subject: Re: [ANCP] ANCP =
Framework =0A=
update<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; On 20 Oct 2008, at 12:22, =
OOGHE =0A=
Sven wrote:<BR>&gt;<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Francois,<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Another approach we could take is to let =
the =0A=
framework<BR>&gt; requirements be agnostic as to how the Access Node =
knows =0A=
whether or<BR>not<BR>&gt; Bandwidth Delegation applies. We could =
describe the =0A=
notion of<BR>Bandwidth<BR>&gt; Delegation and the respective =
requirements for =0A=
the Access Node and NAS<BR>&gt; in this case.<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =0A=
details of how the use of Bandwidth Delegation is<BR>&gt; communicated =
to the =0A=
Access Node - using a flag, some "on/off" knob or<BR>&gt; both - would =
be left =0A=
to the actual protocol specification work.<BR>&gt;<BR>&gt;<BR>&gt; Good =
idea. It =0A=
will avoid these cross dependencies between framework<BR>and<BR>&gt; =
protocol, =0A=
which indeed reflect that we are probably trying to be too<BR>&gt; =0A=
precise/prescriptive in the framework.<BR>&gt;<BR>&gt;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I =0A=
think following this path would require relatively small edits<BR>&gt; =
to the =0A=
document. I'm ok to take a first shot at it.<BR>&gt;<BR>&gt;<BR>&gt; =
That would =0A=
be good.<BR>&gt;<BR>&gt; Thanks<BR>&gt;<BR>&gt; =
Francois<BR>&gt;<BR>&gt;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Regards,<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sven<BR>&gt;<BR>&gt; =0A=
________________________________<BR>&gt;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
From: Francois Le Faucheur IMAP [<A =0A=
href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>]<BR>&gt;=
 =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: maandag 20 oktober 2008 =
12:01<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: OOGHE Sven<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: Francois Le Faucheur IMAP; =0A=
ancp@ietf.org<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re: [ANCP] =
ANCP =0A=
Framework update<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Sven and =0A=
all,<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; o&nbsp; Upon =
receiving a =0A=
join to a multicast flow which<BR>&gt; matches the Grey<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is flagged as "no =0A=
Bandwidth<BR>&gt; Delegation" for the<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
relevant Access Port, the AN must support using<BR>&gt; ANCP to query =0A=
the<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to =0A=
receive a response indicating whether that<BR>&gt; join is to be<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; In this case, =
the NAS =0A=
will<BR>&gt; perform both the<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
necessary conditional access and the admission<BR>&gt; control checks =0A=
for<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =0A=
new flow.<BR>&gt;<BR>&gt;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Roberta, Tom =0A=
and myself have started drafting an I-D that will<BR>&gt; propose ANCP =
protocol =0A=
extensions supporting some of those requirements<BR>&gt; (building on =
top of =0A=
ancp-mc-multicast).<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In doing so, =
we =0A=
revisited a point that came up multiple times:<BR>&gt; do we really need =
to =0A=
provision a flag in each and every Grey/White<BR>List<BR>&gt; entry to =0A=
activate/deactivate Bandwidth Delegation?<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The current approach (as correctly =
reflected in =0A=
the updated<BR>&gt; Framework) is:<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * =0A=
define a flag in each Grey/White List entry<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * =
assume =0A=
that this flag will normally either always be set in<BR>&gt; all entries =
or =0A=
never set.<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * setting/no-setting the flag is all =
entries =0A=
effectively acts as<BR>&gt; the knob to enable/disable Bandwidth =
Delegation, =0A=
therefore we did not<BR>&gt; need to specify a specific knob to =
enable/disable =0A=
Bandwidth<BR>Delegation.<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Another approach would be:<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * remove flag from White/Grey list =0A=
entries<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * define a specific knob to =
enable/disable =0A=
Bandwidth Delegation<BR>&gt; at the AN granularity<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * in fact, define a generic AN-level =
provisioning =0A=
method that<BR>&gt; could be used to enable/disable BAndwidth =
delegation, but =0A=
could also<BR>be<BR>&gt; used for provisioning the "Service Profiles" =
that are =0A=
currently<BR>assumed<BR>&gt; to be configured in AN, as well as =
provisioning the =0A=
Multicast<BR>&gt; White/Grey/Black Profiles<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Considering that:<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - we got =
several times =0A=
the feedback that per-entry BAndwidth<BR>&gt; Delegation flag was =
confusing =0A=
since Bandwidth Delegation granularity<BR>is<BR>&gt; more AN-level (and =
may lead =0A=
to difficulties if it is set on some<BR>entries<BR>&gt; and not on =0A=
others)<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - it is likely that we'll =
need, =0A=
anyways, a mechanism to<BR>&gt; provision things at AN level, that could =
be =0A=
easily used to convey<BR>&gt; Bandwidth Delegation enable/disable =
knob.<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; we =
would =0A=
like to propose to evolve to the newer approach.<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thoughts?<BR>&gt;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Francois<BR>&gt;<BR>&gt; =0A=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PS: Sven, if we go for the new approach, =
we can =0A=
document in an<BR>&gt; email the deltas that would be needed to reflect =
that in =0A=
framework.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>---=
---------------------------------------------------------------------<BR>=
&gt;<BR>&gt; =0A=
_______________________________________________<BR>&gt; ANCP mailing =0A=
list<BR>&gt; ANCP@ietf.org<BR>&gt; <A =0A=
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>____________________________________________=
___<BR>ANCP =0A=
mailing list<BR>ANCP@ietf.org<BR><A =0A=
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>____________________________________________=
___<BR>ANCP =0A=
mailing list<BR>ANCP@ietf.org<BR><A =0A=
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C93921.AB89B14D--

--===============0720411633==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0720411633==--


From ancp-bounces@ietf.org  Wed Oct 29 10:50:44 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99BA93A66B4;
	Wed, 29 Oct 2008 10:50:44 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A84EE3A66B4
	for <ancp@core3.amsl.com>; Wed, 29 Oct 2008 10:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.114
X-Spam-Level: ***
X-Spam-Status: No, score=3.114 tagged_above=-999 required=5 tests=[AWL=-2.835, 
	BAYES_40=-0.185, CN_BODY_35=0.339, EXTRA_MPART_TYPE=1,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,
	MIME_CHARSET_FARAWAY=2.45, MY_CID_AND_ARIAL2=1.46]
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 jNNZY3LOzQJH for <ancp@core3.amsl.com>;
	Wed, 29 Oct 2008 10:50:39 -0700 (PDT)
Received: from dtc034.detecon.net (dtc034.detecon.net [194.25.60.134])
	by core3.amsl.com (Postfix) with ESMTP id 9F19D3A67A5
	for <ancp@ietf.org>; Wed, 29 Oct 2008 10:50:37 -0700 (PDT)
Received: from unknown (HELO dc00356.detecon.com) ([172.16.10.106])
	by relay.dtc034.detecon.net with ESMTP; 29 Oct 2008 18:50:28 +0100
Received: from DC00331.detecon.com ([172.16.10.78]) by dc00356.detecon.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 29 Oct 2008 18:50:28 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 18:50:26 +0100
Message-ID: <D4ECB93FEDE50045B2657B56894BADF207B78960@DC00331.detecon.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA (was: ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScgAKwVUcAA5YynwAAUSsJAAGA9s4AAcFwNQ
References: <004201c9397d$c1d61da0$7b27460a@china.huawei.com>
From: "Reith, Lothar" <Lothar.Reith@detecon.com>
To: "Fortune HUANG" <fqhuang@huawei.com>, <ancp@ietf.org>,
	"OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>,
	"Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
	"Tina TSOU" <tena@huawei.com>, "Tom Taylor" <tom.taylor@rogers.com>,
	"Maglione Roberta" <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec \(wdec\)" <wdec@cisco.com>,
	"Haag, Thomas" <HaagT@telekom.de>, <stefaan.de_cnodder@alcatel-lucent.be>
X-OriginalArrivalTime: 29 Oct 2008 17:50:28.0269 (UTC)
	FILETIME=[D43F55D0:01C939EE]
Subject: Re: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0306481008=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0306481008==
Content-class: urn:content-classes:message
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----_=_NextPart_001_01C939EE.D334C302"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C939EE.D334C302
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C939EE.D334C302"


------_=_NextPart_002_01C939EE.D334C302
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hi Fortune,
=20
I agree, that we have to be pragmatic.=20
=20
I recommend to check the meaning of bandwidth delegation, in order make =
the live of operators easier, who deploy ANs from multiple =
manufacturers.=20
=20
Based on my over 20 years experience in packet switching, I am afraid =
that there may be a risk of different interpretation of what "bandwidth" =
means.
=20
Just stating kilobit/sec is not enough, you also have to state what you =
count  and how you enforce, with- our without buffering and how deep the =
buffer is.
=20
In other words, while you delegate the authority for bandwidth control, =
you better also specify the meter used to control the bandwidth, for =
example by specifying the two parameters of the token bucket used, which =
defines the height and refill rate of the token bucket.
=20
I assume there is consensus between the Access Node vendors on what is =
being counted, like the IP packet including the header ??? or PPPoE ???? =
or Ethernet ???? or only the payload ???
=20
The point is, yes, you can do this bandwidth delegation by agreeing on =
the meter. And pragmatically, that is probably a good idea to meet =
delivery deadlines.  But it would be more flexible and extensible if the =
delegation of authority explicitly defines the meter as well, which the =
AN shall use for enforcement.
=20
Best Regards=20
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20
=20
=20
=20
=20
=20
=20
=20



________________________________

	Von: Fortune HUANG [mailto:fqhuang@huawei.com]=20
	Gesendet: Mittwoch, 29. Oktober 2008 05:21
	An: Reith, Lothar; ancp@ietf.org; 'OOGHE Sven'; 'Francois Le Faucheur =
(flefauch)'; Tina TSOU; Tom Taylor; Maglione Roberta; Wojciech Dec =
(wdec); Haag, Thomas; stefaan.de_cnodder@alcatel-lucent.be
	Betreff: =B4=F0=B8=B4: [ANCP] DOA (was: ANCP Framework update)
=09
=09
	Hi Lothar,
	=20
	Thank you very for your comments.
	=20
	I can accept to extend the bandwidth delegation to Delegation of =
Authority conceptually in this draft.=20
	As I said before, I know the latter would be more generic.=20
	=20
	However, since the bandwidth delegation is so important in =
implementation, I strongly suggest we also specify the bandwidth =
delegation as an explicit instance. The first reason is that I believe =
the bandwidth delegation is the most shining point of the Delegation of =
Authority. The second reason is that the bandwidth delegation will have =
actuall impact on the parameters and encoding of the ANCP messages, =
which we do care very much for we have to implement it.
	=20
	=20
	Best Regards,
	Fortune
	=20

	Huawei Technologies Co., Ltd.  =20

=09


	Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =
518129, P.R. China
	Tel: +86-755-28971871
	Fax: +86-755-28972352
	Mobile: +8615013838060
	Email: fqhuang@huawei.com
	http://www.huawei.com
	=
-------------------------------------------------------------------------=
------------------------------------------------------------
	=
=B1=BE=D3=CA=BC=FE=BC=B0=C6=E4=B8=BD=BC=FE=BA=AC=D3=D0=BB=AA=CE=AA=B9=AB=CB=
=BE=B5=C4=B1=A3=C3=DC=D0=C5=CF=A2=A3=AC=BD=F6=CF=DE=D3=DA=B7=A2=CB=CD=B8=F8=
=C9=CF=C3=E6=B5=D8=D6=B7=D6=D0=C1=D0=B3=F6=B5=C4=B8=F6=C8=CB=BB=F2=C8=BA=D7=
=E9=A1=A3=BD=FB
	=
=D6=B9=C8=CE=BA=CE=C6=E4=CB=FB=C8=CB=D2=D4=C8=CE=BA=CE=D0=CE=CA=BD=CA=B9=D3=
=C3=A3=A8=B0=FC=C0=A8=B5=AB=B2=BB=CF=DE=D3=DA=C8=AB=B2=BF=BB=F2=B2=BF=B7=D6=
=B5=D8=D0=B9=C2=B6=A1=A2=B8=B4=D6=C6=A1=A2=BB=F2=C9=A2=B7=A2=A3=A9=B1=BE=D3=
=CA=BC=FE=D6=D0
	=
=B5=C4=D0=C5=CF=A2=A1=A3=C8=E7=B9=FB=C4=FA=B4=ED=CA=D5=C1=CB=B1=BE=D3=CA=BC=
=FE=A3=AC=C7=EB=C4=FA=C1=A2=BC=B4=B5=E7=BB=B0=BB=F2=D3=CA=BC=FE=CD=A8=D6=AA=
=B7=A2=BC=FE=C8=CB=B2=A2=C9=BE=B3=FD=B1=BE=D3=CA=BC=FE=A3=A1
	This e-mail and its attachments contain confidential information from =
HUAWEI, which=20
	is intended only for the person or entity whose address is listed =
above. Any use of the=20
	information contained herein in any way (including, but not limited to, =
total or partial=20
	disclosure, reproduction, or dissemination) by persons other than the =
intended=20
	recipient(s) is prohibited. If you receive this e-mail in error, please =
notify the sender by=20
	phone or email immediately and delete it!
=09
	=20

________________________________

	=B7=A2=BC=FE=C8=CB: Reith, Lothar [mailto:Lothar.Reith@detecon.com]=20
	=B7=A2=CB=CD=CA=B1=BC=E4: 2008=C4=EA10=D4=C229=C8=D5 1:09
	=CA=D5=BC=FE=C8=CB: Fortune HUANG; ancp@ietf.org
	=D6=F7=CC=E2: AW: [ANCP] DOA (was: ANCP Framework update)
=09
=09
	Hi Fortune,
	=20
	regarding your statement:
	=20
	The bandwidth can be negotiated dynamically in quantity. When the =
bandwidth on AN is insufficient, AN can ask for more from NAS/PS; when =
the bandwidth is insufficient, NAS/PS can ask for more from AN.
	=20
	I would like to comment as follows:
	=20
	Like in the real world, there is a hierarchy with the root being the =
legal owner of the resource, who is also the owner of the authority to =
control the resource. He delegates this authority  downwards through a =
chain of "Delegation of Authority" actions towards some enforcement =
point - in this case the AN. You may well imagine, that the root =
authority over all resource of a telco is with the shareholder annual =
assembly, which delegates it to the Management board, those to the CTO, =
and further to some line managers who delegate the control to some =
Policy Server, where our scope begins.
	=20
	What you refer to as negotiation, is rather a delegation of authority =
which is quantized with a certain amount of bandwidth. Note that the PS =
may have delegated authority to control the full bandwidth to the NAS, =
but the NAS delegates only part of that bandwidth onwards to the AN.=20
	=20
	 And yes, the AN may ask for that Delegation of Authority specifying =
the amount desired, and the NAS may grant it. However, if the NAS needs =
some of the delegated authority back for his own purposes, he withdraws =
part of the quantized authority by claiming back part of the previously =
delegated authority over access circuit bandwidth.
	=20
	The point is:  There is no real negotiation, because the AN and the =
NAS/PS are not peers.=20
	=20
	The AN has to obey to whatever the NAS grants, and is not allowed to =
exceed the delegated quantity of authority.  Note that the authority =
could be quantized in many ways, e.g. a time limited delegation of =
authority is just one example. Or a volume limited delegation of =
authority. This is still in line with the concept of "delegation of =
authority" in real life, and shows that this extensibility is very =
powerful indeed.=20
	=20
	=20
	Best Regards, Lothar Reith
	Detecon International GmbH (Deutsche Telekom Group)
	=20
	=20
	=20
________________________________

	Von: Fortune HUANG [mailto:fqhuang@huawei.com]
	Gesendet: Di 28.10.2008 15:41
	An: 'OOGHE Sven'; Reith, Lothar; ancp@ietf.org
	Betreff: =B4=F0=B8=B4: [ANCP] DOA (was: ANCP Framework update)
=09
=09

	Hi Sven, Lothar et al,

	=20

	Yes, the =A1=B0Delegation of Authority=A1=B1 is more generic than =
=A1=B0Bandwidth Delegation=A1=B1 and I fully agree with the example from =
Lothar was that not only the bandwidth can be delegated but also the =
content access control can be delegated.

	=20

	However, we have to pay attention to the difference of the delegation =
of bandwidth and the delegation of content access control.

	The bandwidth can be negotiated dynamically in quantity. When the =
bandwidth on AN is insufficient, AN can ask for more from NAS/PS; when =
the bandwidth is insufficient, NAS/PS can ask for more from AN.

	But this negotiation can not be applied for the content access control =
properly.

	=20

	That is to say, if we extend the =A1=B0bandwidth delegation=A1=B1 to =
=A1=B0delegation of authority=A1=B1, the negotiation still needs to be =
specified specially for the bandwidth.

	=20

	Best Regards,

	Fortune

	=20

	=20

	=20

=09
________________________________


	=B7=A2=BC=FE=C8=CB: ancp-bounces@ietf.org =
[mailto:ancp-bounces@ietf.org] =B4=FA=B1=ED OOGHE Sven
	=B7=A2=CB=CD=CA=B1=BC=E4: 2008=C4=EA10=D4=C227=C8=D5 18:49
	=CA=D5=BC=FE=C8=CB: Reith, Lothar; ancp@ietf.org
	=D6=F7=CC=E2: Re: [ANCP] DOA (was: ANCP Framework update)

	=20

	Hi Lothar,

	=20

	I think the term "Delegation of Authority" captures the principle of =
what bandwidth delegation is about. I'm fine either way, and would like =
to ask other people on this list what they think.

	=20

	Regards,

	Sven

	=20

=09
________________________________


	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Reith, Lothar
	Sent: zondag 26 oktober 2008 16:47
	To: ancp@ietf.org
	Subject: [ANCP] DOA (was: ANCP Framework update)

	Dear all,

	=20

	the ANCP Framework contains the word "delegation", which in my mind is =
key to the whole concept of ANCP.=20

	=20

	I would like to suggest that the concept of "delegation" should be made =
more extensible.=20

	=20

	Narrowing it to the term "bandwidth delegation" does not lend itself =
very well to extensibility.

	=20

	I would rather propose to introduce the more general term of DOA =
(Delegation of Authority), which is a well known concept in the real =
world, when a resource owner delegates control over part or all of his =
resources to someone else - e.g. during a vacation absence.

	=20

	Today, ANCP does not just support delegation in the form of bandwidth =
delegation, but also in the form of delegation of content access control =
(delegation occurs for whitelist and blacklist content, but not for the =
greylist content).

	=20

	I think the extensible concept "DOA" is very powerful when harnessed =
for Broadband Access using ANCP.

	=20

	While updating the framework it may be worth a consideration to add =
this hook for extensibility by following means:

	=20

	- replace the term "bandwidth delegation" by "DOA for part of access =
circuit bandwidth"

	=20

	- introduce the first extension of the DOA concept by making clear that =
the concepts of  whitelist and blacklist are DOA for Content Access =
Control.

	=20

	One more point with respect to the recent discussion about renaming the =
Policy Server.

	=20

	I like to state that I am fine with the current name "policy server".  =
Historically, I beleive the name was chosen as a compromise between the =
RADIUS camp and the COPS camp.

	=20

	If - given this background - we still want to change the name of the =
policy server, then perhaps DOA-server may be another alternative to =
consider.=20

	=20

	An important argument in this case would be, that the concept of =
"delegation of authority" is well aligned with the proxy concept, =
similar to a RADIUS Proxy Server, where the delegation of authority =
happens along a delegation chain which may span multiple RADIUS proxy =
servers and multiple domains. This aspect is missing in the other =
proposed names.

	=20

	Best Regards,

	=20

	Lothar Reith

	Detecon International GmbH (Deutsche Telekom Group)

	=20

	=20

=09
________________________________


	Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
	Gesendet: Do 23.10.2008 12:57
	An: ancp@ietf.org
	Betreff: Re: [ANCP] ANCP Framework update

	Hi,

	=20

	Here's the updated text. I removed any notion of "flags" or how the =
Access Node is told whether or not Bandwidth Delegation applies. I also =
covered Thomas' comments. Actually not that much work: the general ANCP =
requirements as well as the NAS requirements were written in a =
high-level way already. I only had to update the general text and some =
of the Access Node requirements. Below the extracted text, let me know =
your comments.

	=20

	Regards,

	Sven

	=20

	---

	=20

	General text

	=20

	   o  One approach is for the AN to query the NAS so that Admission
	      Control for the access line is performed by the NAS (possibly =
with
	      interactions with a Policy Server).  This can be done with or
	      without "bandwidth delegation" to the AN.

	=20

	      *  In case of Admission Control without AN Bandwidth Delegation,
	         the AN can use ANCP to query the NAS, that in turn performs
	         multicast Admission Control check for the new multicast flow
	         and responds to the AN indicating whether the join is to be
	         honored (and hence replication performed by the AN) or denied.
	         The NAS may locally maintain available "video" bandwidth on =
the
	         Access Loop (as a portion of the Access Loop net data rate),
	         and perform video bandwidth accounting for the Access Loop.
	         Upon receiving an Admission Request from the AN, the NAS can
	         check available "video" bandwidth before admitting or denying
	         the multicast flow.  In the process, the NAS may communicate

	         with the Policy Server.  For unicast video services such as
	         Video on Demand (VoD), the NAS may also be queried (by a =
Policy
	         Server or via on-path CAC signaling), so that it can perform
	         admission control for the unicast flow, and update the
	         available video bandwidth maintained by the NAS.

	=20

	      *  In case of Admission Control with AN Bandwidth Delegation, the
	         NAS (possibly with interactions with a Policy Server) manages
	         total bandwidth for video admission, performs unicast =
admission
	         control and uses ANCP to delegate a certain amount of =
bandwidth
	         for some multicast flows to the Access Node.  In this =
scenario,
	         upon receiving a join to a multicast flow which matches an
	         entry in the White or Grey List, the AN must perform the
	         necessary bandwidth admission control check for the new
	         multicast flow, before starting the multicast flow =
replication.

	Access Node requirements

	=20

	   o  The AN must deny any join to a multicast flow matching the Black
	      List for the relevant Access Port.

	=20

	   o  The AN must accept any join to a multicast flow matching the =
White
	      List and for which no Bandwidth Delegation is required.

	=20

	   o  Upon receiving a join to a multicast flow which matches the White
	      List whose and for which Bandwidth Delegation is required, the AN
	      must perform the necessary bandwidth admission control check for
	      the new flow before starting the multicast flow replication.

	=20

	   o  Upon receiving a join to a multicast flow which matches the Grey
	      List and for which no Bandwidth Delegation is required, the AN
	      must support using ANCP to query the NAS to receive a response
	      indicating whether that join is to be honored or denied.  In this
	      case, the NAS will perform both the necessary conditional access
	      and the admission control checks for the new flow.

	=20

	   o  Upon receiving a join to a multicast flow which matches the Grey
	      List and for which Bandwidth Delegation is required, the AN must
	      first perform the necessary bandwidth admission control check for
	      the new flow.  If successful, the AN must support using ANCP to
	      query the NAS to receive a response indicating whether that join
	      is to be honored or denied.

	=20

	   o  In case of Admission Control with AN Bandwidth Delegation, the AN
	      must support using ANCP to notify the NAS when the the user =
leaves
	      the multicast flow.

	=20

	   o  In case of Admission Control with AN Bandwidth Delegation, the AN
	      must support using ANCP to query the NAS to request additional
	      delegated multicast bandwidth on a given Access Port; the AN
	      should be able to specify both the minimum and the preferred
	      amount of additional multicast bandwidth requested.

=09
	   o  In case of Admission Control with AN Bandwidth Delegation, upon
	      receiving a Bandwidth Delegation Request from the NAS querying or
	      instructing to decrease the delegated multicast bandwidth on a
	      given Access Port, the AN must support using ANCP to send a
	      Bandwidth Delegation Response indicating the new delegated
	      multicast bandwidth.

	=20

	   o  In case of Admission Control with AN Bandwidth Delegation, the AN
	      must support using ANCP to send a Bandwidth Release message to =
the
	      NAS in order to release unused delegated multicast bandwidth on a
	      given Access Port.

	=20

	Regards,

	Sven

	=20

=09
________________________________


	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:58
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update

	=20

	On 20 Oct 2008, at 12:22, OOGHE Sven wrote:

=09
=09
=09

	Francois,

	=20

	Another approach we could take is to let the framework requirements be =
agnostic as to how the Access Node knows whether or not Bandwidth =
Delegation applies. We could describe the notion of Bandwidth Delegation =
and the respective requirements for the Access Node and NAS in this =
case.

	=20

	The details of how the use of Bandwidth Delegation is communicated to =
the Access Node - using a flag, some "on/off" knob or both - would be =
left to the actual protocol specification work.

	=20

	Good idea. It will avoid these cross dependencies between framework and =
protocol, which indeed reflect that we are probably trying to be too =
precise/prescriptive in the framework.

=09
=09
=09

	=20

	I think following this path would require relatively small edits to the =
document. I'm ok to take a first shot at it.

	=20

	That would be good.

	=20

	Thanks

	=20

	Francois

=09
=09
=09

	=20

	Regards,

	Sven

	=20

=09
________________________________


	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update

	Sven and all,=20

	=20

		   o  Upon receiving a join to a multicast flow which matches the Grey =

		      List whose entry is flagged as "no Bandwidth Delegation" for the =

		      relevant Access Port, the AN must support using ANCP to query =
the=20
		      NAS to receive a response indicating whether that join is to be=20
		      honored or denied.  In this case, the NAS will perform both the=20
		      necessary conditional access and the admission control checks =
for=20
		      the new flow.

	=20

	Roberta, Tom and myself have started drafting an I-D that will propose =
ANCP protocol extensions supporting some of those requirements (building =
on top of ancp-mc-multicast).

	In doing so, we revisited a point that came up multiple times: do we =
really need to provision a flag in each and every Grey/White List entry =
to activate/deactivate Bandwidth Delegation?

	=20

	The current approach (as correctly reflected in the updated Framework) =
is:

	* define a flag in each Grey/White List entry

	* assume that this flag will normally either always be set in all =
entries or never set.

	* setting/no-setting the flag is all entries effectively acts as the =
knob to enable/disable Bandwidth Delegation, therefore we did not need =
to specify a specific knob to enable/disable Bandwidth Delegation.

	=20

	Another approach would be:

	* remove flag from White/Grey list entries

	* define a specific knob to enable/disable Bandwidth Delegation at the =
AN granularity

	* in fact, define a generic AN-level provisioning method that could be =
used to enable/disable BAndwidth delegation, but could also be used for =
provisioning the "Service Profiles" that are currently assumed to be =
configured in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles

	=20

	Considering that:

	- we got several times the feedback that per-entry BAndwidth Delegation =
flag was confusing since Bandwidth Delegation granularity is more =
AN-level (and may lead to difficulties if it is set on some entries and =
not on others)

	- it is likely that we'll need, anyways, a mechanism to provision =
things at AN level, that could be easily used to convey Bandwidth =
Delegation enable/disable knob.

	we would like to propose to evolve to the newer approach.

	=20

	Thoughts?

	=20

	Francois

	=20

	PS: Sven, if we go for the new approach, we can document in an email =
the deltas that would be needed to reflect that in framework.

	=20

	=20


------_=_NextPart_002_01C939EE.D334C302
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.6000.16705" name=3DGENERATOR>
<STYLE>font-face {
	FONT-FAMILY: &#23435; 20307:=20
}
font-face {
	FONT-FAMILY: Tahoma
}
font-face {
	FONT-FAMILY: "@&#23435;&#20307;"
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"
}
SPAN.EmailStyle21 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DZH-CN style=3D"WORD-WRAP: break-word" vLink=3Dblue =
link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Hi Fortune,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>I agree, that we have to be pragmatic.=20
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>I recommend to check the meaning of bandwidth =

delegation, in order make the live of operators easier, who deploy ANs =
from=20
multiple manufacturers. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Based on my over 20 years experience in =
packet=20
switching, I am afraid that there&nbsp;may be&nbsp;a risk of different=20
interpretation of what "bandwidth" means.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Just stating kilobit/sec is not enough, you =
also have=20
to state what you count&nbsp; and how you enforce, with- our without =
buffering=20
and how deep the buffer is.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>In other words, while you delegate the =
authority for=20
bandwidth control, you better also specify the meter used to control the =

bandwidth, for example by specifying the two parameters of the token =
bucket=20
used, which defines the height and refill rate of the token=20
bucket.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>I assume there is consensus between the =
Access Node=20
vendors on what is being counted, like the IP packet including the =
header ??? or=20
PPPoE ???? or Ethernet ???? or only the payload ???</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>The point is, yes, you can do this bandwidth =
delegation=20
by agreeing on the meter. And pragmatically, that is probably a good =
idea to=20
meet delivery deadlines. &nbsp;But it would be more flexible and =
extensible if=20
the delegation of authority explicitly defines the meter as well, which =
the AN=20
shall use for enforcement.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Best Regards </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Lothar Reith</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Detecon International GmbH (Deutsche Telekom=20
Group)</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV><FONT face=3DArial=20
color=3D#0000ff size=3D2></FONT><BR>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>Von:</B> Fortune HUANG =
[mailto:fqhuang@huawei.com]=20
  <BR><B>Gesendet:</B> Mittwoch, 29. Oktober 2008 05:21<BR><B>An:</B> =
Reith,=20
  Lothar; ancp@ietf.org; 'OOGHE Sven'; 'Francois Le Faucheur =
(flefauch)'; Tina=20
  TSOU; Tom Taylor; Maglione Roberta; Wojciech Dec (wdec); Haag, Thomas; =

  stefaan.de_cnodder@alcatel-lucent.be<BR><B>Betreff:</B> =B4=F0=B8=B4: =
[ANCP] DOA (was:=20
  ANCP Framework update)<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Hi Lothar,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Thank you very for your =
comments.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>I can accept to extend the bandwidth =
delegation to=20
  Delegation of Authority conceptually in this draft. =
</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>As I said before, I know the latter would be =
more=20
  generic. </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>However, since&nbsp;the bandwidth delegation =
is so=20
  important in implementation, I strongly suggest we also specify the =
bandwidth=20
  delegation&nbsp;as an explicit instance. The first reason is that I =
believe=20
  the bandwidth delegation is the most shining point&nbsp;of the =
Delegation of=20
  Authority. The second reason is that the bandwidth delegation=20
  </FONT></SPAN><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5 color=3D#0000ff=20
  size=3D2>will have actuall impact on the parameters and encoding of =
the ANCP=20
  messages, which we do care very much for we have to implement=20
  it.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Best Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Fortune</FONT></SPAN></DIV>
  <DIV><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA size=3D2>&nbsp;</DIV>
  <DIV><BR></FONT><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dgray =
size=3D2>Huawei Technologies Co.,=20
  Ltd. </FONT><IMG id=3DridImg alt=3Dhuawei_logo hspace=3D0=20
  src=3D"cid:406312917@29102008-2FB3" align=3Dleft> </DIV>
  <P></P><BR><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dgray =
size=3D1>Addr: Section F, Huawei=20
  Industrial Base, Bantian Longgang, Shenzhen 518129, P.R. China<BR>Tel: =

  +86-755-28971871<BR>Fax: +86-755-28972352<BR>Mobile: =
+8615013838060<BR>Email:=20
  fqhuang@huawei.com<BR>http://www.huawei.com<BR></FONT><FONT =
face=3D=BB=AA=CE=C4=CF=B8=BA=DA=20
  color=3Dgray=20
  =
size=3D1>----------------------------------------------------------------=
---------------------------------------------------------------------<BR>=
=B1=BE=D3=CA=BC=FE=BC=B0=C6=E4=B8=BD=BC=FE=BA=AC=D3=D0=BB=AA=CE=AA=B9=AB=CB=
=BE=B5=C4=B1=A3=C3=DC=D0=C5=CF=A2=A3=AC=BD=F6=CF=DE=D3=DA=B7=A2=CB=CD=B8=F8=
=C9=CF=C3=E6=B5=D8=D6=B7=D6=D0=C1=D0=B3=F6=B5=C4=B8=F6=C8=CB=BB=F2=C8=BA=D7=
=E9=A1=A3=BD=FB<BR>=D6=B9=C8=CE=BA=CE=C6=E4=CB=FB=C8=CB=D2=D4=C8=CE=BA=CE=
=D0=CE=CA=BD=CA=B9=D3=C3=A3=A8=B0=FC=C0=A8=B5=AB=B2=BB=CF=DE=D3=DA=C8=AB=B2=
=BF=BB=F2=B2=BF=B7=D6=B5=D8=D0=B9=C2=B6=A1=A2=B8=B4=D6=C6=A1=A2=BB=F2=C9=A2=
=B7=A2=A3=A9=B1=BE=D3=CA=BC=FE=D6=D0<BR>=B5=C4=D0=C5=CF=A2=A1=A3=C8=E7=B9=
=FB=C4=FA=B4=ED=CA=D5=C1=CB=B1=BE=D3=CA=BC=FE=A3=AC=C7=EB=C4=FA=C1=A2=BC=B4=
=B5=E7=BB=B0=BB=F2=D3=CA=BC=FE=CD=A8=D6=AA=B7=A2=BC=FE=C8=CB=B2=A2=C9=BE=B3=
=FD=B1=BE=D3=CA=BC=FE=A3=A1<BR></FONT><FONT=20
  face=3DArial color=3Dgray size=3D1>This e-mail and its attachments =
contain=20
  confidential information from HUAWEI, which <BR>is intended only for =
the=20
  person or entity whose address is listed above. Any use of the =
<BR>information=20
  contained herein in any way (including, but not limited to, total or =
partial=20
  <BR>disclosure, reproduction, or dissemination) by persons other than =
the=20
  intended <BR>recipient(s) is prohibited. If you receive this e-mail in =
error,=20
  please notify the sender by <BR>phone or email immediately and delete=20
  it!<BR></FONT>
  <DIV>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Dzh-cn dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3D=CB=CE=CC=E5 size=3D2><B>=B7=A2=BC=FE=C8=CB:</B> Reith, =
Lothar=20
  [mailto:Lothar.Reith@detecon.com] <BR><B>=B7=A2=CB=CD=CA=B1=BC=E4:</B> =
2008=C4=EA10=D4=C229=C8=D5=20
  1:09<BR><B>=CA=D5=BC=FE=C8=CB:</B> Fortune HUANG; =
ancp@ietf.org<BR><B>=D6=F7=CC=E2:</B> AW: [ANCP] DOA=20
  (was: ANCP Framework update)<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV id=3DidOWAReplyText70064 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Hi =
Fortune,</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>regarding your =
statement:</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">The =
bandwidth can be=20
  negotiated dynamically in quantity. When the bandwidth on AN is =
insufficient,=20
  AN can ask for more from NAS/PS; when the bandwidth is insufficient, =
NAS/PS=20
  can ask for more from AN.</SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>I would like to comment as follows:</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>Like in the real world, there is a hierarchy with the root =
being the=20
  legal owner of the resource, who is also the owner of the authority to =

  control&nbsp;the resource. He delegates this authority &nbsp;downwards =
through=20
  a chain of "Delegation of Authority" actions towards some enforcement =
point -=20
  in this case the AN. You may well imagine, that the root authority =
over all=20
  resource of a telco is with the shareholder annual assembly, which =
delegates=20
  it to the Management board, those to the CTO, and further to some line =

  managers who delegate the control to some Policy Server, where our =
scope=20
  begins.</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>What you refer to as negotiation, is rather a delegation of =
authority=20
  which is quantized with a certain amount of bandwidth. Note =
that&nbsp;the PS=20
  may have delegated authority to control&nbsp;the full bandwidth to the =
NAS,=20
  but&nbsp;the NAS delegates only part of that bandwidth onwards to the=20
  AN.&nbsp;</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>&nbsp;And yes, the AN may ask for that Delegation of =
Authority=20
  specifying the amount desired, and the NAS may grant it. However, if =
the NAS=20
  needs some of the delegated authority back for his own purposes, he =
withdraws=20
  part of the quantized authority by claiming back part of the =
previously=20
  delegated authority over access circuit bandwidth.</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>The point is:&nbsp; There is no real negotiation, because the =
AN and=20
  the NAS/PS are not peers. </FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>The AN has to obey to whatever the NAS grants, and is not =
allowed to=20
  exceed the delegated quantity of authority.&nbsp; Note that the =
authority=20
  could be quantized in many ways, e.g. a time limited delegation of =
authority=20
  is just one example. Or a volume limited delegation of authority. This =
is=20
  still in line with the concept of "delegation of authority" in real =
life, and=20
  shows that this extensibility is very powerful indeed. =
</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>Best Regards, Lothar Reith</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon=20
  International GmbH (Deutsche Telekom Group)</SPAN></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr>
  <HR tabIndex=3D-1>
  </DIV>
  <DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>Von:</B> Fortune HUANG=20
  [mailto:fqhuang@huawei.com]<BR><B>Gesendet:</B> Di 28.10.2008=20
  15:41<BR><B>An:</B> 'OOGHE Sven'; Reith, Lothar;=20
  ancp@ietf.org<BR><B>Betreff:</B> =B4=F0=B8=B4: [ANCP] DOA (was: ANCP =
Framework=20
  update)<BR></FONT><BR></DIV></DIV>
  <DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DSV=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Hi Sven, =
Lothar et=20
  al,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DSV=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Yes, the =
=A1=B0Delegation=20
  of Authority=A1=B1 is more generic than =A1=B0Bandwidth =
Delegation=A1=B1 and I fully agree=20
  with the example from Lothar was that not only the bandwidth can be =
delegated=20
  but also the content access control can be =
delegated.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">However, we =
have to=20
  pay attention to the difference of the delegation of bandwidth and the =

  delegation of content access control.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">The =
bandwidth can be=20
  negotiated dynamically in quantity. When the bandwidth on AN is =
insufficient,=20
  AN can ask for more from NAS/PS; when the bandwidth is insufficient, =
NAS/PS=20
  can ask for more from AN.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">But this =
negotiation=20
  can not be applied for the content access control =
properly.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">That is to =
say, if we=20
  extend the =A1=B0bandwidth delegation=A1=B1 to =A1=B0delegation of =
authority=A1=B1, the=20
  negotiation still needs to be specified specially for the=20
  bandwidth.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Best=20
  Regards,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial">Fortune</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US =
style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=B7=A2=BC=FE=C8=CB<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> =
ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] </SPAN></FONT><B><FONT =
face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=B4=FA=B1=ED=20
  </SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5">OOGHE =
Sven<BR></SPAN></FONT><B><FONT=20
  face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=B7=A2=CB=CD=CA=B1=BC=E4<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> 2008<SPAN =
lang=3DEN-US><SPAN=20
  lang=3DEN-US>=C4=EA10</SPAN></SPAN><SPAN lang=3DEN-US><SPAN=20
  lang=3DEN-US>=D4=C227</SPAN></SPAN><SPAN lang=3DEN-US><SPAN =
lang=3DEN-US>=C8=D5</SPAN></SPAN>=20
  18:49<BR></SPAN></FONT><B><FONT face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=CA=D5=BC=FE=C8=CB<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> Reith, Lothar;=20
  ancp@ietf.org<BR></SPAN></FONT><B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=D6=F7=CC=E2<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> Re: [ANCP] DOA =
(was: ANCP Framework=20
  update)</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi=20
  Lothar,</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think the =
term=20
  "Delegation of Authority" captures the principle of what bandwidth =
delegation=20
  is about. I'm fine either way, and would like to ask other people on =
this list=20
  what they think.</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN=20
  lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><SPAN=20
  lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US =
style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B><SPAN style=3D"FONT-WEIGHT: bold">On =
Behalf Of=20
  </SPAN></B>Reith, Lothar<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> zondag 26 oktober 2008=20
  16:47<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
  ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> [ANCP]=20
  DOA (was: ANCP Framework update)</SPAN></FONT><SPAN =
lang=3DEN-US></SPAN></P>
  <DIV id=3DidOWAReplyText66978>
  <DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Dear=20
  all,</SPAN></FONT></P></DIV>
  <DIV>
  <DIV id=3DidOWAReplyText68228>
  <DIV id=3DidOWAReplyText93369>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">the ANCP =
Framework=20
  contains the word "delegation", which in my mind is key to the whole =
concept=20
  of ANCP. </SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I would =
like to=20
  suggest that the concept of "delegation" should be made more =
extensible.=20
  </SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Narrowing =
it to the=20
  term "bandwidth delegation" does not lend itself very well to=20
  extensibility.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I would =
rather=20
  propose to introduce the more general term of DOA (Delegation of =
Authority),=20
  which is a well known concept in the real world, when a resource owner =

  delegates control over part or all of his resources to someone else - =
e.g.=20
  during a vacation absence.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Today, =
ANCP does not=20
  just support delegation in the form of bandwidth delegation, but also =
in the=20
  form of delegation of content access control (delegation occurs for =
whitelist=20
  and blacklist content, but not for the greylist=20
  content).</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I think =
the=20
  extensible concept "DOA"&nbsp;is very powerful when harnessed for =
Broadband=20
  Access using ANCP.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">While =
updating the=20
  framework it may be worth a consideration to add this hook for =
extensibility=20
  by following means:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- =
replace&nbsp;the=20
  term "bandwidth delegation" by "DOA for part of access circuit=20
  bandwidth"</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- =
introduce the=20
  first extension of the DOA concept by making clear that the concepts =
of=20
  &nbsp;whitelist and blacklist are DOA for Content Access=20
  Control.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">One more =
point with=20
  respect to the recent discussion about renaming the Policy=20
  Server.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I like to =
state that=20
  I am fine with the current name "policy=20
  server".&nbsp;&nbsp;Historically,&nbsp;I beleive&nbsp;the name was =
chosen as a=20
  compromise between the RADIUS camp and the COPS =
camp.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">If - given =
this=20
  background - we&nbsp;still want to change the name of the policy =
server, then=20
  perhaps DOA-server may be another alternative to consider.=20
  </SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">An =
important=20
  argument in this case would be, that the concept of "delegation of =
authority"=20
  is well aligned with the proxy concept, similar to a RADIUS Proxy =
Server,=20
  where the delegation of authority happens along a delegation chain =
which may=20
  span multiple RADIUS proxy servers and multiple domains. This aspect =
is=20
  missing in the other proposed names.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Best=20
  Regards,</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Lothar=20
  Reith</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon=20
  International GmbH (Deutsche Telekom Group)</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Tahoma">Von:</SPAN></FONT></B><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma">=20
  ancp-bounces@ietf.org im Auftrag von OOGHE Sven<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B> Do 23.10.2008 =
12:57<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">An:</SPAN></B> ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B> Re: [ANCP] ANCP =
Framework=20
  update</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Here's the =
updated=20
  text. I removed any notion of "flags" or how the Access Node is told =
whether=20
  or not Bandwidth Delegation applies. I also covered Thomas' comments. =
Actually=20
  not that much work: the general ANCP requirements as well as the NAS=20
  requirements were written in a high-level way&nbsp;already. I only had =
to=20
  update the general text and some of the Access Node requirements. =
Below the=20
  extracted text, let me know your comments.</SPAN></FONT><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">---</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><STRONG><B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">General=20
  text</SPAN></FONT></B></STRONG><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  One approach is for the AN to query the NAS so that=20
  Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the access =
line is=20
  performed by the NAS (possibly with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  interactions with a Policy Server).&nbsp; This can be done with=20
  or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth delegation" to =
the=20
  AN.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  *&nbsp; In case of Admission Control without AN Bandwidth=20
  Delegation,</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the AN can use ANCP to query the NAS, that in turn=20
  performs</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast Admission Control check for the new multicast=20
  flow</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  and responds to the AN indicating whether the join is to=20
  be</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  honored (and hence replication performed by the AN) or=20
  denied.</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The NAS may locally maintain available "video" bandwidth on=20
  the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Loop (as a portion of the Access Loop net data=20
  rate),</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  and perform video bandwidth accounting for the Access=20
  Loop.</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Upon receiving an Admission Request from the AN, the NAS=20
  can</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  check available "video" bandwidth before admitting or=20
  denying</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the multicast flow.&nbsp; In the process, the NAS may=20
  communicate</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =

  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  with the Policy Server.&nbsp; For unicast video services such=20
  as</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Video on Demand (VoD), the NAS may also be queried (by a=20
  Policy</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Server or via on-path CAC signaling), so that it can=20
  perform</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  admission control for the unicast flow, and update=20
  the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  available video bandwidth maintained by the=20
  NAS.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  *&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  NAS (possibly with interactions with a Policy Server)=20
  manages</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  total bandwidth for video admission, performs unicast=20
  admission</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  control and uses ANCP to delegate a certain amount of=20
  bandwidth</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  for some multicast flows to the Access Node.&nbsp; In this=20
  scenario,</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  upon receiving a join to a multicast flow which matches=20
  an</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  entry in the White or Grey List, the AN must perform=20
  the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  necessary bandwidth admission control check for the=20
  new</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow, before starting the multicast flow=20
  replication.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><STRONG><B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Access=20
  Node requirements</SPAN></FONT></B></STRONG><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  The AN must deny any join to a multicast flow matching the=20
  Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List for the relevant Access=20
  Port.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  The AN must accept any join to a multicast flow matching the=20
  White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which no =
Bandwidth=20
  Delegation is required.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  Upon receiving a join to a multicast flow which matches the=20
  White</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List whose and for which Bandwidth Delegation is required, the=20
  AN</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
perform the=20
  necessary bandwidth admission control check=20
  for</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow before=20
  starting the multicast flow=20
  replication.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  Upon receiving a join to a multicast flow which matches the=20
  Grey</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List and for which no Bandwidth Delegation is required, the=20
  AN</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using=20
  ANCP to query the NAS to receive a=20
  response</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating =
whether=20
  that join is to be honored or denied.&nbsp; In=20
  this</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case, the =
NAS will=20
  perform both the necessary conditional=20
  access</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the =
admission=20
  control checks for the new =
flow.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  Upon receiving a join to a multicast flow which matches the=20
  Grey</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List and for which Bandwidth Delegation is required, the AN=20
  must</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first =
perform the=20
  necessary bandwidth admission control check=20
  for</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow.&nbsp;=20
  If successful, the AN must support using ANCP=20
  to</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the =
NAS to=20
  receive a response indicating whether that=20
  join</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored or=20
  denied.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  In case of Admission Control with AN Bandwidth Delegation, the=20
  AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to notify =
the NAS=20
  when the the user leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast=20
  flow.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  In case of Admission Control with AN Bandwidth Delegation, the=20
  AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS=20
  to request additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated =
multicast=20
  bandwidth on a given Access Port; the =
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  should be able to specify both the minimum and the=20
  preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount of additional =
multicast=20
  bandwidth requested.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><BR>&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =
Delegation=20
  Request from the NAS querying or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
instructing=20
  to decrease the delegated multicast bandwidth on=20
  a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support=20
  using ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth =
Delegation=20
  Response indicating the new =
delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast bandwidth.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  In case of Admission Control with AN Bandwidth Delegation, the=20
  AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to send a =

  Bandwidth Release message to the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =
in=20
  order to release unused delegated multicast bandwidth on=20
  a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access =
Port.</SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> Francois =
Le=20
  Faucheur IMAP [mailto:flefauch@cisco.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 20 oktober 2008=20
  12:58<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> OOGHE=20
  Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Francois =
Le Faucheur=20
  IMAP; ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
  Re: [ANCP] ANCP Framework update</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">On 20 Oct =
2008, at=20
  12:22, OOGHE Sven wrote:</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>
  <DIV style=3D"WORD-WRAP: break-word">
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Francois,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Another =
approach we=20
  could take is to let the framework requirements be agnostic as to how =
the=20
  Access Node knows whether or not Bandwidth Delegation applies. We =
could=20
  describe the notion of Bandwidth Delegation and the respective =
requirements=20
  for the Access Node and NAS in this case.</SPAN></FONT><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The details =
of how=20
  the use of Bandwidth Delegation is communicated to the Access Node - =
using a=20
  flag, some "on/off" knob or both - would be left to the actual =
protocol=20
  specification work.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Good idea. =
It will=20
  avoid these cross dependencies between framework and protocol, which =
indeed=20
  reflect that we are probably trying to be too precise/prescriptive=20
  in&nbsp;the&nbsp;framework.</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>
  <DIV style=3D"WORD-WRAP: break-word">
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think =
following=20
  this path would require relatively small edits to the document. I'm ok =
to take=20
  a first shot at it.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">That would =
be=20
  good.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Thanks</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Francois</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>
  <DIV style=3D"WORD-WRAP: break-word">
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> Francois =
Le=20
  Faucheur IMAP [<A=20
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>] =
<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 20 oktober 2008=20
  12:01<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> OOGHE=20
  Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Francois =
Le Faucheur=20
  IMAP; <A href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] ANCP =
Framework=20
  update</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Sven and =
all,=20
  </SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <DIV>
  <BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt" =
type=3D"cite">
    <DIV>
    <P><I><FONT face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a join to a multicast flow which matches the=20
    Grey</SPAN></FONT></I><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-US=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
whose entry=20
    is flagged as "no Bandwidth Delegation" for the</SPAN></I> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant =
Access=20
    Port, the AN must support using ANCP to query the</SPAN></I> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to =
receive a=20
    response indicating whether that join is to be</SPAN></I> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored =
or=20
    denied.&nbsp; In this case, the NAS will perform both the</SPAN></I> =

    <BR><I><SPAN style=3D"FONT-STYLE: =
italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    necessary conditional access and the admission control checks =
for</SPAN></I>=20
    <BR><I><SPAN style=3D"FONT-STYLE: =
italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
    new flow.</SPAN></I></SPAN></FONT></P></DIV></BLOCKQUOTE>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Roberta, =
Tom and=20
  myself have started drafting an I-D that will propose ANCP protocol =
extensions=20
  supporting some of those requirements (building on top of=20
  ancp-mc-multicast).</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">In doing =
so, we=20
  revisited a point that came up multiple times: do we really need to =
provision=20
  a flag in each and every Grey/White List entry=20
  to&nbsp;activate/deactivate&nbsp;Bandwidth =
Delegation?</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">The =
current approach=20
  (as correctly reflected in the updated Framework) =
is:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* define a =
flag in=20
  each Grey/White List entry</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* assume =
that this=20
  flag will normally either always be set in all entries or never=20
  set.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* =
setting/no-setting=20
  the flag is all entries effectively acts as the knob to enable/disable =

  Bandwidth Delegation, therefore we did not need to specify a specific =
knob to=20
  enable/disable Bandwidth Delegation.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Another =
approach=20
  would be:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* remove =
flag from=20
  White/Grey list entries</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* define a =
specific=20
  knob to enable/disable Bandwidth Delegation at the AN=20
  granularity</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* in fact, =
define a=20
  generic&nbsp;AN-level provisioning method that could be used to =
enable/disable=20
  BAndwidth delegation, but&nbsp;could&nbsp;also be used for =
provisioning the=20
  "Service Profiles" that are currently assumed to be configured in AN, =
as well=20
  as provisioning the Multicast White/Grey/Black=20
Profiles</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Considering=20
  that:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- we got =
several=20
  times the feedback that per-entry BAndwidth Delegation flag was =
confusing=20
  since&nbsp;Bandwidth Delegation granularity is more AN-level (and may =
lead to=20
  difficulties if it is set on some entries and not on=20
  others)</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- it is =
likely that=20
  we'll need, anyways, a mechanism to provision things at AN level, that =
could=20
  be easily used to convey Bandwidth Delegation enable/disable=20
  knob.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">we&nbsp;would&nbsp;like=20
  to propose to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer=20
  approach.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Thoughts?</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Francois</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">PS: Sven, =
if we go=20
  for&nbsp;the&nbsp;new approach, we can document in an email the deltas =

  that&nbsp;would&nbsp;be needed to reflect that in=20
  framework.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></DIV></DIV></DIV>=
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_002_01C939EE.D334C302--

------_=_NextPart_001_01C939EE.D334C302
Content-Type: image/jpeg;
	name="att12f37.jpg"
Content-Transfer-Encoding: base64
Content-ID: <406312917@29102008-2FB3>
Content-Description: att12f37.jpg
Content-Location: att12f37.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/7QxmUGhvdG9zaG9wIDMuMAA4QklNBCUAAAAAABAAAAAAAAAA
AAAAAAAAAAAAOEJJTQPtAAAAAAAQAEgAAAABAAIASAAAAAEAAjhCSU0EJgAAAAAADgAAAAAAAAAA
AAA/gAAAOEJJTQQNAAAAAAAEAAAAHjhCSU0EGQAAAAAABAAAAB44QklNA/MAAAAAAAkAAAAAAAAA
AAEAOEJJTQQKAAAAAAABAAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgAB
AGxmZgAGAAAAAAABAC9mZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0A
AAAGAAAAAAABOEJJTQP4AAAAAABwAAD/////////////////////////////A+gAAAAA////////
/////////////////////wPoAAAAAP////////////////////////////8D6AAAAAD/////////
////////////////////A+gAADhCSU0EAAAAAAAAAgAAOEJJTQQCAAAAAAACAAA4QklNBDAAAAAA
AAEBADhCSU0ELQAAAAAABgABAAAABjhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBB4A
AAAAAAQAAAAAOEJJTQQaAAAAAAM9AAAABgAAAAAAAAAAAAAAIAAAAGYAAAAEAGwAbwBnAG8AAAAB
AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAGYAAAAgAAAAAAAAAAAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAAAAAAAAAEAAAAAEAAAAAAABudWxsAAAAAgAAAAZib3VuZHNPYmpjAAAAAQAAAAAA
AFJjdDEAAAAEAAAAAFRvcCBsb25nAAAAAAAAAABMZWZ0bG9uZwAAAAAAAAAAQnRvbWxvbmcAAAAg
AAAAAFJnaHRsb25nAAAAZgAAAAZzbGljZXNWbExzAAAAAU9iamMAAAABAAAAAAAFc2xpY2UAAAAS
AAAAB3NsaWNlSURsb25nAAAAAAAAAAdncm91cElEbG9uZwAAAAAAAAAGb3JpZ2luZW51bQAAAAxF
U2xpY2VPcmlnaW4AAAANYXV0b0dlbmVyYXRlZAAAAABUeXBlZW51bQAAAApFU2xpY2VUeXBlAAAA
AEltZyAAAAAGYm91bmRzT2JqYwAAAAEAAAAAAABSY3QxAAAABAAAAABUb3AgbG9uZwAAAAAAAAAA
TGVmdGxvbmcAAAAAAAAAAEJ0b21sb25nAAAAIAAAAABSZ2h0bG9uZwAAAGYAAAADdXJsVEVYVAAA
AAEAAAAAAABudWxsVEVYVAAAAAEAAAAAAABNc2dlVEVYVAAAAAEAAAAAAAZhbHRUYWdURVhUAAAA
AQAAAAAADmNlbGxUZXh0SXNIVE1MYm9vbAEAAAAIY2VsbFRleHRURVhUAAAAAQAAAAAACWhvcnpB
bGlnbmVudW0AAAAPRVNsaWNlSG9yekFsaWduAAAAB2RlZmF1bHQAAAAJdmVydEFsaWduZW51bQAA
AA9FU2xpY2VWZXJ0QWxpZ24AAAAHZGVmYXVsdAAAAAtiZ0NvbG9yVHlwZWVudW0AAAARRVNsaWNl
QkdDb2xvclR5cGUAAAAATm9uZQAAAAl0b3BPdXRzZXRsb25nAAAAAAAAAApsZWZ0T3V0c2V0bG9u
ZwAAAAAAAAAMYm90dG9tT3V0c2V0bG9uZwAAAAAAAAALcmlnaHRPdXRzZXRsb25nAAAAAAA4QklN
BCgAAAAAAAwAAAABP/AAAAAAAAA4QklNBBEAAAAAAAEBADhCSU0EFAAAAAAABAAAAAg4QklNBAwA
AAAABnAAAAABAAAAZgAAACAAAAE0AAAmgAAABlQAGAAB/9j/4AAQSkZJRgABAgAASABIAAD/7QAM
QWRvYmVfQ00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUT
ExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4O
Dg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMB
IgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEB
AAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSR
obFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSF
tJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIR
AyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVV
NnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEA
AhEDEQA/APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC6
6f56f3t30Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUs
VaDHl/dl/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5Vtns
U/qp1vqPUvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9
w9+kqfV+qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVh
fWLCzerW9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX
146P1azqFWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKeh
SWDk/XHpVHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8t
bvSU9Ikucy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uo
JBeNpMtfRc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxb
qtG20uI0PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv
/QXjOu9COI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5F
ztrrn/usXoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4
HX+6yY/jQHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v
6hNyW9Q6jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m
+u1tQc9n0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6
tfRj2YnTgMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJ
JT5b0bpfUrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6r
WuLnfpNjXu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z
OEJJTQQhAAAAAABVAAAAAQEAAAAPAEEAZABvAGIAZQAgAFAAaABvAHQAbwBzAGgAbwBwAAAAEwBB
AGQAbwBiAGUAIABQAGgAbwB0AG8AcwBoAG8AcAAgAEMAUwAyAAAAAQA4QklNBAYAAAAAAAcABQAA
AAEBAP/hB4ZFeGlmAABJSSoACAAAAAcAEgEDAAEAAAABAAAAGgEFAAEAAABiAAAAGwEFAAEAAABq
AAAAKAEDAAEAAAACAAAAMQECABwAAAByAAAAMgECABQAAACOAAAAaYcEAAEAAACiAAAAzAAAAID8
CgAQJwAAgPwKABAnAABBZG9iZSBQaG90b3Nob3AgQ1MyIFdpbmRvd3MAMjAwNzowMjoyNiAxNjox
ODo1MwADAAGgAwABAAAA/////wKgBAABAAAAZgAAAAOgBAABAAAAIAAAAAAAAAAGAAMBAwABAAAA
BgAAABoBBQABAAAAGgEAABsBBQABAAAAIgEAACgBAwABAAAAAgAAAAECBAABAAAAKgEAAAICBAAB
AAAAVAYAAAAAAABIAAAAAQAAAEgAAAABAAAA/9j/4AAQSkZJRgABAgAASABIAAD/7QAMQWRvYmVf
Q00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwM
DAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwM
DAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMBIgACEQED
EQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAA
AAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQV
UsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0
pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRB
UWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKz
hMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/
APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC66f56f3t3
0Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUsVaDHl/dl
/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5VtnsU/qp1vqP
UvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9w9+kqfV+
qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVhfWLCzerW
9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX146P1azq
FWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKehSWDk/XHp
VHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8tbvSU9Iku
cy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uoJBeNpMtf
Rc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxbqtG20uI0
PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv/QXjOu9C
OI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5Fztrrn/us
XoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4HX+6yY/j
QHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v6hNyW9Q6
jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m+u1tQc9n
0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6tfRj2YnT
gMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJJT5b0bpf
UrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6rWuLnfpNj
Xu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z/9sAQwAI
BgYHBgUIBwcHCQkICgwUDQwLCwwZEhMPFB0aHx4dGhwcICQuJyAiLCMcHCg3KSwwMTQ0NB8nOT04
MjwuMzQy/9sAQwEJCQkMCwwYDQ0YMiEcITIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIy/8AAEQgAIABmAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAA
AAABAgMEBQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGh
CCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV
1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkK
C//EALURAAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy
0QoWJDThJfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKD
hIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm
5+jp6vLz9PX29/j5+v/aAAwDAQACEQMRAD8A99LKCASAT0FcOvxDin8XjRre2Bt1l8mS4Zud3Tge
ma5X4j67qukeObG5hdkhto1e3H8L5+9n1z0rnriVIvF9pqdmP9E1CdLiPn7pLDcp9wcj8q8+vimn
yx0sz6zLsihOj7WtrzxbXk/87a/f2PazrqpqL27oBEsnlhwec+4rYyCSM8jtXj0OupJ4hvZbhytr
aSvNOfYHhfqTgVJ4G8R6nrfxAuLklzbTRMZlz8qKPu/THSnSxT5rS1u9Dlr5HNU5VVooxu/8vX/g
dz1+iszX9at/Dug3mr3Su9vax+Y4jGWI9qz9U8ZafpXgtfFE0U7WTQpKEVRvw2McZ967z506Oiuf
03xbY6n4juNDhjmFzBaR3bMw+Xa4BA+vIp2leKrHV9d1nSIElSfSXVJ2cAKdwyMH8KAN6iuM0P4l
6J4hn1eDTkuJJdNRpCpUAzICQWTnkZFK/wASdEj8Ar4wInNiSF8sKPMD7tu3GcZBoA7KiuSu/iDo
9p4NsvE22eW0vWRII41BkZ2OAuM9Rg/lVbUviXptnq82lWem6pql7bgfaUsbfzBCT2Y5xn2oA7ai
uB134q6V4b0nTb7VdM1K3N/v2W7xASJtOPmGeOtFAHnupab4l8P3s+kX+nT6ro/mFoCVLgAngo45
RvUfpWr4a8NnUmFrB5qwxyrcol0hSS3YEZB7MrDjI74r0TxX4MtPFSRNLd3VpcRcLNbyEHHcEdDV
zQPDGn+G7XyrNZHdv9ZPM5d3+p/oK4/q153ex9Is9ccNyrSfktL93/wN+uh5n4m8NNp8ssEvm+Rc
TtcyC2QvJOSTtUDsqjue5NZumaX4h1meLStP06fTNLLgzHaV3Ad3c8sfbp7V7Frnh6w8QWohvEcM
v3JYmKun0P8AjVHwx4PtfDJleO7urueQYMk75wvoB0FTLC+/psa0s/UcLaWtRbXWl++/57dNCp8S
reR/hjrlvBG8shtNqqilmbkdhXmniXwPqEPweS7XW/EFzKbWE/2dI+6MHjK7MZwP6V73RXcfLHj8
V+3g34ivrOq2F9/ZmoaPbwx3MFu0oWRAMqwUZB4rDe/1hIPGWsaXpl/HJ4lu4rPTPMhZXIwQ0hGM
qAO59a98ooA8Fl0Dxb4DvvDmuXNnp8tlpiiwnTTUdpJIHPJcEc4Jzx3pkOgagvj2HwV9gmfw+dY/
thZmQ+X5XllvLPGOuePWvfaKAPBfD2iapL48svB91ZTLpGhalPqKTsp2SKeY1B6cE5/Oqg0u58Le
LfEMes33imwjvLs3FvcaOheKdSSfmwCcjOK+haKAPm34sWlxqvhPwrJpi6zqcY8/M13CxnPzD74x
ke3tRX0lRQB//9k=

------_=_NextPart_001_01C939EE.D334C302--

--===============0306481008==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============0306481008==--


From ancp-bounces@ietf.org  Thu Oct 30 03:08:35 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CB3C3A68B4;
	Thu, 30 Oct 2008 03:08:35 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6456428C0F7
	for <ancp@core3.amsl.com>; Thu, 30 Oct 2008 03:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.767
X-Spam-Level: ****
X-Spam-Status: No, score=4.767 tagged_above=-999 required=5 tests=[AWL=-1.719, 
	BAYES_50=0.001, CN_BODY_35=0.339, EXTRA_MPART_TYPE=1,
	HELO_EQ_FR=0.35, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001,
	MIME_CHARSET_FARAWAY=2.45, MY_CID_AND_ARIAL2=1.46]
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 w-GDvBhgacFQ for <ancp@core3.amsl.com>;
	Thu, 30 Oct 2008 03:08:30 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 48A703A6881
	for <ancp@ietf.org>; Thu, 30 Oct 2008 03:08:29 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.ad2.ad.alcatel.com
	[155.132.6.78])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9UA7nke026833; 
	Thu, 30 Oct 2008 11:07:49 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.56]) by
	FRVELSBHS06.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 30 Oct 2008 11:07:48 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 11:07:45 +0100
Message-ID: <7168964CAC5C144685272595141B6DBA01552FF5@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <5661758E3E93364685B91DD8272F2876437EC5@S4DE8PSAAQC.mitte.t-com.de>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA (was: ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScgAKwVUcAA5YynwAAUSsJAAGA9s4AAcFwNQAB37q4AABIQQEA==
References: <004201c9397d$c1d61da0$7b27460a@china.huawei.com>
	<D4ECB93FEDE50045B2657B56894BADF207B78960@DC00331.detecon.com>
	<5661758E3E93364685B91DD8272F2876437EC5@S4DE8PSAAQC.mitte.t-com.de>
From: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.be>
To: "Haag, Thomas" <HaagT@telekom.de>, <Lothar.Reith@detecon.com>,
	<fqhuang@huawei.com>, <ancp@ietf.org>, <flefauch@cisco.com>,
	<tena@huawei.com>, <tom.taylor@rogers.com>,
	<roberta.maglione@telecomitalia.it>, <wdec@cisco.com>,
	"DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
X-OriginalArrivalTime: 30 Oct 2008 10:07:48.0489 (UTC)
	FILETIME=[5C8ACF90:01C93A77]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1812714312=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1812714312==
Content-class: urn:content-classes:message
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----_=_NextPart_001_01C93A77.5C366394"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93A77.5C366394
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C93A77.5C366394"


------_=_NextPart_002_01C93A77.5C366394
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Thomas, Lothar,
=20
I agree that we should be clear on the terminology used. The actual net =
data rate defines the "bitpipe" that is conveyed from the Access Node to =
the NAS. It enables the NAS to use the bitpipe as it sees fit. In an =
Ethernet network, it would fill the bitpipe with Ethernet frames =
(regardless of higher layer protocols, PPPoE, IPoE, IPv4/IPv6 etc).
=20
In terms of bandwidth delegation, I think we are referring to =
"delegation of authority to perform admission control on a subset of the =
actual net data rate". That's a mouthful but should be the most accurate =
description.
=20
In my understanding, "bandwidth" refers to the notion of filling this =
"bitpipe". So when referring to=20
=20
"The NAS may locally maintain available "video" bandwidth  on the Access =
Loop, and perform video bandwidth accounting..."
=20
I think this is actually correct. "video bandwidth" refers to a portion =
of the "bitpipe" that is used for video applications. How the NAS =
converts video bitrates into Ethernet frame rates and corresponding =
"video bandwidth" is IMHO beyond the scope of the ANCP framework.
=20
Basically, I would prefer maintaining the definitions of net data rate =
and the existing text on "video bandwidth", clarifying that the latter =
can be a subset of the net data rate.
=20
Regards,
Sven

________________________________

From: Haag, Thomas [mailto:HaagT@telekom.de]=20
Sent: donderdag 30 oktober 2008 9:12
To: Lothar.Reith@detecon.com; fqhuang@huawei.com; ancp@ietf.org; OOGHE =
Sven; flefauch@cisco.com; tena@huawei.com; tom.taylor@rogers.com; =
roberta.maglione@telecomitalia.it; wdec@cisco.com; DE CNODDER Stefaan
Subject: AW: [ANCP] DOA (was: ANCP Framework update)


All,
=20
from my point of view we should not start a discussion about =
fundamentals which already defined.
=20
The terminology "Actual data rate Up- and Downstream" is defined in =
TR-101 Table 3 and WT-147 Table 1. Actual Data Rate refers to ITU-T =
G.997.1 section 7.5.2.1 which means net data rate which is a common =
standardized reference. The terminology of bandwidth is not defined =
which is really a risk Lothar already mentioned.
=20
Please see also my comment:
=20
...The NAS may locally maintain available "video" bandwidth  [T.H.:]  =
(net data rate) on the=20
         Access Loop, and perform video bandwidth accounting for the=20

So considering the definition mentioned above reflecting the discussion =
about bandwidth delegation I think this does not match in detail.
=20
Bandwidth delegation is used in a sense of video servcie oriented =
bandwidth. NAS works on layer3 which is different to AN net data rate =
which is reported by ANCP.
=20
So I think delegation of bandwidth is misleading due to non harmonized =
definitions.=20
>From my point of view the only way out is to refer to already =
standardized defintions having a common agreed reference.

Regards=20
Thomas Haag=20
Deutsche Telekom AG



________________________________

Von: Reith, Lothar=20
Gesendet: Mittwoch, 29. Oktober 2008 18:50
An: Fortune HUANG; ancp@ietf.org; OOGHE Sven; Francois Le Faucheur =
(flefauch); Tina TSOU; Tom Taylor; Maglione Roberta; Wojciech Dec =
(wdec); Haag, Thomas; stefaan.de_cnodder@alcatel-lucent.be
Betreff: AW: [ANCP] DOA (was: ANCP Framework update)


Hi Fortune,
=20
I agree, that we have to be pragmatic.=20
=20
I recommend to check the meaning of bandwidth delegation, in order make =
the live of operators easier, who deploy ANs from multiple =
manufacturers.=20
=20
Based on my over 20 years experience in packet switching, I am afraid =
that there may be a risk of different interpretation of what "bandwidth" =
means.
=20
Just stating kilobit/sec is not enough, you also have to state what you =
count  and how you enforce, with- our without buffering and how deep the =
buffer is.
=20
In other words, while you delegate the authority for bandwidth control, =
you better also specify the meter used to control the bandwidth, for =
example by specifying the two parameters of the token bucket used, which =
defines the height and refill rate of the token bucket.
=20
I assume there is consensus between the Access Node vendors on what is =
being counted, like the IP packet including the header ??? or PPPoE ???? =
or Ethernet ???? or only the payload ???
=20
The point is, yes, you can do this bandwidth delegation by agreeing on =
the meter. And pragmatically, that is probably a good idea to meet =
delivery deadlines.  But it would be more flexible and extensible if the =
delegation of authority explicitly defines the meter as well, which the =
AN shall use for enforcement.
=20
Best Regards=20
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20
=20
=20
=20
=20
=20
=20
=20



________________________________

	Von: Fortune HUANG [mailto:fqhuang@huawei.com]=20
	Gesendet: Mittwoch, 29. Oktober 2008 05:21
	An: Reith, Lothar; ancp@ietf.org; 'OOGHE Sven'; 'Francois Le Faucheur =
(flefauch)'; Tina TSOU; Tom Taylor; Maglione Roberta; Wojciech Dec =
(wdec); Haag, Thomas; stefaan.de_cnodder@alcatel-lucent.be
	Betreff: =B4=F0=B8=B4: [ANCP] DOA (was: ANCP Framework update)
=09
=09
	Hi Lothar,
	=20
	Thank you very for your comments.
	=20
	I can accept to extend the bandwidth delegation to Delegation of =
Authority conceptually in this draft.=20
	As I said before, I know the latter would be more generic.=20
	=20
	However, since the bandwidth delegation is so important in =
implementation, I strongly suggest we also specify the bandwidth =
delegation as an explicit instance. The first reason is that I believe =
the bandwidth delegation is the most shining point of the Delegation of =
Authority. The second reason is that the bandwidth delegation will have =
actuall impact on the parameters and encoding of the ANCP messages, =
which we do care very much for we have to implement it.
	=20
	=20
	Best Regards,
	Fortune
	=20

	Huawei Technologies Co., Ltd.  =20

=09


	Addr: Section F, Huawei Industrial Base, Bantian Longgang, Shenzhen =
518129, P.R. China
	Tel: +86-755-28971871
	Fax: +86-755-28972352
	Mobile: +8615013838060
	Email: fqhuang@huawei.com
	http://www.huawei.com
	=
-------------------------------------------------------------------------=
------------------------------------------------------------
	=
=B1=BE=D3=CA=BC=FE=BC=B0=C6=E4=B8=BD=BC=FE=BA=AC=D3=D0=BB=AA=CE=AA=B9=AB=CB=
=BE=B5=C4=B1=A3=C3=DC=D0=C5=CF=A2=A3=AC=BD=F6=CF=DE=D3=DA=B7=A2=CB=CD=B8=F8=
=C9=CF=C3=E6=B5=D8=D6=B7=D6=D0=C1=D0=B3=F6=B5=C4=B8=F6=C8=CB=BB=F2=C8=BA=D7=
=E9=A1=A3=BD=FB
	=
=D6=B9=C8=CE=BA=CE=C6=E4=CB=FB=C8=CB=D2=D4=C8=CE=BA=CE=D0=CE=CA=BD=CA=B9=D3=
=C3=A3=A8=B0=FC=C0=A8=B5=AB=B2=BB=CF=DE=D3=DA=C8=AB=B2=BF=BB=F2=B2=BF=B7=D6=
=B5=D8=D0=B9=C2=B6=A1=A2=B8=B4=D6=C6=A1=A2=BB=F2=C9=A2=B7=A2=A3=A9=B1=BE=D3=
=CA=BC=FE=D6=D0
	=
=B5=C4=D0=C5=CF=A2=A1=A3=C8=E7=B9=FB=C4=FA=B4=ED=CA=D5=C1=CB=B1=BE=D3=CA=BC=
=FE=A3=AC=C7=EB=C4=FA=C1=A2=BC=B4=B5=E7=BB=B0=BB=F2=D3=CA=BC=FE=CD=A8=D6=AA=
=B7=A2=BC=FE=C8=CB=B2=A2=C9=BE=B3=FD=B1=BE=D3=CA=BC=FE=A3=A1
	This e-mail and its attachments contain confidential information from =
HUAWEI, which=20
	is intended only for the person or entity whose address is listed =
above. Any use of the=20
	information contained herein in any way (including, but not limited to, =
total or partial=20
	disclosure, reproduction, or dissemination) by persons other than the =
intended=20
	recipient(s) is prohibited. If you receive this e-mail in error, please =
notify the sender by=20
	phone or email immediately and delete it!
=09
	=20

________________________________

	=B7=A2=BC=FE=C8=CB: Reith, Lothar [mailto:Lothar.Reith@detecon.com]=20
	=B7=A2=CB=CD=CA=B1=BC=E4: 2008=C4=EA10=D4=C229=C8=D5 1:09
	=CA=D5=BC=FE=C8=CB: Fortune HUANG; ancp@ietf.org
	=D6=F7=CC=E2: AW: [ANCP] DOA (was: ANCP Framework update)
=09
=09
	Hi Fortune,
	=20
	regarding your statement:
	=20
	The bandwidth can be negotiated dynamically in quantity. When the =
bandwidth on AN is insufficient, AN can ask for more from NAS/PS; when =
the bandwidth is insufficient, NAS/PS can ask for more from AN.
	=20
	I would like to comment as follows:
	=20
	Like in the real world, there is a hierarchy with the root being the =
legal owner of the resource, who is also the owner of the authority to =
control the resource. He delegates this authority  downwards through a =
chain of "Delegation of Authority" actions towards some enforcement =
point - in this case the AN. You may well imagine, that the root =
authority over all resource of a telco is with the shareholder annual =
assembly, which delegates it to the Management board, those to the CTO, =
and further to some line managers who delegate the control to some =
Policy Server, where our scope begins.
	=20
	What you refer to as negotiation, is rather a delegation of authority =
which is quantized with a certain amount of bandwidth. Note that the PS =
may have delegated authority to control the full bandwidth to the NAS, =
but the NAS delegates only part of that bandwidth onwards to the AN.=20
	=20
	 And yes, the AN may ask for that Delegation of Authority specifying =
the amount desired, and the NAS may grant it. However, if the NAS needs =
some of the delegated authority back for his own purposes, he withdraws =
part of the quantized authority by claiming back part of the previously =
delegated authority over access circuit bandwidth.
	=20
	The point is:  There is no real negotiation, because the AN and the =
NAS/PS are not peers.=20
	=20
	The AN has to obey to whatever the NAS grants, and is not allowed to =
exceed the delegated quantity of authority.  Note that the authority =
could be quantized in many ways, e.g. a time limited delegation of =
authority is just one example. Or a volume limited delegation of =
authority. This is still in line with the concept of "delegation of =
authority" in real life, and shows that this extensibility is very =
powerful indeed.=20
	=20
	=20
	Best Regards, Lothar Reith
	Detecon International GmbH (Deutsche Telekom Group)
	=20
	=20
	=20
________________________________

	Von: Fortune HUANG [mailto:fqhuang@huawei.com]
	Gesendet: Di 28.10.2008 15:41
	An: 'OOGHE Sven'; Reith, Lothar; ancp@ietf.org
	Betreff: =B4=F0=B8=B4: [ANCP] DOA (was: ANCP Framework update)
=09
=09

	Hi Sven, Lothar et al,

	=20

	Yes, the =A1=B0Delegation of Authority=A1=B1 is more generic than =
=A1=B0Bandwidth Delegation=A1=B1 and I fully agree with the example from =
Lothar was that not only the bandwidth can be delegated but also the =
content access control can be delegated.

	=20

	However, we have to pay attention to the difference of the delegation =
of bandwidth and the delegation of content access control.

	The bandwidth can be negotiated dynamically in quantity. When the =
bandwidth on AN is insufficient, AN can ask for more from NAS/PS; when =
the bandwidth is insufficient, NAS/PS can ask for more from AN.

	But this negotiation can not be applied for the content access control =
properly.

	=20

	That is to say, if we extend the =A1=B0bandwidth delegation=A1=B1 to =
=A1=B0delegation of authority=A1=B1, the negotiation still needs to be =
specified specially for the bandwidth.

	=20

	Best Regards,

	Fortune

	=20

	=20

	=20

=09
________________________________


	=B7=A2=BC=FE=C8=CB: ancp-bounces@ietf.org =
[mailto:ancp-bounces@ietf.org] =B4=FA=B1=ED OOGHE Sven
	=B7=A2=CB=CD=CA=B1=BC=E4: 2008=C4=EA10=D4=C227=C8=D5 18:49
	=CA=D5=BC=FE=C8=CB: Reith, Lothar; ancp@ietf.org
	=D6=F7=CC=E2: Re: [ANCP] DOA (was: ANCP Framework update)

	=20

	Hi Lothar,

	=20

	I think the term "Delegation of Authority" captures the principle of =
what bandwidth delegation is about. I'm fine either way, and would like =
to ask other people on this list what they think.

	=20

	Regards,

	Sven

	=20

=09
________________________________


	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Reith, Lothar
	Sent: zondag 26 oktober 2008 16:47
	To: ancp@ietf.org
	Subject: [ANCP] DOA (was: ANCP Framework update)

	Dear all,

	=20

	the ANCP Framework contains the word "delegation", which in my mind is =
key to the whole concept of ANCP.=20

	=20

	I would like to suggest that the concept of "delegation" should be made =
more extensible.=20

	=20

	Narrowing it to the term "bandwidth delegation" does not lend itself =
very well to extensibility.

	=20

	I would rather propose to introduce the more general term of DOA =
(Delegation of Authority), which is a well known concept in the real =
world, when a resource owner delegates control over part or all of his =
resources to someone else - e.g. during a vacation absence.

	=20

	Today, ANCP does not just support delegation in the form of bandwidth =
delegation, but also in the form of delegation of content access control =
(delegation occurs for whitelist and blacklist content, but not for the =
greylist content).

	=20

	I think the extensible concept "DOA" is very powerful when harnessed =
for Broadband Access using ANCP.

	=20

	While updating the framework it may be worth a consideration to add =
this hook for extensibility by following means:

	=20

	- replace the term "bandwidth delegation" by "DOA for part of access =
circuit bandwidth"

	=20

	- introduce the first extension of the DOA concept by making clear that =
the concepts of  whitelist and blacklist are DOA for Content Access =
Control.

	=20

	One more point with respect to the recent discussion about renaming the =
Policy Server.

	=20

	I like to state that I am fine with the current name "policy server".  =
Historically, I beleive the name was chosen as a compromise between the =
RADIUS camp and the COPS camp.

	=20

	If - given this background - we still want to change the name of the =
policy server, then perhaps DOA-server may be another alternative to =
consider.=20

	=20

	An important argument in this case would be, that the concept of =
"delegation of authority" is well aligned with the proxy concept, =
similar to a RADIUS Proxy Server, where the delegation of authority =
happens along a delegation chain which may span multiple RADIUS proxy =
servers and multiple domains. This aspect is missing in the other =
proposed names.

	=20

	Best Regards,

	=20

	Lothar Reith

	Detecon International GmbH (Deutsche Telekom Group)

	=20

	=20

=09
________________________________


	Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
	Gesendet: Do 23.10.2008 12:57
	An: ancp@ietf.org
	Betreff: Re: [ANCP] ANCP Framework update

	Hi,

	=20

	Here's the updated text. I removed any notion of "flags" or how the =
Access Node is told whether or not Bandwidth Delegation applies. I also =
covered Thomas' comments. Actually not that much work: the general ANCP =
requirements as well as the NAS requirements were written in a =
high-level way already. I only had to update the general text and some =
of the Access Node requirements. Below the extracted text, let me know =
your comments.

	=20

	Regards,

	Sven

	=20

	---

	=20

	General text

	=20

	   o  One approach is for the AN to query the NAS so that Admission
	      Control for the access line is performed by the NAS (possibly =
with
	      interactions with a Policy Server).  This can be done with or
	      without "bandwidth delegation" to the AN.

	=20

	      *  In case of Admission Control without AN Bandwidth Delegation,
	         the AN can use ANCP to query the NAS, that in turn performs
	         multicast Admission Control check for the new multicast flow
	         and responds to the AN indicating whether the join is to be
	         honored (and hence replication performed by the AN) or denied.
	         The NAS may locally maintain available "video" bandwidth on =
the
	         Access Loop (as a portion of the Access Loop net data rate),
	         and perform video bandwidth accounting for the Access Loop.
	         Upon receiving an Admission Request from the AN, the NAS can
	         check available "video" bandwidth before admitting or denying
	         the multicast flow.  In the process, the NAS may communicate

	         with the Policy Server.  For unicast video services such as
	         Video on Demand (VoD), the NAS may also be queried (by a =
Policy
	         Server or via on-path CAC signaling), so that it can perform
	         admission control for the unicast flow, and update the
	         available video bandwidth maintained by the NAS.

	=20

	      *  In case of Admission Control with AN Bandwidth Delegation, the
	         NAS (possibly with interactions with a Policy Server) manages
	         total bandwidth for video admission, performs unicast =
admission
	         control and uses ANCP to delegate a certain amount of =
bandwidth
	         for some multicast flows to the Access Node.  In this =
scenario,
	         upon receiving a join to a multicast flow which matches an
	         entry in the White or Grey List, the AN must perform the
	         necessary bandwidth admission control check for the new
	         multicast flow, before starting the multicast flow =
replication.

	Access Node requirements

	=20

	   o  The AN must deny any join to a multicast flow matching the Black
	      List for the relevant Access Port.

	=20

	   o  The AN must accept any join to a multicast flow matching the =
White
	      List and for which no Bandwidth Delegation is required.

	=20

	   o  Upon receiving a join to a multicast flow which matches the White
	      List whose and for which Bandwidth Delegation is required, the AN
	      must perform the necessary bandwidth admission control check for
	      the new flow before starting the multicast flow replication.

	=20

	   o  Upon receiving a join to a multicast flow which matches the Grey
	      List and for which no Bandwidth Delegation is required, the AN
	      must support using ANCP to query the NAS to receive a response
	      indicating whether that join is to be honored or denied.  In this
	      case, the NAS will perform both the necessary conditional access
	      and the admission control checks for the new flow.

	=20

	   o  Upon receiving a join to a multicast flow which matches the Grey
	      List and for which Bandwidth Delegation is required, the AN must
	      first perform the necessary bandwidth admission control check for
	      the new flow.  If successful, the AN must support using ANCP to
	      query the NAS to receive a response indicating whether that join
	      is to be honored or denied.

	=20

	   o  In case of Admission Control with AN Bandwidth Delegation, the AN
	      must support using ANCP to notify the NAS when the the user =
leaves
	      the multicast flow.

	=20

	   o  In case of Admission Control with AN Bandwidth Delegation, the AN
	      must support using ANCP to query the NAS to request additional
	      delegated multicast bandwidth on a given Access Port; the AN
	      should be able to specify both the minimum and the preferred
	      amount of additional multicast bandwidth requested.

=09
	   o  In case of Admission Control with AN Bandwidth Delegation, upon
	      receiving a Bandwidth Delegation Request from the NAS querying or
	      instructing to decrease the delegated multicast bandwidth on a
	      given Access Port, the AN must support using ANCP to send a
	      Bandwidth Delegation Response indicating the new delegated
	      multicast bandwidth.

	=20

	   o  In case of Admission Control with AN Bandwidth Delegation, the AN
	      must support using ANCP to send a Bandwidth Release message to =
the
	      NAS in order to release unused delegated multicast bandwidth on a
	      given Access Port.

	=20

	Regards,

	Sven

	=20

=09
________________________________


	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:58
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update

	=20

	On 20 Oct 2008, at 12:22, OOGHE Sven wrote:

=09
=09
=09

	Francois,

	=20

	Another approach we could take is to let the framework requirements be =
agnostic as to how the Access Node knows whether or not Bandwidth =
Delegation applies. We could describe the notion of Bandwidth Delegation =
and the respective requirements for the Access Node and NAS in this =
case.

	=20

	The details of how the use of Bandwidth Delegation is communicated to =
the Access Node - using a flag, some "on/off" knob or both - would be =
left to the actual protocol specification work.

	=20

	Good idea. It will avoid these cross dependencies between framework and =
protocol, which indeed reflect that we are probably trying to be too =
precise/prescriptive in the framework.

=09
=09
=09

	=20

	I think following this path would require relatively small edits to the =
document. I'm ok to take a first shot at it.

	=20

	That would be good.

	=20

	Thanks

	=20

	Francois

=09
=09
=09

	=20

	Regards,

	Sven

	=20

=09
________________________________


	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Framework update

	Sven and all,=20

	=20

		   o  Upon receiving a join to a multicast flow which matches the Grey =

		      List whose entry is flagged as "no Bandwidth Delegation" for the =

		      relevant Access Port, the AN must support using ANCP to query =
the=20
		      NAS to receive a response indicating whether that join is to be=20
		      honored or denied.  In this case, the NAS will perform both the=20
		      necessary conditional access and the admission control checks =
for=20
		      the new flow.

	=20

	Roberta, Tom and myself have started drafting an I-D that will propose =
ANCP protocol extensions supporting some of those requirements (building =
on top of ancp-mc-multicast).

	In doing so, we revisited a point that came up multiple times: do we =
really need to provision a flag in each and every Grey/White List entry =
to activate/deactivate Bandwidth Delegation?

	=20

	The current approach (as correctly reflected in the updated Framework) =
is:

	* define a flag in each Grey/White List entry

	* assume that this flag will normally either always be set in all =
entries or never set.

	* setting/no-setting the flag is all entries effectively acts as the =
knob to enable/disable Bandwidth Delegation, therefore we did not need =
to specify a specific knob to enable/disable Bandwidth Delegation.

	=20

	Another approach would be:

	* remove flag from White/Grey list entries

	* define a specific knob to enable/disable Bandwidth Delegation at the =
AN granularity

	* in fact, define a generic AN-level provisioning method that could be =
used to enable/disable BAndwidth delegation, but could also be used for =
provisioning the "Service Profiles" that are currently assumed to be =
configured in AN, as well as provisioning the Multicast White/Grey/Black =
Profiles

	=20

	Considering that:

	- we got several times the feedback that per-entry BAndwidth Delegation =
flag was confusing since Bandwidth Delegation granularity is more =
AN-level (and may lead to difficulties if it is set on some entries and =
not on others)

	- it is likely that we'll need, anyways, a mechanism to provision =
things at AN level, that could be easily used to convey Bandwidth =
Delegation enable/disable knob.

	we would like to propose to evolve to the newer approach.

	=20

	Thoughts?

	=20

	Francois

	=20

	PS: Sven, if we go for the new approach, we can document in an email =
the deltas that would be needed to reflect that in framework.

	=20

	=20


------_=_NextPart_002_01C93A77.5C366394
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR>
<STYLE>font-face {
	FONT-FAMILY: &#23435; 20307:=20
}
font-face {
	FONT-FAMILY: Tahoma
}
font-face {
	FONT-FAMILY: "@&#23435;&#20307;"
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"
}
SPAN.EmailStyle21 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DZH-CN style=3D"WORD-WRAP: break-word" vLink=3Dblue =
link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thomas, Lothar,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I agree that we should be clear on the =
terminology used.=20
The actual net data rate defines the "bitpipe" that is conveyed from the =
Access=20
Node to the NAS. It enables the NAS to use the bitpipe as it sees fit. =
In an=20
Ethernet network, it would fill the bitpipe with Ethernet frames =
(regardless of=20
higher layer protocols, PPPoE, IPoE, IPv4/IPv6 etc).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In terms of bandwidth delegation, I think we =
are referring=20
to "<STRONG>delegation of authority to perform admission control on a =
subset of=20
the actual net data rate</STRONG>". That's a mouthful but should be the =
most=20
accurate description.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In my understanding, "bandwidth" refers to the =
notion of=20
filling this "bitpipe". So when referring to </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><EM>"The NAS may locally maintain available =
"video"=20
bandwidth&nbsp; on the&nbsp;Access Loop, and perform video bandwidth=20
accounting..."</EM></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D147205709-30102008><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
think this is actually correct. "video bandwidth" refers to a portion of =
the=20
"bitpipe" that is used for video applications. How the NAS converts =
video=20
bitrates into Ethernet frame rates and corresponding "video bandwidth" =
is IMHO=20
beyond the scope of the ANCP framework.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D147205709-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Basically, I would prefer maintaining the =
definitions of=20
net data rate and the existing text on "video bandwidth", clarifying =
that the=20
latter can be a subset of the net data rate.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D147205709-30102008></SPAN><FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>R<SPAN=20
class=3D147205709-30102008>egards,</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=3D147205709-30102008></SPAN><SPAN=20
class=3D147205709-30102008></SPAN><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2>S<SPAN =
class=3D147205709-30102008>ven</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Haag, Thomas =
[mailto:HaagT@telekom.de]=20
<BR><B>Sent:</B> donderdag 30 oktober 2008 9:12<BR><B>To:</B>=20
Lothar.Reith@detecon.com; fqhuang@huawei.com; ancp@ietf.org; OOGHE Sven; =

flefauch@cisco.com; tena@huawei.com; tom.taylor@rogers.com;=20
roberta.maglione@telecomitalia.it; wdec@cisco.com; DE CNODDER=20
Stefaan<BR><B>Subject:</B> AW: [ANCP] DOA (was: ANCP Framework=20
update)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>All,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>from my point of view we should not start a =
discussion=20
about fundamentals which already defined.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The terminology "<SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-size: 10.0pt; mso-fareast-font-family: Times; =
mso-ansi-language: EN-US; mso-fareast-language: EN-US; =
mso-bidi-language: AR-SA"><FONT=20
color=3D#000000>Actual data rate Up- and Downstream</FONT></SPAN>" is =
defined in=20
TR-101 Table 3&nbsp;and WT-147 Table 1. Actual Data Rate refers to ITU-T =
G.997.1=20
section 7.5.2.1 which means net data rate which is a common standardized =

reference. The terminology of bandwidth is not defined which is really a =
risk=20
Lothar already mentioned.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Please see also my comment:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D606024807-30102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>...<EM><FONT color=3D#000000>The NAS may =
locally maintain=20
available "video" bandwidth&nbsp;</FONT><SPAN =
class=3D734534408-22102008><FONT=20
color=3D#0000ff>&nbsp;[T.H.:]&nbsp;</SPAN><SPAN=20
class=3D734534408-22102008>&nbsp;(net data =
rate)&nbsp;</SPAN></EM></FONT><EM><FONT=20
color=3D#000000>on the</FONT></EM><FONT color=3D#000000><FONT =
face=3D"Times New Roman"=20
size=3D3> <BR></FONT><I><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Access Loop, and perform video bandwidth accounting for=20
the</SPAN></FONT></I><FONT face=3D"Times New Roman" size=3D3>=20
</FONT></FONT><BR></FONT></SPAN></DIV>
<DIV><SPAN class=3D606024807-30102008><FONT face=3DArial color=3D#0000ff =
size=3D2>So=20
considering the definition mentioned above reflecting the discussion =
about=20
bandwidth delegation I think this does not match in =
detail.</FONT></SPAN></DIV>
<DIV><SPAN class=3D606024807-30102008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D606024807-30102008><FONT face=3DArial color=3D#0000ff =

size=3D2>Bandwidth delegation is used in a sense of&nbsp;video servcie =
oriented=20
bandwidth. NAS works on layer3 which is different to AN net data rate =
which is=20
reported by ANCP.</FONT></SPAN></DIV>
<DIV><SPAN class=3D606024807-30102008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D606024807-30102008><FONT face=3DArial color=3D#0000ff =
size=3D2>So I=20
think delegation of&nbsp;bandwidth is misleading due to non harmonized=20
definitions.&nbsp;</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#0000ff><SPAN=20
class=3D606024807-30102008>From my point of view t</SPAN><SPAN=20
class=3D606024807-30102008><FONT size=3D+0>he only way out is to refer =
to already=20
standardized defintions having a common agreed=20
reference.</FONT></SPAN></FONT></FONT></FONT></DIV><!-- Converted from =
text/rtf format -->
<P><B><SPAN lang=3Dde><FONT size=3D2><SPAN=20
class=3D606024807-30102008>R</SPAN>egards</FONT></SPAN></B><SPAN =
lang=3Dde></SPAN>=20
<BR><SPAN lang=3Dde><B><FONT size=3D2>Thomas Haag</FONT></B></SPAN> =
<BR><SPAN=20
lang=3Dde><FONT color=3D#808080 size=3D2>Deutsche Telekom =
AG<BR></FONT></SPAN></P><BR>
<DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>Von:</B> Reith, Lothar =
<BR><B>Gesendet:</B>=20
Mittwoch, 29. Oktober 2008 18:50<BR><B>An:</B> Fortune HUANG; =
ancp@ietf.org;=20
OOGHE Sven; Francois Le Faucheur (flefauch); Tina TSOU; Tom Taylor; =
Maglione=20
Roberta; Wojciech Dec (wdec); Haag, Thomas;=20
stefaan.de_cnodder@alcatel-lucent.be<BR><B>Betreff:</B> AW: [ANCP] DOA =
(was:=20
ANCP Framework update)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Hi Fortune,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>I agree, that we have to be pragmatic.=20
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>I recommend to check the meaning of bandwidth =

delegation, in order make the live of operators easier, who deploy ANs =
from=20
multiple manufacturers. </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Based on my over 20 years experience in =
packet=20
switching, I am afraid that there&nbsp;may be&nbsp;a risk of different=20
interpretation of what "bandwidth" means.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Just stating kilobit/sec is not enough, you =
also have=20
to state what you count&nbsp; and how you enforce, with- our without =
buffering=20
and how deep the buffer is.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>In other words, while you delegate the =
authority for=20
bandwidth control, you better also specify the meter used to control the =

bandwidth, for example by specifying the two parameters of the token =
bucket=20
used, which defines the height and refill rate of the token=20
bucket.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>I assume there is consensus between the =
Access Node=20
vendors on what is being counted, like the IP packet including the =
header ??? or=20
PPPoE ???? or Ethernet ???? or only the payload ???</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>The point is, yes, you can do this bandwidth =
delegation=20
by agreeing on the meter. And pragmatically, that is probably a good =
idea to=20
meet delivery deadlines. &nbsp;But it would be more flexible and =
extensible if=20
the delegation of authority explicitly defines the meter as well, which =
the AN=20
shall use for enforcement.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Best Regards </SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Lothar Reith</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008>Detecon International GmbH (Deutsche Telekom=20
Group)</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D406312917-29102008></SPAN></FONT>&nbsp;</DIV><FONT face=3DArial=20
color=3D#0000ff size=3D2></FONT><BR>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>Von:</B> Fortune HUANG =
[mailto:fqhuang@huawei.com]=20
  <BR><B>Gesendet:</B> Mittwoch, 29. Oktober 2008 05:21<BR><B>An:</B> =
Reith,=20
  Lothar; ancp@ietf.org; 'OOGHE Sven'; 'Francois Le Faucheur =
(flefauch)'; Tina=20
  TSOU; Tom Taylor; Maglione Roberta; Wojciech Dec (wdec); Haag, Thomas; =

  stefaan.de_cnodder@alcatel-lucent.be<BR><B>Betreff:</B> =B4=F0=B8=B4: =
[ANCP] DOA (was:=20
  ANCP Framework update)<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Hi Lothar,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Thank you very for your =
comments.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>I can accept to extend the bandwidth =
delegation to=20
  Delegation of Authority conceptually in this draft. =
</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>As I said before, I know the latter would be =
more=20
  generic. </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>However, since&nbsp;the bandwidth delegation =
is so=20
  important in implementation, I strongly suggest we also specify the =
bandwidth=20
  delegation&nbsp;as an explicit instance. The first reason is that I =
believe=20
  the bandwidth delegation is the most shining point&nbsp;of the =
Delegation of=20
  Authority. The second reason is that the bandwidth delegation=20
  </FONT></SPAN><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5 color=3D#0000ff=20
  size=3D2>will have actuall impact on the parameters and encoding of =
the ANCP=20
  messages, which we do care very much for we have to implement=20
  it.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Best Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D351130504-29102008><FONT =
face=3D=CB=CE=CC=E5=20
  color=3D#0000ff size=3D2>Fortune</FONT></SPAN></DIV>
  <DIV><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA size=3D2>&nbsp;</DIV>
  <DIV><BR></FONT><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dgray =
size=3D2>Huawei Technologies Co.,=20
  Ltd. </FONT><IMG id=3DridImg alt=3Dhuawei_logo hspace=3D0=20
  src=3D"cid:147205709@30102008-2E10" align=3Dleft> </DIV>
  <P></P><BR><FONT face=3D=BB=AA=CE=C4=CF=B8=BA=DA color=3Dgray =
size=3D1>Addr: Section F, Huawei=20
  Industrial Base, Bantian Longgang, Shenzhen 518129, P.R. China<BR>Tel: =

  +86-755-28971871<BR>Fax: +86-755-28972352<BR>Mobile: =
+8615013838060<BR>Email:=20
  fqhuang@huawei.com<BR>http://www.huawei.com<BR></FONT><FONT =
face=3D=BB=AA=CE=C4=CF=B8=BA=DA=20
  color=3Dgray=20
  =
size=3D1>----------------------------------------------------------------=
---------------------------------------------------------------------<BR>=
=B1=BE=D3=CA=BC=FE=BC=B0=C6=E4=B8=BD=BC=FE=BA=AC=D3=D0=BB=AA=CE=AA=B9=AB=CB=
=BE=B5=C4=B1=A3=C3=DC=D0=C5=CF=A2=A3=AC=BD=F6=CF=DE=D3=DA=B7=A2=CB=CD=B8=F8=
=C9=CF=C3=E6=B5=D8=D6=B7=D6=D0=C1=D0=B3=F6=B5=C4=B8=F6=C8=CB=BB=F2=C8=BA=D7=
=E9=A1=A3=BD=FB<BR>=D6=B9=C8=CE=BA=CE=C6=E4=CB=FB=C8=CB=D2=D4=C8=CE=BA=CE=
=D0=CE=CA=BD=CA=B9=D3=C3=A3=A8=B0=FC=C0=A8=B5=AB=B2=BB=CF=DE=D3=DA=C8=AB=B2=
=BF=BB=F2=B2=BF=B7=D6=B5=D8=D0=B9=C2=B6=A1=A2=B8=B4=D6=C6=A1=A2=BB=F2=C9=A2=
=B7=A2=A3=A9=B1=BE=D3=CA=BC=FE=D6=D0<BR>=B5=C4=D0=C5=CF=A2=A1=A3=C8=E7=B9=
=FB=C4=FA=B4=ED=CA=D5=C1=CB=B1=BE=D3=CA=BC=FE=A3=AC=C7=EB=C4=FA=C1=A2=BC=B4=
=B5=E7=BB=B0=BB=F2=D3=CA=BC=FE=CD=A8=D6=AA=B7=A2=BC=FE=C8=CB=B2=A2=C9=BE=B3=
=FD=B1=BE=D3=CA=BC=FE=A3=A1<BR></FONT><FONT=20
  face=3DArial color=3Dgray size=3D1>This e-mail and its attachments =
contain=20
  confidential information from HUAWEI, which <BR>is intended only for =
the=20
  person or entity whose address is listed above. Any use of the =
<BR>information=20
  contained herein in any way (including, but not limited to, total or =
partial=20
  <BR>disclosure, reproduction, or dissemination) by persons other than =
the=20
  intended <BR>recipient(s) is prohibited. If you receive this e-mail in =
error,=20
  please notify the sender by <BR>phone or email immediately and delete=20
  it!<BR></FONT>
  <DIV>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Dzh-cn dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3D=CB=CE=CC=E5 size=3D2><B>=B7=A2=BC=FE=C8=CB:</B> Reith, =
Lothar=20
  [mailto:Lothar.Reith@detecon.com] <BR><B>=B7=A2=CB=CD=CA=B1=BC=E4:</B> =
2008=C4=EA10=D4=C229=C8=D5=20
  1:09<BR><B>=CA=D5=BC=FE=C8=CB:</B> Fortune HUANG; =
ancp@ietf.org<BR><B>=D6=F7=CC=E2:</B> AW: [ANCP] DOA=20
  (was: ANCP Framework update)<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV id=3DidOWAReplyText70064 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Hi =
Fortune,</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>regarding your =
statement:</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">The =
bandwidth can be=20
  negotiated dynamically in quantity. When the bandwidth on AN is =
insufficient,=20
  AN can ask for more from NAS/PS; when the bandwidth is insufficient, =
NAS/PS=20
  can ask for more from AN.</SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>I would like to comment as follows:</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>Like in the real world, there is a hierarchy with the root =
being the=20
  legal owner of the resource, who is also the owner of the authority to =

  control&nbsp;the resource. He delegates this authority &nbsp;downwards =
through=20
  a chain of "Delegation of Authority" actions towards some enforcement =
point -=20
  in this case the AN. You may well imagine, that the root authority =
over all=20
  resource of a telco is with the shareholder annual assembly, which =
delegates=20
  it to the Management board, those to the CTO, and further to some line =

  managers who delegate the control to some Policy Server, where our =
scope=20
  begins.</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>What you refer to as negotiation, is rather a delegation of =
authority=20
  which is quantized with a certain amount of bandwidth. Note =
that&nbsp;the PS=20
  may have delegated authority to control&nbsp;the full bandwidth to the =
NAS,=20
  but&nbsp;the NAS delegates only part of that bandwidth onwards to the=20
  AN.&nbsp;</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>&nbsp;And yes, the AN may ask for that Delegation of =
Authority=20
  specifying the amount desired, and the NAS may grant it. However, if =
the NAS=20
  needs some of the delegated authority back for his own purposes, he =
withdraws=20
  part of the quantized authority by claiming back part of the =
previously=20
  delegated authority over access circuit bandwidth.</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>The point is:&nbsp; There is no real negotiation, because the =
AN and=20
  the NAS/PS are not peers. </FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>The AN has to obey to whatever the NAS grants, and is not =
allowed to=20
  exceed the delegated quantity of authority.&nbsp; Note that the =
authority=20
  could be quantized in many ways, e.g. a time limited delegation of =
authority=20
  is just one example. Or a volume limited delegation of authority. This =
is=20
  still in line with the concept of "delegation of authority" in real =
life, and=20
  shows that this extensibility is very powerful indeed. =
</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2>Best Regards, Lothar Reith</FONT></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon=20
  International GmbH (Deutsche Telekom Group)</SPAN></SPAN></DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr>
  <HR tabIndex=3D-1>
  </DIV>
  <DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>Von:</B> Fortune HUANG=20
  [mailto:fqhuang@huawei.com]<BR><B>Gesendet:</B> Di 28.10.2008=20
  15:41<BR><B>An:</B> 'OOGHE Sven'; Reith, Lothar;=20
  ancp@ietf.org<BR><B>Betreff:</B> =B4=F0=B8=B4: [ANCP] DOA (was: ANCP =
Framework=20
  update)<BR></FONT><BR></DIV></DIV>
  <DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DSV=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Hi Sven, =
Lothar et=20
  al,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DSV=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Yes, the =
=A1=B0Delegation=20
  of Authority=A1=B1 is more generic than =A1=B0Bandwidth =
Delegation=A1=B1 and I fully agree=20
  with the example from Lothar was that not only the bandwidth can be =
delegated=20
  but also the content access control can be =
delegated.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">However, we =
have to=20
  pay attention to the difference of the delegation of bandwidth and the =

  delegation of content access control.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">The =
bandwidth can be=20
  negotiated dynamically in quantity. When the bandwidth on AN is =
insufficient,=20
  AN can ask for more from NAS/PS; when the bandwidth is insufficient, =
NAS/PS=20
  can ask for more from AN.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">But this =
negotiation=20
  can not be applied for the content access control =
properly.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">That is to =
say, if we=20
  extend the =A1=B0bandwidth delegation=A1=B1 to =A1=B0delegation of =
authority=A1=B1, the=20
  negotiation still needs to be specified specially for the=20
  bandwidth.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Best=20
  Regards,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial">Fortune</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US =
style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=B7=A2=BC=FE=C8=CB<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> =
ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] </SPAN></FONT><B><FONT =
face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=B4=FA=B1=ED=20
  </SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5">OOGHE =
Sven<BR></SPAN></FONT><B><FONT=20
  face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=B7=A2=CB=CD=CA=B1=BC=E4<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> 2008<SPAN =
lang=3DEN-US><SPAN=20
  lang=3DEN-US>=C4=EA10</SPAN></SPAN><SPAN lang=3DEN-US><SPAN=20
  lang=3DEN-US>=D4=C227</SPAN></SPAN><SPAN lang=3DEN-US><SPAN =
lang=3DEN-US>=C8=D5</SPAN></SPAN>=20
  18:49<BR></SPAN></FONT><B><FONT face=3D=CB=CE=CC=E5 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=CA=D5=BC=FE=C8=CB<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> Reith, Lothar;=20
  ancp@ietf.org<BR></SPAN></FONT><B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
=CB=CE=CC=E5">=D6=F7=CC=E2<SPAN=20
  lang=3DEN-US>:</SPAN></SPAN></FONT></B><FONT face=3D=CB=CE=CC=E5 =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =CB=CE=CC=E5"> Re: [ANCP] DOA =
(was: ANCP Framework=20
  update)</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi=20
  Lothar,</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think the =
term=20
  "Delegation of Authority" captures the principle of what bandwidth =
delegation=20
  is about. I'm fine either way, and would like to ask other people on =
this list=20
  what they think.</SPAN></FONT><SPAN lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN=20
  lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><SPAN=20
  lang=3DEN-US></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US =
style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B><SPAN style=3D"FONT-WEIGHT: bold">On =
Behalf Of=20
  </SPAN></B>Reith, Lothar<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> zondag 26 oktober 2008=20
  16:47<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
  ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> [ANCP]=20
  DOA (was: ANCP Framework update)</SPAN></FONT><SPAN =
lang=3DEN-US></SPAN></P>
  <DIV id=3DidOWAReplyText66978>
  <DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Dear=20
  all,</SPAN></FONT></P></DIV>
  <DIV>
  <DIV id=3DidOWAReplyText68228>
  <DIV id=3DidOWAReplyText93369>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">the ANCP =
Framework=20
  contains the word "delegation", which in my mind is key to the whole =
concept=20
  of ANCP. </SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I would =
like to=20
  suggest that the concept of "delegation" should be made more =
extensible.=20
  </SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Narrowing =
it to the=20
  term "bandwidth delegation" does not lend itself very well to=20
  extensibility.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I would =
rather=20
  propose to introduce the more general term of DOA (Delegation of =
Authority),=20
  which is a well known concept in the real world, when a resource owner =

  delegates control over part or all of his resources to someone else - =
e.g.=20
  during a vacation absence.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Today, =
ANCP does not=20
  just support delegation in the form of bandwidth delegation, but also =
in the=20
  form of delegation of content access control (delegation occurs for =
whitelist=20
  and blacklist content, but not for the greylist=20
  content).</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I think =
the=20
  extensible concept "DOA"&nbsp;is very powerful when harnessed for =
Broadband=20
  Access using ANCP.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">While =
updating the=20
  framework it may be worth a consideration to add this hook for =
extensibility=20
  by following means:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- =
replace&nbsp;the=20
  term "bandwidth delegation" by "DOA for part of access circuit=20
  bandwidth"</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- =
introduce the=20
  first extension of the DOA concept by making clear that the concepts =
of=20
  &nbsp;whitelist and blacklist are DOA for Content Access=20
  Control.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">One more =
point with=20
  respect to the recent discussion about renaming the Policy=20
  Server.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I like to =
state that=20
  I am fine with the current name "policy=20
  server".&nbsp;&nbsp;Historically,&nbsp;I beleive&nbsp;the name was =
chosen as a=20
  compromise between the RADIUS camp and the COPS =
camp.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">If - given =
this=20
  background - we&nbsp;still want to change the name of the policy =
server, then=20
  perhaps DOA-server may be another alternative to consider.=20
  </SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">An =
important=20
  argument in this case would be, that the concept of "delegation of =
authority"=20
  is well aligned with the proxy concept, similar to a RADIUS Proxy =
Server,=20
  where the delegation of authority happens along a delegation chain =
which may=20
  span multiple RADIUS proxy servers and multiple domains. This aspect =
is=20
  missing in the other proposed names.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Best=20
  Regards,</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Lothar=20
  Reith</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Detecon=20
  International GmbH (Deutsche Telekom Group)</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Tahoma">Von:</SPAN></FONT></B><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma">=20
  ancp-bounces@ietf.org im Auftrag von OOGHE Sven<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B> Do 23.10.2008 =
12:57<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">An:</SPAN></B> ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B> Re: [ANCP] ANCP =
Framework=20
  update</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Here's the =
updated=20
  text. I removed any notion of "flags" or how the Access Node is told =
whether=20
  or not Bandwidth Delegation applies. I also covered Thomas' comments. =
Actually=20
  not that much work: the general ANCP requirements as well as the NAS=20
  requirements were written in a high-level way&nbsp;already. I only had =
to=20
  update the general text and some of the Access Node requirements. =
Below the=20
  extracted text, let me know your comments.</SPAN></FONT><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">---</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><STRONG><B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">General=20
  text</SPAN></FONT></B></STRONG><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  One approach is for the AN to query the NAS so that=20
  Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the access =
line is=20
  performed by the NAS (possibly with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  interactions with a Policy Server).&nbsp; This can be done with=20
  or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth delegation" to =
the=20
  AN.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  *&nbsp; In case of Admission Control without AN Bandwidth=20
  Delegation,</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the AN can use ANCP to query the NAS, that in turn=20
  performs</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast Admission Control check for the new multicast=20
  flow</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  and responds to the AN indicating whether the join is to=20
  be</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  honored (and hence replication performed by the AN) or=20
  denied.</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The NAS may locally maintain available "video" bandwidth on=20
  the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Access Loop (as a portion of the Access Loop net data=20
  rate),</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  and perform video bandwidth accounting for the Access=20
  Loop.</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Upon receiving an Admission Request from the AN, the NAS=20
  can</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  check available "video" bandwidth before admitting or=20
  denying</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the multicast flow.&nbsp; In the process, the NAS may=20
  communicate</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =

  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  with the Policy Server.&nbsp; For unicast video services such=20
  as</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Video on Demand (VoD), the NAS may also be queried (by a=20
  Policy</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Server or via on-path CAC signaling), so that it can=20
  perform</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  admission control for the unicast flow, and update=20
  the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  available video bandwidth maintained by the=20
  NAS.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  *&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  the</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  NAS (possibly with interactions with a Policy Server)=20
  manages</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  total bandwidth for video admission, performs unicast=20
  admission</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  control and uses ANCP to delegate a certain amount of=20
  bandwidth</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  for some multicast flows to the Access Node.&nbsp; In this=20
  scenario,</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  upon receiving a join to a multicast flow which matches=20
  an</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  entry in the White or Grey List, the AN must perform=20
  the</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  necessary bandwidth admission control check for the=20
  new</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast flow, before starting the multicast flow=20
  replication.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><STRONG><B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Access=20
  Node requirements</SPAN></FONT></B></STRONG><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  The AN must deny any join to a multicast flow matching the=20
  Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List for the relevant Access=20
  Port.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  The AN must accept any join to a multicast flow matching the=20
  White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which no =
Bandwidth=20
  Delegation is required.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  Upon receiving a join to a multicast flow which matches the=20
  White</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List whose and for which Bandwidth Delegation is required, the=20
  AN</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
perform the=20
  necessary bandwidth admission control check=20
  for</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow before=20
  starting the multicast flow=20
  replication.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  Upon receiving a join to a multicast flow which matches the=20
  Grey</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List and for which no Bandwidth Delegation is required, the=20
  AN</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must =
support using=20
  ANCP to query the NAS to receive a=20
  response</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating =
whether=20
  that join is to be honored or denied.&nbsp; In=20
  this</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case, the =
NAS will=20
  perform both the necessary conditional=20
  access</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the =
admission=20
  control checks for the new =
flow.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  Upon receiving a join to a multicast flow which matches the=20
  Grey</SPAN></FONT></I></EM><I><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-STYLE: italic; =
FONT-FAMILY: Arial"><BR><EM><I><FONT=20
  face=3DArial><SPAN style=3D"FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  List and for which Bandwidth Delegation is required, the AN=20
  must</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; first =
perform the=20
  necessary bandwidth admission control check=20
  for</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new =
flow.&nbsp;=20
  If successful, the AN must support using ANCP=20
  to</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the =
NAS to=20
  receive a response indicating whether that=20
  join</SPAN></FONT></I></EM><BR><EM><I><FONT face=3DArial><SPAN=20
  style=3D"FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be =
honored or=20
  denied.</SPAN></FONT></I></EM></SPAN></FONT></I><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  In case of Admission Control with AN Bandwidth Delegation, the=20
  AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to notify =
the NAS=20
  when the the user leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast=20
  flow.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  In case of Admission Control with AN Bandwidth Delegation, the=20
  AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to query =
the NAS=20
  to request additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delegated =
multicast=20
  bandwidth on a given Access Port; the =
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  should be able to specify both the minimum and the=20
  preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount of additional =
multicast=20
  bandwidth requested.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><BR>&nbsp;&nbsp;=20
  o&nbsp; In case of Admission Control with AN Bandwidth Delegation,=20
  upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth =
Delegation=20
  Request from the NAS querying or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
instructing=20
  to decrease the delegated multicast bandwidth on=20
  a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support=20
  using ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth =
Delegation=20
  Response indicating the new =
delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  multicast bandwidth.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;&nbsp; o&nbsp;=20
  In case of Admission Control with AN Bandwidth Delegation, the=20
  AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to send a =

  Bandwidth Release message to the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS =
in=20
  order to release unused delegated multicast bandwidth on=20
  a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access =
Port.</SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> Francois =
Le=20
  Faucheur IMAP [mailto:flefauch@cisco.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 20 oktober 2008=20
  12:58<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> OOGHE=20
  Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Francois =
Le Faucheur=20
  IMAP; ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
  Re: [ANCP] ANCP Framework update</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">On 20 Oct =
2008, at=20
  12:22, OOGHE Sven wrote:</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>
  <DIV style=3D"WORD-WRAP: break-word">
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Francois,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Another =
approach we=20
  could take is to let the framework requirements be agnostic as to how =
the=20
  Access Node knows whether or not Bandwidth Delegation applies. We =
could=20
  describe the notion of Bandwidth Delegation and the respective =
requirements=20
  for the Access Node and NAS in this case.</SPAN></FONT><FONT =
face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The details =
of how=20
  the use of Bandwidth Delegation is communicated to the Access Node - =
using a=20
  flag, some "on/off" knob or both - would be left to the actual =
protocol=20
  specification work.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Good idea. =
It will=20
  avoid these cross dependencies between framework and protocol, which =
indeed=20
  reflect that we are probably trying to be too precise/prescriptive=20
  in&nbsp;the&nbsp;framework.</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>
  <DIV style=3D"WORD-WRAP: break-word">
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think =
following=20
  this path would require relatively small edits to the document. I'm ok =
to take=20
  a first shot at it.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
  lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">That would =
be=20
  good.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Thanks</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Francois</SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><BR><BR></SPAN></FONT></P>
  <DIV style=3D"WORD-WRAP: break-word">
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sven</SPAN></FONT><FONT=20
  face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT face=3DArial=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma color=3Dblack size=3D2><SPAN lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Tahoma"> Francois =
Le=20
  Faucheur IMAP [<A=20
  href=3D"mailto:flefauch@cisco.com">mailto:flefauch@cisco.com</A>] =
<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 20 oktober 2008=20
  12:01<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> OOGHE=20
  Sven<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Francois =
Le Faucheur=20
  IMAP; <A href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A><BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] ANCP =
Framework=20
  update</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Sven and =
all,=20
  </SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <DIV>
  <BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt" =
type=3D"cite">
    <DIV>
    <P><I><FONT face=3DArial color=3Dblack size=3D2><SPAN lang=3DEN-US=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-STYLE: italic; =
FONT-FAMILY: Arial">&nbsp;&nbsp;=20
    o&nbsp; Upon receiving a join to a multicast flow which matches the=20
    Grey</SPAN></FONT></I><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DEN-US=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List =
whose entry=20
    is flagged as "no Bandwidth Delegation" for the</SPAN></I> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant =
Access=20
    Port, the AN must support using ANCP to query the</SPAN></I> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to =
receive a=20
    response indicating whether that join is to be</SPAN></I> =
<BR><I><SPAN=20
    style=3D"FONT-STYLE: italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored =
or=20
    denied.&nbsp; In this case, the NAS will perform both the</SPAN></I> =

    <BR><I><SPAN style=3D"FONT-STYLE: =
italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    necessary conditional access and the admission control checks =
for</SPAN></I>=20
    <BR><I><SPAN style=3D"FONT-STYLE: =
italic">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
    new flow.</SPAN></I></SPAN></FONT></P></DIV></BLOCKQUOTE>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Roberta, =
Tom and=20
  myself have started drafting an I-D that will propose ANCP protocol =
extensions=20
  supporting some of those requirements (building on top of=20
  ancp-mc-multicast).</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">In doing =
so, we=20
  revisited a point that came up multiple times: do we really need to =
provision=20
  a flag in each and every Grey/White List entry=20
  to&nbsp;activate/deactivate&nbsp;Bandwidth =
Delegation?</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">The =
current approach=20
  (as correctly reflected in the updated Framework) =
is:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* define a =
flag in=20
  each Grey/White List entry</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* assume =
that this=20
  flag will normally either always be set in all entries or never=20
  set.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* =
setting/no-setting=20
  the flag is all entries effectively acts as the knob to enable/disable =

  Bandwidth Delegation, therefore we did not need to specify a specific =
knob to=20
  enable/disable Bandwidth Delegation.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Another =
approach=20
  would be:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* remove =
flag from=20
  White/Grey list entries</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* define a =
specific=20
  knob to enable/disable Bandwidth Delegation at the AN=20
  granularity</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">* in fact, =
define a=20
  generic&nbsp;AN-level provisioning method that could be used to =
enable/disable=20
  BAndwidth delegation, but&nbsp;could&nbsp;also be used for =
provisioning the=20
  "Service Profiles" that are currently assumed to be configured in AN, =
as well=20
  as provisioning the Multicast White/Grey/Black=20
Profiles</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Considering=20
  that:</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- we got =
several=20
  times the feedback that per-entry BAndwidth Delegation flag was =
confusing=20
  since&nbsp;Bandwidth Delegation granularity is more AN-level (and may =
lead to=20
  difficulties if it is set on some entries and not on=20
  others)</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">- it is =
likely that=20
  we'll need, anyways, a mechanism to provision things at AN level, that =
could=20
  be easily used to convey Bandwidth Delegation enable/disable=20
  knob.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">we&nbsp;would&nbsp;like=20
  to propose to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer=20
  approach.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Thoughts?</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Francois</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">PS: Sven, =
if we go=20
  for&nbsp;the&nbsp;new approach, we can document in an email the deltas =

  that&nbsp;would&nbsp;be needed to reflect that in=20
  framework.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DEN-US=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></DIV></DIV></DIV>=
</BLOCKQUOTE></BODY></HTML>

------_=_NextPart_002_01C93A77.5C366394--

------_=_NextPart_001_01C93A77.5C366394
Content-Type: image/jpeg;
	name="att12f37.jpg"
Content-Transfer-Encoding: base64
Content-ID: <147205709@30102008-2E10>
Content-Description: att12f37.jpg
Content-Location: att12f37.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/7QxmUGhvdG9zaG9wIDMuMAA4QklNBCUAAAAAABAAAAAAAAAA
AAAAAAAAAAAAOEJJTQPtAAAAAAAQAEgAAAABAAIASAAAAAEAAjhCSU0EJgAAAAAADgAAAAAAAAAA
AAA/gAAAOEJJTQQNAAAAAAAEAAAAHjhCSU0EGQAAAAAABAAAAB44QklNA/MAAAAAAAkAAAAAAAAA
AAEAOEJJTQQKAAAAAAABAAA4QklNJxAAAAAAAAoAAQAAAAAAAAACOEJJTQP1AAAAAABIAC9mZgAB
AGxmZgAGAAAAAAABAC9mZgABAKGZmgAGAAAAAAABADIAAAABAFoAAAAGAAAAAAABADUAAAABAC0A
AAAGAAAAAAABOEJJTQP4AAAAAABwAAD/////////////////////////////A+gAAAAA////////
/////////////////////wPoAAAAAP////////////////////////////8D6AAAAAD/////////
////////////////////A+gAADhCSU0EAAAAAAAAAgAAOEJJTQQCAAAAAAACAAA4QklNBDAAAAAA
AAEBADhCSU0ELQAAAAAABgABAAAABjhCSU0ECAAAAAAAEAAAAAEAAAJAAAACQAAAAAA4QklNBB4A
AAAAAAQAAAAAOEJJTQQaAAAAAAM9AAAABgAAAAAAAAAAAAAAIAAAAGYAAAAEAGwAbwBnAG8AAAAB
AAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAGYAAAAgAAAAAAAAAAAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAAAAAAAAAEAAAAAEAAAAAAABudWxsAAAAAgAAAAZib3VuZHNPYmpjAAAAAQAAAAAA
AFJjdDEAAAAEAAAAAFRvcCBsb25nAAAAAAAAAABMZWZ0bG9uZwAAAAAAAAAAQnRvbWxvbmcAAAAg
AAAAAFJnaHRsb25nAAAAZgAAAAZzbGljZXNWbExzAAAAAU9iamMAAAABAAAAAAAFc2xpY2UAAAAS
AAAAB3NsaWNlSURsb25nAAAAAAAAAAdncm91cElEbG9uZwAAAAAAAAAGb3JpZ2luZW51bQAAAAxF
U2xpY2VPcmlnaW4AAAANYXV0b0dlbmVyYXRlZAAAAABUeXBlZW51bQAAAApFU2xpY2VUeXBlAAAA
AEltZyAAAAAGYm91bmRzT2JqYwAAAAEAAAAAAABSY3QxAAAABAAAAABUb3AgbG9uZwAAAAAAAAAA
TGVmdGxvbmcAAAAAAAAAAEJ0b21sb25nAAAAIAAAAABSZ2h0bG9uZwAAAGYAAAADdXJsVEVYVAAA
AAEAAAAAAABudWxsVEVYVAAAAAEAAAAAAABNc2dlVEVYVAAAAAEAAAAAAAZhbHRUYWdURVhUAAAA
AQAAAAAADmNlbGxUZXh0SXNIVE1MYm9vbAEAAAAIY2VsbFRleHRURVhUAAAAAQAAAAAACWhvcnpB
bGlnbmVudW0AAAAPRVNsaWNlSG9yekFsaWduAAAAB2RlZmF1bHQAAAAJdmVydEFsaWduZW51bQAA
AA9FU2xpY2VWZXJ0QWxpZ24AAAAHZGVmYXVsdAAAAAtiZ0NvbG9yVHlwZWVudW0AAAARRVNsaWNl
QkdDb2xvclR5cGUAAAAATm9uZQAAAAl0b3BPdXRzZXRsb25nAAAAAAAAAApsZWZ0T3V0c2V0bG9u
ZwAAAAAAAAAMYm90dG9tT3V0c2V0bG9uZwAAAAAAAAALcmlnaHRPdXRzZXRsb25nAAAAAAA4QklN
BCgAAAAAAAwAAAABP/AAAAAAAAA4QklNBBEAAAAAAAEBADhCSU0EFAAAAAAABAAAAAg4QklNBAwA
AAAABnAAAAABAAAAZgAAACAAAAE0AAAmgAAABlQAGAAB/9j/4AAQSkZJRgABAgAASABIAAD/7QAM
QWRvYmVfQ00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUT
ExgRDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4O
Dg4UEQwMDAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMB
IgACEQEDEQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEB
AAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSR
obFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSF
tJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIR
AyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVV
NnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEA
AhEDEQA/APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC6
6f56f3t30Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUs
VaDHl/dl/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5Vtns
U/qp1vqPUvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9
w9+kqfV+qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVh
fWLCzerW9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX
146P1azqFWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKeh
SWDk/XHpVHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8t
bvSU9Ikucy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uo
JBeNpMtfRc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxb
qtG20uI0PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv
/QXjOu9COI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5F
ztrrn/usXoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4
HX+6yY/jQHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v
6hNyW9Q6jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m
+u1tQc9n0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6
tfRj2YnTgMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJ
JT5b0bpfUrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6r
WuLnfpNjXu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z
OEJJTQQhAAAAAABVAAAAAQEAAAAPAEEAZABvAGIAZQAgAFAAaABvAHQAbwBzAGgAbwBwAAAAEwBB
AGQAbwBiAGUAIABQAGgAbwB0AG8AcwBoAG8AcAAgAEMAUwAyAAAAAQA4QklNBAYAAAAAAAcABQAA
AAEBAP/hB4ZFeGlmAABJSSoACAAAAAcAEgEDAAEAAAABAAAAGgEFAAEAAABiAAAAGwEFAAEAAABq
AAAAKAEDAAEAAAACAAAAMQECABwAAAByAAAAMgECABQAAACOAAAAaYcEAAEAAACiAAAAzAAAAID8
CgAQJwAAgPwKABAnAABBZG9iZSBQaG90b3Nob3AgQ1MyIFdpbmRvd3MAMjAwNzowMjoyNiAxNjox
ODo1MwADAAGgAwABAAAA/////wKgBAABAAAAZgAAAAOgBAABAAAAIAAAAAAAAAAGAAMBAwABAAAA
BgAAABoBBQABAAAAGgEAABsBBQABAAAAIgEAACgBAwABAAAAAgAAAAECBAABAAAAKgEAAAICBAAB
AAAAVAYAAAAAAABIAAAAAQAAAEgAAAABAAAA/9j/4AAQSkZJRgABAgAASABIAAD/7QAMQWRvYmVf
Q00AAv/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwM
DAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwM
DAwMEREMDAwMDAwRDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIACAAZgMBIgACEQED
EQH/3QAEAAf/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAA
AAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQV
UsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0
pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRB
UWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKz
hMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/
APVJAIBOp4C5ofXOq3rw6ZTTNDbPSsvcdd3HsZ+7uWF9durdTwPrLjX1OLasdjX4/wC66f56f3t3
0Fk3WMr69Rn4v9Gz7WX1/wAklw9ao/yqrPaqmXmCDwx04ZDi8Yu/yPweEsQy5an7+GUsVaDHl/dl
/X4P/Uj6R+1g3LdS9o9IP2B4Os+bVoSJidR2Xn1fVmP6rk2XOjHxbH3XnyafZWP5VtnsU/qp1vqP
UvrTbfJNF1bje381rW/zP9Xb9FHHzB4uGWvFKo+TBm+DzGOeQVAYcQyTvaUukP7/AA/9w9+kqfV+
qUdI6ZkdSyA51OKz1HhmriP5KqZ/1mwcH6vD6wWssdiurZaGNA3xZG32z/KVpx3XSWVhfWLCzerW
9Jqa8X049eS5zh7dloBYB/K9yfp/1gw8/qXUem1Ne23pbmtvc4ANO8bhsPySU6iS53pX146P1azq
FWE2x9nTmueWkAG1jS5pfj6+9u5qd/136Oz6sD6zHf8AYyQ30wB6m8u9L0ts7dzXJKehSWDk/XHp
VHQMbr0WWY2Y5jKK2AGwvsO0V7Z+k3a5Bzfrz0/HzrOn4uLldRyscD7SzFr3isn8yx8tbvSU9Iku
cy/rrj4tOC6zp+Z9o6iLTThisesPRG9+6vd+4NySSn//0GzsL6w9JyLemZmLZ1Lpm8uoJBeNpMtf
Rc2X0W/vq90PoZzHCineK2WNyGMvaWWUvaRua7822m5ns31/nrr/AKw/VjF661hsuuxbqtG20uI0
PLHs+i5WOj9Cwej0+njBz3uH6S6xxc939Zx/76q/3f13+i7I+MEctwjTMf3R6OL/ADkv/QXjOu9C
OI99Vm/0r7XZFgoaX2Wkk+nUxv8Ag6qG/n2f4RUsDA671G1nTsLFs6f08vBuMFsgfn5Fztrrn/us
XoXVejYPVqfSymuDm/QtrJa9v9V7VW6D9W8bovqPZfbk3WaGy50w391jPotTTy3r00h4HX+6yY/j
QHLVL1Z4/KJx4sfF/nB6vmj/AF/8Br/Ximx31N6nTU11j/s+1rWglxgt/NauN659Vc6v6hNyW9Q6
jkWGik/s97t1YJ2zX6AZv21r1JJWnCfP68x31e+tbuqdRxr/ALBndOx6q8iqt1obZW1m+u1tQc9n
0VmOzOrNr+sXU+n4mRW/6xZFWL0zfW5ryCHMtyHsjdVW1n5716mkkp8ts6R9aPqvk9I6tfRj2YnT
gMK9mEHusfRYfe+9jh79rzv9qjV0jOH1mr+q32Z7+inqH7VbaWn0/SNZt+znTb/OL1RJJT5b0bpf
UrPrNjfVrIx3jpnRc2/PZc4HY9p9+JU130PY96AMDI6J1zqzOqZHVsJmXkG/HyOnNL6rWuLnfpNj
Xu9Rm5espJKfMuturf8A828tmR1N2JW3M9TPDHHMbLHsbu9m5u5/6P8A4tJempJKf//Z/9sAQwAI
BgYHBgUIBwcHCQkICgwUDQwLCwwZEhMPFB0aHx4dGhwcICQuJyAiLCMcHCg3KSwwMTQ0NB8nOT04
MjwuMzQy/9sAQwEJCQkMCwwYDQ0YMiEcITIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIy/8AAEQgAIABmAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAA
AAABAgMEBQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGh
CCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV
1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkK
C//EALURAAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy
0QoWJDThJfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKD
hIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm
5+jp6vLz9PX29/j5+v/aAAwDAQACEQMRAD8A99LKCASAT0FcOvxDin8XjRre2Bt1l8mS4Zud3Tge
ma5X4j67qukeObG5hdkhto1e3H8L5+9n1z0rnriVIvF9pqdmP9E1CdLiPn7pLDcp9wcj8q8+vimn
yx0sz6zLsihOj7WtrzxbXk/87a/f2PazrqpqL27oBEsnlhwec+4rYyCSM8jtXj0OupJ4hvZbhytr
aSvNOfYHhfqTgVJ4G8R6nrfxAuLklzbTRMZlz8qKPu/THSnSxT5rS1u9Dlr5HNU5VVooxu/8vX/g
dz1+iszX9at/Dug3mr3Su9vax+Y4jGWI9qz9U8ZafpXgtfFE0U7WTQpKEVRvw2McZ967z506Oiuf
03xbY6n4juNDhjmFzBaR3bMw+Xa4BA+vIp2leKrHV9d1nSIElSfSXVJ2cAKdwyMH8KAN6iuM0P4l
6J4hn1eDTkuJJdNRpCpUAzICQWTnkZFK/wASdEj8Ar4wInNiSF8sKPMD7tu3GcZBoA7KiuSu/iDo
9p4NsvE22eW0vWRII41BkZ2OAuM9Rg/lVbUviXptnq82lWem6pql7bgfaUsbfzBCT2Y5xn2oA7ai
uB134q6V4b0nTb7VdM1K3N/v2W7xASJtOPmGeOtFAHnupab4l8P3s+kX+nT6ro/mFoCVLgAngo45
RvUfpWr4a8NnUmFrB5qwxyrcol0hSS3YEZB7MrDjI74r0TxX4MtPFSRNLd3VpcRcLNbyEHHcEdDV
zQPDGn+G7XyrNZHdv9ZPM5d3+p/oK4/q153ex9Is9ccNyrSfktL93/wN+uh5n4m8NNp8ssEvm+Rc
TtcyC2QvJOSTtUDsqjue5NZumaX4h1meLStP06fTNLLgzHaV3Ad3c8sfbp7V7Frnh6w8QWohvEcM
v3JYmKun0P8AjVHwx4PtfDJleO7urueQYMk75wvoB0FTLC+/psa0s/UcLaWtRbXWl++/57dNCp8S
reR/hjrlvBG8shtNqqilmbkdhXmniXwPqEPweS7XW/EFzKbWE/2dI+6MHjK7MZwP6V73RXcfLHj8
V+3g34ivrOq2F9/ZmoaPbwx3MFu0oWRAMqwUZB4rDe/1hIPGWsaXpl/HJ4lu4rPTPMhZXIwQ0hGM
qAO59a98ooA8Fl0Dxb4DvvDmuXNnp8tlpiiwnTTUdpJIHPJcEc4Jzx3pkOgagvj2HwV9gmfw+dY/
thZmQ+X5XllvLPGOuePWvfaKAPBfD2iapL48svB91ZTLpGhalPqKTsp2SKeY1B6cE5/Oqg0u58Le
LfEMes33imwjvLs3FvcaOheKdSSfmwCcjOK+haKAPm34sWlxqvhPwrJpi6zqcY8/M13CxnPzD74x
ke3tRX0lRQB//9k=

------_=_NextPart_001_01C93A77.5C366394--

--===============1812714312==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1812714312==--


From ancp-bounces@ietf.org  Thu Oct 30 08:06:38 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 788073A696A;
	Thu, 30 Oct 2008 08:06:38 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C87103A696A
	for <ancp@core3.amsl.com>; Thu, 30 Oct 2008 08:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433, 
	BAYES_00=-2.599]
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 DmA44Zqy6dUC for <ancp@core3.amsl.com>;
	Thu, 30 Oct 2008 08:06:33 -0700 (PDT)
Received: from smtp125.rog.mail.re2.yahoo.com (smtp125.rog.mail.re2.yahoo.com
	[206.190.53.30]) by core3.amsl.com (Postfix) with SMTP id 0C59D3A691D
	for <ancp@ietf.org>; Thu, 30 Oct 2008 08:06:32 -0700 (PDT)
Received: (qmail 22503 invoked from network); 30 Oct 2008 15:06:31 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com;
	h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
	b=MgrPjFFINBsfVxYKv7IoPJy/gKsAIvkt/1KeOJkx37DlzKVbntAtWgaw8bV/fkDiXB+OzZoZbmfrkdNPB4pXa/HytNSgImHMKoWl1UOeVc+kMgecWayxw1k40yQ7ItjDVdD+oUUv8wUiy005cQst37xet/lVrvsyzSF6DAlpEcE=
	; 
Received: from unknown (HELO ?192.168.0.100?) (tom.taylor@72.140.46.24 with
	plain)
	by smtp125.rog.mail.re2.yahoo.com with SMTP; 30 Oct 2008 15:06:31 -0000
X-YMail-OSG: oFtixHUVM1nfKslQ2mNJezCHMcK2jLdBDJZ30tOyoC7rTxs.dW7TJRn_tKWWWIPi4A--
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4909CD76.2030100@rogers.com>
Date: Thu, 30 Oct 2008 11:06:30 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: ancp@ietf.org
Subject: [ANCP] Address family for white/grey/black lists
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

One of the issues that came up when defining provisioning messages for the 
white/grey/black lists was whether IPv4 and IPv6 would both be present in the 
same profile. I believe, if they are both present, that this implies that the 
user device or home gateway is dual stack. I'm sure someone will correct me if 
this is an invalid assumption.

In any event, the current design of the multicast service provisioning message 
allows mixed address families in the same list, but assumes that in the case of 
source-specific multicast the source address is of the same family as the 
multicast group.

If all addresses in the same profile can be assumed to belong to the same 
family, we could save an octet per list entry and just have one common value as 
a sub-attribute.

On the other hand, if the source and group addresses can belong to different 
address families in the SSM case, the current structure has to change.

Comments on the true requirements are invited.

Tom Taylor
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Thu Oct 30 15:14:56 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEE123A6A24;
	Thu, 30 Oct 2008 15:14:56 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FCA23A6A24
	for <ancp@core3.amsl.com>; Thu, 30 Oct 2008 15:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 CJwooxVG6JeD for <ancp@core3.amsl.com>;
	Thu, 30 Oct 2008 15:14:53 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	by core3.amsl.com (Postfix) with ESMTP id BA4AB3A67A4
	for <ancp@ietf.org>; Thu, 30 Oct 2008 15:14:52 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m9UMGTEs031072;
	Thu, 30 Oct 2008 17:16:29 -0500
Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 17:14:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 18:14:47 -0400
Message-ID: <35815C929B41D2479A224FE098A27227066892BB@ecamlmw720.eamcs.ericsson.se>
In-Reply-To: <D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA (was: ANCP Framework update)
Thread-Index: Ackyos176Ghs4uw5RrWfzFn5s+o2MQCWjYGQAJ4XScgA2ImP0A==
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com>
	<D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>
From: "Alan Kavanagh" <alan.kavanagh@ericsson.com>
To: "Reith, Lothar" <Lothar.Reith@detecon.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 30 Oct 2008 22:14:47.0894 (UTC)
	FILETIME=[EBBBCF60:01C93ADC]
Subject: Re: [ANCP] DOA (was: ANCP Framework update)
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1129329486=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1129329486==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93ADC.EB5B3605"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93ADC.EB5B3605
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all
=20
Some comments on Sven's updates on the ANCP Framework draft inline below
marked {A.K.}
=20
________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Reith, Lothar
Sent: October 26, 2008 11:47 AM
To: ancp@ietf.org
Subject: [ANCP] DOA (was: ANCP Framework update)


Dear all,
=20
the ANCP Framework contains the word "delegation", which in my mind is
key to the whole concept of ANCP.=20
=20
I would like to suggest that the concept of "delegation" should be made
more extensible.=20
=20
Narrowing it to the term "bandwidth delegation" does not lend itself
very well to extensibility.
=20
I would rather propose to introduce the more general term of DOA
(Delegation of Authority), which is a well known concept in the real
world, when a resource owner delegates control over part or all of his
resources to someone else - e.g. during a vacation absence.
=20
Today, ANCP does not just support delegation in the form of bandwidth
delegation, but also in the form of delegation of content access control
(delegation occurs for whitelist and blacklist content, but not for the
greylist content).=20
{A.K} I see this as a delpoyment choice on whom manages what list and
what list should take local decisions or ask for further authority. I do
not see this as related to the delegation only. I think what we do need
is that when an Authoritive node such as the NAS informs an enforcement
point that this is what has been delegated to it so it can take local
decisions with or without informing/requesting the NAS on that local
decision.=20
=20
I think the extensible concept "DOA" is very powerful when harnessed for
Broadband Access using ANCP.
=20
While updating the framework it may be worth a consideration to add this
hook for extensibility by following means:
=20
- replace the term "bandwidth delegation" by "DOA for part of access
circuit bandwidth"
=20
- introduce the first extension of the DOA concept by making clear that
the concepts of  whitelist and blacklist are DOA for Content Access
Control.
=20
{A.K>} I dont think we need more terms here.
=20
One more point with respect to the recent discussion about renaming the
Policy Server.
=20
I like to state that I am fine with the current name "policy server".
Historically, I beleive the name was chosen as a compromise between the
RADIUS camp and the COPS camp.
=20
If - given this background - we still want to change the name of the
policy server, then perhaps DOA-server may be another alternative to
consider.=20
=20
{A.K} I think the name Policy Server is sufficent in the current ANCP
Framework and we should not start a terminology change/debate on this at
this late stage.
=20
 An important argument in this case would be, that the concept of
"delegation of authority" is well aligned with the proxy concept,
similar to a RADIUS Proxy Server, where the delegation of authority
happens along a delegation chain which may span multiple RADIUS proxy
servers and multiple domains. This aspect is missing in the other
proposed names.
=20
Best Regards,
=20
Lothar Reith
Detecon International GmbH (Deutsche Telekom Group)
=20

________________________________

Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
Gesendet: Do 23.10.2008 12:57
An: ancp@ietf.org
Betreff: Re: [ANCP] ANCP Framework update


Hi,
=20
Here's the updated text. I removed any notion of "flags" or how the
Access Node is told whether or not Bandwidth Delegation applies. I also
covered Thomas' comments. Actually not that much work: the general ANCP
requirements as well as the NAS requirements were written in a
high-level way already. I only had to update the general text and some
of the Access Node requirements. Below the extracted text, let me know
your comments.
=20
Regards,
Sven
=20
---
=20
General text
=20
   o  One approach is for the AN to query the NAS so that Admission
      Control for the access line is performed by the NAS (possibly with
      interactions with a Policy Server).  This can be done with or
      without "bandwidth delegation" to the AN.
=20
      *  In case of Admission Control without AN Bandwidth Delegation,
         the AN can use ANCP to query the NAS, that in turn performs
         multicast Admission Control check for the new multicast flow
         and responds to the AN indicating whether the join is to be
         honored (and hence replication performed by the AN) or denied.
         The NAS may locally maintain available "video" bandwidth on the
         Access Loop (as a portion of the Access Loop net data rate),
         and perform video bandwidth accounting for the Access Loop.
         Upon receiving an Admission Request from the AN, the NAS can
         check available "video" bandwidth before admitting or denying
         the multicast flow.  In the process, the NAS may communicate
         with the Policy Server.  For unicast video services such as
         Video on Demand (VoD), the NAS may also be queried (by a Policy
         Server or via on-path CAC signaling), so that it can perform
         admission control for the unicast flow, and update the
         available video bandwidth maintained by the NAS.
=20
      *  In case of Admission Control with AN Bandwidth Delegation, the
         NAS (possibly with interactions with a Policy Server) manages
         total bandwidth for video admission, performs unicast admission
         control and uses ANCP to delegate a certain amount of bandwidth
         for some multicast flows to the Access Node.  In this scenario,
         upon receiving a join to a multicast flow which matches an
         entry in the White or Grey List, the AN must perform the
         necessary bandwidth admission control check for the new
         multicast flow, before starting the multicast flow replication.

=20
{A.K}--> The AN "MAY" perform the necessary bandwidth adm ctl check, i
think this is more a deployment issue where some Service Providers may
decide that they allocate the max required b/w to satisfy all services
within the White/Grey lists. So if i say that i allocate 16MB od b/w
which should be sufficent for SD adn HD type TV channels, why would i
need to always check for necessary bandwidth, this is not required, and
should be a MAY only. =20

Access Node requirements
=20
   o  The AN must deny any join to a multicast flow matching the Black
      List for the relevant Access Port.
=20
   o  The AN must accept any join to a multicast flow matching the White
      List and for which no Bandwidth Delegation is required.
=20
   o  Upon receiving a join to a multicast flow which matches the White
      List whose and for which Bandwidth Delegation is required, the AN
      must perform the necessary bandwidth admission control check for
      the new flow before starting the multicast flow replication.=20
=20
{A.K}--> same as my above comment, this is a MAY.=20
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which no Bandwidth Delegation is required, the AN
      must support using ANCP to query the NAS to receive a response
      indicating whether that join is to be honored or denied.  In this
      case, the NAS will perform both the necessary conditional access
      and the admission control checks for the new flow.
=20
   o  Upon receiving a join to a multicast flow which matches the Grey
      List and for which Bandwidth Delegation is required, the AN must
      first perform the necessary bandwidth admission control check for
      the new flow.  If successful, the AN must support using ANCP to
      query the NAS to receive a response indicating whether that join
      is to be honored or denied.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to notify the NAS when the the user leaves
      the multicast flow.
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to query the NAS to request additional
      delegated multicast bandwidth on a given Access Port; the AN
      should be able to specify both the minimum and the preferred
      amount of additional multicast bandwidth requested.=20
=20
{A.K} I see this as more the NAS informing the AN of additional b/w
available for a given service type, not the AN requesting additional
b/w. =20

   o  In case of Admission Control with AN Bandwidth Delegation, upon
      receiving a Bandwidth Delegation Request from the NAS querying or
      instructing to decrease the delegated multicast bandwidth on a
      given Access Port, the AN must support using ANCP to send a
      Bandwidth Delegation Response indicating the new delegated
      multicast bandwidth.=20
=20
{A.K}--> wait so here you are saying the NAS will request, same as aboev
comment, this is more about the NAS informing/delegating the AN on what
services it can make local decisions upon and that a given service may
have this associated b/w. I think we just need to make this clearer
here.=20
=20
   o  In case of Admission Control with AN Bandwidth Delegation, the AN
      must support using ANCP to send a Bandwidth Release message to the
      NAS in order to release unused delegated multicast bandwidth on a
      given Access Port.=20
=20
{A.K}--> So this i do not see how this would work if the NAS has
delegated a "given amount of b/w" to the AN, then the AN maintains this
delegated b/w CAP regardless if it is used or not. The AN may inform the
NAS of what b/w is currently consumed from the delageted b/w but nothing
more than this, so i do not agree with this requirement. =20
=20
Regards,
Sven

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: maandag 20 oktober 2008 12:58
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp@ietf.org
Subject: Re: [ANCP] ANCP Framework update




On 20 Oct 2008, at 12:22, OOGHE Sven wrote:


	Francois,
	=20
	Another approach we could take is to let the framework
requirements be agnostic as to how the Access Node knows whether or not
Bandwidth Delegation applies. We could describe the notion of Bandwidth
Delegation and the respective requirements for the Access Node and NAS
in this case.
	=20
	The details of how the use of Bandwidth Delegation is
communicated to the Access Node - using a flag, some "on/off" knob or
both - would be left to the actual protocol specification work.



Good idea. It will avoid these cross dependencies between framework and
protocol, which indeed reflect that we are probably trying to be too
precise/prescriptive in the framework.


	=20
	I think following this path would require relatively small edits
to the document. I'm ok to take a first shot at it.



That would be good.


Thanks


Francois


	=20
	Regards,
	Sven

=09
________________________________

	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com
<mailto:flefauch@cisco.com> ]=20
	Sent: maandag 20 oktober 2008 12:01
	To: OOGHE Sven
	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
<mailto:ancp@ietf.org>=20
	Subject: Re: [ANCP] ANCP Framework update
=09
=09
=09
	Sven and all,=20
=09
=09

		   o  Upon receiving a join to a multicast flow which
matches the Grey=20
		      List whose entry is flagged as "no Bandwidth
Delegation" for the=20
		      relevant Access Port, the AN must support using
ANCP to query the=20
		      NAS to receive a response indicating whether that
join is to be=20
		      honored or denied.  In this case, the NAS will
perform both the=20
		      necessary conditional access and the admission
control checks for=20
		      the new flow.


	Roberta, Tom and myself have started drafting an I-D that will
propose ANCP protocol extensions supporting some of those requirements
(building on top of ancp-mc-multicast).
	In doing so, we revisited a point that came up multiple times:
do we really need to provision a flag in each and every Grey/White List
entry to activate/deactivate Bandwidth Delegation?
=09
=09
	The current approach (as correctly reflected in the updated
Framework) is:
	* define a flag in each Grey/White List entry
=09
	* assume that this flag will normally either always be set in
all entries or never set.
=09
	* setting/no-setting the flag is all entries effectively acts as
the knob to enable/disable Bandwidth Delegation, therefore we did not
need to specify a specific knob to enable/disable Bandwidth Delegation.
=09
=09
=09
	Another approach would be:
	* remove flag from White/Grey list entries
=09
	* define a specific knob to enable/disable Bandwidth Delegation
at the AN granularity
	* in fact, define a generic AN-level provisioning method that
could be used to enable/disable BAndwidth delegation, but could also be
used for provisioning the "Service Profiles" that are currently assumed
to be configured in AN, as well as provisioning the Multicast
White/Grey/Black Profiles
=09
=09
=09
	Considering that:
	- we got several times the feedback that per-entry BAndwidth
Delegation flag was confusing since Bandwidth Delegation granularity is
more AN-level (and may lead to difficulties if it is set on some entries
and not on others)
	- it is likely that we'll need, anyways, a mechanism to
provision things at AN level, that could be easily used to convey
Bandwidth Delegation enable/disable knob.
=09
	we would like to propose to evolve to the newer approach.
=09
=09
	Thoughts?
=09
=09
	Francois
=09
=09
	PS: Sven, if we go for the new approach, we can document in an
email the deltas that would be needed to reflect that in framework.
=09
=09



------_=_NextPart_001_01C93ADC.EB5B3605
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1613" name=3DGENERATOR></HEAD>
<BODY style=3D"WORD-WRAP: break-word">
<DIV><SPAN class=3D203113621-30102008><FONT face=3DArial>Hi =
all</FONT></SPAN></DIV>
<DIV><SPAN class=3D203113621-30102008><FONT =
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D203113621-30102008><FONT face=3DArial>Some comments =
on Sven's=20
updates on the ANCP Framework draft inline below marked=20
{A.K.}</FONT></SPAN></DIV>
<DIV><SPAN class=3D203113621-30102008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Reith, =
Lothar<BR><B>Sent:</B>=20
October 26, 2008 11:47 AM<BR><B>To:</B> ancp@ietf.org<BR><B>Subject:</B> =
[ANCP]=20
DOA (was: ANCP Framework update)<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=3DidOWAReplyText66978 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000>
<DIV dir=3Dltr><FONT color=3D#000000 size=3D2>Dear all,</FONT></DIV>
<DIV>
<DIV id=3DidOWAReplyText68228 dir=3Dltr>
<DIV id=3DidOWAReplyText93369 dir=3Dltr>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>the ANCP Framework contains the word =
"delegation",=20
which in my mind is key to the whole concept of ANCP. </FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>I would like to suggest that the concept =
of=20
"delegation" should be made more extensible. </FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>Narrowing it to the term "bandwidth =
delegation" does=20
not lend itself very well to extensibility.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>I would rather propose to introduce the =
more general=20
term of DOA (Delegation of Authority), which is a well known concept in =
the real=20
world, when a resource owner delegates control over part or all of his =
resources=20
to someone else - e.g. during a vacation absence.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>Today, ANCP does not just support =
delegation in the=20
form of bandwidth delegation, but also in the form of delegation of =
content=20
access control (delegation occurs for whitelist and blacklist content, =
but not=20
for the greylist content).<SPAN class=3D203113621-30102008><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2><SPAN class=3D203113621-30102008><FONT=20
color=3D#0000ff>{A.K} I see this as a delpoyment choice on =
whom&nbsp;manages what=20
list and what list should take local decisions or ask for further =
authority. I=20
do not see this as related to the delegation only. I think what we do =
need is=20
that when an Authoritive node such as the NAS informs an enforcement =
point that=20
this is what&nbsp;has been delegated to it so it can take local =
decisions with=20
or without informing/requesting&nbsp;the NAS on that local=20
decision.</FONT>&nbsp;</SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>I think the extensible concept =
"DOA"&nbsp;is very=20
powerful when harnessed for Broadband Access using ANCP.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>While updating the framework it may be =
worth a=20
consideration to add this hook for extensibility by following=20
means:</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>- replace&nbsp;the term "bandwidth =
delegation" by "DOA=20
for part of access circuit bandwidth"</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>- introduce the first extension of the DOA =
concept by=20
making clear that the concepts of &nbsp;whitelist and blacklist are DOA =
for=20
Content Access Control.</FONT></DIV>
<DIV dir=3Dltr><SPAN class=3D203113621-30102008><FONT=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr><SPAN class=3D203113621-30102008>{A.K&gt;} I dont think =
we need more=20
terms here.</SPAN></DIV>
<DIV dir=3Dltr><SPAN class=3D203113621-30102008><FONT=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>One more point with respect to the recent =
discussion=20
about renaming the Policy Server.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>I like to state that I am fine with the =
current name=20
"policy server".&nbsp;&nbsp;Historically,&nbsp;I beleive&nbsp;the name =
was=20
chosen as a compromise between the RADIUS camp and the COPS =
camp.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>If - given this background - we&nbsp;still =
want to=20
change the name of the policy server, then perhaps DOA-server may be =
another=20
alternative to consider. </FONT></DIV>
<DIV dir=3Dltr><SPAN class=3D203113621-30102008><FONT=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr><SPAN class=3D203113621-30102008><FONT size=3D2>{A.K} I =
think the name=20
Policy Server is sufficent in the current ANCP Framework and we should =
not start=20
a terminology change/debate on this at this late =
stage.</FONT></SPAN></DIV>
<DIV dir=3Dltr><FONT size=3D2><SPAN class=3D203113621-30102008><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2><SPAN =
class=3D203113621-30102008>&nbsp;</SPAN>An=20
important argument in this case would be, that the concept of =
"delegation of=20
authority" is well aligned with the proxy concept, similar to a RADIUS =
Proxy=20
Server, where the delegation of authority happens along a delegation =
chain which=20
may span multiple RADIUS proxy servers and multiple domains. This aspect =
is=20
missing in the other proposed names.</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>Best Regards,</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT size=3D2>Lothar Reith</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2>Detecon International GmbH (Deutsche =
Telekom=20
Group)</FONT></DIV>
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV></DIV>
<DIV dir=3Dltr><BR><FONT size=3D2>
<HR tabIndex=3D-1>
</FONT><FONT size=3D2><FONT face=3DTahoma><B>Von:</B> =
ancp-bounces@ietf.org im=20
Auftrag von OOGHE Sven<BR><B>Gesendet:</B> Do 23.10.2008 =
12:57<BR><B>An:</B>=20
ancp@ietf.org<BR><B>Betreff:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></FONT></DIV>
<DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>Here's the updated text. I removed any notion of "flags" or how =
the=20
Access Node is told whether or not Bandwidth Delegation applies. I also =
covered=20
Thomas' comments. Actually not that much work: the general ANCP =
requirements as=20
well as the NAS requirements were written in a high-level =
way&nbsp;already. I=20
only had to update the general text and some of the Access Node =
requirements.=20
Below the extracted text, let me know your comments.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>Sven</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>---</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2><STRONG>General text</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>&nbsp;&nbsp; o&nbsp; One approach is for the AN to query the =
NAS so that=20
Admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Control for the access line =
is=20
performed by the NAS (possibly with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
interactions with a Policy Server).&nbsp; This can be done with=20
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without "bandwidth delegation" to =
the=20
AN.</FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission =
Control=20
without AN Bandwidth=20
Delegation,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN =
can use=20
ANCP to query the NAS, that in turn=20
performs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =
Admission=20
Control check for the new multicast=20
flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and responds to =
the AN=20
indicating whether the join is to=20
be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored (and =
hence=20
replication performed by the AN) or=20
denied.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The NAS may =
locally=20
maintain available "video" bandwidth on=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Access Loop (as =
a=20
portion of the Access Loop net data=20
rate),<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and perform =
video=20
bandwidth accounting for the Access=20
Loop.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Upon receiving =
an=20
Admission Request from the AN, the NAS=20
can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check available =
"video"=20
bandwidth before admitting or=20
denying<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
multicast=20
flow.&nbsp; In the process, the NAS may=20
communicate</EM></FONT></SPAN></DIV><SPAN class=3D852244910-23102008>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with the =
Policy=20
Server.&nbsp; For unicast video services such=20
as<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Video on Demand =
(VoD),=20
the NAS may also be queried (by a=20
Policy<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Server or via =
on-path=20
CAC signaling), so that it can=20
perform<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; admission =
control=20
for the unicast flow, and update=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available video=20
bandwidth maintained by the NAS.</EM></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><FONT=20
size=3D2><EM>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp; In case of Admission =
Control=20
with AN Bandwidth Delegation,=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS (possibly =
with=20
interactions with a Policy Server)=20
manages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; total =
bandwidth for=20
video admission, performs unicast=20
admission<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control =
and uses=20
ANCP to delegate a certain amount of=20
bandwidth<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for some =
multicast=20
flows to the Access Node.&nbsp; In this=20
scenario,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; upon =
receiving a=20
join to a multicast flow which matches=20
an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entry in the =
White or=20
Grey List, the AN must perform=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary =
bandwidth=20
admission control check for the=20
new<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast flow, =
before=20
starting the multicast flow replication.</EM><SPAN=20
class=3D203113621-30102008>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203113621-30102008><EM></EM></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT><SPAN =
class=3D203113621-30102008><EM>{A.K}--&gt; The=20
AN&nbsp;"MAY" perform the necessary bandwidth adm ctl check, i think =
this is=20
more a deployment issue where some Service Providers may decide that =
they=20
allocate the max required b/w to satisfy all services within the =
White/Grey=20
lists.&nbsp;So if i say that i allocate 16MB od b/w which should be =
sufficent=20
for SD adn HD type TV channels, why would i need to always check for =
necessary=20
bandwidth, this is not required, and should be a MAY=20
only.&nbsp;</EM>&nbsp;</SPAN><BR></DIV></FONT>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2><STRONG>Access Node requirements</STRONG></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>&nbsp;&nbsp; o&nbsp; The AN must deny any join to a multicast =
flow=20
matching the Black<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List for the =
relevant=20
Access Port.</FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>&nbsp;&nbsp; o&nbsp; The AN must accept any join to a multicast =
flow=20
matching the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which =
no=20
Bandwidth Delegation is required.</FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff><FONT=20
size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join to a multicast =
flow which=20
matches the White<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose and for =
which=20
Bandwidth Delegation is required, the =
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must=20
perform the necessary bandwidth admission control check=20
for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new flow before starting the =
multicast=20
flow replication.</EM><SPAN=20
class=3D203113621-30102008>&nbsp;</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN=20
class=3D203113621-30102008><EM></EM></SPAN></FONT></FONT></SPAN>&nbsp;</D=
IV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT><SPAN =

class=3D203113621-30102008><EM>{A.K}--&gt; same as my above comment, =
this is=20
a&nbsp;MAY.</EM>&nbsp;</SPAN></FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join to a multicast =
flow which=20
matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which no =

Bandwidth Delegation is required, the =
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must=20
support using ANCP to query the NAS to receive a=20
response<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating whether that join =
is to be=20
honored or denied.&nbsp; In this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; case, =
the NAS=20
will perform both the necessary conditional=20
access<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and the admission control =
checks for=20
the new flow.</EM></FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2><EM>&nbsp;&nbsp; o&nbsp; Upon receiving a join to a multicast =
flow which=20
matches the Grey<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List and for which =
Bandwidth=20
Delegation is required, the AN must<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
first=20
perform the necessary bandwidth admission control check=20
for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new flow.&nbsp; If successful, =
the AN=20
must support using ANCP to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; query the =
NAS to=20
receive a response indicating whether that=20
join<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is to be honored or=20
denied.</EM></FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN =
Bandwidth=20
Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to=20
notify the NAS when the the user =
leaves<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the=20
multicast flow.</FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff><FONT=20
size=3D2>&nbsp;&nbsp; o&nbsp; In case of Admission Control with AN =
Bandwidth=20
Delegation, the AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using =
ANCP to=20
query the NAS to request additional<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
delegated=20
multicast bandwidth on a given Access Port; the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should be able to specify both the =
minimum=20
and the preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; amount of additional =

multicast bandwidth requested.<SPAN=20
class=3D203113621-30102008>&nbsp;</SPAN></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN =
class=3D203113621-30102008></SPAN></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT><SPAN =

class=3D203113621-30102008>{A.K} I see this as more =
the&nbsp;NAS&nbsp;informing=20
the AN of additional b/w available for a given service type, not the AN=20
requesting additional b/w. &nbsp;</SPAN></FONT></SPAN></DIV><SPAN=20
class=3D852244910-23102008>
<DIV><BR><FONT color=3D#0000ff><FONT size=3D2>&nbsp;&nbsp; o&nbsp; In =
case of=20
Admission Control with AN Bandwidth Delegation,=20
upon<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; receiving a Bandwidth Delegation =
Request=20
from the NAS querying or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instructing =
to=20
decrease the delegated multicast bandwidth on=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given Access Port, the AN must =
support using=20
ANCP to send a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth Delegation =
Response=20
indicating the new delegated<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast =

bandwidth.<SPAN =
class=3D203113621-30102008>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D203113621-30102008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT><SPAN class=3D203113621-30102008>{A.K}--&gt; wait so here you =
are=20
saying the NAS will request, same as aboev comment, this is more =
about&nbsp;the=20
NAS informing/delegating the AN on what services it can&nbsp;make local=20
decisions upon and that a given service&nbsp;may have this associated =
b/w. I=20
think we just need to make this clearer here.&nbsp;</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><FONT =
size=3D2>&nbsp;&nbsp; o&nbsp; In=20
case of Admission Control with AN Bandwidth Delegation, the=20
AN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; must support using ANCP to send a =
Bandwidth=20
Release message to the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS in order to =
release=20
unused delegated multicast bandwidth on =
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
given Access Port.<SPAN=20
class=3D203113621-30102008>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D203113621-30102008></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT><SPAN =
class=3D203113621-30102008>{A.K}--&gt;&nbsp;So=20
this&nbsp;i do not see how this would work if the NAS has delegated a =
"given=20
amount of b/w" to the AN, then the AN maintains this delegated b/w CAP=20
regardless if it is used or not. The AN may inform the NAS of what b/w =
is=20
currently consumed from the delageted b/w but nothing more than this, so =
i do=20
not agree with this requirement. &nbsp;</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV></SPAN></SPAN>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D852244910-23102008><FONT =
color=3D#0000ff=20
size=3D2>Sven</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT size=3D2>
<HR tabIndex=3D-1>
</FONT><FONT size=3D2><FONT face=3DTahoma><B>From:</B> Francois Le =
Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> maandag 20 oktober 2008=20
12:58<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> Francois Le Faucheur IMAP;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP Framework=20
update<BR></FONT><BR></FONT></DIV>
<DIV><FONT size=3D2></FONT></DIV><FONT face=3DArial =
color=3D#0000ff></FONT><FONT=20
face=3DArial color=3D#0000ff></FONT><BR>
<DIV>
<DIV><FONT size=3D2>On 20 Oct 2008, at 12:22, OOGHE Sven =
wrote:</FONT></DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Another approach we could take is to let the =
framework=20
  requirements be agnostic as to how the Access Node knows whether or =
not=20
  Bandwidth Delegation applies. We could describe the notion of =
Bandwidth=20
  Delegation and the respective requirements for the Access Node and NAS =
in this=20
  case.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The details of how the use of Bandwidth =
Delegation is=20
  communicated to the Access Node - using a flag, some "on/off" knob or =
both -=20
  would be left to the actual protocol specification=20
  work.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><FONT size=3D2><BR></FONT></DIV>
<DIV><FONT size=3D2>Good idea. It will avoid these cross dependencies =
between=20
framework and protocol, which indeed reflect that we are probably trying =
to be=20
too precise/prescriptive in&nbsp;the&nbsp;framework.</FONT></DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I think following this path would require =
relatively=20
  small edits to the document. I'm ok to take a first shot at=20
  it.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><FONT size=3D2><BR></FONT></DIV>
<DIV><FONT size=3D2>That would be good.</FONT></DIV>
<DIV><FONT size=3D2><BR></FONT></DIV>
<DIV><FONT size=3D2>Thanks</FONT></DIV>
<DIV><FONT size=3D2><BR></FONT></DIV>
<DIV><FONT size=3D2>Francois</FONT></DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"WORD-WRAP: break-word">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D427541610-20102008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Sven</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT size=3D2>
  <HR tabIndex=3D-1>
  </FONT><FONT face=3DTahoma><FONT size=3D2><B>From:</B> Francois Le =
Faucheur IMAP=20
  [</FONT><A href=3D"mailto:flefauch@cisco.com"><FONT=20
  size=3D2>mailto:flefauch@cisco.com</FONT></A><FONT size=3D2>] =
<BR><B>Sent:</B>=20
  maandag 20 oktober 2008 12:01<BR><B>To:</B> OOGHE Sven<BR><B>Cc:</B> =
Francois=20
  Le Faucheur IMAP; </FONT><A href=3D"mailto:ancp@ietf.org"><FONT=20
  size=3D2>ancp@ietf.org</FONT></A><BR><FONT size=3D2><B>Subject:</B> =
Re: [ANCP]=20
  ANCP Framework update<BR></FONT></FONT><BR></DIV>
  <DIV><FONT size=3D2></FONT></DIV><FONT size=3D2>Sven and all, </FONT>
  <DIV><FONT face=3DArial color=3D#0000ff></FONT><BR></DIV>
  <DIV>
  <DIV>
  <BLOCKQUOTE type=3D"cite">
    <DIV>
    <P><FONT size=3D2><I><FONT face=3DArial>&nbsp;&nbsp; o&nbsp; Upon =
receiving a=20
    join to a multicast flow which matches the Grey</FONT></I> =
<BR><I><FONT=20
    face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List whose entry is =
flagged as "no=20
    Bandwidth Delegation" for the</FONT></I> <BR><I><FONT=20
    face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; relevant Access Port, =
the AN must=20
    support using ANCP to query the</FONT></I> <BR><I><FONT=20
    face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAS to receive a =
response=20
    indicating whether that join is to be</FONT></I> <BR><I><FONT=20
    face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; honored or denied.&nbsp; =
In this=20
    case, the NAS will perform both the</FONT></I> <BR><I><FONT=20
    face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; necessary conditional =
access and=20
    the admission control checks for</FONT></I> <BR><I><FONT=20
    face=3DArial>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the new=20
    flow.</FONT></I></FONT></P></DIV></BLOCKQUOTE><BR></DIV>
  <DIV>
  <DIV><FONT size=3D2>Roberta, Tom and myself have started drafting an =
I-D that=20
  will propose ANCP protocol extensions supporting some of those =
requirements=20
  (building on top of ancp-mc-multicast).</FONT></DIV>
  <DIV><FONT size=3D2>In doing so, we revisited a point that came up =
multiple=20
  times: do we really need to provision a flag in each and every =
Grey/White List=20
  entry to&nbsp;activate/deactivate&nbsp;Bandwidth =
Delegation?</FONT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial color=3D#0000ff></FONT><FONT =
face=3DArial=20
  color=3D#0000ff></FONT><BR></FONT></DIV>
  <DIV><FONT size=3D2>The current approach (as correctly reflected in =
the updated=20
  Framework) is:</FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>*=20
  define a flag in each Grey/White List entry<BR></FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>*=20
  assume that this flag will normally either always be set in all =
entries or=20
  never set.<BR></FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>*=20
  setting/no-setting the flag is all entries effectively acts as the =
knob to=20
  enable/disable Bandwidth Delegation, therefore we did not need to =
specify a=20
  specific knob to enable/disable Bandwidth Delegation.<BR></FONT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial =
color=3D#0000ff></FONT><BR></FONT></DIV>
  <DIV><FONT size=3D2>Another approach would be:</FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>*=20
  remove flag from White/Grey list entries<BR></FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>*=20
  define a specific knob to enable/disable Bandwidth Delegation at the =
AN=20
  granularity</FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>*=20
  in fact, define a generic&nbsp;AN-level provisioning method that could =
be used=20
  to enable/disable BAndwidth delegation, but&nbsp;could&nbsp;also be =
used for=20
  provisioning the "Service Profiles" that are currently assumed to be=20
  configured in AN, as well as provisioning the Multicast =
White/Grey/Black=20
  Profiles<BR></FONT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial =
color=3D#0000ff></FONT><BR></FONT></DIV>
  <DIV><FONT size=3D2>Considering that:</FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>-=20
  we got several times the feedback that per-entry BAndwidth Delegation =
flag was=20
  confusing since&nbsp;Bandwidth Delegation granularity is more AN-level =
(and=20
  may lead to difficulties if it is set on some entries and not on=20
  others)</FONT></DIV>
  <DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN><FONT size=3D2>-=20
  it is likely that we'll need, anyways, a mechanism to provision things =
at AN=20
  level, that could be easily used to convey Bandwidth Delegation =
enable/disable=20
  knob.<BR></FONT></DIV>
  <DIV><FONT size=3D2>we&nbsp;would&nbsp;like to propose=20
  to&nbsp;evolve&nbsp;to&nbsp;the&nbsp;newer approach.</FONT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial =
color=3D#0000ff></FONT><BR></FONT></DIV>
  <DIV><FONT size=3D2>Thoughts?</FONT></DIV>
  <DIV><FONT size=3D2><BR></FONT></DIV>
  <DIV><FONT size=3D2>Francois</FONT></DIV>
  <DIV><FONT size=3D2><BR></FONT></DIV>
  <DIV><FONT size=3D2>PS: Sven, if we go for&nbsp;the&nbsp;new approach, =
we can=20
  document in an email the deltas that&nbsp;would&nbsp;be needed to =
reflect that=20
  in framework.</FONT></DIV>
  <DIV><FONT=20
size=3D2><BR></FONT></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV>=
</DIV></DIV></FONT></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C93ADC.EB5B3605--

--===============1129329486==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

--===============1129329486==--


From ancp-bounces@ietf.org  Thu Oct 30 15:31:13 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6AAF528C16A;
	Thu, 30 Oct 2008 15:31:13 -0700 (PDT)
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B77228C16A
	for <ancp@core3.amsl.com>; Thu, 30 Oct 2008 15:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.56
X-Spam-Level: 
X-Spam-Status: No, score=-5.56 tagged_above=-999 required=5 tests=[AWL=-1.038, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077]
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 Zvvt5v+RBnfW for <ancp@core3.amsl.com>;
	Thu, 30 Oct 2008 15:31:10 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	by core3.amsl.com (Postfix) with ESMTP id AE0753A6AB0
	for <ancp@ietf.org>; Thu, 30 Oct 2008 15:31:10 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m9UMUgR4002086;
	Thu, 30 Oct 2008 17:30:42 -0500
Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 17:30:42 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 18:30:41 -0400
Message-ID: <35815C929B41D2479A224FE098A27227066892C8@ecamlmw720.eamcs.ericsson.se>
In-Reply-To: <3525C9833C09ED418C6FD6CD9514668C04F70C13@emailwf1.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] DOA
Thread-Index: Ack4/XL8dDL57Sh4Rp2O9SGfurF1GwAEP36gAHQlAzA=
References: <7168964CAC5C144685272595141B6DBA0145165D@FRVELSMBS22.ad2.ad.alcatel.com><FB1E235C-173F-40A3-A821-7BD52296EDC9@cisco.com><7168964CAC5C144685272595141B6DBA01451C46@FRVELSMBS22.ad2.ad.alcatel.com><B574433E-1B70-4243-8A48-87B832982F98@cisco.com><7168964CAC5C144685272595141B6DBA014FB12F@FRVELSMBS22.ad2.ad.alcatel.com><D4ECB93FEDE50045B2657B56894BADF204FA838E@DC00331.detecon.com>	<7168964CAC5C144685272595141B6DBA014FBB9B@FRVELSMBS22.ad2.ad.alcatel.com><5661758E3E93364685B91DD8272F28763F84AA@S4DE8PSAAQC.mitte.t-com.de><49070D5D.2020604@rogers.com>
	<3525C9833C09ED418C6FD6CD9514668C04F70C13@emailwf1.jnpr.net>
From: "Alan Kavanagh" <alan.kavanagh@ericsson.com>
To: "Jerome Moisand" <jmoisand@juniper.net>,
	"Tom Taylor" <tom.taylor@rogers.com>, "Haag, Thomas" <HaagT@telekom.de>
X-OriginalArrivalTime: 30 Oct 2008 22:30:42.0281 (UTC)
	FILETIME=[2497B590:01C93ADF]
Cc: Sven.Ooghe@alcatel-lucent.be, ancp@ietf.org
Subject: Re: [ANCP] DOA
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list
	<ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>,
	<mailto:ancp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hi All

I think this captures this quite well and support this!
BR
Alan K 

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Jerome Moisand
Sent: October 28, 2008 11:11 AM
To: Tom Taylor; Haag, Thomas
Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org
Subject: Re: [ANCP] DOA

Folks,

Actually, in the very early days of L2CP (wasn't called ANCP by then)
discussions in the DSL-Forum, we did come up with the term "Delegation
of Authorization" terminology to describe the essence of the concept.

"Authorization" is a direct reference to AAA concepts, whether this is
an initial authorization (at user session establishment time), or
dynamic change of authorization (i.e. in-session).

We certainly didn't notice the unfortunate side-effect with ambulance
driver reports... But still, I always liked this "Delegation of
Authorization" terminology. A BRAS/BNG is essentially an authorization
enforcer for subscriber/service management. And ANCP is a mechanism to
delegate some of that enforcement to the access node.

Cheers,
Jerome - the ghost

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Tom Taylor
Sent: Tuesday, October 28, 2008 9:02 AM
To: Haag, Thomas
Cc: Sven.Ooghe@alcatel-lucent.be; ancp@ietf.org
Subject: Re: [ANCP] DOA

I don't mind. I coined the phrase "bandwidth delegation" to express what
was happening. The only thing is, "DOA" has unfortunate connotations --
it's a notation that appears on ambulance drivers' reports (Dead on
Arrival) when their patient dies before reaching the hospital. So I'd
prefer that "Delegation of Authority" be spelled out.

Haag, Thomas wrote:
> Hi Sven,
>  
> I also agree on DOA. 
> This covers the issue in a better way.
>  
> Regards
> Thomas
> 
> ________________________________
> 
> Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag
von
> OOGHE Sven
> Gesendet: Montag, 27. Oktober 2008 11:49
> An: Reith, Lothar; ancp@ietf.org
> Betreff: Re: [ANCP] DOA (was: ANCP Framework update)
> 
> 
> Hi Lothar,
>  
> I think the term "Delegation of Authority" captures the principle of 
> what bandwidth delegation is about. I'm fine either way, and would
like
> to ask other people on this list what they think.
>  
> Regards,
> Sven
> 
> ________________________________
> 
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf
Of
> Reith, Lothar
> Sent: zondag 26 oktober 2008 16:47
> To: ancp@ietf.org
> Subject: [ANCP] DOA (was: ANCP Framework update)
> 
> 
> Dear all,
>  
> the ANCP Framework contains the word "delegation", which in my mind is

> key to the whole concept of ANCP.
>  
> I would like to suggest that the concept of "delegation" should be
made
> more extensible. 
>  
> Narrowing it to the term "bandwidth delegation" does not lend itself 
> very well to extensibility.
>  
> I would rather propose to introduce the more general term of DOA 
> (Delegation of Authority), which is a well known concept in the real 
> world, when a resource owner delegates control over part or all of his

> resources to someone else - e.g. during a vacation absence.
>  
> Today, ANCP does not just support delegation in the form of bandwidth 
> delegation, but also in the form of delegation of content access
control
> (delegation occurs for whitelist and blacklist content, but not for
the
> greylist content).
>  
> I think the extensible concept "DOA" is very powerful when harnessed
for
> Broadband Access using ANCP.
>  
> While updating the framework it may be worth a consideration to add
this
> hook for extensibility by following means:
>  
> - replace the term "bandwidth delegation" by "DOA for part of access 
> circuit bandwidth"
>  
> - introduce the first extension of the DOA concept by making clear
that
> the concepts of  whitelist and blacklist are DOA for Content Access 
> Control.
>  
> One more point with respect to the recent discussion about renaming
the
> Policy Server.
>  
> I like to state that I am fine with the current name "policy server".
> Historically, I beleive the name was chosen as a compromise between
the
> RADIUS camp and the COPS camp.
>  
> If - given this background - we still want to change the name of the 
> policy server, then perhaps DOA-server may be another alternative to 
> consider.
>  
> An important argument in this case would be, that the concept of 
> "delegation of authority" is well aligned with the proxy concept, 
> similar to a RADIUS Proxy Server, where the delegation of authority 
> happens along a delegation chain which may span multiple RADIUS proxy 
> servers and multiple domains. This aspect is missing in the other 
> proposed names.
>  
> Best Regards,
>  
> Lothar Reith
> Detecon International GmbH (Deutsche Telekom Group)
>  
> 
> ________________________________
> 
> Von: ancp-bounces@ietf.org im Auftrag von OOGHE Sven
> Gesendet: Do 23.10.2008 12:57
> An: ancp@ietf.org
> Betreff: Re: [ANCP] ANCP Framework update
> 
> 
> Hi,
>  
> Here's the updated text. I removed any notion of "flags" or how the 
> Access Node is told whether or not Bandwidth Delegation applies. I
also
> covered Thomas' comments. Actually not that much work: the general
ANCP
> requirements as well as the NAS requirements were written in a 
> high-level way already. I only had to update the general text and some

> of the Access Node requirements. Below the extracted text, let me know

> your comments.
>  
> Regards,
> Sven
>  
> ---
>  
> General text
>  
>    o  One approach is for the AN to query the NAS so that Admission
>       Control for the access line is performed by the NAS (possibly
with
>       interactions with a Policy Server).  This can be done with or
>       without "bandwidth delegation" to the AN.
>  
>       *  In case of Admission Control without AN Bandwidth Delegation,
>          the AN can use ANCP to query the NAS, that in turn performs
>          multicast Admission Control check for the new multicast flow
>          and responds to the AN indicating whether the join is to be
>          honored (and hence replication performed by the AN) or
denied.
>          The NAS may locally maintain available "video" bandwidth on
the
>          Access Loop (as a portion of the Access Loop net data rate),
>          and perform video bandwidth accounting for the Access Loop.
>          Upon receiving an Admission Request from the AN, the NAS can
>          check available "video" bandwidth before admitting or denying
>          the multicast flow.  In the process, the NAS may communicate
>          with the Policy Server.  For unicast video services such as
>          Video on Demand (VoD), the NAS may also be queried (by a
Policy
>          Server or via on-path CAC signaling), so that it can perform
>          admission control for the unicast flow, and update the
>          available video bandwidth maintained by the NAS.
>  
>       *  In case of Admission Control with AN Bandwidth Delegation,
the
>          NAS (possibly with interactions with a Policy Server) manages
>          total bandwidth for video admission, performs unicast
admission
>          control and uses ANCP to delegate a certain amount of
bandwidth
>          for some multicast flows to the Access Node.  In this
scenario,
>          upon receiving a join to a multicast flow which matches an
>          entry in the White or Grey List, the AN must perform the
>          necessary bandwidth admission control check for the new
>          multicast flow, before starting the multicast flow
replication.
> 
> Access Node requirements
>  
>    o  The AN must deny any join to a multicast flow matching the Black
>       List for the relevant Access Port.
>  
>    o  The AN must accept any join to a multicast flow matching the
White
>       List and for which no Bandwidth Delegation is required.
>  
>    o  Upon receiving a join to a multicast flow which matches the
White
>       List whose and for which Bandwidth Delegation is required, the
AN
>       must perform the necessary bandwidth admission control check for
>       the new flow before starting the multicast flow replication.
>  
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which no Bandwidth Delegation is required, the AN
>       must support using ANCP to query the NAS to receive a response
>       indicating whether that join is to be honored or denied.  In
this
>       case, the NAS will perform both the necessary conditional access
>       and the admission control checks for the new flow.
>  
>    o  Upon receiving a join to a multicast flow which matches the Grey
>       List and for which Bandwidth Delegation is required, the AN must
>       first perform the necessary bandwidth admission control check
for
>       the new flow.  If successful, the AN must support using ANCP to
>       query the NAS to receive a response indicating whether that join
>       is to be honored or denied.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to notify the NAS when the the user
leaves
>       the multicast flow.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to query the NAS to request additional
>       delegated multicast bandwidth on a given Access Port; the AN
>       should be able to specify both the minimum and the preferred
>       amount of additional multicast bandwidth requested.
> 
>    o  In case of Admission Control with AN Bandwidth Delegation, upon
>       receiving a Bandwidth Delegation Request from the NAS querying
or
>       instructing to decrease the delegated multicast bandwidth on a
>       given Access Port, the AN must support using ANCP to send a
>       Bandwidth Delegation Response indicating the new delegated
>       multicast bandwidth.
>  
>    o  In case of Admission Control with AN Bandwidth Delegation, the
AN
>       must support using ANCP to send a Bandwidth Release message to
the
>       NAS in order to release unused delegated multicast bandwidth on
a
>       given Access Port.
>  
> Regards,
> Sven
> 
> ________________________________
> 
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]
> Sent: maandag 20 oktober 2008 12:58
> To: OOGHE Sven
> Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> Subject: Re: [ANCP] ANCP Framework update
> 
> 
> 
> 
> On 20 Oct 2008, at 12:22, OOGHE Sven wrote:
> 
> 
> 	Francois,
> 	 
> 	Another approach we could take is to let the framework
requirements 
> be agnostic as to how the Access Node knows whether or
not
> Bandwidth Delegation applies. We could describe the notion of
Bandwidth
> Delegation and the respective requirements for the Access Node and NAS

> in this case.
> 	 
> 	The details of how the use of Bandwidth Delegation is
communicated to 
> the Access Node - using a flag, some "on/off" knob or both - would be 
> left to the actual protocol specification work.
> 
> 
> Good idea. It will avoid these cross dependencies between framework
and
> protocol, which indeed reflect that we are probably trying to be too 
> precise/prescriptive in the framework.
> 
> 
> 	 
> 	I think following this path would require relatively small edits
to 
> the document. I'm ok to take a first shot at it.
> 
> 
> That would be good.
> 
> Thanks
> 
> Francois
> 
> 
> 	 
> 	Regards,
> 	Sven
> 
> ________________________________
> 
> 	From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] 
> 	Sent: maandag 20 oktober 2008 12:01
> 	To: OOGHE Sven
> 	Cc: Francois Le Faucheur IMAP; ancp@ietf.org
> 	Subject: Re: [ANCP] ANCP Framework update
> 	
> 	
> 	Sven and all,
> 	
> 	
> 
> 		   o  Upon receiving a join to a multicast flow which
matches the 
> Grey
> 		      List whose entry is flagged as "no Bandwidth
Delegation" for 
> the
> 		      relevant Access Port, the AN must support using
ANCP to query 
> the
> 		      NAS to receive a response indicating whether that
join is to 
> be
> 		      honored or denied.  In this case, the NAS will
perform both 
> the
> 		      necessary conditional access and the admission
control checks 
> for
> 		      the new flow.
> 
> 
> 	Roberta, Tom and myself have started drafting an I-D that will 
> propose ANCP protocol extensions supporting some of those requirements

> (building on top of ancp-mc-multicast).
> 	In doing so, we revisited a point that came up multiple times:
> do we really need to provision a flag in each and every Grey/White
List
> entry to activate/deactivate Bandwidth Delegation?
> 	
> 	
> 	The current approach (as correctly reflected in the updated
> Framework) is:
> 	* define a flag in each Grey/White List entry
> 	
> 	* assume that this flag will normally either always be set in
all 
> entries or never set.
> 	
> 	* setting/no-setting the flag is all entries effectively acts as
the 
> knob to enable/disable Bandwidth Delegation, therefore we did not need

> to specify a specific knob to enable/disable Bandwidth
Delegation.
> 	
> 	
> 	
> 	Another approach would be:
> 	* remove flag from White/Grey list entries
> 	
> 	* define a specific knob to enable/disable Bandwidth Delegation
at 
> the AN granularity
> 	* in fact, define a generic AN-level provisioning method that
could 
> be used to enable/disable BAndwidth delegation, but could also
be
> used for provisioning the "Service Profiles" that are currently
assumed
> to be configured in AN, as well as provisioning the Multicast 
> White/Grey/Black Profiles
> 	
> 	
> 	
> 	Considering that:
> 	- we got several times the feedback that per-entry BAndwidth 
> Delegation flag was confusing since Bandwidth Delegation granularity
is
> more AN-level (and may lead to difficulties if it is set on some
entries
> and not on others)
> 	- it is likely that we'll need, anyways, a mechanism to
provision 
> things at AN level, that could be easily used to convey Bandwidth 
> Delegation enable/disable knob.
> 	
> 	we would like to propose to evolve to the newer approach.
> 	
> 	
> 	Thoughts?
> 
> 	Francois
> 
> 	PS: Sven, if we go for the new approach, we can document in an
email 
> the deltas that would be needed to reflect that in framework.
> 
> 
> 
> 
> 
> 
>
------------------------------------------------------------------------
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


