Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH ChannelTypeallocationpolicy

"BOCCI Matthew" <Matthew.Bocci@alcatel-lucent.com> Mon, 20 October 2008 15:43 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 AF52D3A6AB4; Mon, 20 Oct 2008 08:43:39 -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 DD98C3A67D7; Mon, 20 Oct 2008 08:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level:
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[AWL=0.211, 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 zrXD9esMSIep; Mon, 20 Oct 2008 08:43:37 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id DCC533A67E4; Mon, 20 Oct 2008 08:43:35 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com [155.132.6.74]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9KFikQ1004076; Mon, 20 Oct 2008 17:44:46 +0200
Received: from FRVELSMBS11.ad2.ad.alcatel.com ([155.132.6.33]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 20 Oct 2008 17:44:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 17:44:42 +0200
Message-ID: <0458D2EE0C36744BABB36BE37805C29A02B9F5B6@FRVELSMBS11.ad2.ad.alcatel.com>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02605EA9DB9@ftrdmel2>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] [mpls] [mpls-tp] FW: Changes to PW ACH ChannelTypeallocationpolicy
Thread-Index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8OmkALQvDPAAqc+IYAInM/ww
References: <C50AC39D.C5BD%benjamin.niven-jenkins@bt.com><001601c92786$bfe979a0$6d02a8c0@china.huawei.com> <7DBAFEC6A76F3E42817DF1EBE64CB02605EA9DB9@ftrdmel2>
From: BOCCI Matthew <Matthew.Bocci@alcatel-lucent.com>
To: pwe3@ietf.org, mpls@ietf.org, ccamp@ietf.org, mpls-tp@ietf.org
X-OriginalArrivalTime: 20 Oct 2008 15:44:46.0431 (UTC) FILETIME=[C73E6EF0:01C932CA]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH ChannelTypeallocationpolicy
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: pwe3@ietf.org
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

It is not clear that there is rough consensus for changing the
allocation policy for the ACH channel type to be either expert review or
first come first served or any of the other proposed options.
Nevertheless, there are a significant number of participants who would
like to be able to develop and test proprietary ACH protocols prior to
any proposal for a standardised function being made.

We would therefore like to propose the following way forward. This is to
allocate a small range (say 16) of Experimental code points. These would
follow the rules of RFC3692, should be disabled by default, and mapping
of a code point to any specific function must be configurable. The
remainder of the channel type registry would remain as IETF consensus.

Please reply with any comments to the PWE3 list only.

Regards

Matthew

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of julien.meuric@orange-ftgroup.com
> Sent: 09 October 2008 17:36
> To: maarten.vissers@huawei.com
> Cc: l2vpn@ietf.org; mpls@ietf.org; ccamp@ietf.org; 
> pwe3@ietf.org; mpls-tp@ietf.org
> Subject: Re: [PWE3] [mpls] [mpls-tp] FW: Changes to PW ACH 
> ChannelTypeallocationpolicy
> 
> Hi Maarten.
> 
> That might be true sometimes, but the IETF allocation policy 
> is not the limiting factor in that kind of processes... ;-)
> 
> Regards,
> 
> Julien
> 
> 
> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On 
> Behalf Of Maarten Vissers
> 
> [...]
> 
> The use of NT devices to support new (non standard) services 
> not only allows differentiation by vendors, but also 
> differentiation by operators.
> Operators
> wanting to differentiate their service offerings can ask a NT 
> device vendor to add their operator specific service to the NT device.
> 
> Regards,
> Maarten
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls