Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy
"BUSI ITALO" <Italo.Busi@alcatel-lucent.it> Fri, 03 October 2008 07:57 UTC
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 295EB28C197; Fri, 3 Oct 2008 00:57:19 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0339F3A68EB; Fri, 3 Oct 2008 00:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5PbpdW2vdTc; Fri, 3 Oct 2008 00:57:17 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 7E9103A686A; Fri, 3 Oct 2008 00:57:16 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com [155.132.6.75]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m937vcAh023013; Fri, 3 Oct 2008 09:57:38 +0200
Received: from FRVELSMBS21.ad2.ad.alcatel.com ([155.132.6.55]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 09:57:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 03 Oct 2008 09:57:47 +0200
Message-ID: <6FD21B53861BF44AA90A288402036AB40193FA1C@FRVELSMBS21.ad2.ad.alcatel.com>
In-Reply-To: <C50A3312.E217%tom.nadeau@bt.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy
Thread-Index: Ackj3Q1bqBGtuyWETZaWG4drFEnw4AAf+XvQAArRnjgAKVxUoA==
References: <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com> <C50A3312.E217%tom.nadeau@bt.com>
From: BUSI ITALO <Italo.Busi@alcatel-lucent.it>
To: "Thomas D. Nadeau" <tom.nadeau@bt.com>, Vishwas Manral <vishwas.ietf@gmail.com>, Shahram Davari <davari@tpack.com>
X-OriginalArrivalTime: 03 Oct 2008 07:57:38.0831 (UTC) FILETIME=[B47851F0:01C9252D]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org
Subject: Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
See my reply to the same question made by Stewart Italo > -----Original Message----- > From: Thomas D. Nadeau [mailto:tom.nadeau@bt.com] > Sent: Thursday, October 02, 2008 2:13 PM > To: BUSI ITALO; Vishwas Manral; Shahram Davari > Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; > ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org > Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel > Type allocationpolicy > > > > > On 10/2/08 3:11 AM, "BUSI ITALO" <Italo.Busi@alcatel-lucent.it> wrote: > > > Vishwas, > > > > I think this is a good idea > > > > Both this proposal and option 2 (fist-come-first-served) meet the > > requirements to make the ACH mechanism extensible. > > How does the existing mechanism not meet the requirement > to make an ACH > mechanism extensible? > > --Tom > > > > The advantage of this approach is that we do not have to > worry about how > > many codepoints we need to allocate for proprietary > extensions: we just > > need one codepoint. > > > > Italo > > > >> -----Original Message----- > >> From: mpls-tp-bounces@ietf.org > >> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Vishwas Manral > >> Sent: Wednesday, October 01, 2008 5:47 PM > >> To: Shahram Davari > >> Cc: l2vpn@ietf.org; BOCCI Matthew; mpls@ietf.org; > >> ccamp@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org > >> Subject: Re: [mpls-tp] [PWE3] FW: Changes to PW ACH Channel > >> Type allocationpolicy > >> > >> Hi Matthew, > >> > >> I would like to propose another option if it is for vendor > proprietery > >> "Channel Type" values in the ACH header. With the number > of values of > >> the channel type being limited and the number of vendors actually a > >> lot, I would think something in the lines of what the draft below > >> talks about may make sense: > >> > >> http://tools.ietf.org/draft-ietf-isis-proprietary-tlv-00 > >> > >> The idea is give a channel type value, for vendor specific > >> implemntations and further define the structure of the next header > >> value for such a "channel type" to actually have a Vendor > OUI value. > >> > >> This will allow for unlimited innovation without affecting > >> interoperability, unlike the other options you have mentioned. > >> > >> Thanks, > >> Vishwas > >> > >> > >> On 10/1/08, Shahram Davari <davari@tpack.com> wrote: > >>> Hi Mathew, > >>> > >>> I support option 2, since a terminating node that doesn't > >> understand the > >>> VCCV channel type can always drop it. This would allow more > >> innovation and > >>> faster time to market. > >>> > >>> Best regards, > >>> Shahram > >>> > >>> > >>> -----Original Message----- > >>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] > >> On Behalf Of > >>> BOCCI Matthew > >>> Sent: September-30-08 12:23 PM > >>> To: pwe3@ietf.org; mpls-tp@ietf.org; mpls@ietf.org; > ccamp@ietf.org; > >>> l2vpn@ietf.org > >>> Subject: [PWE3] FW: Changes to PW ACH Channel Type > allocation policy > >>> > >>> The PWE3 chairs would like feedback on proposed changes to the > >>> allocation policy for the PW ACH codepoint registry. > Please see the > >>> email below, and provide any feedback copying the PWE3 list. > >>> > >>> Best regards > >>> > >>> Matthew > >>> > >>> -----Original Message----- > >>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] > >> On Behalf Of > >>> BOCCI Matthew > >>> Sent: 25 September 2008 16:36 > >>> To: pwe3@ietf.org > >>> Subject: [PWE3] Changes to PW ACH Channel Type allocation policy > >>> > >>> > >>> > >>> The current IANA allocation policy for the PW associated > >> channel type > >>> registry is by IETF consensus. This policy was chosen in > >> RFC 4385 based > >>> on WG consensus that since the associated channel exists > in the data > >>> path, and VCCV packets are typically processed by the > >> control processor > >>> on many PEs, it was prudent for the IETF to maintain strict > >> control over > >>> what types of channels were allocated and to ensure that > >> they complied > >>> to the PWE3 architecture. > >>> > >>> However, a need has been identified to provide a more > >> flexible approach > >>> to allocating code points for VCCV channel types. This has > >> partly arisen > >>> from the MPLS-TP work, where MPLS would be deployed in a transport > >>> network and where a much wider range of applications for the PW > >>> associated channel is envisioned, and partialy from a > >> desire to extend > >>> the OAM capabilities for regular MPLS. We can support MPLS-TP and > >>> general MPLS apps with the current policy which requires standards > >>> action. > >>> > >>> However we are receiving requests to allow proprietary OAM > >> and signaling > >>> protocols to be used in transport applications, and need to > >> decide on > >>> the best way forward. We considered providing extension mechanisms > >>> within the standards track protocols, but believe that > the standards > >>> track protocols would be much cleaner if the proprietary > >> protocols ran > >>> on their own ACH code points. > >>> > >>> Note that we are talking about vendor protocols here. Other > >> SDOs would > >>> be required to publish an RFC and would only be allocated > >> an ACH through > >>> Standards Action. > >>> > >>> There are two ways to address the requests for proprietary > >> protocol ACH > >>> code points: > >>> > >>> 1) Allow a range of the associated channel type registry to > >> be allocated > >>> through expert review. Guidelines would be provided for the expert > >>> reviewer to guide them in assessing the request, which > >> would have to be > >>> made in the form of an internet draft, while making sure that the > >>> request is dealt with in a timely and fair manner. This > policy would > >>> include hurdles with regard to security, congestion etc > >> that would be > >>> derived from those specified in the VCCV design. > >>> > >>> 2) Allow a range of the associated channel type registry to > >> be allocated > >>> on a first-come-first-served basis. This does not provide > >> the level of > >>> control that expert review provides, but this is balanced > >> to some degree > >>> by the fact that the VCCV channel type is indicated in the > >> data path, > >>> and so a PE can choose to discard or rate limit VCCV packets on an > >>> unrecognised associated channel. > >>> > >>> Any change to the ACH allocation policy would be outlined > >> in the GE-ACH > >>> draft, which would update RFC 4385. > >>> > >>> We would appreciate feedback on the list as to which > approach the WG > >>> prefers. > >>> > >>> Regards, > >>> > >>> Stewart and Matthew > >>> > >>> _______________________________________________ > >>> pwe3 mailing list > >>> pwe3@ietf.org > >>> https://www.ietf.org/mailman/listinfo/pwe3 > >>> _______________________________________________ > >>> pwe3 mailing list > >>> pwe3@ietf.org > >>> https://www.ietf.org/mailman/listinfo/pwe3 > >>> > >>> > >>> > >>> _______________________________________________ > >>> pwe3 mailing list > >>> pwe3@ietf.org > >>> https://www.ietf.org/mailman/listinfo/pwe3 > >>> > >> _______________________________________________ > >> mpls-tp mailing list > >> mpls-tp@ietf.org > >> https://www.ietf.org/mailman/listinfo/mpls-tp > >> > > _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls
- [mpls] FW: [PWE3] Changes to PW ACH Channel Type … BOCCI Matthew
- Re: [mpls] [mpls-tp] FW: [PWE3] Changes to PW ACH… Shah, Himanshu
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… Vishwas Manral
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Stewart Bryant
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Andrew G. Malis
- Re: [mpls] [PWE3] Changes to PW ACH Channel Type … Shane Amante
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… BUSI ITALO
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… BUSI ITALO
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… Stewart Bryant
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Vishwas Manral
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Huub van Helvoort
- Re: [mpls] FW: [PWE3] Changes to PW ACH Channel T… Loa Andersson
- Re: [mpls] [PWE3] Changes to PW ACH Channel Type … BRUNGARD, DEBORAH A, ATTLABS
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Shane Amante
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Lou Berger
- Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Cha… julien.meuric
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Loa Andersson
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Vishwas Manral
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Shane Amante
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… BOCCI Matthew
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Shane Amante
- Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Cha… BUSI ITALO
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… BUSI ITALO
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… BUSI ITALO
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Shahram Davari
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… Stewart Bryant
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… BUSI ITALO
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… BUSI ITALO
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls] FW: [PWE3] Changes to PW ACH Channel T… Sam Aldrin
- Re: [mpls] FW: [PWE3] Changes to PW ACH Channel T… Tom Petch
- Re: [mpls] [mpls-tp] FW: [PWE3] Changes to PW ACH… Thomas D. Nadeau
- Re: [mpls] [PWE3] FW: Changes to PW ACH Channel T… Shahram Davari
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Thomas D. Nadeau
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Thomas D. Nadeau
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Shahram Davari
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Thomas D. Nadeau
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Shahram Davari
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Ben Niven-Jenkins
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Ben Niven-Jenkins
- Re: [mpls] [Bulk] Re: [PWE3] [mpls-tp] FW: Change… Shahram Davari
- Re: [mpls] [Bulk] Re: [PWE3] [mpls-tp] FW: Change… Thomas D. Nadeau
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Luca Martini
- Re: [mpls] [Bulk] Re: [PWE3] [mpls-tp] FW: Change… Shahram Davari
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… BUSI ITALO
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… BUSI ITALO
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Shahram Davari
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Eric Gray
- Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Cha… BRUNGARD, DEBORAH A, ATTLABS
- Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Cha… Thomas D. Nadeau
- Re: [mpls] [PWE3] [mpls-tp] Changes to PW ACH Cha… Shahram Davari
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Luca Martini
- Re: [mpls] [mpls-tp] [PWE3] Changes to PW ACH Cha… Shane Amante
- Re: [mpls] Changes to PW ACH Channel Type allocat… Loa Andersson
- Re: [mpls] [mpls-tp] FW: [PWE3] Changes to PW ACH… Annamaria Fulignoli
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Annamaria Fulignoli
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Maarten Vissers
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Maarten Vissers
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… Alexander Vainshtein
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… julien.meuric
- Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH… BOCCI Matthew
- Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH… Annamaria Fulignoli