Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH ChannelTypeallocationpolicy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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 at ietf.org [mailto:pwe3-bounces at ietf.org] On 
> Behalf Of julien.meuric at orange-ftgroup.com
> Sent: 09 October 2008 17:36
> To: maarten.vissers at huawei.com
> Cc: l2vpn at ietf.org; mpls at ietf.org; ccamp at ietf.org; 
> pwe3 at ietf.org; mpls-tp at 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 at ietf.org [mailto:mpls-bounces at 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 at ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> 
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.