
From tom111.taylor@bell.net  Fri Jun 18 20:15:42 2010
Return-Path: <tom111.taylor@bell.net>
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 749283A6874 for <ancp@core3.amsl.com>; Fri, 18 Jun 2010 20:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.604
X-Spam-Level: **
X-Spam-Status: No, score=2.604 tagged_above=-999 required=5 tests=[AWL=-1.799,  BAYES_95=3, J_CHICKENPOX_74=0.6, MSGID_FROM_MTA_HEADER=0.803]
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 8Jd2h8YBWN+f for <ancp@core3.amsl.com>; Fri, 18 Jun 2010 20:15:41 -0700 (PDT)
Received: from blu0-omc2-s25.blu0.hotmail.com (blu0-omc2-s25.blu0.hotmail.com [65.55.111.100]) by core3.amsl.com (Postfix) with ESMTP id A6D033A6873 for <ancp@ietf.org>; Fri, 18 Jun 2010 20:15:41 -0700 (PDT)
Received: from BLU0-SMTP23 ([65.55.111.73]) by blu0-omc2-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 18 Jun 2010 20:15:47 -0700
X-Originating-IP: [70.26.19.89]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP23B434BF8D9CD2BFB5EA6CD8C10@phx.gbl>
Received: from [192.168.2.11] ([70.26.19.89]) by BLU0-SMTP23.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 18 Jun 2010 20:15:46 -0700
Date: Fri, 18 Jun 2010 23:15:42 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jun 2010 03:15:47.0083 (UTC) FILETIME=[B60C5DB0:01CB0F5D]
Subject: [ANCP] Description of message structure in the base protocol document
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/mail-archive/web/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>
X-List-Received-Date: Sat, 19 Jun 2010 03:15:42 -0000

Currently it is a bit tricky to put together a picture of ANCP message structure 
because the individual components are scattered through several sections with 
cross-references between them. It seems to me that the general description 
(Section 5) should say: here is the general structure. Then the presentation 
should be:

1. Figure 7 (TCP header + GSMP message)with its description

2. Figure 6 (Generic message format) and its description.

3. Mention that for specific message types there may be additional
    fixed fields at the beginning of the "message payload" identified
    in Figure 6.

4. Following these fixed fields some message types use the following generic
    building blocks:
    a. The extension block as a combination of Figures 10 and 12
       (since they always occur together).
    b. The TLV, Figure 16, which may be used with or without an extension
       block wrapper, depending on the message type. Note also that TLVs
       may be contained in other TLVs.

Everything that follows can then refer to section 5 as necessary, rather than 
current network of cross-references.

Tom Taylor


From wdec@cisco.com  Wed Jun 23 09:17:57 2010
Return-Path: <wdec@cisco.com>
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 6AE7F3A69AA for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 09:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.854
X-Spam-Level: 
X-Spam-Status: No, score=-9.854 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 EEY0zkX43tkQ for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 09:17:56 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 298E93A6831 for <ancp@ietf.org>; Wed, 23 Jun 2010 09:17:52 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkoGANLQIUxAZnwM/2dsb2JhbACfLGsGqFiaSYUbBA
X-IronPort-AV: E=Sophos;i="4.53,468,1272844800"; d="scan'208";a="124658114"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 23 Jun 2010 16:17:59 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5NGHvKC014210 for <ancp@ietf.org>; Wed, 23 Jun 2010 16:17:59 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 18:17:51 +0200
Received: from 10.55.215.35 ([10.55.215.35]) by XMB-AMS-111.cisco.com ([144.254.74.86]) with Microsoft Exchange Server HTTP-DAV ;  Wed, 23 Jun 2010 16:17:51 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Wed, 23 Jun 2010 18:17:56 +0200
From: Wojciech Dec <wdec@cisco.com>
To: "ancp@ietf.org" <ancp@ietf.org>
Message-ID: <C8480054.4FF1%wdec@cisco.com>
Thread-Topic: IETF78 ANCP WG meeting
Thread-Index: AcsS76ODIynYh5xQSUKvIFazNCJZ0g==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2010 16:17:51.0879 (UTC) FILETIME=[A10F0170:01CB12EF]
Subject: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 16:17:57 -0000

Hi All,


We welcome requests for agenda slots at our next ANCP WG meeting in
Maastricht. Please respond with any requests.

Thanks,
Matthew & Woj


From tom111.taylor@bell.net  Wed Jun 23 09:34:24 2010
Return-Path: <tom111.taylor@bell.net>
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 D94233A6966 for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 09:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.004
X-Spam-Level: *
X-Spam-Status: No, score=1.004 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 TAhyzU1a1fBx for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 09:34:23 -0700 (PDT)
Received: from blu0-omc2-s23.blu0.hotmail.com (blu0-omc2-s23.blu0.hotmail.com [65.55.111.98]) by core3.amsl.com (Postfix) with ESMTP id 373C83A6831 for <ancp@ietf.org>; Wed, 23 Jun 2010 09:34:20 -0700 (PDT)
Received: from BLU0-SMTP62 ([65.55.111.72]) by blu0-omc2-s23.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 09:34:03 -0700
X-Originating-IP: [70.26.19.89]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP62FF1EE880E91A725EB300D8C50@phx.gbl>
Received: from [192.168.2.11] ([70.26.19.89]) by BLU0-SMTP62.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 09:34:02 -0700
Date: Wed, 23 Jun 2010 12:33:57 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Wojciech Dec <wdec@cisco.com>, ancp@ietf.org
References: <C8480054.4FF1%wdec@cisco.com>
In-Reply-To: <C8480054.4FF1%wdec@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2010 16:34:02.0872 (UTC) FILETIME=[E3D0C780:01CB12F1]
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 16:34:25 -0000

I don't see any multicast issues this time around. I'd better complete my 
update, but the document is basically ready for WGLC once that's done, I think.

I'm part-way through finishing up my review of the base protocol document. So 
far no real technical issues, just a lot of editorial comments.

Wojciech Dec wrote:
> Hi All,
> 
> 
> We welcome requests for agenda slots at our next ANCP WG meeting in
> Maastricht. Please respond with any requests.
> 
> Thanks,
> Matthew & Woj
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
> 
> 

From flefauch@cisco.com  Wed Jun 23 09:45:27 2010
Return-Path: <flefauch@cisco.com>
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 27B223A6AC3 for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 09:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.578
X-Spam-Level: 
X-Spam-Status: No, score=-6.578 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_GIF_ATTACH=1.42]
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 DS7cSPoM9Xgz for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 09:45:26 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id BE29D3A6ABE for <ancp@ietf.org>; Wed, 23 Jun 2010 09:45:25 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: None : None
X-IronPort-AV: E=Sophos;i="4.53,468,1272844800";  d="gif'147?scan'147,208,217,147";a="124670474"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 23 Jun 2010 16:45:33 +0000
Received: from ams-flefauch-8718.cisco.com (ams-flefauch-8718.cisco.com [10.55.161.201]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5NGjUrk029091; Wed, 23 Jun 2010 16:45:31 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-353-504222692
From: Francois Le Faucheur <flefauch@cisco.com>
In-Reply-To: <BLU0-SMTP62FF1EE880E91A725EB300D8C50@phx.gbl>
Date: Wed, 23 Jun 2010 18:47:29 +0200
Message-Id: <C6611251-3A8A-4CE7-A3F3-F2352F9DCDBF@cisco.com>
References: <C8480054.4FF1%wdec@cisco.com> <BLU0-SMTP62FF1EE880E91A725EB300D8C50@phx.gbl>
To: Tom Taylor <tom111.taylor@bell.net>
X-Mailer: Apple Mail (2.1081)
Cc: ancp@ietf.org
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 16:45:27 -0000

--Apple-Mail-353-504222692
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 23 Jun 2010, at 18:33, Tom Taylor wrote:

> I don't see any multicast issues this time around. I'd better complete =
my update, but the document is basically ready for WGLC once that's =
done, I think.

I thought we agreed to take on a bit of extra work to address the =
"Admitted Bandwidth Reporting" use case:
see http://www.ietf.org/mail-archive/web/ancp/current/msg01101.html

Or did you see that as part of "your update" ?

Thanks

Francois

>=20
> I'm part-way through finishing up my review of the base protocol =
document. So far no real technical issues, just a lot of editorial =
comments.
>=20
> Wojciech Dec wrote:
>> Hi All,
>> We welcome requests for agenda slots at our next ANCP WG meeting in
>> Maastricht. Please respond with any requests.
>> Thanks,
>> Matthew & Woj
>> _______________________________________________
>> 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



Francois Le Faucheur
Distinguished Engineer
Corporate Development
flefauch@cisco.com
Phone: +33 49 723 2619
Mobile: +33 6 19 98 50 90



Cisco Systems France
Greenside
400 Ave de Roumanille
06410 Sophia Antipolis
France
Cisco.com


=20

 Think before you print.

This email may contain confidential and privileged material for the sole =
use of the intended recipient. Any review, use, distribution or =
disclosure by others is strictly prohibited. If you are not the intended =
recipient (or authorized to receive for the recipient), please contact =
the sender by reply email and delete all copies of this message.

Cisco Systems France, Soci=E9t=E9 =E0 responsabiit=E9 limit=E9e, Rue =
Camille Desmoulins =96 Imm Atlantis Zac Forum Seine Ilot 7 92130 Issy =
les Moulineaux, Au capital de 91.470 =80, 349 166 561 RCS Nanterre, =
Directeur de la publication: Jean-Luc Michel Givone.

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html



--Apple-Mail-353-504222692
Content-Type: multipart/related;
	type="text/html";
	boundary=Apple-Mail-354-504222692


--Apple-Mail-354-504222692
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 23 Jun 2010, at 18:33, Tom Taylor wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>I =
don't see any multicast issues this time around. I'd better complete my =
update, but the document is basically ready for WGLC once that's done, I =
think.<br></div></blockquote><div><br></div><div>I thought we agreed to =
take on a bit of extra work to address the "Admitted Bandwidth =
Reporting" use case:</div><div>see&nbsp;<a =
href=3D"http://www.ietf.org/mail-archive/web/ancp/current/msg01101.html">h=
ttp://www.ietf.org/mail-archive/web/ancp/current/msg01101.html</a></div><d=
iv><br></div><div>Or did you see that as part of "your update" =
?</div><div><br></div><div>Thanks</div><div><br></div><div>Francois</div><=
br><blockquote type=3D"cite"><div><br>I'm part-way through finishing up =
my review of the base protocol document. So far no real technical =
issues, just a lot of editorial comments.<br><br>Wojciech Dec =
wrote:<br><blockquote type=3D"cite">Hi All,<br></blockquote><blockquote =
type=3D"cite">We welcome requests for agenda slots at our next ANCP WG =
meeting in<br></blockquote><blockquote type=3D"cite">Maastricht. Please =
respond with any requests.<br></blockquote><blockquote =
type=3D"cite">Thanks,<br></blockquote><blockquote type=3D"cite">Matthew =
&amp; Woj<br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">ANCP mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br></blockquote><blockquot=
e type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><br></blockquote>_________________________________=
______________<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></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<div><table width=3D"543" border=3D"0" cellpadding=3D"0" cellspacing=3D"0"=
 style=3D"font-family: Times; "><tbody><tr><td><span><img height=3D"73" =
width=3D"110" id=3D"a11598ca-7c8b-490c-af66-e6b3727e20ec" =
apple-width=3D"yes" apple-height=3D"yes" =
src=3D"cid:B6233B58-6B62-4B4F-AF7B-B5B6E5797A0A@cisco.com"></span><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: medium; 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: 0px; "><span class=3D"Apple-style-span" =
style=3D"font-family: Times; "></span></span><table width=3D"543" =
border=3D"0" cellpadding=3D"0" cellspacing=3D"0" =
style=3D"background-image: =
url(http://www.cisco.com/global/EMEA/brand/signature/corporate/none.jpg); =
background-attachment: initial; -webkit-background-clip: initial; =
-webkit-background-origin: initial; background-color: initial; =
background-repeat: no-repeat; background-position: 50% 0%; =
"><tbody><tr></tr></tbody></table><table width=3D"543" border=3D"0" =
cellpadding=3D"0" cellspacing=3D"0" style=3D"background-image: =
url(http://www.cisco.com/global/EMEA/brand/signature/corporate/none.jpg); =
background-attachment: initial; -webkit-background-clip: initial; =
-webkit-background-origin: initial; background-color: initial; =
background-repeat: no-repeat; background-position: 50% 0%; =
"><tbody><tr><td valign=3D"top" align=3D"left" nowrap=3D"nowrap" =
style=3D"padding-left: 24px; padding-bottom: 15px; "><p =
style=3D"font-family: Arial, Helvetica, sans-serif; font-size: 11px; =
font-weight: normal; color: rgb(102, 102, 102); "><strong><br =
class=3D"Apple-interchange-newline">Francois Le =
Faucheur</strong><br><strong>Distinguished =
Engineer</strong><br><strong>Corporate Development</strong><br><a =
href=3D"mailto:flefauch@cisco.com" style=3D"color: rgb(102, 102, 102); =
">flefauch@cisco.com</a><br>Phone:&nbsp;<strong>+33 49 723 =
2619</strong><br>Mobile:&nbsp;<strong>+33 6 19 98 50 =
90</strong><br><br><br></p></td><td valign=3D"top" nowrap=3D"nowrap" =
style=3D"padding-left: 20px; padding-bottom: 10px; "><p =
style=3D"font-family: Arial, Helvetica, sans-serif; font-size: 11px; =
font-weight: normal; color: rgb(102, 102, 102); "><strong>Cisco Systems =
France</strong><br>Greenside<br>400 Ave de Roumanille<br>06410 Sophia =
Antipolis<br>France<br><a href=3D"http://www.cisco.com" style=3D"color: =
rgb(102, 102, 102); ">Cisco.com</a><br><br></p></td><td =
width=3D"200">&nbsp;</td></tr></tbody></table><span><img height=3D"19" =
width=3D"18" id=3D"bb0f1a7e-d704-4af5-b471-ee16aa6664b7" =
apple-width=3D"yes" apple-height=3D"yes" =
src=3D"cid:EA80D384-C41E-4B98-81FE-095B29784C9D@cisco.com"></span><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: medium; 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: 0px; "><span class=3D"Apple-style-span" =
style=3D"font-family: Times; "></span></span><table width=3D"400" =
border=3D"0" cellpadding=3D"0" cellspacing=3D"0"><tbody><tr></tr><tr><td =
style=3D"font-family: Arial, Helvetica, sans-serif; font-size: 10px; =
padding-left: 24px; padding-right: 24px; padding-top: 0px; =
padding-bottom: 0px; color: rgb(0, 153, 0); ">&nbsp;Think before you =
print.</td></tr><tr><td style=3D"font-family: Arial, Helvetica, =
sans-serif; font-size: 10px; color: rgb(153, 153, 153); padding-left: =
24px; padding-right: 24px; padding-top: 7px; padding-bottom: 6px; =
"><br>This email may contain confidential and privileged material for =
the sole use of the intended recipient. Any review, use, distribution or =
disclosure by others is strictly prohibited. If you are not the intended =
recipient (or authorized to receive for the recipient), please contact =
the sender by reply email and delete all copies of this =
message.<br><br>Cisco Systems France, Soci=E9t=E9 =E0 responsabiit=E9 =
limit=E9e, Rue Camille Desmoulins =96 Imm Atlantis Zac Forum Seine Ilot =
7 92130 Issy les Moulineaux, Au capital de 91.470 =80, 349 166 561 RCS =
Nanterre, Directeur de la publication: Jean-Luc Michel =
Givone.<br><br>For corporate legal information go to:<br><a =
href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.html=
">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a><b=
r><br></td></tr>

</tbody></table></td></tr></tbody></table></div></div><br></body></html>=

--Apple-Mail-354-504222692
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename=logo.gif
Content-Type: image/gif;
	name="logo.gif"
Content-Id: <B6233B58-6B62-4B4F-AF7B-B5B6E5797A0A@cisco.com>

R0lGODlhbgBJAMQAAP///3OXqtapqq1MTcmRki9mgZkAALpqbMl/f6g5O/Xq6+vX2OTIyaMqK/nz
9OW/v5sVFsbV3Nfh5p0PD5kFBf78/P38/Pz6+v/+/rZdXpcKDKAhIvv396QvMO/g4Ny4uSH5BAAA
AAAALAAAAABuAEkAQAX/ICCOZGmeaKqubOu+cCzPdG3feK6nkln8pp5LSPoVgrucsbQsAp1HKPM5
alapImtyy+16SwKDmJBCiBEWgMUsPgg8JMHEQCGTMACP2HDgiBQZYglfOQ+GDy2HhiqKKI2EkJGS
k5SVlpeYmZpfWkpYmypEV1GjU6QjolmfnZ0AqZWvrj6fski2UiWxsZkcHxkNYg0IABUibAjFIgsH
wAYNBwokvb8QEMIOJAwICQYQCQgLoCgLHWIdHwoKCwzExmdpGBwcxRgDYhkXAOTm6OoMfg4CiRGg
wAOBOXzEKVzIsKHDhxAjSpxIsaKNCAEibMGo0WKLVjdAVgxQIICpEiRN/7JIeZIEy4WsVsk8BSAm
TZstLb0csVMVzZ4AgALtJLQkRY4bM3pcupDAHgMduA1Q484AGmJO7x04kCCaCAIaxFCISmGAVwZP
u+1pEK5hVgPYUBxLQ4yBvacfvlIwMCFuCbRi2I34sHfDQ0BpDUyFNxfABTZPGwgGACjsU7MiLLx9
ukEA08+gQ4seTbq06dOoU6tezbq169evd92QHRooDtujRdbQDZr3DN8RkeIaIXxFcZ8ljkPEOVwF
81ILlT9HTkL6zJwilE+aXvN68+43vUO3xL28eOrj0VdSbp0me6XV4acH8L6jRNw28IumXYM/7P8k
PJLIISkIWIKBD3GwmcIYiwGAQWP6cJMWHCIoCEFamInwQTNPdYCIQwqUM8YCC3zgWTKNOXAAg14p
kA9lIkJAAIkmYsPBim0YcsBeVjn0llcnQAjYHh14phdfQGazx2QAEGaAYQ2FMVAZ75BggTZ7HFCM
HHQYWcICeyAjgormPASZYgN00CAAjV0gwAEEEACZlsbwCMEAaWb4wFMJJMDjBkwypAABErbRzoNn
FFPBghnkRcKgCVimwQF+VSDAXXw1CuCmnHbq6aeghirqqDiEAAA7

--Apple-Mail-354-504222692
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename=green.gif
Content-Type: image/gif;
	name="green.gif"
Content-Id: <EA80D384-C41E-4B98-81FE-095B29784C9D@cisco.com>

R0lGODlhEgATAJEAAAAAAP///wCZAP///yH5BAEAAAMALAAAAAASABMAAAIojI+pGyK8nINqUiTf
bVnfvHEg1UmhdZRqaawu6XZVjKb0/CYxo8JOAQA7

--Apple-Mail-354-504222692--

--Apple-Mail-353-504222692--

From tom111.taylor@bell.net  Wed Jun 23 10:51:35 2010
Return-Path: <tom111.taylor@bell.net>
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 E30F23A6AEA for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 10:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.968
X-Spam-Level: 
X-Spam-Status: No, score=0.968 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 q2N8aYnm1Um2 for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 10:51:34 -0700 (PDT)
Received: from blu0-omc2-s23.blu0.hotmail.com (blu0-omc2-s23.blu0.hotmail.com [65.55.111.98]) by core3.amsl.com (Postfix) with ESMTP id EA2063A6AE6 for <ancp@ietf.org>; Wed, 23 Jun 2010 10:51:33 -0700 (PDT)
Received: from BLU0-SMTP95 ([65.55.111.71]) by blu0-omc2-s23.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 10:51:41 -0700
X-Originating-IP: [70.26.19.89]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP9520921594237DED490AD0D8C50@phx.gbl>
Received: from [192.168.2.11] ([70.26.19.89]) by BLU0-SMTP95.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 10:51:41 -0700
Date: Wed, 23 Jun 2010 13:51:37 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Francois Le Faucheur <flefauch@cisco.com>
References: <C8480054.4FF1%wdec@cisco.com> <BLU0-SMTP62FF1EE880E91A725EB300D8C50@phx.gbl> <C6611251-3A8A-4CE7-A3F3-F2352F9DCDBF@cisco.com>
In-Reply-To: <C6611251-3A8A-4CE7-A3F3-F2352F9DCDBF@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2010 17:51:41.0669 (UTC) FILETIME=[BCACC950:01CB12FC]
Cc: ancp@ietf.org
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 17:51:35 -0000

Yes, that is part of the update.

Francois Le Faucheur wrote:
> On 23 Jun 2010, at 18:33, Tom Taylor wrote:
> 
>> I don't see any multicast issues this time around. I'd better complete my 
>> update, but the document is basically ready for WGLC once that's done, I think.
> 
> I thought we agreed to take on a bit of extra work to address the "Admitted 
> Bandwidth Reporting" use case:
> see http://www.ietf.org/mail-archive/web/ancp/current/msg01101.html
> 
> Or did you see that as part of "your update" ?
> 
> Thanks
> 
> Francois
> 
...

From hormuzd.m.khosravi@intel.com  Wed Jun 23 10:52:54 2010
Return-Path: <hormuzd.m.khosravi@intel.com>
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 BE3893A68BD for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 10:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.378
X-Spam-Level: 
X-Spam-Status: No, score=-4.378 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, RCVD_IN_DNSWL_MED=-4, TVD_SPACE_RATIO=2.219]
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 l5A-JBnXTBw7 for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 10:52:54 -0700 (PDT)
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by core3.amsl.com (Postfix) with ESMTP id 1968A3A6ABC for <ANCP@ietf.org>; Wed, 23 Jun 2010 10:52:51 -0700 (PDT)
Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP; 23 Jun 2010 10:52:30 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.53,468,1272870000";  d="scan'208,217";a="810813166"
Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by fmsmga001.fm.intel.com with ESMTP; 23 Jun 2010 10:52:56 -0700
Received: from orsmsx606.amr.corp.intel.com (10.22.226.128) by orsmsx602.amr.corp.intel.com (10.22.226.211) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 23 Jun 2010 10:52:58 -0700
Received: from orsmsx502.amr.corp.intel.com ([10.22.226.210]) by orsmsx606.amr.corp.intel.com ([10.22.226.128]) with mapi; Wed, 23 Jun 2010 10:52:58 -0700
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: "ANCP@ietf.org" <ANCP@ietf.org>
Date: Wed, 23 Jun 2010 10:52:46 -0700
Thread-Topic: unsubscribe
Thread-Index: AcsS/OMVSpgsfOoCTMiraACR50+hPQ==
Message-ID: <4C5E6457CD7911469A07260381288C28AECFF031@orsmsx502.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_4C5E6457CD7911469A07260381288C28AECFF031orsmsx502amrcor_"
MIME-Version: 1.0
Subject: [ANCP] unsubscribe
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 17:52:54 -0000

--_000_4C5E6457CD7911469A07260381288C28AECFF031orsmsx502amrcor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

unsubscribe

--_000_4C5E6457CD7911469A07260381288C28AECFF031orsmsx502amrcor_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>unsubscribe<o:p></o:p></p>

</div>

</body>

</html>

--_000_4C5E6457CD7911469A07260381288C28AECFF031orsmsx502amrcor_--

From kristian.poscic@alcatel-lucent.com  Wed Jun 23 11:28:36 2010
Return-Path: <kristian.poscic@alcatel-lucent.com>
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 B60333A6AF4 for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 11:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 XnCeXKSoDnDv for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 11:28:35 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id C842E3A6AEB for <ancp@ietf.org>; Wed, 23 Jun 2010 11:28:35 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id o5NIRw6i017604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jun 2010 13:27:58 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o5NIRvGL028798; Wed, 23 Jun 2010 13:27:58 -0500
Received: from USNAVSXCHMBSC3.ndc.alcatel-lucent.com ([135.3.39.146]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Wed, 23 Jun 2010 13:27:54 -0500
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: Wojciech Dec <wdec@cisco.com>, "ancp@ietf.org" <ancp@ietf.org>
Date: Wed, 23 Jun 2010 13:27:49 -0500
Thread-Topic: IETF78 ANCP WG meeting
Thread-Index: AcsS76ODIynYh5xQSUKvIFazNCJZ0gAET7rg
Message-ID: <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
References: <C8480054.4FF1%wdec@cisco.com>
In-Reply-To: <C8480054.4FF1%wdec@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 18:28:36 -0000

Hi there -=20
A quick question. In ANCP protocol draft there are some Target TLVs defined=
 but are mostly used for DSLAMs.=20
How can I use a Target tlv for example for GPONs?


Let say that I need to submit a certain request from the NAS to the OLT, an=
d that I need to address:
- uplink from the OLT towards the NAS
- or a particular PON port (slot 1/ port 1)
- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)


Do we have provisions for this in any of the ANCP drafts?
Thanks,
Kris


-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec
Sent: Wednesday, June 23, 2010 9:18 AM
To: ancp@ietf.org
Subject: [ANCP] IETF78 ANCP WG meeting

Hi All,


We welcome requests for agenda slots at our next ANCP WG meeting in
Maastricht. Please respond with any requests.

Thanks,
Matthew & Woj

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

From tom111.taylor@bell.net  Wed Jun 23 12:01:42 2010
Return-Path: <tom111.taylor@bell.net>
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 7B9D43A6ABF for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 12:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.954
X-Spam-Level: 
X-Spam-Status: No, score=0.954 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 hUta9PW1z37F for <ancp@core3.amsl.com>; Wed, 23 Jun 2010 12:01:41 -0700 (PDT)
Received: from bay0-omc1-s21.bay0.hotmail.com (bay0-omc1-s21.bay0.hotmail.com [65.54.190.32]) by core3.amsl.com (Postfix) with ESMTP id AF0C03A6963 for <ancp@ietf.org>; Wed, 23 Jun 2010 12:01:30 -0700 (PDT)
Received: from BLU0-SMTP14.blu0.hotmail.com ([65.54.190.61]) by bay0-omc1-s21.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 23 Jun 2010 12:01:38 -0700
Received: from mail pickup service by BLU0-SMTP14.blu0.hotmail.com with Microsoft SMTPSVC; Wed, 23 Jun 2010 12:01:38 -0700
X-Originating-IP: [70.26.17.94]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP146CA753275332FF32E01ED8C50@phx.gbl>
Received: from [192.168.2.11] ([70.26.17.94]) by BLU0-SMTP14.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 12:01:35 -0700
Date: Wed, 23 Jun 2010 15:01:31 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
References: <C8480054.4FF1%wdec@cisco.com> <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
In-Reply-To: <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Jun 2010 19:01:35.0863 (UTC) FILETIME=[809C0070:01CB1306]
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Wed, 23 Jun 2010 19:01:42 -0000

That's going to take an extension, presumably in the PON-related draft(s).

Poscic, Kristian (Kristian) wrote:
> Hi there - 
> A quick question. In ANCP protocol draft there are some Target TLVs defined but are mostly used for DSLAMs. 
> How can I use a Target tlv for example for GPONs?
> 
> 
> Let say that I need to submit a certain request from the NAS to the OLT, and that I need to address:
> - uplink from the OLT towards the NAS
> - or a particular PON port (slot 1/ port 1)
> - or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)
> 
> 
> Do we have provisions for this in any of the ANCP drafts?
> Thanks,
> Kris
> 
> 
> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec
> Sent: Wednesday, June 23, 2010 9:18 AM
> To: ancp@ietf.org
> Subject: [ANCP] IETF78 ANCP WG meeting
> 
> Hi All,
> 
> 
> We welcome requests for agenda slots at our next ANCP WG meeting in
> Maastricht. Please respond with any requests.
> 
> Thanks,
> Matthew & Woj
> 
> _______________________________________________
> 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 wdec@cisco.com  Thu Jun 24 01:19:52 2010
Return-Path: <wdec@cisco.com>
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 DA6BB3A67F0 for <ancp@core3.amsl.com>; Thu, 24 Jun 2010 01:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.495
X-Spam-Level: 
X-Spam-Status: No, score=-8.495 tagged_above=-999 required=5 tests=[AWL=-1.360, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 Uaf7BRuOCOz7 for <ancp@core3.amsl.com>; Thu, 24 Jun 2010 01:19:51 -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 124003A694E for <ancp@ietf.org>; Thu, 24 Jun 2010 01:19:50 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8GAKGxIkyrR7Ht/2dsb2JhbACBQ50YWAJxpVeaR4UbBI1h
X-IronPort-AV: E=Sophos;i="4.53,472,1272844800";  d="scan'208,217";a="216999693"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 24 Jun 2010 08:19:56 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5O8JNMx003100; Thu, 24 Jun 2010 08:19:56 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 24 Jun 2010 10:19:55 +0200
Received: from 144.254.204.74 ([144.254.204.74]) by XMB-AMS-111.cisco.com ([144.254.74.86]) with Microsoft Exchange Server HTTP-DAV ;  Thu, 24 Jun 2010 08:19:55 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Thu, 24 Jun 2010 10:20:01 +0200
From: Wojciech Dec <wdec@cisco.com>
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>, <ancp@ietf.org>
Message-ID: <C848E1D1.505D%wdec@cisco.com>
Thread-Topic: [ANCP] IETF78 ANCP WG meeting
Thread-Index: AcsS76ODIynYh5xQSUKvIFazNCJZ0gAET7rgAB1J+G8=
In-Reply-To: <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3360219602_8980366"
X-OriginalArrivalTime: 24 Jun 2010 08:19:55.0427 (UTC) FILETIME=[06F96F30:01CB1376]
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Thu, 24 Jun 2010 08:19:53 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3360219602_8980366
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Kristian,

That is something waiting to be defined, and we welcome your
proposals/drafts. We have accepted a WG draft to look at GPON extensions,
but this one is still in early phases:
http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03

Regards,
Woj.


On 23/06/2010 20:27, "Poscic, Kristian (Kristian)"
<kristian.poscic@alcatel-lucent.com> wrote:

> Hi there -
> A quick question. In ANCP protocol draft there are some Target TLVs defined
> but are mostly used for DSLAMs.
> How can I use a Target tlv for example for GPONs?
> 
> 
> Let say that I need to submit a certain request from the NAS to the OLT, and
> that I need to address:
> - uplink from the OLT towards the NAS
> - or a particular PON port (slot 1/ port 1)
> - or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)
> 
> 
> Do we have provisions for this in any of the ANCP drafts?
> Thanks,
> Kris
> 
> 
> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
> Wojciech Dec
> Sent: Wednesday, June 23, 2010 9:18 AM
> To: ancp@ietf.org
> Subject: [ANCP] IETF78 ANCP WG meeting
> 
> Hi All,
> 
> 
> We welcome requests for agenda slots at our next ANCP WG meeting in
> Maastricht. Please respond with any requests.
> 
> Thanks,
> Matthew & Woj
> 
> _______________________________________________
> 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
> 


--B_3360219602_8980366
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [ANCP] IETF78 ANCP WG meeting</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Hi Kristian,<BR>
<BR>
That is something waiting to be defined, and we welcome your proposals/draf=
ts. We have accepted a WG draft to look at GPON extensions, but this one is =
still in early phases:<BR>
<a href=3D"http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03">http://=
tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03</a><BR>
<BR>
Regards,<BR>
Woj.<BR>
<BR>
<BR>
On 23/06/2010 20:27, &quot;Poscic, Kristian (Kristian)&quot; &lt;<a href=3D"k=
ristian.poscic@alcatel-lucent.com">kristian.poscic@alcatel-lucent.com</a>&gt=
; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>Hi there -<BR>
A quick question. In ANCP protocol draft there are some Target TLVs defined=
 but are mostly used for DSLAMs.<BR>
How can I use a Target tlv for example for GPONs?<BR>
<BR>
<BR>
Let say that I need to submit a certain request from the NAS to the OLT, an=
d that I need to address:<BR>
- uplink from the OLT towards the NAS<BR>
- or a particular PON port (slot 1/ port 1)<BR>
- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)<=
BR>
<BR>
<BR>
Do we have provisions for this in any of the ANCP drafts?<BR>
Thanks,<BR>
Kris<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: <a href=3D"ancp-bounces@ietf.org">ancp-bounces@ietf.org</a> [<a href=3D"m=
ailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</a>] On Behalf Of =
Wojciech Dec<BR>
Sent: Wednesday, June 23, 2010 9:18 AM<BR>
To: <a href=3D"ancp@ietf.org">ancp@ietf.org</a><BR>
Subject: [ANCP] IETF78 ANCP WG meeting<BR>
<BR>
Hi All,<BR>
<BR>
<BR>
We welcome requests for agenda slots at our next ANCP WG meeting in<BR>
Maastricht. Please respond with any requests.<BR>
<BR>
Thanks,<BR>
Matthew &amp; Woj<BR>
<BR>
_______________________________________________<BR>
ANCP mailing list<BR>
<a href=3D"ANCP@ietf.org">ANCP@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><BR>
_______________________________________________<BR>
ANCP mailing list<BR>
<a href=3D"ANCP@ietf.org">ANCP@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/m=
ailman/listinfo/ancp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3360219602_8980366--


From lihy@huawei.com  Thu Jun 24 18:39:15 2010
Return-Path: <lihy@huawei.com>
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 51F383A677D for <ancp@core3.amsl.com>; Thu, 24 Jun 2010 18:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[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 SI2Fj5hGKamG for <ancp@core3.amsl.com>; Thu, 24 Jun 2010 18:39:14 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 01F5F3A68A5 for <ancp@ietf.org>; Thu, 24 Jun 2010 18:39:14 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4J0093NR9AHX@szxga05-in.huawei.com> for ancp@ietf.org; Fri, 25 Jun 2010 09:39:10 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4J00E65R9ADA@szxga05-in.huawei.com> for ancp@ietf.org; Fri, 25 Jun 2010 09:39:10 +0800 (CST)
Received: from l00150618 ([10.70.40.85]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4J003FHR95F0@szxml04-in.huawei.com> for ancp@ietf.org; Fri, 25 Jun 2010 09:39:10 +0800 (CST)
Date: Fri, 25 Jun 2010 09:39:05 +0800
From: Hongyu Li <lihy@huawei.com>
In-reply-to: <C848E1D1.505D%wdec@cisco.com>
To: 'Wojciech Dec' <wdec@cisco.com>, "'Poscic, Kristian (Kristian)'" <kristian.poscic@alcatel-lucent.com>, ancp@ietf.org
Message-id: <0BFE41237CD6431FBB75C15FC7AED927@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_rrcU4dLLvK1YJSEw5DLRLw)"
Thread-index: AcsS76ODIynYh5xQSUKvIFazNCJZ0gAET7rgAB1J+G8AJAIHUA==
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Jun 2010 01:39:15 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_rrcU4dLLvK1YJSEw5DLRLw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi all,
 
IMHO, this draft
<http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03>
http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03 covers PON
framework, but multicast AC takes half weight of the full contents, which
could be applied to both DSL and PON. Therefore, I would suggest split this
draft into two, one for PON and one for multicast AC.
 
cheers,
Hongyu



  _____  

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec
Sent: Thursday, June 24, 2010 4:20 PM
To: Poscic, Kristian (Kristian); ancp@ietf.org
Subject: Re: [ANCP] IETF78 ANCP WG meeting


Hi Kristian,

That is something waiting to be defined, and we welcome your
proposals/drafts. We have accepted a WG draft to look at GPON extensions,
but this one is still in early phases:
http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03

Regards,
Woj.


On 23/06/2010 20:27, "Poscic, Kristian (Kristian)"
<kristian.poscic@alcatel-lucent.com> wrote:



Hi there -
A quick question. In ANCP protocol draft there are some Target TLVs defined
but are mostly used for DSLAMs.
How can I use a Target tlv for example for GPONs?


Let say that I need to submit a certain request from the NAS to the OLT, and
that I need to address:
- uplink from the OLT towards the NAS
- or a particular PON port (slot 1/ port 1)
- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)


Do we have provisions for this in any of the ANCP drafts?
Thanks,
Kris


-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec
Sent: Wednesday, June 23, 2010 9:18 AM
To: ancp@ietf.org
Subject: [ANCP] IETF78 ANCP WG meeting

Hi All,


We welcome requests for agenda slots at our next ANCP WG meeting in
Maastricht. Please respond with any requests.

Thanks,
Matthew & Woj

_______________________________________________
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_rrcU4dLLvK1YJSEw5DLRLw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [ANCP] IETF78 ANCP WG meeting</TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18904"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff face=Corbel><SPAN 
class=218023101-25062010>Hi all,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff face=Corbel><SPAN 
class=218023101-25062010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=ltr align=left><FONT color=#0000ff face=Corbel><SPAN 
class=218023101-25062010>IMHO, this draft <A 
href="http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03"><FONT 
face=Calibri>http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03</FONT></A>&nbsp;covers 
PON framework, but multicast AC takes half weight of the full contents, which 
could be applied to both DSL and PON. Therefore, I would suggest split this 
draft into two, one for PON and one for multicast AC.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Corbel><SPAN 
class=218023101-25062010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Corbel><SPAN 
class=218023101-25062010>cheers,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Corbel><SPAN class=218023101-25062010>Hongyu</DIV>
<DIV dir=ltr align=left><BR></DIV></SPAN></FONT><BR>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px" 
dir=ltr>
  <DIV dir=ltr lang=zh-cn class=OutlookMessageHeader align=left>
  <HR tabIndex=-1>
  <FONT size=2 face=Tahoma><B>From:</B> ancp-bounces@ietf.org 
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech 
  Dec<BR><B>Sent:</B> Thursday, June 24, 2010 4:20 PM<BR><B>To:</B> Poscic, 
  Kristian (Kristian); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] IETF78 ANCP 
  WG meeting<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face="Calibri, Verdana, Helvetica, Arial"><SPAN 
  style="FONT-SIZE: 11pt">Hi Kristian,<BR><BR>That is something waiting to be 
  defined, and we welcome your proposals/drafts. We have accepted a WG draft to 
  look at GPON extensions, but this one is still in early phases:<BR><A 
  href="http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03">http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03</A><BR><BR>Regards,<BR>Woj.<BR><BR><BR>On 
  23/06/2010 20:27, "Poscic, Kristian (Kristian)" &lt;<A 
  href="kristian.poscic@alcatel-lucent.com">kristian.poscic@alcatel-lucent.com</A>&gt; 
  wrote:<BR><BR></SPAN></FONT>
  <BLOCKQUOTE><FONT face="Calibri, Verdana, Helvetica, Arial"><SPAN 
    style="FONT-SIZE: 11pt">Hi there -<BR>A quick question. In ANCP protocol 
    draft there are some Target TLVs defined but are mostly used for 
    DSLAMs.<BR>How can I use a Target tlv for example for GPONs?<BR><BR><BR>Let 
    say that I need to submit a certain request from the NAS to the OLT, and 
    that I need to address:<BR>- uplink from the OLT towards the NAS<BR>- or a 
    particular PON port (slot 1/ port 1)<BR>- or maybe even a particular 
    subscriber on the OLT (slot 1, port 1, GEM 1)<BR><BR><BR>Do we have 
    provisions for this in any of the ANCP 
    drafts?<BR>Thanks,<BR>Kris<BR><BR><BR>-----Original Message-----<BR>From: <A 
    href="ancp-bounces@ietf.org">ancp-bounces@ietf.org</A> [<A 
    href="mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>] On 
    Behalf Of Wojciech Dec<BR>Sent: Wednesday, June 23, 2010 9:18 AM<BR>To: <A 
    href="ancp@ietf.org">ancp@ietf.org</A><BR>Subject: [ANCP] IETF78 ANCP WG 
    meeting<BR><BR>Hi All,<BR><BR><BR>We welcome requests for agenda slots at 
    our next ANCP WG meeting in<BR>Maastricht. Please respond with any 
    requests.<BR><BR>Thanks,<BR>Matthew &amp; 
    Woj<BR><BR>_______________________________________________<BR>ANCP mailing 
    list<BR><A href="ANCP@ietf.org">ANCP@ietf.org</A><BR><A 
    href="https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/mailman/listinfo/ancp</A><BR>_______________________________________________<BR>ANCP 
    mailing list<BR><A href="ANCP@ietf.org">ANCP@ietf.org</A><BR><A 
    href="https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/mailman/listinfo/ancp</A><BR><BR></SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_rrcU4dLLvK1YJSEw5DLRLw)--

From HaagT@telekom.de  Fri Jun 25 01:31:14 2010
Return-Path: <HaagT@telekom.de>
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 F04233A67B2 for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 01:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level: 
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 yMoz8OBmiUHx for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 01:31:00 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id CD7C33A6846 for <ancp@ietf.org>; Fri, 25 Jun 2010 01:30:57 -0700 (PDT)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail71.telekom.de with ESMTP; 25 Jun 2010 10:30:57 +0200
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 25 Jun 2010 10:30:25 +0200
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB1440.A890840B"
Date: Fri, 25 Jun 2010 10:30:24 +0200
Message-ID: <5661758E3E93364685B91DD8272F2876031800BC@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <0BFE41237CD6431FBB75C15FC7AED927@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] IETF78 ANCP WG meeting
Thread-Index: AcsS76ODIynYh5xQSUKvIFazNCJZ0gAET7rgAB1J+G8AJAIHUAANhZbA
References: <C848E1D1.505D%wdec@cisco.com> <0BFE41237CD6431FBB75C15FC7AED927@china.huawei.com>
From: <HaagT@telekom.de>
To: <lihy@huawei.com>, <wdec@cisco.com>, <kristian.poscic@alcatel-lucent.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 25 Jun 2010 08:30:25.0263 (UTC) FILETIME=[A8CC87F0:01CB1440]
Cc: B.Witschurke@telekom.de
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Jun 2010 08:31:15 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB1440.A890840B
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
>From my understanding ancp-framework, ancp-protocol + multicast
extension address four use cases.
=20
Looking to GPON we currently have only one draft which addresses
multicast mainly. In section 2 "Introduction" is stated:
=20
..."The focus in this document will be on the ANCP requirements needed
for coordinated admission control of unicast and multicast video in FTTP
PON environments
between the AN complex and the NAS, specifically focusing on bandwidth
dedicated for multicast and shared bandwidth between multicast and
unicast."...
=20
Considering the structure of that draft it implies that all use cases
are adressed. But I think it's not described in details that it can be
used for protocol development. Also document structure and introduction
have some differences.
=20
I think it would be useful  to update current PON draft by using similar
structure as used in protocol draft and elaborate TLVs which are PON
specific (e.g. for FTTH deployment) and adopt TLVs already covered (e.g.
to be used in FTTC/B deployment).
=20
Regards
=20
Thomas
=20

________________________________

Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von
Hongyu Li
Gesendet: Freitag, 25. Juni 2010 03:39
An: 'Wojciech Dec'; 'Poscic, Kristian (Kristian)'; ancp@ietf.org
Betreff: Re: [ANCP] IETF78 ANCP WG meeting


Hi all,
=20
IMHO, this draft
http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03
<http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03>  covers PON
framework, but multicast AC takes half weight of the full contents,
which could be applied to both DSL and PON. Therefore, I would suggest
split this draft into two, one for PON and one for multicast AC.
=20
cheers,
Hongyu



________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec
	Sent: Thursday, June 24, 2010 4:20 PM
	To: Poscic, Kristian (Kristian); ancp@ietf.org
	Subject: Re: [ANCP] IETF78 ANCP WG meeting
=09
=09
	Hi Kristian,
=09
	That is something waiting to be defined, and we welcome your
proposals/drafts. We have accepted a WG draft to look at GPON
extensions, but this one is still in early phases:
	http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03
=09
	Regards,
	Woj.
=09
=09
	On 23/06/2010 20:27, "Poscic, Kristian (Kristian)"
<kristian.poscic@alcatel-lucent.com> wrote:
=09
=09

		Hi there -
		A quick question. In ANCP protocol draft there are some
Target TLVs defined but are mostly used for DSLAMs.
		How can I use a Target tlv for example for GPONs?
	=09
	=09
		Let say that I need to submit a certain request from the
NAS to the OLT, and that I need to address:
		- uplink from the OLT towards the NAS
		- or a particular PON port (slot 1/ port 1)
		- or maybe even a particular subscriber on the OLT (slot
1, port 1, GEM 1)
	=09
	=09
		Do we have provisions for this in any of the ANCP
drafts?
		Thanks,
		Kris
	=09
	=09
		-----Original Message-----
		From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec
		Sent: Wednesday, June 23, 2010 9:18 AM
		To: ancp@ietf.org
		Subject: [ANCP] IETF78 ANCP WG meeting
	=09
		Hi All,
	=09
	=09
		We welcome requests for agenda slots at our next ANCP WG
meeting in
		Maastricht. Please respond with any requests.
	=09
		Thanks,
		Matthew & Woj
	=09
		_______________________________________________
		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
	=09
	=09


------_=_NextPart_001_01CB1440.A890840B
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [ANCP] IETF78 ANCP WG meeting</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3676" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi all,</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><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>From my understanding ancp-framework, =
</FONT></SPAN><SPAN=20
class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =
size=3D2>ancp-protocol +=20
<SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =
size=3D2>multicast=20
extension </FONT></SPAN>address four use cases.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Looking to GPON we currently have only one =
draft which=20
addresses multicast mainly. In section 2 "Introduction" is=20
stated:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>..."The focus in this document will be on the =
ANCP=20
requirements needed for coordinated admission control of unicast and =
multicast=20
video in FTTP PON environments<BR>between the AN complex and the NAS,=20
specifically focusing on bandwidth dedicated for multicast and shared =
bandwidth=20
between multicast and unicast."...</FONT></SPAN></DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =

size=3D2>Considering the structure of that draft it implies that all use =
cases are=20
adressed. But I think it's not described in details that it can be used =
for=20
protocol development. Also document structure and introduction have some =

differences.</FONT></SPAN></DIV>
<DIV><SPAN class=3D644125807-25062010></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
think it&nbsp;would be useful&nbsp;</FONT>&nbsp;<FONT face=3DArial =
color=3D#0000ff=20
size=3D2>to u</FONT></SPAN><SPAN class=3D644125807-25062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>pdate current PON draft by using similar =
structure as used=20
in protocol draft and&nbsp;e</FONT></SPAN><SPAN =
class=3D644125807-25062010><FONT=20
face=3DArial color=3D#0000ff size=3D2>laborate TLVs which are PON =
specific (e.g. for=20
FTTH deployment) and adopt TLVs&nbsp;already covered (e.g. to be used in =
FTTC/B=20
deployment).</FONT></SPAN></DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D644125807-25062010><FONT face=3DArial color=3D#0000ff =

size=3D2>Thomas</FONT></SPAN></DIV>
<DIV>&nbsp;</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>Hongyu=20
Li<BR><B>Gesendet:</B> Freitag, 25. Juni 2010 03:39<BR><B>An:</B> =
'Wojciech=20
Dec'; 'Poscic, Kristian (Kristian)'; ancp@ietf.org<BR><B>Betreff:</B> =
Re: [ANCP]=20
IETF78 ANCP WG meeting<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCorbel color=3D#0000ff><SPAN=20
class=3D218023101-25062010>Hi all,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCorbel color=3D#0000ff><SPAN=20
class=3D218023101-25062010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DCorbel color=3D#0000ff><SPAN=20
class=3D218023101-25062010>IMHO, this draft <A=20
href=3D"http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03"><FONT =

face=3DCalibri>http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03<=
/FONT></A>&nbsp;covers=20
PON framework, but multicast AC takes half weight of the full contents, =
which=20
could be applied to both DSL and PON. Therefore, I would suggest split =
this=20
draft into two, one for PON and one for multicast =
AC.</SPAN></FONT></DIV>
<DIV><FONT face=3DCorbel color=3D#0000ff><SPAN=20
class=3D218023101-25062010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCorbel color=3D#0000ff><SPAN=20
class=3D218023101-25062010>cheers,</SPAN></FONT></DIV>
<DIV><FONT face=3DCorbel color=3D#0000ff><SPAN =
class=3D218023101-25062010>Hongyu</DIV>
<DIV dir=3Dltr align=3Dleft><BR></DIV></SPAN></FONT><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=3Dzh-cn 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>Wojciech=20
  Dec<BR><B>Sent:</B> Thursday, June 24, 2010 4:20 PM<BR><B>To:</B> =
Poscic,=20
  Kristian (Kristian); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] =
IETF78 ANCP=20
  WG meeting<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 11pt">Hi Kristian,<BR><BR>That is something =
waiting to be=20
  defined, and we welcome your proposals/drafts. We have accepted a WG =
draft to=20
  look at GPON extensions, but this one is still in early phases:<BR><A=20
  =
href=3D"http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03">http:/=
/tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-03</A><BR><BR>Regards,<B=
R>Woj.<BR><BR><BR>On=20
  23/06/2010 20:27, "Poscic, Kristian (Kristian)" &lt;<A=20
  =
href=3D"kristian.poscic@alcatel-lucent.com">kristian.poscic@alcatel-lucen=
t.com</A>&gt;=20
  wrote:<BR><BR></SPAN></FONT>
  <BLOCKQUOTE><FONT face=3D"Calibri, Verdana, Helvetica, Arial"><SPAN=20
    style=3D"FONT-SIZE: 11pt">Hi there -<BR>A quick question. In ANCP =
protocol=20
    draft there are some Target TLVs defined but are mostly used for=20
    DSLAMs.<BR>How can I use a Target tlv for example for =
GPONs?<BR><BR><BR>Let=20
    say that I need to submit a certain request from the NAS to the OLT, =
and=20
    that I need to address:<BR>- uplink from the OLT towards the =
NAS<BR>- or a=20
    particular PON port (slot 1/ port 1)<BR>- or maybe even a particular =

    subscriber on the OLT (slot 1, port 1, GEM 1)<BR><BR><BR>Do we have=20
    provisions for this in any of the ANCP=20
    drafts?<BR>Thanks,<BR>Kris<BR><BR><BR>-----Original =
Message-----<BR>From: <A=20
    href=3D"ancp-bounces@ietf.org">ancp-bounces@ietf.org</A> [<A=20
    =
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>] =
On=20
    Behalf Of Wojciech Dec<BR>Sent: Wednesday, June 23, 2010 9:18 =
AM<BR>To: <A=20
    href=3D"ancp@ietf.org">ancp@ietf.org</A><BR>Subject: [ANCP] IETF78 =
ANCP WG=20
    meeting<BR><BR>Hi All,<BR><BR><BR>We welcome requests for agenda =
slots at=20
    our next ANCP WG meeting in<BR>Maastricht. Please respond with any=20
    requests.<BR><BR>Thanks,<BR>Matthew &amp;=20
    Woj<BR><BR>_______________________________________________<BR>ANCP =
mailing=20
    list<BR><A href=3D"ANCP@ietf.org">ANCP@ietf.org</A><BR><A=20
    =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>____________________________________________=
___<BR>ANCP=20
    mailing list<BR><A href=3D"ANCP@ietf.org">ANCP@ietf.org</A><BR><A=20
    =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR><BR></SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE>=
</BODY></HTML>

------_=_NextPart_001_01CB1440.A890840B--

From HaagT@telekom.de  Fri Jun 25 01:40:38 2010
Return-Path: <HaagT@telekom.de>
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 791AC3A691D for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 01:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level: 
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=1.208,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 OnHhOKJiubgv for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 01:40:37 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 380BF3A63C9 for <ancp@ietf.org>; Fri, 25 Jun 2010 01:40:36 -0700 (PDT)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail71.telekom.de with ESMTP; 25 Jun 2010 10:40:43 +0200
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 25 Jun 2010 10:40:43 +0200
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Jun 2010 10:40:43 +0200
Message-ID: <5661758E3E93364685B91DD8272F2876031800E3@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <C8480054.4FF1%wdec@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] IETF78 ANCP WG meeting
Thread-Index: AcsS76ODIynYh5xQSUKvIFazNCJZ0gBUZruw
References: <C8480054.4FF1%wdec@cisco.com>
From: <HaagT@telekom.de>
To: <wdec@cisco.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 25 Jun 2010 08:40:43.0587 (UTC) FILETIME=[19594930:01CB1442]
Cc: Sven.Ooghe@alcatel-lucent.be
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Jun 2010 08:40:38 -0000

Hi all,

Based on expiriences running ANCP in carrier grade environment DT would =
like to present a problem statement in order to change the default value =
of T1 timer in document " draft-ietf-ancp-mib-an-03".

Regards
Thomas

-----Urspr=FCngliche Nachricht-----
Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von =
Wojciech Dec
Gesendet: Mittwoch, 23. Juni 2010 18:18
An: ancp@ietf.org
Betreff: [ANCP] IETF78 ANCP WG meeting

Hi All,


We welcome requests for agenda slots at our next ANCP WG meeting in
Maastricht. Please respond with any requests.

Thanks,
Matthew & Woj

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

From swadhwa01@yahoo.com  Fri Jun 25 06:11:43 2010
Return-Path: <swadhwa01@yahoo.com>
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 BD2533A698C for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 06:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 gtqcMmFdp1en for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 06:11:40 -0700 (PDT)
Received: from n2d.bullet.mail.ac4.yahoo.com (n2d.bullet.mail.ac4.yahoo.com [76.13.13.86]) by core3.amsl.com (Postfix) with SMTP id 23AB43A6985 for <ancp@ietf.org>; Fri, 25 Jun 2010 06:11:38 -0700 (PDT)
Received: from [76.13.13.26] by n2.bullet.mail.ac4.yahoo.com with NNFMP; 25 Jun 2010 13:11:44 -0000
Received: from [67.195.9.83] by t3.bullet.mail.ac4.yahoo.com with NNFMP; 25 Jun 2010 13:11:43 -0000
Received: from [98.137.27.208] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 25 Jun 2010 13:11:43 -0000
Received: from [127.0.0.1] by omp118.mail.gq1.yahoo.com with NNFMP; 25 Jun 2010 13:11:43 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 752585.19858.bm@omp118.mail.gq1.yahoo.com
Received: (qmail 37745 invoked by uid 60001); 25 Jun 2010 13:11:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1277471503; bh=YS/q9yyOtsOOPOmxP0ckaCBgi6uSNCmSROqvdH4Ri9A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=hR10UVcK4+rtBL14317YkFDBAFwN4u95ri2T/V6X9DMOMIGJ4qVxigvFHCel/mtGj8S0NOlA1i84YfQnDanuc/WJ0tnjcdVULElXg9j2gDq5DJ2I7Vqj+tfIq9xpcQOhHXQdDuh8X7/+yS4oTu+gYxwlEj1oibDQsGo6Okg1iyU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JTHhWyDXXTsiQVMW41bWl8xRf9eif7GW5kWpdlkljFpO8MK+rZxuMHgVjO3zphi0pVSDTnEO1kalpjbn4dDgz9WerFIxV/onwl4y8nB/ara6AoDpXY6ir1w0KekbMqVNoBjoje/WJGdGa8C41Gi9KKhW9pW9PJe3FTjnVykBC0I=;
Message-ID: <662192.37732.qm@web113803.mail.gq1.yahoo.com>
X-YMail-OSG: tmCFT9sVM1nfP0wTV5O5p11dulYT6EJ00bn4iGRCt0EKX.a BAell7KOlbJ77q0g_GQTmfqRoS7kbuKSSS7ASoSgbzHKH9.OitkAEQoWRrKg w2_ucttPv8G9K4d287J3Hyr3I_Ldbw.GfYhcu8FzQ3fu3oL9JGDv0eCDj_7k TSLitsRVS6bwfZCphUwHQlgD0zUWlI2qFtgnKT1mrnPusmEpqcyQIaNdwMZD hRIqymteaUh2yFq6UbpOv.0iHnpf0C5qWZSFqcB5NdIKD2cQur6CFO6RnIL1 DF42ZH4VpIT_OseLb_yrJNETnY4NBXVSONh_mCJS4IHazzW0Jf9UMrQ7_PkB pJF0hqf.oXVXnEYGTtAys8h_UrGY.g4vMqzvrtw--
Received: from [209.116.57.121] by web113803.mail.gq1.yahoo.com via HTTP; Fri, 25 Jun 2010 06:11:43 PDT
X-Mailer: YahooMailRC/397.8 YahooMailWebService/0.8.104.274457
References: <C8480054.4FF1%wdec@cisco.com> <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
Date: Fri, 25 Jun 2010 06:11:43 -0700 (PDT)
From: Sanjay Wadhwa <swadhwa01@yahoo.com>
To: "Poscic, Kristian \(Kristian\)" <kristian.poscic@alcatel-lucent.com>, Wojciech Dec <wdec@cisco.com>, "ancp@ietf.org" <ancp@ietf.org>
In-Reply-To: <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1768812244-1277471503=:37732"
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Jun 2010 13:11:43 -0000

--0-1768812244-1277471503=:37732
Content-Type: text/plain; charset=us-ascii

Hi Kris
  The protocol draft will require extensions to define PON specific target TLVs. In defining these elements,  we can try to remain consistent with formats defined in BBF TR-156 for ACI and underlying port identification elements (also usable for uplink and PON ports). Please also see inline [SW].

Thanks
-Sanjay



________________________________
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: Wojciech Dec <wdec@cisco.com>; "ancp@ietf.org" <ancp@ietf.org>
Sent: Wed, June 23, 2010 2:27:49 PM
Subject: Re: [ANCP] IETF78 ANCP WG meeting

Hi there - 
A quick question. In ANCP protocol draft there are some Target TLVs defined but are mostly used for DSLAMs. 
How can I use a Target tlv for example for GPONs?


Let say that I need to submit a certain request from the NAS to the OLT, and that I need to address:
- uplink from the OLT towards the NAS
- or a particular PON port (slot 1/ port 1)
- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)


[SW] I am hoping NAS doesn't need to know about GEM IDs. The addressing should be generic to the extent possible with OLT deriving GEM IDs (from slot/port, VLAN tags...).

Do we have provisions for this in any of the ANCP drafts?
Thanks,
Kris


-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec
Sent: Wednesday, June 23, 2010 9:18 AM
To: ancp@ietf.org
Subject: [ANCP] IETF78 ANCP WG meeting

Hi All,


We welcome requests for agenda slots at our next ANCP WG meeting in
Maastricht. Please respond with any requests.

Thanks,
Matthew & Woj

_______________________________________________
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



      
--0-1768812244-1277471503=:37732
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:'times new roman', 'new york', times, serif;font-size:12pt"><div><div>Hi Kris</div><div>&nbsp;&nbsp;The protocol draft will require extensions to define PON specific target TLVs. In defining these elements, &nbsp;we can try to remain consistent with formats defined in BBF TR-156 for ACI and underlying port identification elements (also usable for uplink and PON ports). Please also see inline [SW].</div><div><br></div><div>Thanks</div><div>-Sanjay</div></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> "Poscic, Kristian (Kristian)" &lt;kristian.poscic@alcatel-lucent.com&gt;<br><b><span style="font-weight: bold;">To:</span></b> Wojciech Dec
 &lt;wdec@cisco.com&gt;; "ancp@ietf.org" &lt;ancp@ietf.org&gt;<br><b><span style="font-weight: bold;">Sent:</span></b> Wed, June 23, 2010 2:27:49 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [ANCP] IETF78 ANCP WG meeting<br></font><br>
Hi there - <br>A quick question. In ANCP protocol draft there are some Target TLVs defined but are mostly used for DSLAMs. <br>How can I use a Target tlv for example for GPONs?<br><br><br>Let say that I need to submit a certain request from the NAS to the OLT, and that I need to address:<br>- uplink from the OLT towards the NAS<br>- or a particular PON port (slot 1/ port 1)<br>- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)<br><span class="Apple-style-span" style="font-family: 'times new roman', 'new york', times, serif; font-size: 16px; "><br></span></div><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><span class="Apple-style-span" style="font-family: 'times new roman', 'new york', times, serif; font-size: 16px; ">[SW] I am hoping NAS doesn't need to know about GEM IDs. The addressing should be generic to the extent possible with OLT deriving GEM IDs (from slot/port, VLAN tags...).</span><br><br>Do we
 have provisions for this in any of the ANCP drafts?<br>Thanks,<br>Kris<br><br><br>-----Original Message-----<br>From: <a ymailto="mailto:ancp-bounces@ietf.org" href="mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a> [mailto:<a ymailto="mailto:ancp-bounces@ietf.org" href="mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a>] On Behalf Of Wojciech Dec<br>Sent: Wednesday, June 23, 2010 9:18 AM<br>To: <a ymailto="mailto:ancp@ietf.org" href="mailto:ancp@ietf.org">ancp@ietf.org</a><br>Subject: [ANCP] IETF78 ANCP WG meeting<br><br>Hi All,<br><br><br>We welcome requests for agenda slots at our next ANCP WG meeting in<br>Maastricht. Please respond with any requests.<br><br>Thanks,<br>Matthew &amp; Woj<br><br>_______________________________________________<br>ANCP mailing list<br><a ymailto="mailto:ANCP@ietf.org" href="mailto:ANCP@ietf.org">ANCP@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/ancp"
 target="_blank">https://www.ietf.org/mailman/listinfo/ancp</a><br>_______________________________________________<br>ANCP mailing list<br><a ymailto="mailto:ANCP@ietf.org" href="mailto:ANCP@ietf.org">ANCP@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/ancp" target="_blank">https://www.ietf.org/mailman/listinfo/ancp</a><br></div></div><div style="position:fixed"></div>


</div><br>

      </body></html>
--0-1768812244-1277471503=:37732--


From kristian.poscic@alcatel-lucent.com  Fri Jun 25 07:05:10 2010
Return-Path: <kristian.poscic@alcatel-lucent.com>
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 76DA03A69AA for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 07:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level: 
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, 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 aX6OSotnYOO5 for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 07:05:03 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 0B19B3A689F for <ancp@ietf.org>; Fri, 25 Jun 2010 07:05:02 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id o5PE5AZY004045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jun 2010 09:05:10 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o5PE5Atj011846; Fri, 25 Jun 2010 09:05:10 -0500
Received: from USNAVSXCHMBSC3.ndc.alcatel-lucent.com ([135.3.39.146]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Fri, 25 Jun 2010 09:04:49 -0500
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: Sanjay Wadhwa <swadhwa01@yahoo.com>, Wojciech Dec <wdec@cisco.com>, "ancp@ietf.org" <ancp@ietf.org>
Date: Fri, 25 Jun 2010 09:04:46 -0500
Thread-Topic: [ANCP] IETF78 ANCP WG meeting
Thread-Index: AcsUZ/ZJb0FcDlPaSc6hAOqdeXvHAAABsehA
Message-ID: <2073A6C5467C99478898544C6EBA3F46029F649016@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
References: <C8480054.4FF1%wdec@cisco.com> <2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com> <662192.37732.qm@web113803.mail.gq1.yahoo.com>
In-Reply-To: <662192.37732.qm@web113803.mail.gq1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2073A6C5467C99478898544C6EBA3F46029F649016USNAVSXCHMBSC_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Jun 2010 14:05:10 -0000

--_000_2073A6C5467C99478898544C6EBA3F46029F649016USNAVSXCHMBSC_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks Sanjay.
You mean the ANCP protocol draft or the GPON one? Some people think that th=
is needs to go to the GPON draft.
I personally think that it should be part of ANCP protocol draft where the =
Target TLV is defined. But I'm fine either way.
Kris

From: Sanjay Wadhwa [mailto:swadhwa01@yahoo.com]
Sent: Friday, June 25, 2010 6:12 AM
To: Poscic, Kristian (Kristian); Wojciech Dec; ancp@ietf.org
Subject: Re: [ANCP] IETF78 ANCP WG meeting

Hi Kris
  The protocol draft will require extensions to define PON specific target =
TLVs. In defining these elements,  we can try to remain consistent with for=
mats defined in BBF TR-156 for ACI and underlying port identification eleme=
nts (also usable for uplink and PON ports). Please also see inline [SW].

Thanks
-Sanjay

________________________________
From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
To: Wojciech Dec <wdec@cisco.com>; "ancp@ietf.org" <ancp@ietf.org>
Sent: Wed, June 23, 2010 2:27:49 PM
Subject: Re: [ANCP] IETF78 ANCP WG meeting

Hi there -
A quick question. In ANCP protocol draft there are some Target TLVs defined=
 but are mostly used for DSLAMs.
How can I use a Target tlv for example for GPONs?


Let say that I need to submit a certain request from the NAS to the OLT, an=
d that I need to address:
- uplink from the OLT towards the NAS
- or a particular PON port (slot 1/ port 1)
- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)
[SW] I am hoping NAS doesn't need to know about GEM IDs. The addressing sho=
uld be generic to the extent possible with OLT deriving GEM IDs (from slot/=
port, VLAN tags...).

Do we have provisions for this in any of the ANCP drafts?
Thanks,
Kris


-----Original Message-----
From: ancp-bounces@ietf.org<mailto:ancp-bounces@ietf.org> [mailto:ancp-boun=
ces@ietf.org<mailto:ancp-bounces@ietf.org>] On Behalf Of Wojciech Dec
Sent: Wednesday, June 23, 2010 9:18 AM
To: ancp@ietf.org<mailto:ancp@ietf.org>
Subject: [ANCP] IETF78 ANCP WG meeting

Hi All,


We welcome requests for agenda slots at our next ANCP WG meeting in
Maastricht. Please respond with any requests.

Thanks,
Matthew & Woj

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


--_000_2073A6C5467C99478898544C6EBA3F46029F649016USNAVSXCHMBSC_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[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 Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Thanks Sanjay.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>You mean the ANCP protocol draft or the GPON one? Some peopl=
e
think that this needs to go to the GPON draft.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I personally think that it should be part of ANCP protocol d=
raft
where the Target TLV is defined. But I&#8217;m fine either way.<o:p></o:p><=
/span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Kris<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal style=3D'margin-left:.5in'><b><span style=3D'font-size=
:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size=
:10.0pt;
font-family:"Tahoma","sans-serif"'> Sanjay Wadhwa [mailto:swadhwa01@yahoo.c=
om] <br>
<b>Sent:</b> Friday, June 25, 2010 6:12 AM<br>
<b>To:</b> Poscic, Kristian (Kristian); Wojciech Dec; ancp@ietf.org<br>
<b>Subject:</b> Re: [ANCP] IETF78 ANCP WG meeting<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p>

<div>

<div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>Hi Kris<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>&nbsp;&nbsp;The protocol dr=
aft will
require extensions to define PON specific target TLVs. In defining these
elements, &nbsp;we can try to remain consistent with formats defined in BBF
TR-156 for ACI and underlying port identification elements (also usable for
uplink and PON ports). Please also see inline [SW].<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>Thanks<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'>-Sanjay<o:p></o:p></p>

</div>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'margin-left:.5in;text-align:=
center'><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:0in;margin-right:0in;margi=
n-bottom:
12.0pt;margin-left:.5in'><b><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> &quot;Poscic,
Kristian (Kristian)&quot; &lt;kristian.poscic@alcatel-lucent.com&gt;<br>
<b>To:</b> Wojciech Dec &lt;wdec@cisco.com&gt;; &quot;ancp@ietf.org&quot;
&lt;ancp@ietf.org&gt;<br>
<b>Sent:</b> Wed, June 23, 2010 2:27:49 PM<br>
<b>Subject:</b> Re: [ANCP] IETF78 ANCP WG meeting<br>
</span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><b=
r>
Hi there - <br>
A quick question. In ANCP protocol draft there are some Target TLVs defined=
 but
are mostly used for DSLAMs. <br>
How can I use a Target tlv for example for GPONs?<br>
<br>
<br>
Let say that I need to submit a certain request from the NAS to the OLT, an=
d
that I need to address:<br>
- uplink from the OLT towards the NAS<br>
- or a particular PON port (slot 1/ port 1)<br>
- or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)<=
o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><span class=3Dapple-style-s=
pan>[SW] I
am hoping NAS doesn't need to know about GEM IDs. The addressing should be
generic to the extent possible with OLT deriving GEM IDs (from slot/port, V=
LAN
tags...).</span><span style=3D'font-size:10.0pt;font-family:"Arial","sans-s=
erif"'><br>
<br>
Do we have provisions for this in any of the ANCP drafts?<br>
Thanks,<br>
Kris<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a> [m=
ailto:<a
href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a>] On Behalf =
Of
Wojciech Dec<br>
Sent: Wednesday, June 23, 2010 9:18 AM<br>
To: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
Subject: [ANCP] IETF78 ANCP WG meeting<br>
<br>
Hi All,<br>
<br>
<br>
We welcome requests for agenda slots at our next ANCP WG meeting in<br>
Maastricht. Please respond with any requests.<br>
<br>
Thanks,<br>
Matthew &amp; Woj<br>
<br>
_______________________________________________<br>
ANCP mailing list<br>
<a href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ancp" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ancp</a><br>
_______________________________________________<br>
ANCP mailing list<br>
<a href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ancp" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ancp</a><o:p></o:p></span></p>

</div>

</div>

</div>

<p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

--_000_2073A6C5467C99478898544C6EBA3F46029F649016USNAVSXCHMBSC_--

From tom111.taylor@bell.net  Fri Jun 25 07:16:23 2010
Return-Path: <tom111.taylor@bell.net>
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 BC4E53A6972 for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 07:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.553
X-Spam-Level: 
X-Spam-Status: No, score=0.553 tagged_above=-999 required=5 tests=[AWL=0.490,  BAYES_20=-0.74, MSGID_FROM_MTA_HEADER=0.803]
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 EGR+wz37MZc1 for <ancp@core3.amsl.com>; Fri, 25 Jun 2010 07:16:22 -0700 (PDT)
Received: from blu0-omc2-s13.blu0.hotmail.com (blu0-omc2-s13.blu0.hotmail.com [65.55.111.88]) by core3.amsl.com (Postfix) with ESMTP id A69E83A693A for <ancp@ietf.org>; Fri, 25 Jun 2010 07:16:22 -0700 (PDT)
Received: from BLU0-SMTP49 ([65.55.111.73]) by blu0-omc2-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 25 Jun 2010 07:16:31 -0700
X-Originating-IP: [70.26.17.94]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP498FB3860A2963EFCA44A2D8C70@phx.gbl>
Received: from [192.168.2.11] ([70.26.17.94]) by BLU0-SMTP49.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 25 Jun 2010 07:16:30 -0700
Date: Fri, 25 Jun 2010 10:16:26 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
References: <C8480054.4FF1%wdec@cisco.com>	<2073A6C5467C99478898544C6EBA3F46029F4D08F4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>	<662192.37732.qm@web113803.mail.gq1.yahoo.com> <2073A6C5467C99478898544C6EBA3F46029F649016@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
In-Reply-To: <2073A6C5467C99478898544C6EBA3F46029F649016@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2010 14:16:31.0009 (UTC) FILETIME=[0225E910:01CB1471]
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] IETF78 ANCP WG meeting
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/mail-archive/web/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>
X-List-Received-Date: Fri, 25 Jun 2010 14:16:24 -0000

I object on principle to a series of application-specific extensions to the base 
protocol document. If that is necessary, the base was badly designed. Extensions 
should go into their own documents.

Poscic, Kristian (Kristian) wrote:
> Thanks Sanjay.
> You mean the ANCP protocol draft or the GPON one? Some people think that this needs to go to the GPON draft.
> I personally think that it should be part of ANCP protocol draft where the Target TLV is defined. But I'm fine either way.
> Kris
> 
> From: Sanjay Wadhwa [mailto:swadhwa01@yahoo.com]
> Sent: Friday, June 25, 2010 6:12 AM
> To: Poscic, Kristian (Kristian); Wojciech Dec; ancp@ietf.org
> Subject: Re: [ANCP] IETF78 ANCP WG meeting
> 
> Hi Kris
>   The protocol draft will require extensions to define PON specific target TLVs. In defining these elements,  we can try to remain consistent with formats defined in BBF TR-156 for ACI and underlying port identification elements (also usable for uplink and PON ports). Please also see inline [SW].
> 
> Thanks
> -Sanjay
> 
> ________________________________
> From: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>
> To: Wojciech Dec <wdec@cisco.com>; "ancp@ietf.org" <ancp@ietf.org>
> Sent: Wed, June 23, 2010 2:27:49 PM
> Subject: Re: [ANCP] IETF78 ANCP WG meeting
> 
> Hi there -
> A quick question. In ANCP protocol draft there are some Target TLVs defined but are mostly used for DSLAMs.
> How can I use a Target tlv for example for GPONs?
> 
> 
> Let say that I need to submit a certain request from the NAS to the OLT, and that I need to address:
> - uplink from the OLT towards the NAS
> - or a particular PON port (slot 1/ port 1)
> - or maybe even a particular subscriber on the OLT (slot 1, port 1, GEM 1)
> [SW] I am hoping NAS doesn't need to know about GEM IDs. The addressing should be generic to the extent possible with OLT deriving GEM IDs (from slot/port, VLAN tags...).
> 
> Do we have provisions for this in any of the ANCP drafts?
> Thanks,
> Kris
> 
> 
> -----Original Message-----
> From: ancp-bounces@ietf.org<mailto:ancp-bounces@ietf.org> [mailto:ancp-bounces@ietf.org<mailto:ancp-bounces@ietf.org>] On Behalf Of Wojciech Dec
> Sent: Wednesday, June 23, 2010 9:18 AM
> To: ancp@ietf.org<mailto:ancp@ietf.org>
> Subject: [ANCP] IETF78 ANCP WG meeting
> 
> Hi All,
> 
> 
> We welcome requests for agenda slots at our next ANCP WG meeting in
> Maastricht. Please respond with any requests.
> 
> Thanks,
> Matthew & Woj
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org<mailto:ANCP@ietf.org>
> https://www.ietf.org/mailman/listinfo/ancp
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org<mailto:ANCP@ietf.org>
> https://www.ietf.org/mailman/listinfo/ancp
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp

From stefaan.de_cnodder@alcatel-lucent.com  Mon Jun 28 06:55:23 2010
Return-Path: <stefaan.de_cnodder@alcatel-lucent.com>
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 128FA28C112 for <ancp@core3.amsl.com>; Mon, 28 Jun 2010 06:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 Euq4yn697cNf for <ancp@core3.amsl.com>; Mon, 28 Jun 2010 06:55:22 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id D02E93A6A4C for <ancp@ietf.org>; Mon, 28 Jun 2010 06:55:21 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o5SDtDV4025686 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <ancp@ietf.org>; Mon, 28 Jun 2010 15:55:26 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.40]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 28 Jun 2010 15:55:05 +0200
From: "DE CNODDER, STEFAAN (STEFAAN)" <stefaan.de_cnodder@alcatel-lucent.com>
To: "ancp@ietf.org" <ancp@ietf.org>
Date: Mon, 28 Jun 2010 15:55:04 +0200
Thread-Topic: AN-ANCP MIB update
Thread-Index: AcsWyYJZLaY0n1ndRUyboK/v1Xbw9g==
Message-ID: <05B6A5C4AE3BDA4EB276DB70EB548BA30B41B1DC@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_05B6A5C4AE3BDA4EB276DB70EB548BA30B41B1DCFRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Subject: [ANCP] AN-ANCP MIB 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/mail-archive/web/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>
X-List-Received-Date: Mon, 28 Jun 2010 13:55:23 -0000

--_000_05B6A5C4AE3BDA4EB276DB70EB548BA30B41B1DCFRMRSSXCHMBSB1d_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I want to upload a new version of the AN MIB.  Based on the last discussion=
 related to capabilities where the base spec only reserves the multicast ca=
pability without defining it, the MIB does not have to be changed, i.e., th=
e AncpSessionCapabilities (see below), stays as it is.  If you think this i=
s not correct, or something else has to be changed/added, please let me kno=
w before Thursday.  The MIB only covers the base spec, and there is no MIB =
for the multicast extensions defined in draft-ietf-ancp-mc-extensions-02<ht=
tp://datatracker.ietf.org/doc/draft-ietf-ancp-mc-extensions/>.  I believe t=
his is fine for now?

Regards,
Stefaan


AncpSessionCapabilities ::=3D TEXTUAL-CONVENTION
       STATUS current
       DESCRIPTION
             "ANCP capabilities supported by the AN.
              The following capabilities are available:
                 topologyDiscovery (0)- Access Topology Discovery
                 lineConfig (1)       - Line Configuration
                 multicast (2)        - Multicast
                 l2Oam (3)            - Layer 2 OAM
              A bit set means the associated capability is supported."
       SYNTAX BITS {
                     topologyDiscovery (0),
                     lineConfig (1),
                     multicast (2),
                     l2Oam (3)
                   }


--_000_05B6A5C4AE3BDA4EB276DB70EB548BA30B41B1DCFRMRSSXCHMBSB1d_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Trebuchet MS, sans-serif" size=3D"2">
<div>Hi,</div>
<div>&nbsp;</div>
<div>I want to upload a new version of the AN MIB.&nbsp; Based on the last =
discussion related to capabilities where the base spec only reserves the mu=
lticast capability without defining it, the MIB does not have to be changed=
, i.e., the AncpSessionCapabilities (see
below), stays as it is.&nbsp; If you think this is not correct, or somethin=
g else has to be changed/added, please let me know before Thursday.&nbsp; T=
he MIB only covers the base spec, and there is no MIB for the multicast ext=
ensions defined in <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-an=
cp-mc-extensions/">draft-ietf-ancp-mc-extensions-02</a>.&nbsp;
I believe this is fine for now?</div>
<div><font face=3D"Calibri, sans-serif">&nbsp;</font></div>
<div>Regards,</div>
<div>Stefaan</div>
<div><font face=3D"Calibri, sans-serif">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif">&nbsp;</font></div>
<div>AncpSessionCapabilities ::=3D TEXTUAL-CONVENTION</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS current</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; &quot;ANCP capabilities supported by the AN.</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; The following capabilities are available:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; topologyDiscovery (0)- Access Topology Discovery=
</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; lineConfig (1)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; - Line Configuration</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; multicast (2)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; - Multicast</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; l2Oam (3)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; - Layer 2 OAM</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; A bit set means the associated capability is supported.&quot;</div=
>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYNTAX BITS {</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; topologyDiscovery (0),</=
div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lineConfig (1),</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; multicast (2),</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; l2Oam (3)</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }</div>
<div><font face=3D"Calibri, sans-serif">&nbsp;</font></div>
</font>
</body>
</html>

--_000_05B6A5C4AE3BDA4EB276DB70EB548BA30B41B1DCFRMRSSXCHMBSB1d_--

From wdec@cisco.com  Tue Jun 29 08:47:28 2010
Return-Path: <wdec@cisco.com>
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 62DC63A6BBD for <ancp@core3.amsl.com>; Tue, 29 Jun 2010 08:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.717
X-Spam-Level: 
X-Spam-Status: No, score=-9.717 tagged_above=-999 required=5 tests=[AWL=0.882,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 V+owA-MEbvaG for <ancp@core3.amsl.com>; Tue, 29 Jun 2010 08:47:27 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id CE54C3A6BE2 for <ancp@ietf.org>; Tue, 29 Jun 2010 08:47:18 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmUGANqxKUytJV2c/2dsb2JhbACTC4w3caV9mlOFJAQ
X-IronPort-AV: E=Sophos;i="4.53,505,1272844800"; d="scan'208";a="126816369"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2010 15:47:23 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id o5TFlMZP031049;  Tue, 29 Jun 2010 15:47:23 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Jun 2010 17:47:21 +0200
Received: from 10.55.215.35 ([10.55.215.35]) by XMB-AMS-111.cisco.com ([144.254.74.86]) with Microsoft Exchange Server HTTP-DAV ;  Tue, 29 Jun 2010 15:47:21 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Tue, 29 Jun 2010 17:47:35 +0200
From: Wojciech Dec <wdec@cisco.com>
To: <ancp@ietf.org>
Message-ID: <C84FE237.531B%wdec@cisco.com>
Thread-Topic: ANCP protocol spec editor
Thread-Index: AcsXomSXo/VCyUOENEiZF3dYoohnQg==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Jun 2010 15:47:22.0154 (UTC) FILETIME=[5CEFA0A0:01CB17A2]
Cc: "Bocci, Matthew \(Matthew\)" <matthew.bocci@alcatel-lucent.com>
Subject: [ANCP] ANCP protocol spec editor
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/mail-archive/web/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>
X-List-Received-Date: Tue, 29 Jun 2010 15:47:28 -0000

Hello All,

We would like to announce that Tom Taylor has kindly agreed to take on the
editorship of the WG's ANCP protocol draft (currently
http://tools.ietf.org/html/draft-ietf-ancp-protocol-09). The change follows
the stepping down from that role of Roberta Maglione. We would like to thank
Roberta for the significant contribution made over the past few years into
progressing and editing the draft.

As always, please share your review comments with Tom and the WG on the
alias. The draft is effectively in WG last-call.

Regards,
Woj & Matthew.


From tom111.taylor@bell.net  Tue Jun 29 20:51:02 2010
Return-Path: <tom111.taylor@bell.net>
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 6C02A3A6892 for <ancp@core3.amsl.com>; Tue, 29 Jun 2010 20:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.872
X-Spam-Level: 
X-Spam-Status: No, score=0.872 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 nC3kBDsAyVmH for <ancp@core3.amsl.com>; Tue, 29 Jun 2010 20:51:01 -0700 (PDT)
Received: from blu0-omc2-s16.blu0.hotmail.com (blu0-omc2-s16.blu0.hotmail.com [65.55.111.91]) by core3.amsl.com (Postfix) with ESMTP id A87BD3A688A for <ancp@ietf.org>; Tue, 29 Jun 2010 20:51:01 -0700 (PDT)
Received: from BLU0-SMTP70 ([65.55.111.71]) by blu0-omc2-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Jun 2010 20:51:11 -0700
X-Originating-IP: [70.26.17.94]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP7050FCD8D94A69F14E385BD8CC0@phx.gbl>
Received: from [192.168.2.11] ([70.26.17.94]) by BLU0-SMTP70.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Jun 2010 20:51:11 -0700
Date: Tue, 29 Jun 2010 23:51:08 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Jun 2010 03:51:11.0904 (UTC) FILETIME=[7B159200:01CB1807]
Subject: [ANCP] Tech Type and Capabilities
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Jun 2010 03:51:02 -0000

Reviewing Figure 8 and section 5.3 of the base protocol spec, I was left with a 
couple of questions in my mind.

1) Can a given AN partition support more than one Tech Type? If so, do we need 
to specify how to indicate multiple sets of capabilities in the adjacency 
message, one set for each Tech Type supported?

2) Have we defined any capabilities that depend on Tech Type? I'm sure the 
multicast stuff is technology independent. But how about line configuration and 
OAM?

Tom Taylor

From lihy@huawei.com  Tue Jun 29 23:16:06 2010
Return-Path: <lihy@huawei.com>
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 3F0CE3A6C0F for <ancp@core3.amsl.com>; Tue, 29 Jun 2010 23:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.546
X-Spam-Level: 
X-Spam-Status: No, score=-1.546 tagged_above=-999 required=5 tests=[AWL=1.053,  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 lh7bK-mqol9O for <ancp@core3.amsl.com>; Tue, 29 Jun 2010 23:15:57 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 249823A680F for <ancp@ietf.org>; Tue, 29 Jun 2010 23:15:56 -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 <0L4T00DWIDEU3O@szxga04-in.huawei.com> for ancp@ietf.org; Wed, 30 Jun 2010 14:16:06 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4T006YADEU6J@szxga04-in.huawei.com> for ancp@ietf.org; Wed, 30 Jun 2010 14:16:06 +0800 (CST)
Received: from l00150618 ([10.70.40.85]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4T0042UDEUIS@szxml04-in.huawei.com> for ancp@ietf.org; Wed, 30 Jun 2010 14:16:06 +0800 (CST)
Date: Wed, 30 Jun 2010 14:16:06 +0800
From: Hongyu Li <lihy@huawei.com>
In-reply-to: <BLU0-SMTP7050FCD8D94A69F14E385BD8CC0@phx.gbl>
To: 'Tom Taylor' <tom111.taylor@bell.net>, ancp@ietf.org
Message-id: <2045724C4D2E45F581E2A31B963A55F3@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcsYB4QV1R4POc31R323SHkXSyFYgwAE3sBQ
Subject: Re: [ANCP] Tech Type and Capabilities
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Jun 2010 06:16:06 -0000

There would be more than one type of access technology existing on an Access
Node, while they may belong to a same partition.

At present, I can see line parameters for DSL and PON are totally different.
Even identifications of DSL line and PON port are different, where the
former is identified by DSL line and the latter should be something related
with ONU ID.

Cheers,
Hongyu


> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On 
> Behalf Of Tom Taylor
> Sent: Wednesday, June 30, 2010 11:51 AM
> To: ancp@ietf.org
> Subject: [ANCP] Tech Type and Capabilities
> 
> Reviewing Figure 8 and section 5.3 of the base protocol spec, 
> I was left with a couple of questions in my mind.
> 
> 1) Can a given AN partition support more than one Tech Type? 
> If so, do we need to specify how to indicate multiple sets of 
> capabilities in the adjacency message, one set for each Tech 
> Type supported?
> 
> 2) Have we defined any capabilities that depend on Tech Type? 
> I'm sure the multicast stuff is technology independent. But 
> how about line configuration and OAM?
> 
> Tom Taylor
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
> 


From tom111.taylor@bell.net  Wed Jun 30 05:46:22 2010
Return-Path: <tom111.taylor@bell.net>
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 5C3013A680A for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 05:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.866
X-Spam-Level: 
X-Spam-Status: No, score=0.866 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 zVxz39FAuCa1 for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 05:46:21 -0700 (PDT)
Received: from blu0-omc2-s17.blu0.hotmail.com (blu0-omc2-s17.blu0.hotmail.com [65.55.111.92]) by core3.amsl.com (Postfix) with ESMTP id 4D1343A6909 for <ancp@ietf.org>; Wed, 30 Jun 2010 05:46:20 -0700 (PDT)
Received: from BLU0-SMTP82 ([65.55.111.71]) by blu0-omc2-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 05:46:31 -0700
X-Originating-IP: [70.26.17.94]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP82B74105EA1897E390E384D8CC0@phx.gbl>
Received: from [192.168.2.11] ([70.26.17.94]) by BLU0-SMTP82.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 05:46:31 -0700
Date: Wed, 30 Jun 2010 08:46:29 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Hongyu Li <lihy@huawei.com>
References: <2045724C4D2E45F581E2A31B963A55F3@china.huawei.com>
In-Reply-To: <2045724C4D2E45F581E2A31B963A55F3@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Jun 2010 12:46:31.0458 (UTC) FILETIME=[43D49020:01CB1852]
Cc: ancp@ietf.org
Subject: Re: [ANCP] Tech Type and Capabilities
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Jun 2010 12:46:22 -0000

I think that has two implications, as I indicated in my original note:

1) Instead of one set of capabilities in an adjacency message, we have to carry 
multiple sets, each identified by the Tech Type to which it applies.

2) In the IANA registry of capabilities and in the capability descriptions 
themselves, we have to identify the Tech Type(s) for which the capabilities are 
defined. For example, we may end up with capability type 
Line-Configuration-for-DSL (0x02) and Line-Configuration-For-PON (0x09, for 
example).

I would hope it would be possible for some capabilities to say that they apply 
to all Tech Types. Then we have a choice: repeat such capabilities in each set 
reported in the adjacency message (my recommendation, for flexibility, in case a 
Tech Type gets defined for which the capability doesn't apply after all), or 
have a Tech Type "all" and list such capabilities under that.

Could I have comments on these observations? I can work up examples if people 
need further information. Note that this will mean a real change from ANCPv3.1 
to ANCPv3.2.

Oh, and I wouldn't mind guidance on whether all three of the capabilities 
currently documented -- topology, line configuration, and OAM -- are for DSL only.

Tom Taylor

Hongyu Li wrote:
> There would be more than one type of access technology existing on an Access
> Node, while they may belong to a same partition.
> 
> At present, I can see line parameters for DSL and PON are totally different.
> Even identifications of DSL line and PON port are different, where the
> former is identified by DSL line and the latter should be something related
> with ONU ID.
> 
> Cheers,
> Hongyu
> 
> 
>> -----Original Message-----
>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On 
>> Behalf Of Tom Taylor
>> Sent: Wednesday, June 30, 2010 11:51 AM
>> To: ancp@ietf.org
>> Subject: [ANCP] Tech Type and Capabilities
>>
>> Reviewing Figure 8 and section 5.3 of the base protocol spec, 
>> I was left with a couple of questions in my mind.
>>
>> 1) Can a given AN partition support more than one Tech Type? 
>> If so, do we need to specify how to indicate multiple sets of 
>> capabilities in the adjacency message, one set for each Tech 
>> Type supported?
>>
>> 2) Have we defined any capabilities that depend on Tech Type? 
>> I'm sure the multicast stuff is technology independent. But 
>> how about line configuration and OAM?
>>
>> Tom Taylor
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>>
> 
> 
> 

From tom111.taylor@bell.net  Wed Jun 30 06:32:05 2010
Return-Path: <tom111.taylor@bell.net>
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 9AD5A28C108 for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 06:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.864
X-Spam-Level: 
X-Spam-Status: No, score=0.864 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 uvotIPIQUszX for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 06:32:04 -0700 (PDT)
Received: from blu0-omc2-s3.blu0.hotmail.com (blu0-omc2-s3.blu0.hotmail.com [65.55.111.78]) by core3.amsl.com (Postfix) with ESMTP id AA79728B23E for <ancp@ietf.org>; Wed, 30 Jun 2010 06:31:48 -0700 (PDT)
Received: from BLU0-SMTP25 ([65.55.111.71]) by blu0-omc2-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 06:31:36 -0700
X-Originating-IP: [70.26.17.94]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP257F3A041B386C7F8E7C03D8CC0@phx.gbl>
Received: from [192.168.2.11] ([70.26.17.94]) by BLU0-SMTP25.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 06:31:36 -0700
Date: Wed, 30 Jun 2010 09:31:34 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 30 Jun 2010 13:31:36.0832 (UTC) FILETIME=[905BE000:01CB1858]
Subject: [ANCP] Can we modify IANA registries set up for GSMPv3?
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Jun 2010 13:32:05 -0000

This issue may affect other registries, but I realized it when I was looking at 
the reallocation of bits between Result and Code compared with GSMPv3. I'm sure 
it's legitimate to add code points to a registry for an older protocol, but this 
reallocation of bits means that the limits on the possible values change. Can we 
do that (implying that we obsolete GSMPv3 itself), or must we establish new 
parallel registries for ANCP?

There is an intermediate solution where we continue to use GSMPv3 registries but 
segregate the codepoints falling outside the limits for one protocol or the 
other, noting that they apply only to one protocol. Thus in the Result value 
registry we would add a note that any values greater than 15 apply to GSMPv3 
only, while in the Code registry, values greater than 255 apply to ANCP only. 
This sounds like the best solution, though I had to talk myself around to it.

Tom Taylor

From wdec@cisco.com  Wed Jun 30 09:06:21 2010
Return-Path: <wdec@cisco.com>
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 3296E28C0E7 for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 09:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.149
X-Spam-Level: 
X-Spam-Status: No, score=-9.149 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_05=-1.11, RCVD_IN_DNSWL_HI=-8]
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 xTcFg+OHtHO4 for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 09:06:20 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id DEF363A6781 for <ancp@ietf.org>; Wed, 30 Jun 2010 09:06:19 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIMIK0xAZnwM/2dsb2JhbACfUXGmYpowhSUEiCOCHw
X-IronPort-AV: E=Sophos;i="4.53,513,1272844800"; d="scan'208";a="127373982"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 30 Jun 2010 16:06:30 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5UG6Twx005907; Wed, 30 Jun 2010 16:06:30 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 18:06:30 +0200
Received: from 10.55.215.35 ([10.55.215.35]) by XMB-AMS-111.cisco.com ([144.254.74.86]) with Microsoft Exchange Server HTTP-DAV ;  Wed, 30 Jun 2010 16:06:29 +0000
User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Wed, 30 Jun 2010 18:06:43 +0200
From: Wojciech Dec <wdec@cisco.com>
To: Tom Taylor <tom111.taylor@bell.net>, <ancp@ietf.org>, Ralph Droms <rdroms@cisco.com>
Message-ID: <C8513833.53CC%wdec@cisco.com>
Thread-Topic: [ANCP] Can we modify IANA registries set up for GSMPv3?
Thread-Index: AcsYbjtEhZtSGMQ930OqKCM8VsajSw==
In-Reply-To: <BLU0-SMTP257F3A041B386C7F8E7C03D8CC0@phx.gbl>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 30 Jun 2010 16:06:30.0074 (UTC) FILETIME=[339011A0:01CB186E]
Subject: Re: [ANCP] Can we modify IANA registries set up for GSMPv3?
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/mail-archive/web/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>
X-List-Received-Date: Wed, 30 Jun 2010 16:06:21 -0000

Adding Ralph...

The core issue looks like being that ANCP still rides on the GSMP protocol
code point, even though it is incompatible.
I'm not sure if there is a precedent for a re-branding of a protocol type,
but if that is an option, along with declaring GSMP deprecated, then we
could have an alternative. (Note: Previous searches into finding operational
implementations of GSMP have not found any, but we will never know for sure.
That said, it's highly unlikely that the two will meet.)

-Woj.


On 30/06/2010 15:31, "Tom Taylor" <tom111.taylor@bell.net> wrote:

> This issue may affect other registries, but I realized it when I was looking
> at 
> the reallocation of bits between Result and Code compared with GSMPv3. I'm
> sure 
> it's legitimate to add code points to a registry for an older protocol, but
> this 
> reallocation of bits means that the limits on the possible values change. Can
> we 
> do that (implying that we obsolete GSMPv3 itself), or must we establish new
> parallel registries for ANCP?
> 
> There is an intermediate solution where we continue to use GSMPv3 registries
> but 
> segregate the codepoints falling outside the limits for one protocol or the
> other, noting that they apply only to one protocol. Thus in the Result value
> registry we would add a note that any values greater than 15 apply to GSMPv3
> only, while in the Code registry, values greater than 255 apply to ANCP only.
> This sounds like the best solution, though I had to talk myself around to it.
> 
> Tom Taylor
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp


From tom111.taylor@bell.net  Wed Jun 30 18:26:39 2010
Return-Path: <tom111.taylor@bell.net>
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 AC6273A68AC for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 18:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.861
X-Spam-Level: 
X-Spam-Status: No, score=0.861 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
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 bT9iWoP12H44 for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 18:26:38 -0700 (PDT)
Received: from blu0-omc2-s18.blu0.hotmail.com (blu0-omc2-s18.blu0.hotmail.com [65.55.111.93]) by core3.amsl.com (Postfix) with ESMTP id C0CF73A6883 for <ancp@ietf.org>; Wed, 30 Jun 2010 18:26:33 -0700 (PDT)
Received: from BLU0-SMTP42 ([65.55.111.72]) by blu0-omc2-s18.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 18:26:44 -0700
X-Originating-IP: [70.26.17.94]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP42EDB43BD1B1FE90103CE7D8CD0@phx.gbl>
Received: from [192.168.2.11] ([70.26.17.94]) by BLU0-SMTP42.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Jun 2010 18:26:44 -0700
Date: Wed, 30 Jun 2010 21:26:41 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Jul 2010 01:26:44.0537 (UTC) FILETIME=[77581290:01CB18BC]
Subject: [ANCP] Action For TLV Type Not Understood
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/mail-archive/web/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>
X-List-Received-Date: Thu, 01 Jul 2010 01:26:40 -0000

Currently there is text in the description of TLVs in the base document (section 
5.4.2, just below Figure 13) that says the NAS will ignore any TLV it does not 
understand. I am guessing that this should also be true for the AN when it is 
the receiver of a message. I'm going to make the change in the text without 
waiting for comments, but if anyone objects, let the list know.

Tom Taylor

From srinivasa.nalluri@wipro.com  Wed Jun 30 20:22:09 2010
Return-Path: <srinivasa.nalluri@wipro.com>
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 F2D293A68D7 for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 20:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.605
X-Spam-Level: 
X-Spam-Status: No, score=-2.605 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RELAY_IS_203=0.994]
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 INB2neVkQS+w for <ancp@core3.amsl.com>; Wed, 30 Jun 2010 20:22:07 -0700 (PDT)
Received: from wipro-blr-out01.wipro.com (wipro-blr-out01.wipro.com [203.91.198.74]) by core3.amsl.com (Postfix) with ESMTP id DDB0B3A672E for <ancp@ietf.org>; Wed, 30 Jun 2010 20:22:06 -0700 (PDT)
X-AuditID: cb5bdd57-b7ca9ae0000026a4-bb-4c2c09e8af2b
Received: from blr-ec-aa01.wipro.com ( [10.201.18.41]) by wipro-blr-out01.wipro.com (Symantec Mail Security) with SMTP id 03.39.09892.8E90C2C4; Thu,  1 Jul 2010 08:52:16 +0530 (IST)
Received: from blr-ec-bh02.wipro.com ([10.201.50.92]) by blr-ec-aa01.wipro.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Jul 2010 08:52:15 +0530
Received: from BLR-EC-MBX02.wipro.com ([10.201.50.162]) by blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Jul 2010 08:52:17 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Jul 2010 08:47:04 +0530
Message-ID: <70E3BF80B2DA6E469688AD5C3BBCC6C4071A5364@BLR-EC-MBX02.wipro.com>
In-Reply-To: <BLU0-SMTP82B74105EA1897E390E384D8CC0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Tech Type and Capabilities
Thread-Index: AcsYUk3aSU9W33MER46JG6yvDvBaXQAeH4sQ
References: <2045724C4D2E45F581E2A31B963A55F3@china.huawei.com> <BLU0-SMTP82B74105EA1897E390E384D8CC0@phx.gbl>
From: <srinivasa.nalluri@wipro.com>
To: <tom111.taylor@bell.net>, <lihy@huawei.com>
X-OriginalArrivalTime: 01 Jul 2010 03:22:17.0000 (UTC) FILETIME=[9B69FA80:01CB18CC]
X-Brightmail-Tracker: AAAAAA==
Cc: ancp@ietf.org
Subject: Re: [ANCP] Tech Type and Capabilities
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/mail-archive/web/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>
X-List-Received-Date: Thu, 01 Jul 2010 03:22:09 -0000

Tom,

Does this mean we will have separate set of TLV and sub-TLVs to define
PON line (ONU/ONT level) attributes.
Today, in protocol document I cannot see TLVs for PON line attributes.=20

How about considering other wireless access technologies?



Regards
Srinivas

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Tom Taylor
Sent: Wednesday, June 30, 2010 6:16 PM
To: Hongyu Li
Cc: ancp@ietf.org
Subject: Re: [ANCP] Tech Type and Capabilities

I think that has two implications, as I indicated in my original note:

1) Instead of one set of capabilities in an adjacency message, we have
to carry=20
multiple sets, each identified by the Tech Type to which it applies.

2) In the IANA registry of capabilities and in the capability
descriptions=20
themselves, we have to identify the Tech Type(s) for which the
capabilities are=20
defined. For example, we may end up with capability type=20
Line-Configuration-for-DSL (0x02) and Line-Configuration-For-PON (0x09,
for=20
example).

I would hope it would be possible for some capabilities to say that they
apply=20
to all Tech Types. Then we have a choice: repeat such capabilities in
each set=20
reported in the adjacency message (my recommendation, for flexibility,
in case a=20
Tech Type gets defined for which the capability doesn't apply after
all), or=20
have a Tech Type "all" and list such capabilities under that.

Could I have comments on these observations? I can work up examples if
people=20
need further information. Note that this will mean a real change from
ANCPv3.1=20
to ANCPv3.2.

Oh, and I wouldn't mind guidance on whether all three of the
capabilities=20
currently documented -- topology, line configuration, and OAM -- are for
DSL only.

Tom Taylor

Hongyu Li wrote:
> There would be more than one type of access technology existing on an
Access
> Node, while they may belong to a same partition.
>=20
> At present, I can see line parameters for DSL and PON are totally
different.
> Even identifications of DSL line and PON port are different, where the
> former is identified by DSL line and the latter should be something
related
> with ONU ID.
>=20
> Cheers,
> Hongyu
>=20
>=20
>> -----Original Message-----
>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On=20
>> Behalf Of Tom Taylor
>> Sent: Wednesday, June 30, 2010 11:51 AM
>> To: ancp@ietf.org
>> Subject: [ANCP] Tech Type and Capabilities
>>
>> Reviewing Figure 8 and section 5.3 of the base protocol spec,=20
>> I was left with a couple of questions in my mind.
>>
>> 1) Can a given AN partition support more than one Tech Type?=20
>> If so, do we need to specify how to indicate multiple sets of=20
>> capabilities in the adjacency message, one set for each Tech=20
>> Type supported?
>>
>> 2) Have we defined any capabilities that depend on Tech Type?=20
>> I'm sure the multicast stuff is technology independent. But=20
>> how about line configuration and OAM?
>>
>> Tom Taylor
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>>
>=20
>=20
>=20
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp
