From Matthew.Bocci@alcatel-lucent.com Mon Mar 2 01:46:31 2009 Return-Path: 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 73B943A6A50 for ; Mon, 2 Mar 2009 01:46:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.156 X-Spam-Level: X-Spam-Status: No, score=-6.156 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 3ttzTmVdd9Ek for ; Mon, 2 Mar 2009 01:46:30 -0800 (PST) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 6AEFF3A68C7 for ; Mon, 2 Mar 2009 01:46:30 -0800 (PST) Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n229kqK6019007; Mon, 2 Mar 2009 10:46:53 +0100 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.37]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 2 Mar 2009 10:46:52 +0100 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: Mon, 2 Mar 2009 10:44:14 +0100 Message-ID: <0458D2EE0C36744BABB36BE37805C29A036AAEA0@FRVELSMBS11.ad2.ad.alcatel.com> In-Reply-To: <49A6C7E0.4090200@rogers.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] IANA Considerations in the protocol document Thread-Index: AcmYMhLAV9IrahyNSFKCh2ZoKL/RsAC5wD2A References: <49A6C7E0.4090200@rogers.com> From: "BOCCI Matthew" To: "Tom Taylor" , X-OriginalArrivalTime: 02 Mar 2009 09:46:52.0227 (UTC) FILETIME=[D08FB130:01C99B1B] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: Re: [ANCP] IANA Considerations in the 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 09:46:31 -0000 Tom, Yes, I agree. It is very important to get the registries defined. Matthew =20 > -----Original Message----- > From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On=20 > Behalf Of Tom Taylor > Sent: 26 February 2009 16:49 > To: ancp@ietf.org > Subject: [ANCP] IANA Considerations in the protocol document >=20 > It's really time we got our registries defined and values=20 > assigned. Working on the multicast extensions document, I=20 > find it inconvenient not to have an up-to-date list of=20 > codepoint assignments. I can propose text for the IANA=20 > Considerations section of the base protocol document if the=20 > design team can't do it. >=20 > Tom taylor > _______________________________________________ > ANCP mailing list > ANCP@ietf.org > https://www.ietf.org/mailman/listinfo/ancp >=20 From Lothar.Reith@detecon.com Mon Mar 2 08:45:32 2009 Return-Path: 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 B3C0B3A6A56 for ; Mon, 2 Mar 2009 08:45:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 RTMV3n7LXINd for ; Mon, 2 Mar 2009 08:45:31 -0800 (PST) Received: from dtc034.detecon.net (dtc034.detecon.net [194.25.60.134]) by core3.amsl.com (Postfix) with ESMTP id 2BDA73A6933 for ; Mon, 2 Mar 2009 08:45:31 -0800 (PST) Received: from unknown (HELO dc00356.detecon.com) ([172.16.10.106]) by relay.dtc034.detecon.net with ESMTP; 02 Mar 2009 17:45:33 +0100 Received: from DC00331.detecon.com ([172.16.10.78]) by dc00356.detecon.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Mar 2009 17:45:33 +0100 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: Mon, 2 Mar 2009 17:45:30 +0100 Message-ID: In-Reply-To: <014201c999cb$cb814fb0$0201a8c0@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] Access Node Control Protocol for Source Adress Validation Thread-Index: AcmZy84vanZUpVbzSdS9wVhF/R7lTABiilLQ References: <014201c999cb$cb814fb0$0201a8c0@china.huawei.com> From: "Reith, Lothar" To: X-OriginalArrivalTime: 02 Mar 2009 16:45:33.0104 (UTC) FILETIME=[4DC55300:01C99B56] Subject: Re: [ANCP] Access Node Control Protocol for Source Adress Validation X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2009 16:45:32 -0000 Dear all, below some comments that Frank Xia has suggested that I should put them = forward to the list. Best Regards, Lothar =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= Hi Lothar Absolutely right! Thank you for reviewing. You are appriciated if you can post your comments on the mailing list. BR Frank ----- Original Message ----- From: "Reith, Lothar" To: "Frank Xia" Sent: Sunday, March 01, 2009 3:12 AM Subject: AW: [ANCP] Access Node Control Protocol for Source Adress = Validation Hi Frank, I understand the Draft describes delegation of authority to perform = anti-spoofing enforcement (from the Router to the Access Node/Switch). The implied distribution of the enforcement point closer to the access = loop (in case of DSLAM to the access loop termination point) provides = for better scalability and protection against DoS attacks. Did I get it right? Best Regards, Lothar=20 -----Urspr=FCngliche Nachricht----- Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von = Frank Xia Gesendet: Samstag, 28. Februar 2009 18:42 An: ancp@ietf.org Betreff: [ANCP] Access Node Control Protocol for Source Adress = Validation Hi Folks We just submitted the draft http://www.ietf.org/internet-drafts/draft-kaippallimalil-ancp-sav-00.txt Comments are most welcome. BR Frank ----- Original Message ----- From: "IETF I-D Submission Tool" To: Cc: Sent: Saturday, February 28, 2009 11:24 AM Subject: New Version Notification for draft-kaippallimalil-ancp-sav-00 A new version of I-D, draft-kaippallimalil-ancp-sav-00.txt has been=20 successfuly submitted by Frank Xia and posted to the IETF repository. Filename: draft-kaippallimalil-ancp-sav Revision: 00 Title: Access Node Control Protocol for Source Adress Validation Creation_date: 2009-02-28 WG ID: Independent Submission Number_of_pages: 11 Abstract: This document specifies an extension of Access Node Control Protocol to provide source address validation for IPv4 and IPv6 networks. An access router uses the proposed mechanism to provision source address validation states on a layer 2 device which a host may directly connects to. The solution proposed here can be used in either public access networks or enterprise networks. The IETF Secretariat. _______________________________________________ ANCP mailing list ANCP@ietf.org https://www.ietf.org/mailman/listinfo/ancp From root@core3.amsl.com Wed Mar 4 00:30:01 2009 Return-Path: X-Original-To: ancp@ietf.org Delivered-To: ancp@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id CC88D28C184; Wed, 4 Mar 2009 00:30:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090304083001.CC88D28C184@core3.amsl.com> Date: Wed, 4 Mar 2009 00:30:01 -0800 (PST) Cc: ancp@ietf.org Subject: [ANCP] I-D Action:draft-ietf-ancp-security-threats-07.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2009 08:30:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Access Node Control Protocol Working Group of the IETF. Title : Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) Author(s) : H. Moustafa, et al. Filename : draft-ietf-ancp-security-threats-07.txt Pages : 17 Date : 2009-03-04 The Access Node Control Protocol (ANCP) aims to communicate QoS- related, service-related and subscriber-related configurations and operations between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)). The main goal of this protocol is to allow the NAS to configure, manage and control access equipments including the ability for the access nodes to report information to the NAS. The present document investigates security threats that all ANCP nodes could encounter. This document develops a threat model for ANCP security aiming to decide which security functions are required. Based on this, security requirements regarding the Access Node Control Protocol are defined. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ancp-security-threats-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ancp-security-threats-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-03-04002531.I-D@ietf.org> --NextPart-- From Matthew.Bocci@alcatel-lucent.com Wed Mar 4 10:32:11 2009 Return-Path: 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 3BEC93A69EE for ; Wed, 4 Mar 2009 10:32:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.168 X-Spam-Level: X-Spam-Status: No, score=-6.168 tagged_above=-999 required=5 tests=[AWL=0.080, 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 Wz5H6nTFYvR3 for ; Wed, 4 Mar 2009 10:32:10 -0800 (PST) Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5]) by core3.amsl.com (Postfix) with ESMTP id 029003A67DF for ; Wed, 4 Mar 2009 10:32:09 -0800 (PST) Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n24IWase018862 for ; Wed, 4 Mar 2009 19:32:36 +0100 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.31]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Wed, 4 Mar 2009 19:32:36 +0100 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_01C99CF7.972AC342" Date: Wed, 4 Mar 2009 19:32:35 +0100 Message-ID: <0458D2EE0C36744BABB36BE37805C29A036ABB1F@FRVELSMBS11.ad2.ad.alcatel.com> In-Reply-To: <6CBF6935-E835-40D6-8DF7-2EAB743840F2@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] Time slots for San Francisco Thread-Index: AcmRHg4CNR/m1WeGTamNgMOhhd4K6gL2SXWQ References: <0458D2EE0C36744BABB36BE37805C29A0358B9C8@FRVELSMBS11.ad2.ad.alcatel.com> <6CBF6935-E835-40D6-8DF7-2EAB743840F2@cisco.com> From: "BOCCI Matthew" To: X-OriginalArrivalTime: 04 Mar 2009 18:32:36.0624 (UTC) FILETIME=[97503100:01C99CF7] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Subject: Re: [ANCP] Time slots for San Francisco X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2009 18:32:11 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C99CF7.972AC342 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, =20 Are there any more requests for slots? =20 So far I have: =20 Francois Le Faucheur : draft-lefaucheur-ancp-mc-extensions-01.txt =20 Frank Xia: Access Node Control Protocol for Source Adress Validation =20 Thanks =20 Matthew ________________________________ From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20 Sent: 17 February 2009 16:37 To: BOCCI Matthew Cc: Francois Le Faucheur IMAP; ancp@ietf.org; Tom Taylor; Maglione Roberta Subject: Re: [ANCP] Time slots for San Francisco =09 =09 Hi Matthew,=20 Can we have a slot for : * draft-lefaucheur-ancp-mc-extensions-01.txt The draft will be published before deadline. Thanks Francois On 17 Feb 2009, at 15:30, BOCCI Matthew wrote: Folks,=20 Please can you let me know if you would like a time slot for the ANCP meeting in San Francisco.. Please let me know the subject you would like to discuss and a pointer to the draft, if any. Thanks.=20 Matthew=20 _______________________________________________ ANCP mailing list ANCP@ietf.org https://www.ietf.org/mailman/listinfo/ancp =09 ------_=_NextPart_001_01C99CF7.972AC342 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Folks,
 
Are there any more requests for slots?
 
So far I have:
 
Francois Le = Faucheur=20 : draft-lefaucheur-ancp-mc-extensions-01.txt<= /DIV>
 
Frank Xia: Access Node Control Protocol for=20 Source Adress Validation
 
Thanks
 
Matthew

From: Francois Le Faucheur IMAP=20 [mailto:flefauch@cisco.com]
Sent: 17 February 2009=20 16:37
To: BOCCI Matthew
Cc: Francois Le Faucheur = IMAP;=20 ancp@ietf.org; Tom Taylor; Maglione Roberta
Subject: Re: = [ANCP] Time=20 slots for San Francisco

Hi Matthew,

Can we have a slot for :
* draft-lefaucheur-ancp-mc-extensions-01.txt

The draft will be published before deadline.

Thanks

Francois

On 17 Feb 2009, at 15:30, BOCCI Matthew wrote:

Folks,

Please can you let me know if you = would like a=20 time slot for the ANCP meeting in San Francisco.. Please let me know = the=20 subject you would like to discuss and a pointer to the draft, if=20 any.

Thanks.

Matthew=20

_______________________________________________
ANCP = mailing=20 list
ANCP@ietf.org
https://www.ietf.org/m= ailman/listinfo/ancp

= ------_=_NextPart_001_01C99CF7.972AC342-- From anira@cisco.com Fri Mar 6 02:59:40 2009 Return-Path: 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 CF0BC3A6B0C for ; Fri, 6 Mar 2009 02:59:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMUcFGkf4Lur for ; Fri, 6 Mar 2009 02:59:39 -0800 (PST) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 554003A693F for ; Fri, 6 Mar 2009 02:59:39 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.38,314,1233532800"; d="scan'208";a="140051609" Received: from ind-dkim-1.cisco.com ([64.104.140.57]) by sj-iport-3.cisco.com with ESMTP; 06 Mar 2009 11:00:08 +0000 Received: from india-core-1.cisco.com (india-core-1.cisco.com [64.104.129.221]) by ind-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n26B07JZ010761; Fri, 6 Mar 2009 16:30:07 +0530 Received: from xbh-blr-412.apac.cisco.com (xbh-blr-412.cisco.com [64.104.140.149]) by india-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n26B065b025188; Fri, 6 Mar 2009 11:00:06 GMT Received: from xmb-blr-415.apac.cisco.com ([64.104.140.144]) by xbh-blr-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 6 Mar 2009 16:30:06 +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: Fri, 6 Mar 2009 16:30:07 +0530 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ANCP messages for Multicast query and report Thread-Index: Acl03aoXUeqKXaQARgaXa0fvaISgPwSydzVABahyZTA= References: From: "Aniruddha A (anira)" To: X-OriginalArrivalTime: 06 Mar 2009 11:00:06.0836 (UTC) FILETIME=[B59ACF40:01C99E4A] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12804; t=1236337207; x=1237201207; c=relaxed/simple; s=inddkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=anira@cisco.com; z=From:=20=22Aniruddha=20A=20(anira)=22=20 |Subject:=20RE=3A=20ANCP=20messages=20for=20Multicast=20que ry=20and=20report |Sender:=20; bh=gYh/FOMHIgnDQIeNNwg4Zy4TIYyBrs0rX+O3KKPmtmQ=; b=WLF24ukZxoLmWkvw+4VovcGYhWhWu+zUHOtT6nm1u2l+zyntQuCRq67gmH d3hl/aSlTAKF++QvQ/Yfuu/ZqvA86WZCyCvToiP2vlsTBBtNx0GIQLgYMZjU FYKxJOlS4K; Authentication-Results: ind-dkim-1; header.From=anira@cisco.com; dkim=pass ( sig from cisco.com/inddkim1002 verified; ); Subject: Re: [ANCP] ANCP messages for Multicast query and report X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2009 10:59:40 -0000 =20 Hi All, I propose the following new ANCP message to get all ports on AN for a=20 given Multicast flow (S,G) : - Request message from NAS to AN to get all the ports where a multicast flow is active. The Mandatory Active-Flow-Req TLV is followed by the Flow-ID TLV which identifies which flow we are interested in. 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (0x88-0C) | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers | Sub |MsgType=3D0x92 | Res | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Partition ID | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I| SubMessage Number | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ActiveFlowReq TLV =3D0x103 | ActiveFlow-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast group | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Report message from AN to NAS to send all the ports for a particular flow. The report uses a new TLV - 0x108=20 =20 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (0x88-0C) | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers | Sub |MsgType=3D0x92 | Res | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Partition ID | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I| SubMessage Number | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |ActiveFlow Target Ports =3D 0x108| ActiveFlow-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast group | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Followed by one or more Target-Type TLV which identifies the port +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Target-type-TLV=3D0x1000 | Target-TLV-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ID type | Circuit ID Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Client-ID ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -- Regards, Aniruddha. A -----Original Message----- From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it]=20 Sent: Thursday, February 05, 2009 9:19 PM To: Aniruddha A (anira); ancp@ietf.org Subject: RE: ANCP messages for Multicast query and report Hi Aniruddha, your proposal seems interesting to me, but I have a comment: section 3.4.3 of the ancp-framework draft defines 3 different types of reporting function: - report for one Access Port; - report for one multicast flow; - a global report for one Access Node. If my understanding is correct, your proposal addresses 1 and 3, do you plan to extend it to cover also case 2? Thanks and best regards. Roberta -----Original Message----- From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Aniruddha A (anira) Sent: Monday, January 12, 2009 6:46 PM To: ancp@ietf.org Subject: [ANCP] ANCP messages for Multicast query and report Hi all, In the ANCP multicast extensions, there has to be a way For the NAS to query the AN for the state of active multicast flows on it. We propose the following 2 new messages for this purpose: - Active-Flow Request - Active-Flow Report The query from the NAS can be for all flows on the AN or flows active on a single port. Message Type 0x92 is used. Description and message formats: Active-Flow Request Message The Active Flow Request message is sent by the NAS to the AN to request multicast flow status on the AN. The payload contains the following TLVs: o The Active-Flow-Req TLV (0x103) A Mandatory TLV. o The Target Type TLV. Optional TLV, if present, request is for a single port. On receiving the Active Flow Request message, the AN MUST respond with the Active Flow Report containing the requested information if the Multicast capability has been negotiated. The format of the message is shown below: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (0x88-0C) | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers | Sub |MsgType=3D0x92 | Res | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Partition ID | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I| SubMessage Number | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ActiveFlowReq TLV =3D0x103 | ActiveFlow-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Target-type-TLV=3D0x1000 | Target-TLV-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ID type | Circuit ID Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Client-ID ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1 Active-Flow Report Message The Active Flow Report message is sent from the AN to the NAS in response to the Active Flow Request message. Active Flow Report message contains information on the requested multicast flows. The report can be for a single port, or all ports depending on the Target Type in the request. o Single Port Report If the Active Flow Request had a specific port (the presence of a Target Type TLV), the response has the following format: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (0x88-0C) | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers | Sub |MsgType=3D0x92 | Res | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Partition ID | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I| SubMessage Number | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ActiveFlowPortEntryTLV =3D0x105 | ActiveFlow-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Target-type-TLV=3D0x1000 | Target-TLV-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ID type | Circuit ID Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Client-ID ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2 Followed by the Multicast Flow ID TLVs (0x107), one for each flow on the port. The format of the Flow ID TLV is: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast group | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3 S is the source flag, if set, multicast source address MUST be present (SSM). o Report for all ports If the Active Flow Request did not specify a specific port (no Target Type TLV), the response will have the following format: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (0x88-0C) | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers | Sub |MsgType=3D0x92 | Res | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Partition ID | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I| SubMessage Number | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |ActiveFlowMcastEntryTLV =3D0x104 | ActiveFlow-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AddrFamily | EncType | Mcast group | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4 Followed by the Target Type TLV. A Multicast Entry TLV (0x104) determines the (flow, port), therefore it will have a Flow ID TLV and a Target-Type TLV as its sub TLVs, and there will be as many Multicast Entry TLVs as the number of flows on the AN. We have an implementation running with these message types. -- Regards, Aniruddha. A _______________________________________________ ANCP mailing list ANCP@ietf.org https://www.ietf.org/mailman/listinfo/ancp Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. From root@core3.amsl.com Mon Mar 9 09:45:01 2009 Return-Path: X-Original-To: ancp@ietf.org Delivered-To: ancp@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 56C713A6C94; Mon, 9 Mar 2009 09:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090309164501.56C713A6C94@core3.amsl.com> Date: Mon, 9 Mar 2009 09:45:01 -0700 (PDT) Cc: ancp@ietf.org Subject: [ANCP] I-D Action:draft-ietf-ancp-protocol-05.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 16:45:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Access Node Control Protocol Working Group of the IETF. Title : Protocol for Access Node Control Mechanism in Broadband Networks Author(s) : S. Wadhwa, et al. Filename : draft-ietf-ancp-protocol-05.txt Pages : 62 Date : 2009-03-09 This document describes proposed extensions to the GSMPv3 protocol to allow its use in a broadband environment, as a control plane between Access Nodes (e.g. DSLAM) and Broadband Network Gateways (e.g. NAS). These proposed extensions are required to realize a protocol for "Access Node Control" mechanism as described in [ANCP-FRAMEWORK]. The resulting protocol with the proposed extensions to GSMPv3 [RFC3292] is referred to as "Access Node Control Protocol" (ANCP). This document currently focuses on specific use cases of access node control mechanism for topology discovery, line configuration, and OAM as described in ANCP framework document [ANCP-FRAMEWORK]. It is intended to be augmented by additional protocol specification for future use cases considered in scope by the ANCP charter. ANCP framework document [ANCP-FRAMEWORK] describes the ANCP use-cases in detail. Illustrative text for the use-cases is included here to help the protocol implementer understand the greater context of ANCP protocol interactions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ancp-protocol-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ancp-protocol-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-03-09093234.I-D@ietf.org> --NextPart-- From Matthew.Bocci@alcatel-lucent.com Tue Mar 10 11:37:35 2009 Return-Path: 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 840353A69A1 for ; Tue, 10 Mar 2009 11:37:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.174 X-Spam-Level: X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=0.075, 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 Hiut9VBw59Jp for ; Tue, 10 Mar 2009 11:37:34 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 684053A6407 for ; Tue, 10 Mar 2009 11:37:34 -0700 (PDT) Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2AIc8cp028565 for ; Tue, 10 Mar 2009 19:38:08 +0100 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.31]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 10 Mar 2009 19:38:07 +0100 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_01C9A1AF.5B400BA2" Date: Tue, 10 Mar 2009 19:38:07 +0100 Message-ID: <0458D2EE0C36744BABB36BE37805C29A03777A7C@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: San Francisco Agenda Thread-Index: Acmhr1rs6Kv2zQNjRMC2uVU4og8tFg== From: "BOCCI Matthew" To: X-OriginalArrivalTime: 10 Mar 2009 18:38:07.0771 (UTC) FILETIME=[5B2BB6B0:01C9A1AF] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Subject: [ANCP] San Francisco Agenda X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 18:37:35 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9A1AF.5B400BA2 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please find attached the San Francisco ANCP agenda. Please let me know if you have any comments/updated. Regards, Matthew Tuesday, March 24th, 2009 1520-1700=20 -----------------------------------=20 CHAIRS: Wojciech Dec & Matthew Bocci=20 =20 20 mins WG Status and Update - Chairs=20 15 mins ANCP Multicast Extensions: Francois Le Faucheur (flefauch@cisco.com) http://tools.ietf.org/html/draft-lefaucheur-ancp-mc-extensions-01.txt =20 15 mins Access Node Control Protocol for Source Adress Validation: Frank Xia (xiayangsong@huawei.com) http://www.ietf.org/internet-drafts/draft-kaippallimalil-ancp-sav-00.txt =20 15 mins Applicability of Access Node Control Mechanism to PON based Broadband Networks: Sanjay Wadhwa (swadhwa@juniper.net) http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-01 =20 ------_=_NextPart_001_01C9A1AF.5B400BA2 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable San Francisco Agenda

Please find attached the San Francisco = ANCP agenda.

Please let me know if you have any = comments/updated.

Regards,

Matthew


Tuesday, March 24th, 2009 1520-1700 =
----------------------------------- =
CHAIRS: Wojciech Dec & Matthew = Bocci
        
20 mins WG Status and Update - Chairs =

15 mins ANCP Multicast Extensions: = Francois Le Faucheur (flefauch@cisco.com)
http://tools.ietf.org/html/draft-lefaucheur-ancp-mc-extens= ions-01.txt
 
15 mins Access Node Control Protocol = for Source Adress Validation: Frank Xia (xiayangsong@huawei.com)
http://www.ietf.org/internet-drafts/draft-kaippallimalil-a= ncp-sav-00.txt
        
15 mins Applicability of Access Node = Control Mechanism to PON based Broadband Networks: Sanjay Wadhwa = (swadhwa@juniper.net)

http://tools.ietf.org/html/draft-bitar-wadhwa-ancp-pon-01<= /FONT> 

------_=_NextPart_001_01C9A1AF.5B400BA2-- From Matthew.Bocci@alcatel-lucent.com Mon Mar 16 08:26:23 2009 Return-Path: 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 4556E28C0F8 for ; Mon, 16 Mar 2009 08:26:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.177 X-Spam-Level: X-Spam-Status: No, score=-6.177 tagged_above=-999 required=5 tests=[AWL=0.071, 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 P-IwNRP6wE+o for ; Mon, 16 Mar 2009 08:26:22 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 29E613A683D for ; Mon, 16 Mar 2009 08:26:21 -0700 (PDT) Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.dc-m.alcatel-lucent.com [155.132.6.75]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2GFR0pG028295; Mon, 16 Mar 2009 16:27:01 +0100 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.35]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 16 Mar 2009 16:27:00 +0100 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_01C9A64B.A6215690" Date: Mon, 16 Mar 2009 16:26:59 +0100 Message-ID: <0458D2EE0C36744BABB36BE37805C29A037E9EB2@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Comment on draft-ietf-ancp-protocol-05.txt Thread-Index: AcmmS6XjWGHHld78Smmw3ZalesYFcg== From: "BOCCI Matthew" To: "Sanjay Wadhwa" , "Maglione Roberta" X-OriginalArrivalTime: 16 Mar 2009 15:27:00.0623 (UTC) FILETIME=[A6B249F0:01C9A64B] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Cc: ancp@ietf.org Subject: [ANCP] Comment on draft-ietf-ancp-protocol-05.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 15:26:23 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9A64B.A6215690 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sanjay, Roberta, I have some comments on the latest ANCP protocol draft, specifically related to protocol versioning. I know that we discussed this a while ago and decided that we would use the GSMPv3.1 versioning convention of a 4-bit version field and a 4-bit sub-version. This gives a header that looks like the following: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers | Sub | Message Type | Result| Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ However, the protocol draft is very explicit that ANCP is based on GSMPv3, but the header for GSMPv3 is: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version | Message Type | Result | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Clearly the version numbers are completely incompatible. This means that not only is an ANCP implementation not interoperable with GSMPv3 and it is not clear what an ANCP implementation will do with a GSMP v3 message if it receives it. Section 5 provides some guidance as to what to set the version and sub-version fields to. However, since this is the first use of this version format, I think it would be helpful to define an IANA registry for the version and sub-version values. Please can you also add a statement early in the document (e.g. in the introduction) that although ANCP is based on GSMPv3, it is not interoperable with GSMPv3 defined in RFC3292. Also, in Section 6, please correct "Global Switch Management Protocol version 3 (GSMPv3)" to "General Switch Management Protocol version 3 (GSMPv3)". Regards Matthew ------_=_NextPart_001_01C9A64B.A6215690 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Comment on draft-ietf-ancp-protocol-05.txt

Sanjay, Roberta,

I have some comments on the latest ANCP = protocol draft, specifically related to protocol versioning.

I know that we discussed this a while = ago and decided that we would use the GSMPv3.1 versioning convention of = a 4-bit version field and a 4-bit sub-version. This gives a header that = looks like the following:

 0          &= nbsp;        = 1            =        = 2            =        3
 0 1 2 3 4 5 6 7 8 9 0 1 2 = 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 = 1+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=

| Vers  |  Sub  | = Message Type  | Result|        = Code           = |     = +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<= /P>

However, the protocol draft is = very explicit that ANCP is based on GSMPv3, but the header for GSMPv3 = is:

 0          &= nbsp;        = 1            =        = 2            =        3
 0 1 2 3 4 5 6 7 8 9 0 1 2 = 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1  = +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<= /P>

|    = Version    | Message Type  |    = Result     |     = Code      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Clearly the version numbers are = completely incompatible. This means that not only is an ANCP = implementation not interoperable with GSMPv3 and it is not clear what an = ANCP implementation will do with a GSMP v3 message if it receives = it.

Section 5 provides some guidance = as to what to set the version and sub-version fields to. However, since = this is the first use of this version format, I think it would be = helpful to define an IANA registry for the version and sub-version = values.

Please can you also add a = statement early in the document (e.g. in the introduction) that although = ANCP is based on GSMPv3, it is not interoperable with GSMPv3 defined in = RFC3292.

Also, in Section 6, please = correct "Global Switch Management Protocol version 3 (GSMPv3)" = to "General Switch Management Protocol version 3 = (GSMPv3)".

Regards

Matthew

------_=_NextPart_001_01C9A64B.A6215690-- From roberta.maglione@telecomitalia.it Tue Mar 17 03:51:06 2009 Return-Path: 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 4F0B63A6A5A for ; Tue, 17 Mar 2009 03:51:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.486 X-Spam-Level: X-Spam-Status: No, score=0.486 tagged_above=-999 required=5 tests=[AWL=1.205, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXNEeiSNW3Sn for ; Tue, 17 Mar 2009 03:51:05 -0700 (PDT) Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by core3.amsl.com (Postfix) with ESMTP id 3A7183A67DA for ; Tue, 17 Mar 2009 03:51:05 -0700 (PDT) Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 17 Mar 2009 11:50:05 +0100 Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by grfhub702rm001.griffon.local ([10.19.9.235]) with mapi; Tue, 17 Mar 2009 11:51:45 +0100 From: Maglione Roberta To: 'BOCCI Matthew' Date: Tue, 17 Mar 2009 11:51:44 +0100 Thread-Topic: Comment on draft-ietf-ancp-protocol-05.txt Thread-Index: AcmmS6XjWGHHld78Smmw3ZalesYFcgAobrBw Message-ID: References: <0458D2EE0C36744BABB36BE37805C29A037E9EB2@FRVELSMBS11.ad2.ad.alcatel.com> In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A037E9EB2@FRVELSMBS11.ad2.ad.alcatel.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="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "ancp@ietf.org" Subject: Re: [ANCP] Comment on draft-ietf-ancp-protocol-05.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 10:51:06 -0000 Hello Matthew, thanks for your comments, please see answers in line [RM]. Regards, Roberta ________________________________________ From: BOCCI Matthew [mailto:Matthew.Bocci@alcatel-lucent.com] Sent: Monday, March 16, 2009 4:27 PM To: Sanjay Wadhwa; Maglione Roberta Cc: ancp@ietf.org Subject: Comment on draft-ietf-ancp-protocol-05.txt Sanjay, Roberta, I have some comments on the latest ANCP protocol draft, specifically relate= d to protocol versioning. I know that we discussed this a while ago and decided that we would use the= GSMPv3.1 versioning convention of a 4-bit version field and a 4-bit sub-ve= rsion. This gives a header that looks like the following: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1+-+-+-+-+-+= -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vers |=A0 Sub | Message Type | Result|=A0=A0=A0=A0=A0=A0=A0 Code = |=A0=A0=A0=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+-+-+-+ However, the protocol draft is very explicit that ANCP is based on GSMPv3, = but the header for GSMPv3 is: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+= -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |=A0=A0=A0 Version | Message Type |=A0=A0=A0 Result |=A0=A0=A0=A0 C= ode | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Clearly the version numbers are completely incompatible. This means that no= t only is an ANCP implementation not interoperable with GSMPv3 and it is no= t clear what an ANCP implementation will do with a GSMP v3 message if it re= ceives it. Section 5 provides some guidance as to what to set the version and sub-vers= ion fields to. However, since this is the first use of this version format,= I think it would be helpful to define an IANA registry for the version and= sub-version values. [RM] Ok we will add ANCP specific IANA registry for the version and sub-ver= sion values in next version of the draft. Please can you also add a statement early in the document (e.g. in the intr= oduction) that although ANCP is based on GSMPv3, it is not interoperable wi= th GSMPv3 defined in RFC3292. [RM] Ok we will add this clarification in the introduction. Also, in Section 6, please correct "Global Switch Management Protocol versi= on 3 (GSMPv3)" to "General Switch Management Protocol version 3 (GSMPv3)". [RM] Ok, thanks. Regards Matthew Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per= sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall= a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb= iate ricevuto questo documento per errore siete cortesemente pregati di dar= ne immediata comunicazione al mittente e di provvedere alla sua distruzione= , Grazie. This e-mail and any attachments is confidential and may contain privileged = information intended for the addressee(s) only. Dissemination, copying, pri= nting or use by anybody else is unauthorised. If you are not the intended r= ecipient, please delete this message and any attachments and advise the sen= der by return e-mail, Thanks. From shrirao@cisco.com Fri Mar 20 02:13:58 2009 Return-Path: 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 06BA63A691E for ; Fri, 20 Mar 2009 02:13:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRsgxxA33lxO for ; Fri, 20 Mar 2009 02:13:57 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 07D5E3A6829 for ; Fri, 20 Mar 2009 02:13:57 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,394,1233532800"; d="scan'208";a="270912953" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 20 Mar 2009 09:14:43 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n2K9EgNS029645 for ; Fri, 20 Mar 2009 02:14:42 -0700 Received: from xbh-blr-412.apac.cisco.com (xbh-blr-412.cisco.com [64.104.140.149]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n2K9EJPw011892 for ; Fri, 20 Mar 2009 09:14:41 GMT Received: from xmb-blr-415.apac.cisco.com ([64.104.140.144]) by xbh-blr-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Mar 2009 14:44:40 +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: Fri, 20 Mar 2009 14:44:39 +0530 Message-ID: In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A037E9EB2@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] Comments on draft-lefaucheur-ancp-mc-extensions-01.txt Thread-Index: AcmmS6XjWGHHld78Smmw3ZalesYFcgC7zVNQ References: <0458D2EE0C36744BABB36BE37805C29A037E9EB2@FRVELSMBS11.ad2.ad.alcatel.com> From: "Shridhar Rao (shrirao)" To: X-OriginalArrivalTime: 20 Mar 2009 09:14:40.0453 (UTC) FILETIME=[4C91DF50:01C9A93C] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1413; t=1237540482; x=1238404482; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=shrirao@cisco.com; z=From:=20=22Shridhar=20Rao=20(shrirao)=22=20 |Subject:=20=20[ANCP]=20Comments=20on=20draft-lefaucheur-an cp-mc-extensions-01.txt |Sender:=20; bh=yyPHG6zNBXSKRElr1oysIjBgVd+8u+uLGzJ0kFha7t4=; b=aKYypFmrf6XCnfkU7/Qg48zKIQtyCQzi76LHCk0R68jSsV3iMLmEOSwcgD DdWOTbMHadbhXag01+oMDfCIqqTfegxbGkaeulU7LKZR8zP4Oj+Hwi++jptc AhUnPDG445; Authentication-Results: sj-dkim-3; header.From=shrirao@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Subject: [ANCP] Comments on draft-lefaucheur-ancp-mc-extensions-01.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 09:13:58 -0000 Hi Francois , et al ,=20 =20 Queries/comments/observations : 1. Program limit (I guess the number of multicast flows allowed for a subscriber ) - It is mentioned only once in the draft. There is no TLV mentioned for this. Is this to be configured locally on AN?=20 2. Timing of bandwidth reallocation and multicast admission control messages : if AN is waiting for a response to bandwidth reallocation can it send MCAST admission control in the middle (for the same subscriber port)? What happens if the NAS answers positively to the Mcast Admission control message (i.e. Access Control is OK) but responds negatively to the Bandwidth Allocation message (and thus AN has to reject flow). The draft mentions running a timer at AN after it sends a Multicast admission control but how long can we wait at AN for bandwidth reallocation response? 3. What would happen when bandwidth delegation control TLV is turned on whereas the capability negotiated between AN and NAS through transactional multicast cap. is only 2 (meaning no bandwidth delegation but only admission control) ? If the negotiated Capability is not equal to 3, then NAS should not send bandwidth delegation TLV to activate it. =09 4. Discovering IPV6 multicast joins/leaves: Perhaps it wouldn't hurt to replace "IGMP" by "IGMP/MLD" everywhere so we keep it clear. Thanks and regards, -shridhar- =09 From acassen@freebox.fr Mon Mar 23 05:37:54 2009 Return-Path: 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 8B0BE3A6A92 for ; Mon, 23 Mar 2009 05:37:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.809 X-Spam-Level: * X-Spam-Status: No, score=1.809 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_40=-0.185, HELO_EQ_FR=0.35, RCVD_IN_SBL=1.551] 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 uJbaw5W5XaEU for ; Mon, 23 Mar 2009 05:37:53 -0700 (PDT) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.1]) by core3.amsl.com (Postfix) with ESMTP id 9EE053A67A3 for ; Mon, 23 Mar 2009 05:37:51 -0700 (PDT) Received: from smtp1-g21.free.fr (localhost [127.0.0.1]) by smtp1-g21.free.fr (Postfix) with ESMTP id 7EE0794001B for ; Mon, 23 Mar 2009 13:38:37 +0100 (CET) Received: from mail.lnxos.net (lnxos.staff.proxad.net [213.228.1.83]) by smtp1-g21.free.fr (Postfix) with ESMTP id A8B2E940187 for ; Mon, 23 Mar 2009 13:38:35 +0100 (CET) Received: from [192.168.200.150] (lnxos-dev [192.168.200.150]) by mail.lnxos.net (Postfix) with ESMTP id 736747D0A for ; Mon, 23 Mar 2009 13:38:35 +0100 (CET) From: Alexandre Cassen To: ancp@ietf.org Content-Type: text/plain Organization: Freebox Date: Mon, 23 Mar 2009 13:47:39 +0100 Message-Id: <1237812459.28263.385.camel@lnxos-dev> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Subject: [ANCP] Graceful restart for MC extension X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 12:37:54 -0000 Hi, Having the ability to manage AN multicast membership from NAS is a great flexibility. In such an environnement a NAS manage a lot of AN. Using ANCP replication control message MUST be reliable in respect of service it provides. I mean, if we are using ANCP replication control message to perform IPTV zapping there is an important need to have a fallback adjacency or other kind of mecanism to provide the best end user experience possible especially if active NAS crash down. If a NAS is managing 100 AN, each AN hosting lot of customers then NAS crash will directly impact end user experience by disabling service. Plus, it will provide an 'avalanche' side effect, especially for IPTV zapping use-case. The very first action end-user will have, when zapping is not working, is to RETRY... it generates TONES of retry which will lead to a mass-flood when zapping is back to life (secondary NAS takeover). IMHO, there is an IMPORTANT need to have a transparent and rapid fallback mecanism in order to protect end-user experience and any kind of side-effect. A simple approach would be to define a fallback adjacency as introduced in : http://www.ietf.org/mail-archive/web/ancp/current/msg00787.html Another approach would be to simply remove the non-correlation between layer4 and ANCP. IMHO, if something is wired at layer4 side then ANCP must be sync with this. If TCP RST is received (or any other issue) then ANCP is broken and not working. Why waiting adj timer expiration at AN side to bring up a new adjacency ? Layer4 broken could be put into loss-of-synchronization equation. regards, Alexandre From acassen@freebox.fr Mon Mar 23 05:45:10 2009 Return-Path: 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 5B0473A6A92 for ; Mon, 23 Mar 2009 05:45:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.855 X-Spam-Level: * X-Spam-Status: No, score=1.855 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_SBL=1.551] 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 OodoFF7aIuzE for ; Mon, 23 Mar 2009 05:45:09 -0700 (PDT) Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by core3.amsl.com (Postfix) with ESMTP id 929A03A67A3 for ; Mon, 23 Mar 2009 05:45:07 -0700 (PDT) Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 1D3A6E081AC for ; Mon, 23 Mar 2009 13:45:54 +0100 (CET) Received: from mail.lnxos.net (lnxos.staff.proxad.net [213.228.1.83]) by smtp6-g21.free.fr (Postfix) with ESMTP id 447EDE081E9 for ; Mon, 23 Mar 2009 13:45:52 +0100 (CET) Received: from [192.168.200.150] (lnxos-dev [192.168.200.150]) by mail.lnxos.net (Postfix) with ESMTP id 2B04B7D0A for ; Mon, 23 Mar 2009 13:45:52 +0100 (CET) From: Alexandre Cassen To: ancp@ietf.org Content-Type: text/plain Organization: Freebox Date: Mon, 23 Mar 2009 13:54:55 +0100 Message-Id: <1237812895.28263.392.camel@lnxos-dev> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Subject: [ANCP] Graceful restart : NAS Multi-homing X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 12:45:10 -0000 Hi, hmm, another approach would be to use SCTP instead of TCP. It will then benefit SCTP intrinsec multi-homing design to address graceful restart. regs, Alexandre From Matthew.Bocci@alcatel-lucent.com Tue Mar 31 08:36:02 2009 Return-Path: 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 830823A6D7E for ; Tue, 31 Mar 2009 08:36:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.192 X-Spam-Level: X-Spam-Status: No, score=-6.192 tagged_above=-999 required=5 tests=[AWL=0.056, 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 2N-O7ZJbuqrT for ; Tue, 31 Mar 2009 08:36:01 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 7C0B53A6CA2 for ; Tue, 31 Mar 2009 08:36:00 -0700 (PDT) Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2VFaqEN028204 for ; Tue, 31 Mar 2009 17:36:57 +0200 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 17:36:52 +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_01C9B216.83DD9B1E" Date: Tue, 31 Mar 2009 17:36:52 +0200 Message-ID: <0458D2EE0C36744BABB36BE37805C29A039300A4@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-bitar-wadhwa-ancp-pon-01.txt to WG draft? Thread-Index: AcmyFoOHJTCTudvkSS+NhWzE018hTQ== From: "BOCCI Matthew" To: X-OriginalArrivalTime: 31 Mar 2009 15:36:52.0900 (UTC) FILETIME=[83EAD640:01C9B216] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: [ANCP] draft-bitar-wadhwa-ancp-pon-01.txt to WG draft? X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 15:36:02 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9B216.83DD9B1E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There was a proposal at the last IETF to accept draft-bitar-wadhwa-ancp-pon-01.txt as an ANCP working group draft. This is the start of a two week poll to test the consensus of the WG. Please can you respond to the ANCP list, indicating if you support this (or otherwise). The poll will close on 14th April 2009. Regards Matthew=20 ------_=_NextPart_001_01C9B216.83DD9B1E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable draft-bitar-wadhwa-ancp-pon-01.txt to WG draft?

There was a proposal at the last IETF = to accept draft-bitar-wadhwa-ancp-pon-01.txt as an ANCP working group = draft.

This is the start of a two week poll to = test the consensus of the WG.

Please can you respond to the ANCP = list, indicating if you support this (or otherwise).

The poll will close on 14th April = 2009.

Regards

Matthew

------_=_NextPart_001_01C9B216.83DD9B1E-- From Matthew.Bocci@alcatel-lucent.com Tue Mar 31 08:45:39 2009 Return-Path: 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 984853A6D64 for ; Tue, 31 Mar 2009 08:45:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.194 X-Spam-Level: X-Spam-Status: No, score=-6.194 tagged_above=-999 required=5 tests=[AWL=0.054, 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 9HW5nLMioS04 for ; Tue, 31 Mar 2009 08:45:38 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 5F1B628C16F for ; Tue, 31 Mar 2009 08:45:38 -0700 (PDT) Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2VFkZZg013513 for ; Tue, 31 Mar 2009 17:46:35 +0200 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 17:46:35 +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_01C9B217.DF14249B" Date: Tue, 31 Mar 2009 17:46:34 +0200 Message-ID: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Splitting multicast from protocol doc Thread-Index: AcmyF963r95pJCb0R/a3GxzjO9kQMQ== From: "BOCCI Matthew" To: X-OriginalArrivalTime: 31 Mar 2009 15:46:35.0174 (UTC) FILETIME=[DEFACC60:01C9B217] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Subject: [ANCP] Splitting multicast from protocol doc X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 15:45:39 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9B217.DF14249B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There was a proposal at the last IETF to take the multicast text from draft-ietf-ancp-protocol-05 and merge it with draft-lefaucheur-ancp-mc-extensions-01. We would thus have two protocol drafts: draft-ietf-ancp-protocol : Containing the solutions for the Topology discovery, line configuration and OAM use cases Multicast extensions draft: Containing the transactional multicast solution and all of the content of draft-lefaucheur This would allow us to move forward with WG LC on the basic use case solutions, and also keep all of the multicast extensions in a single draft. Please can you indicate to the list whether you support this proposal. Regards Matthew ------_=_NextPart_001_01C9B217.DF14249B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Splitting multicast from protocol doc

There was a proposal at the last IETF = to take the multicast text from draft-ietf-ancp-protocol-05 and merge it = with draft-lefaucheur-ancp-mc-extensions-01.

We would thus have two protocol = drafts:

draft-ietf-ancp-protocol : Containing = the solutions for the Topology discovery, line configuration and OAM use = cases
Multicast extensions draft: Containing = the transactional multicast solution and all of the content of = draft-lefaucheur

This would allow us to move forward = with WG LC on the basic use case solutions, and also keep all of the = multicast extensions in a single draft.

Please can you indicate to the list = whether you support this proposal.

Regards

Matthew


------_=_NextPart_001_01C9B217.DF14249B-- From Matthew.Bocci@alcatel-lucent.com Tue Mar 31 08:50:53 2009 Return-Path: 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 A47E73A6D64 for ; Tue, 31 Mar 2009 08:50:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.197 X-Spam-Level: X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 DAo2rYBxPTuk for ; Tue, 31 Mar 2009 08:50:52 -0700 (PDT) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id AB3FE3A6837 for ; Tue, 31 Mar 2009 08:50:50 -0700 (PDT) Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.dc-m.alcatel-lucent.com [155.132.6.77]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2VFpZx9015511; Tue, 31 Mar 2009 17:51:46 +0200 Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS05.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 17:51:38 +0200 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: Tue, 31 Mar 2009 17:51:37 +0200 Message-ID: <0458D2EE0C36744BABB36BE37805C29A039300B7@FRVELSMBS11.ad2.ad.alcatel.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] ANCP messages for Multicast query and report Thread-Index: Acl03aoXUeqKXaQARgaXa0fvaISgPwSydzVABahyZTAE87C3AA== References: From: "BOCCI Matthew" To: "Aniruddha A (anira)" , X-OriginalArrivalTime: 31 Mar 2009 15:51:38.0709 (UTC) FILETIME=[93E69050:01C9B218] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Subject: Re: [ANCP] ANCP messages for Multicast query and report X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 15:50:53 -0000 This was discussed in San Francisco, and there seemed to be agreement in principle, but we would appreciate feedback on this proposal on the list from the WG. Matthew =20 > -----Original Message----- > From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On=20 > Behalf Of Aniruddha A (anira) > Sent: 06 March 2009 11:00 > To: ancp@ietf.org > Subject: Re: [ANCP] ANCP messages for Multicast query and report >=20 >=20 > =20 > Hi All, >=20 > I propose the following new ANCP message to get all ports on=20 > AN for a given Multicast flow (S,G) : >=20 > - Request message from NAS to AN to get all the ports where a=20 > multicast > flow is active. > The Mandatory Active-Flow-Req TLV is followed by the Flow-ID TLV > which identifies which flow we are interested in. >=20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type (0x88-0C) | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Vers | Sub |MsgType=3D0x92 | Res | Code = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Partition ID | Transaction Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |I| SubMessage Number | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | ActiveFlowReq TLV =3D0x103 | ActiveFlow-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast source | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast group | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > - Report message from AN to NAS to send all the ports for a=20 > particular flow. > The report uses a new TLV - 0x108=20 > =20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type (0x88-0C) | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Vers | Sub |MsgType=3D0x92 | Res | Code = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Partition ID | Transaction Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |I| SubMessage Number | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |ActiveFlow Target Ports =3D 0x108| ActiveFlow-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast source | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast group | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Followed by one or more Target-Type TLV which identifies the port >=20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Target-type-TLV=3D0x1000 | Target-TLV-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | ID type | Circuit ID Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | > ~ Client-ID ~ > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 >=20 > -- > Regards, > Aniruddha. A >=20 > -----Original Message----- > From: Maglione Roberta [mailto:roberta.maglione@telecomitalia.it] > Sent: Thursday, February 05, 2009 9:19 PM > To: Aniruddha A (anira); ancp@ietf.org > Subject: RE: ANCP messages for Multicast query and report >=20 > Hi Aniruddha, > your proposal seems interesting to me, but I have a comment: > section 3.4.3 of the ancp-framework draft defines 3 different=20 > types of reporting function: > - report for one Access Port; > - report for one multicast flow; > - a global report for one Access Node. >=20 > If my understanding is correct, your proposal addresses 1 and=20 > 3, do you plan to extend it to cover also case 2? >=20 > Thanks and best regards. > Roberta >=20 > -----Original Message----- > From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On=20 > Behalf Of Aniruddha A (anira) > Sent: Monday, January 12, 2009 6:46 PM > To: ancp@ietf.org > Subject: [ANCP] ANCP messages for Multicast query and report >=20 > Hi all, >=20 > In the ANCP multicast extensions, there has to be a way For=20 > the NAS to query the AN for the state of active multicast flows on it. >=20 > We propose the following 2 new messages for this purpose: > - Active-Flow Request > - Active-Flow Report >=20 > The query from the NAS can be for all flows on the AN or=20 > flows active on a single port. Message Type 0x92 is used. >=20 > Description and message formats: >=20 > Active-Flow Request Message >=20 > The Active Flow Request message is sent by the NAS to the AN to > request multicast flow status on the AN. The payload contains the > following TLVs: >=20 > o The Active-Flow-Req TLV (0x103) > A Mandatory TLV. >=20 > o The Target Type TLV. > Optional TLV, if present, request is for a single port. >=20 > On receiving the Active Flow Request message, the AN MUST respond > with the Active Flow Report containing the requested information if > the Multicast capability has been negotiated. The format of the > message is shown below: >=20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type (0x88-0C) | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Vers | Sub |MsgType=3D0x92 | Res | Code = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Partition ID | Transaction Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |I| SubMessage Number | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | ActiveFlowReq TLV =3D0x103 | ActiveFlow-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Target-type-TLV=3D0x1000 | Target-TLV-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | ID type | Circuit ID Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | > ~ Client-ID ~ > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Figure 1 >=20 > Active-Flow Report Message >=20 > The Active Flow Report message is sent from the AN to the NAS in > response to the Active Flow Request message. Active Flow Report > message contains information on the requested multicast flows. The > report can be for a single port, or all ports depending on=20 > the Target > Type in the request. >=20 > o Single Port Report >=20 > If the Active Flow Request had a specific port (the presence of a > Target Type TLV), the response has the following format: >=20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type (0x88-0C) | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Vers | Sub |MsgType=3D0x92 | Res | Code = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Partition ID | Transaction Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |I| SubMessage Number | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | ActiveFlowPortEntryTLV =3D0x105 | ActiveFlow-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Target-type-TLV=3D0x1000 | Target-TLV-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | ID type | Circuit ID Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | > ~ Client-ID ~ > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Figure 2 >=20 > Followed by the Multicast Flow ID TLVs (0x107), one for=20 > each flow on > the port. The format of the Flow ID TLV is: >=20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast source | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast group | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Figure 3 >=20 > S is the source flag, if set, multicast source address MUST be > present (SSM). >=20 > o Report for all ports >=20 > If the Active Flow Request did not specify a specific port=20 > (no Target > Type TLV), the response will have the following format: >=20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type (0x88-0C) | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Vers | Sub |MsgType=3D0x92 | Res | Code = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Partition ID | Transaction Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |I| SubMessage Number | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > |ActiveFlowMcastEntryTLV =3D0x104 | ActiveFlow-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Mcast Flow ID TLV =3D 0x107 |S| Mcast Flow ID-Length = | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast source | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | AddrFamily | EncType | Mcast group | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Figure 4 >=20 > Followed by the Target Type TLV. >=20 > A Multicast Entry TLV (0x104) determines the (flow, port),=20 > therefore > it will have a Flow ID TLV and a Target-Type TLV as its=20 > sub TLVs, and > there will be as many Multicast Entry TLVs as the number=20 > of flows on > the AN. >=20 > We have an implementation running with these message types. > -- > Regards, > Aniruddha. A > _______________________________________________ > ANCP mailing list > ANCP@ietf.org > https://www.ietf.org/mailman/listinfo/ancp >=20 > Questo messaggio e i suoi allegati sono indirizzati=20 > esclusivamente alle persone indicate. La diffusione, copia o=20 > qualsiasi altra azione derivante dalla conoscenza di queste=20 > informazioni sono rigorosamente vietate. Qualora abbiate=20 > ricevuto questo documento per errore siete cortesemente=20 > pregati di darne immediata comunicazione al mittente e di=20 > provvedere alla sua distruzione, Grazie. >=20 > This e-mail and any attachments is confidential and may=20 > contain privileged information intended for the addressee(s) only. > Dissemination, copying, printing or use by anybody else is=20 > unauthorised. > If you are not the intended recipient, please delete this=20 > message and any attachments and advise the sender by return=20 > e-mail, Thanks. >=20 > _______________________________________________ > ANCP mailing list > ANCP@ietf.org > https://www.ietf.org/mailman/listinfo/ancp >=20 From wwwrun@core3.amsl.com Tue Mar 31 08:46:31 2009 Return-Path: X-Original-To: ancp@ietf.org Delivered-To: ancp@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 2F07728C16C; Tue, 31 Mar 2009 08:46:30 -0700 (PDT) To: swadhwa@juniper.net, roberta.maglione@telecomitalia.it, thomas.haag@t-systems.com, jmoisand@juniper.net, ssubramanian@juniper.net, norbert.voigt@siemens.com From: IETF Secretariat Message-Id: <20090331154631.2F07728C16C@core3.amsl.com> Date: Tue, 31 Mar 2009 08:46:31 -0700 (PDT) X-Mailman-Approved-At: Tue, 31 Mar 2009 08:52:23 -0700 Cc: matthew.bocci@alcatel-lucent.com, rdroms@cisco.com, jari.arkko@piuha.net, ancp@ietf.org, ipr-announce@ietf.org Subject: [ANCP] Posting of IPR Disclosure related to Deutsche Telekom AG's Statement about IPR related to draft-ietf-ancp-framework-08 and draft-ietf-ancp-protocol-05 X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 15:46:31 -0000 Dear Sanjay Wadhwa, Roberta Maglione, Thomas Haag, Jerome Moisand, Swami Subramanian, Norber Voigt: An IPR disclosure that pertains to your Internet-Draft entitled "Protocol for Access Node Control Mechanism in Broadband Networks" (draft-ietf-ancp-protocol) was submitted to the IETF Secretariat on 2009-03-31 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1124/). The title of the IPR disclosure is "Deutsche Telekom AG's Statement about IPR related to draft-ietf-ancp-framework-08 and draft-ietf-ancp-protocol-05." The IETF Secretariat From wwwrun@core3.amsl.com Tue Mar 31 08:46:31 2009 Return-Path: X-Original-To: ancp@ietf.org Delivered-To: ancp@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 2B3AA3A6D90; Tue, 31 Mar 2009 08:46:30 -0700 (PDT) To: swadhwa@juniper.net, norbert.voigt@nsn.com, michel.platnic@ecitele.com, sven.ooghe@alcatel-lucent.com, haagt@telekom.de From: IETF Secretariat Message-Id: <20090331154631.2B3AA3A6D90@core3.amsl.com> Date: Tue, 31 Mar 2009 08:46:31 -0700 (PDT) X-Mailman-Approved-At: Tue, 31 Mar 2009 08:52:23 -0700 Cc: matthew.bocci@alcatel-lucent.com, rdroms@cisco.com, jari.arkko@piuha.net, ancp@ietf.org, ipr-announce@ietf.org Subject: [ANCP] Posting of IPR Disclosure related to Deutsche Telekom AG's Statement about IPR related to draft-ietf-ancp-framework-08 and draft-ietf-ancp-protocol-05 X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 15:46:31 -0000 Dear Sanjay Wadhwa, Norbert Voigt, Michel Platnic, Sven Ooghe, Thomas Haag: An IPR disclosure that pertains to your Internet-Draft entitled "Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks" (draft-ietf-ancp-framework) was submitted to the IETF Secretariat on 2009-03-31 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1124/). The title of the IPR disclosure is "Deutsche Telekom AG's Statement about IPR related to draft-ietf-ancp-framework-08 and draft-ietf-ancp-protocol-05." The IETF Secretariat From tom.taylor@rogers.com Tue Mar 31 08:54:11 2009 Return-Path: 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 964F93A6DA6 for ; Tue, 31 Mar 2009 08:54:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.146 X-Spam-Level: X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[AWL=0.453, 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 HGtuTcPWF-jV for ; Tue, 31 Mar 2009 08:54:10 -0700 (PDT) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by core3.amsl.com (Postfix) with SMTP id A58E53A6D98 for ; Tue, 31 Mar 2009 08:54:10 -0700 (PDT) Received: (qmail 99504 invoked from network); 31 Mar 2009 15:55:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=tyFUlhhdSYz28MXp+v+am0FDgkNgkvcuwJtz9O3LX/FYF2UaLi/TBw37UM+hF9w7BlltC6OoJhmfCV5HHhTaFS3dfHWCJYNpwBf7aWVbd02PGlH+ezzJaRjG1p4NxqZpX3FeZO/HzE81Q6u37ALGSWyZ13OGbvESWfGSw43VMd4= ; Received: from unknown (HELO ?192.168.0.100?) (tom.taylor@72.140.46.24 with plain) by smtp100.rog.mail.re2.yahoo.com with SMTP; 31 Mar 2009 15:55:09 -0000 X-YMail-OSG: wmUn6xMVM1n1GhO0DRtGVabHVYS.W4S67mYf18YsZUQP9fGzZEdVzRncdm4ZT93qUg-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <49D23CDF.7090504@rogers.com> Date: Tue, 31 Mar 2009 11:55:11 -0400 From: Tom Taylor User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: BOCCI Matthew References: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ancp@ietf.org Subject: Re: [ANCP] Splitting multicast from protocol doc X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 15:54:11 -0000 I support the proposal. I do have suggestions for editorial reorganization of the base document, which I discussed in broad outline with Roberta and Sanjay. I undertook to follow up with a detailed proposal to them. Basically I think that the organization we have in the mc-extensions document is a bit more accessible. In particular, all TLV documentation should be moved to one section. BOCCI Matthew wrote: > There was a proposal at the last IETF to take the multicast text from > draft-ietf-ancp-protocol-05 and merge it with > draft-lefaucheur-ancp-mc-extensions-01. > > We would thus have two protocol drafts: > > draft-ietf-ancp-protocol : Containing the solutions for the Topology > discovery, line configuration and OAM use cases > Multicast extensions draft: Containing the transactional multicast > solution and all of the content of draft-lefaucheur > > This would allow us to move forward with WG LC on the basic use case > solutions, and also keep all of the multicast extensions in a single > draft. > > Please can you indicate to the list whether you support this proposal. > > Regards > > Matthew > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > ANCP mailing list > ANCP@ietf.org > https://www.ietf.org/mailman/listinfo/ancp From tom.taylor@rogers.com Tue Mar 31 09:04:49 2009 Return-Path: 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 057453A6D98 for ; Tue, 31 Mar 2009 09:04:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.16 X-Spam-Level: X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[AWL=0.439, 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 Iev-sB8XCLeM for ; Tue, 31 Mar 2009 09:04:48 -0700 (PDT) Received: from smtp117.rog.mail.re2.yahoo.com (smtp117.rog.mail.re2.yahoo.com [68.142.225.233]) by core3.amsl.com (Postfix) with SMTP id 113863A681D for ; Tue, 31 Mar 2009 09:04:47 -0700 (PDT) Received: (qmail 69440 invoked from network); 31 Mar 2009 16:05:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=KOuMHhN1Siho6zGoSVgG96Q2Kgin2WOQjjPHhYxjIRFmsvQrbdCCpJdHWmKOYSGlGjyWEvxeRzZh8mA8ZPCdCBetHRxP6O08FW/uUxnsgzTh7B0inSlLQdi+lLOkVR1uJg/5QcloUkYaBBGxZ0fIAewvytaTuxuIoX45ZTsWWNs= ; Received: from unknown (HELO ?192.168.0.100?) (tom.taylor@72.140.46.24 with plain) by smtp117.rog.mail.re2.yahoo.com with SMTP; 31 Mar 2009 16:05:46 -0000 X-YMail-OSG: QYQYm_MVM1ntGv5KQC8wLxxLvyIYLFHPomxLkp5yYbrOI5fFavqC0sT5u042kB6o5Q-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <49D23F5C.7020808@rogers.com> Date: Tue, 31 Mar 2009 12:05:48 -0400 From: Tom Taylor User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: BOCCI Matthew References: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> <49D23CDF.7090504@rogers.com> In-Reply-To: <49D23CDF.7090504@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ancp@ietf.org Subject: Re: [ANCP] Splitting multicast from protocol doc X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 16:04:49 -0000 One more point on the base document: it should specify in detail the usage of all fields in the general message header, or where this is not suitable, it should specify what information other documents must provide and under what circumstances they must provide it, presumably in their message descriptions. There is material of this sort in the mc-extensions document that I think should be covered in the base document only. Tom Taylor wrote: > I support the proposal. I do have suggestions for editorial > reorganization of the base document, which I discussed in broad outline > with Roberta and Sanjay. I undertook to follow up with a detailed > proposal to them. Basically I think that the organization we have in the > mc-extensions document is a bit more accessible. In particular, all TLV > documentation should be moved to one section. > ... From agmalis@gmail.com Tue Mar 31 10:09:36 2009 Return-Path: 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 847F63A68BA for ; Tue, 31 Mar 2009 10:09:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.099 X-Spam-Level: X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 KM9XxTQhJ8pl for ; Tue, 31 Mar 2009 10:09:35 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by core3.amsl.com (Postfix) with ESMTP id B0F163A6894 for ; Tue, 31 Mar 2009 10:09:35 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id d11so2352261and.4 for ; Tue, 31 Mar 2009 10:10:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=mY5EWFWSjVwb0p4iZ9gw0IJ+01r8VtyYIqyBjVbyOho=; b=FELy3QtMqkcma2wBsngic2dTzn9VmL4zvxM4vYbQlQ66ZL/h6peFb+5hURHGPR5oOW BWmSB5JZFbUStPkT3Cw/CGrfhcoeO/KfJ86sWMDufidrZsUjqZ4giWfqteOBvXXFAHYH Iy2QeuswnGbTGn0h0q9epx5DdZ+PfXbOwi7pg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=B/56N7ZQsxWTFh25dWdDf0NTuRmo0SCXQTQnz20W2UMCbfp4FwZdaZBVw71vQl5dq3 JAfyD6jDf8OqOpS4dDLiVhY0X+fAcM/wyuJDdj7eFrQh+RfnGVtkouzA9g8JSGRPgi9D O5i7tAfpdNOVwz+Uwx0efwKxBEAfLLxeo/HqQ= MIME-Version: 1.0 In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A039300A4@FRVELSMBS11.ad2.ad.alcatel.com> References: <0458D2EE0C36744BABB36BE37805C29A039300A4@FRVELSMBS11.ad2.ad.alcatel.com> Date: Tue, 31 Mar 2009 13:10:19 -0400 Received: by 10.100.96.9 with SMTP id t9mr5163351anb.95.1238519434401; Tue, 31 Mar 2009 10:10:34 -0700 (PDT) Message-ID: <8c99930d0903311010i3619eb76s4ba3f1a46e57e303@mail.gmail.com> From: "Andrew G. Malis" To: ancp@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [ANCP] draft-bitar-wadhwa-ancp-pon-01.txt to WG draft? X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 17:09:36 -0000 Support. 2009/3/31 BOCCI Matthew : > There was a proposal at the last IETF to accept > draft-bitar-wadhwa-ancp-pon-01.txt as an ANCP working group draft. > > This is the start of a two week poll to test the consensus of the WG. > > Please can you respond to the ANCP list, indicating if you support this (or > otherwise). > > The poll will close on 14th April 2009. > > Regards > > Matthew > > _______________________________________________ > ANCP mailing list > ANCP@ietf.org > https://www.ietf.org/mailman/listinfo/ancp > > From flefauch@cisco.com Tue Mar 31 13:20:07 2009 Return-Path: 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 5A8D728C148 for ; Tue, 31 Mar 2009 13:20:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.931 X-Spam-Level: X-Spam-Status: No, score=-9.931 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 IjkfkvEOMI5j for ; Tue, 31 Mar 2009 13:20:05 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 779AE3A6AEF for ; Tue, 31 Mar 2009 13:20:05 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.39,303,1235952000"; d="scan'208,217";a="37144200" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 31 Mar 2009 20:21:03 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n2VKL3O0016856; Tue, 31 Mar 2009 22:21:03 +0200 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n2VKL3fN012429; Tue, 31 Mar 2009 20:21:03 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Mar 2009 22:21:03 +0200 Received: from ams-flefauch-8715.cisco.com ([10.55.161.198]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Mar 2009 22:21:02 +0200 Message-Id: From: Francois Le Faucheur IMAP To: BOCCI Matthew In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> Content-Type: multipart/alternative; boundary=Apple-Mail-4-378139791 Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 31 Mar 2009 22:21:01 +0200 References: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 31 Mar 2009 20:21:03.0095 (UTC) FILETIME=[36A02070:01C9B23E] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2861; t=1238530863; x=1239394863; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20 |Subject:=20Re=3A=20[ANCP]=20Splitting=20multicast=20from=2 0protocol=20doc |Sender:=20; bh=/xlH72kdr+nCxq+pWDcqVdtFsAHAbJi9evjqc4T+azM=; b=elifZeFVPdfYgyPguq2hfjP2R9CepE5OFDx66gL/OezNybj2emt3iRN2Ab sUXBhPQ2/4vxh/IJIqpXZ6KZs924uEuW86e+nJURlMDPJ3Tk3QuQEsuag4sd fnwVlCaEso; Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: ancp@ietf.org Subject: Re: [ANCP] Splitting multicast from protocol doc X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 20:20:07 -0000 --Apple-Mail-4-378139791 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit support. Francois On 31 Mar 2009, at 17:46, BOCCI Matthew wrote: > There was a proposal at the last IETF to take the multicast text > from draft-ietf-ancp-protocol-05 and merge it with draft-lefaucheur- > ancp-mc-extensions-01. > > We would thus have two protocol drafts: > > draft-ietf-ancp-protocol : Containing the solutions for the Topology > discovery, line configuration and OAM use cases > Multicast extensions draft: Containing the transactional multicast > solution and all of the content of draft-lefaucheur > > This would allow us to move forward with WG LC on the basic use case > solutions, and also keep all of the multicast extensions in a single > draft. > > Please can you indicate to the list whether you support this proposal. > > Regards > > Matthew > > > _______________________________________________ > ANCP mailing list > ANCP@ietf.org > https://www.ietf.org/mailman/listinfo/ancp --Apple-Mail-4-378139791 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
=

There was a proposal at the last IETF to take the = multicast text from draft-ietf-ancp-protocol-05 and merge it with = draft-lefaucheur-ancp-mc-extensions-01.

We would thus have two protocol drafts: =

draft-ietf-ancp-protocol : = Containing the solutions for the Topology discovery, line configuration = and OAM use cases
Multicast = extensions draft: Containing the transactional multicast solution and = all of the content of draft-lefaucheur

This would allow us to move forward with WG LC on the = basic use case solutions, and also keep all of the multicast extensions = in a single draft.

Please = can you indicate to the list whether you support this proposal. =

Regards

Matthew


= _______________________________________________
ANCP mailing = list
ANCP@ietf.org
https://www.ietf.org/ma= ilman/listinfo/ancp

= --Apple-Mail-4-378139791-- From swadhwa@juniper.net Tue Mar 31 17:41:13 2009 Return-Path: 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 867853A6ADC for ; Tue, 31 Mar 2009 17:41:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.098 X-Spam-Level: X-Spam-Status: No, score=-4.098 tagged_above=-999 required=5 tests=[AWL=-2.501, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001, J_BACKHAIR_12=1, J_BACKHAIR_21=1, J_BACKHAIR_22=1, J_BACKHAIR_42=1, J_BACKHAIR_52=1, 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 vY7SRu7bgTr0 for ; Tue, 31 Mar 2009 17:41:12 -0700 (PDT) Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by core3.amsl.com (Postfix) with ESMTP id A68A33A6888 for ; Tue, 31 Mar 2009 17:41:12 -0700 (PDT) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKSdK4Ylt7YzASyby7KyzMdr1VRMl5Z8Us@postini.com; Tue, 31 Mar 2009 17:42:12 PDT Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Tue, 31 Mar 2009 17:37:21 -0700 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 17:37:21 -0700 Received: from antipi.jnpr.net ([10.10.2.34]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 31 Mar 2009 17:37:21 -0700 Received: from proton.jnpr.net ([10.10.2.37]) by antipi.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Mar 2009 20:37:20 -0400 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_01C9B262.03C40E92" Date: Tue, 31 Mar 2009 20:37:18 -0400 Message-ID: <9BD5D7887235424FA97DFC223CAE3C281BB10E8F@proton.jnpr.net> In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] Splitting multicast from protocol doc Thread-Index: AcmyF963r95pJCb0R/a3GxzjO9kQMQASf1CA References: <0458D2EE0C36744BABB36BE37805C29A039300AF@FRVELSMBS11.ad2.ad.alcatel.com> From: Sanjay Wadhwa To: "BOCCI Matthew" , X-OriginalArrivalTime: 01 Apr 2009 00:37:20.0113 (UTC) FILETIME=[040ADE10:01C9B262] Subject: Re: [ANCP] Splitting multicast from protocol doc X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2009 00:41:13 -0000 ------_=_NextPart_001_01C9B262.03C40E92 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I propose keeping all use-cases (including multicast) in the same draft. =20 -Sanjay =20 ________________________________ From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of BOCCI Matthew Sent: Tuesday, March 31, 2009 11:47 AM To: ancp@ietf.org Subject: [ANCP] Splitting multicast from protocol doc =20 There was a proposal at the last IETF to take the multicast text from draft-ietf-ancp-protocol-05 and merge it with draft-lefaucheur-ancp-mc-extensions-01. We would thus have two protocol drafts:=20 draft-ietf-ancp-protocol : Containing the solutions for the Topology discovery, line configuration and OAM use cases=20 Multicast extensions draft: Containing the transactional multicast solution and all of the content of draft-lefaucheur=20 This would allow us to move forward with WG LC on the basic use case solutions, and also keep all of the multicast extensions in a single draft. Please can you indicate to the list whether you support this proposal.=20 Regards=20 Matthew=20 =20 ------_=_NextPart_001_01C9B262.03C40E92 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Splitting multicast from protocol doc

I propose keeping all use-cases (including multicast) in the same = draft.

 

-Sanjay

=

 

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of BOCCI = Matthew
Sent: Tuesday, March 31, = 2009 11:47 AM
To: ancp@ietf.org
Subject: [ANCP] Splitting multicast from protocol doc

 

There was a proposal at the last IETF to take the multicast text from draft-ietf-ancp-protocol-05 and merge it with draft-lefaucheur-ancp-mc-extensions-01.

We would thus have two protocol drafts:

draft-ietf-ancp-protocol : Containing the solutions for the Topology discovery, line = configuration and OAM use cases
Multicast extensions draft: Containing the transactional multicast solution and = all of the content of draft-lefaucheur

This would allow us to move forward with WG LC on the basic use case solutions, and also = keep all of the multicast extensions in a single draft.

Please can you indicate to the list whether you = support this proposal.

Regards

Matthew

 

------_=_NextPart_001_01C9B262.03C40E92-- From HaagT@telekom.de Tue Mar 31 23:28:16 2009 Return-Path: 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 3F8883A6ACF for ; Tue, 31 Mar 2009 23:28:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.759 X-Spam-Level: X-Spam-Status: No, score=-1.759 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 9StMF+1Xnrcu for ; Tue, 31 Mar 2009 23:28:15 -0700 (PDT) Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 23AD33A672F for ; Tue, 31 Mar 2009 23:28:14 -0700 (PDT) Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail71.telekom.de with ESMTP; 01 Apr 2009 08:29:13 +0200 Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Apr 2009 08:29:13 +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_01C9B293.2C1FB92E" Date: Wed, 1 Apr 2009 08:29:10 +0200 Message-ID: <5661758E3E93364685B91DD8272F2876010E8DEF@S4DE8PSAAQC.mitte.t-com.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: TC Information "unknown" State Thread-Index: AcmykynN/76iRUjbRlynF3ZIly2OZw== From: To: X-OriginalArrivalTime: 01 Apr 2009 06:29:13.0185 (UTC) FILETIME=[2C69FD10:01C9B293] Subject: [ANCP] TC Information "unknown" State X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2009 06:28:16 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9B293.2C1FB92E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, operating a DSL port in multi mode which means that ADSL2plus (ATM ) and VDSL2 (ETH) is enabled the following situation occur: For a DSL port which has never been synchronized with a CPE (regardless if ADSL2plus or VDSL2) there is the situation, which layer 2 information has to be reported to BNG via ANCP port status message. In that case new information in the protocol is necessary to inform the BNG about this "unknown" State which is neither represented by ATM nor ETH. I like to encourage ANCP working group to tackle this issue and define a new TC information [ATM, ETH; UNKNOWN] in the protocol draft to indicate the port status as described above. Best regards Thomas=20 ------_=_NextPart_001_01C9B293.2C1FB92E Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable TC Information "unknown" State

All,

operating a DSL = port in multi mode which means that ADSL2plus (ATM ) and VDSL2 (ETH) is enabled the = following situation occur:

For a DSL port which has = never been synchronized with a CPE (regardless if ADSL2plus or VDSL2) there is = the situation, which = layer 2 information has to be reported to BNG via ANCP port status = message. In that case new information in the protocol is necessary to inform the BNG about this "unknown" State which is neither = represented by ATM nor ETH.

I like to encourage = ANCP working group to tackle this issue and define a new TC information = [ATM, ETH; UNKNOWN] in the protocol draft to indicate the port = status as described above.

Best = regards

Thomas =

------_=_NextPart_001_01C9B293.2C1FB92E-- From HaagT@telekom.de Tue Mar 31 23:58:55 2009 Return-Path: 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 A90C93A6BF3 for ; Tue, 31 Mar 2009 23:58:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.248 X-Spam-Level: X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjJu5-3j0A5e for ; Tue, 31 Mar 2009 23:58:54 -0700 (PDT) Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id 981F73A6A7E for ; Tue, 31 Mar 2009 23:58:54 -0700 (PDT) Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail31.telekom.de with ESMTP; 01 Apr 2009 08:59:53 +0200 Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Apr 2009 08:59:53 +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_01C9B297.74DAA6D2" Date: Wed, 1 Apr 2009 08:59:52 +0200 Message-ID: <5661758E3E93364685B91DD8272F2876010E8E41@S4DE8PSAAQC.mitte.t-com.de> In-Reply-To: <0458D2EE0C36744BABB36BE37805C29A039300A4@FRVELSMBS11.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ANCP] draft-bitar-wadhwa-ancp-pon-01.txt to WG draft? Thread-Index: AcmyFoOHJTCTudvkSS+NhWzE018hTQAgIdmQ References: <0458D2EE0C36744BABB36BE37805C29A039300A4@FRVELSMBS11.ad2.ad.alcatel.com> From: To: X-OriginalArrivalTime: 01 Apr 2009 06:59:53.0048 (UTC) FILETIME=[750ECD80:01C9B297] Subject: Re: [ANCP] draft-bitar-wadhwa-ancp-pon-01.txt to WG draft? X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2009 06:58:55 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9B297.74DAA6D2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Full support. =20 Regards =20 Thomas =20 ________________________________ Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von = BOCCI Matthew Gesendet: Dienstag, 31. M=E4rz 2009 17:37 An: ancp@ietf.org Betreff: [ANCP] draft-bitar-wadhwa-ancp-pon-01.txt to WG draft? There was a proposal at the last IETF to accept = draft-bitar-wadhwa-ancp-pon-01.txt as an ANCP working group draft.=20 This is the start of a two week poll to test the consensus of the WG.=20 Please can you respond to the ANCP list, indicating if you support this = (or otherwise).=20 The poll will close on 14th April 2009.=20 Regards=20 Matthew=20 ------_=_NextPart_001_01C9B297.74DAA6D2 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable draft-bitar-wadhwa-ancp-pon-01.txt to WG = draft?
Full support.
 
Regards
 
Thomas
 

Von: ancp-bounces@ietf.org=20 [mailto:ancp-bounces@ietf.org] Im Auftrag von BOCCI=20 Matthew
Gesendet: Dienstag, 31. März 2009 = 17:37
An:=20 ancp@ietf.org
Betreff: [ANCP] = draft-bitar-wadhwa-ancp-pon-01.txt to WG=20 draft?

There was a proposal at the last IETF to = accept=20 draft-bitar-wadhwa-ancp-pon-01.txt as an ANCP working group = draft.

This is the start of a two week poll to = test the=20 consensus of the WG.

Please can you respond to the ANCP list, = indicating=20 if you support this (or otherwise).

The poll will close on 14th April = 2009.

Regards

Matthew

------_=_NextPart_001_01C9B297.74DAA6D2--