Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocationpolicy
"Vishwas Manral" <vishwas.ietf@gmail.com> Thu, 02 October 2008 07:21 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 417FD28C1B6; Thu, 2 Oct 2008 00:21:14 -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 57FC028C152 for <mpls@core3.amsl.com>; Thu, 2 Oct 2008 00:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level:
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 Pu0fFsjcvdwF for <mpls@core3.amsl.com>; Thu, 2 Oct 2008 00:21:12 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by core3.amsl.com (Postfix) with ESMTP id B6B403A63EC for <mpls@ietf.org>; Thu, 2 Oct 2008 00:21:11 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so640244fga.41 for <mpls@ietf.org>; Thu, 02 Oct 2008 00:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=+WJ0gBmd03TT1U+IGlTzkNGgUl1n35g81V/kPFXHbAc=; b=QNjruWVpkN6Nuz4So+2dXqDs8NwOsE/uPu+vO3aCq6L012GHp1Q2U0Dpy9AxFYLwOw ulI2Z6LoU7bmU8mF2jUBssBLtu7kHjJ2FSnt2PDc0bm2u65l/Vc8s7f2AhULcTC/m/t8 YSfSbcVyCpe7RhlCC0lK1hCBRd2T8tyvSghBk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=M0jH/j6mMZPZGqIP1VOp/0Z1zMkn2IcIdE1po2z0WLe/x4rKmR/6APPUQ9NzWDt36c K39ruwMeljK02jne64VMa2bCb6CKbjP1aeQhVCocXcj8BeRR64bvuR7koawFC8k+9+9y stMIbeQFDbJGAjxSjyUuPl+WNrlvVG7FFgwXM=
Received: by 10.180.249.4 with SMTP id w4mr5222096bkh.79.1222932087655; Thu, 02 Oct 2008 00:21:27 -0700 (PDT)
Received: by 10.180.226.2 with HTTP; Thu, 2 Oct 2008 00:21:27 -0700 (PDT)
Message-ID: <77ead0ec0810020021l47d220f7n3a42651d1a17a6b4@mail.gmail.com>
Date: Thu, 02 Oct 2008 12:51:27 +0530
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: BUSI ITALO <Italo.Busi@alcatel-lucent.it>
In-Reply-To: <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <0458D2EE0C36744BABB36BE37805C29A029C6251@FRVELSMBS11.ad2.ad.alcatel.com> <ba6305ea8b6f7b41bae8dcbb49c37c7c@mail.cph.tpack.net> <77ead0ec0810010847r10efb0f0ncb4e24f5d9b4c492@mail.gmail.com> <6FD21B53861BF44AA90A288402036AB40193F737@FRVELSMBS21.ad2.ad.alcatel.com>
Cc: l2vpn@ietf.org, BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>, mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org, pwe3@ietf.org, Shahram Davari <davari@tpack.com>
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
Hi Italo, I agree and that was my exact aim. The other added advantage is that there are no interoperability issues and no bottlenecks of assignments for a particular type. Thanks, Vishwas On 10/2/08, 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. > > 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