Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type allocationpolicy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type allocationpolicy
- To: 'Ben Niven-Jenkins' <benjamin.niven-jenkins at bt.com>, 'Shahram Davari' <davari at tpack.com>, 'Shane Amante' <shane at castlepoint.net>
- Subject: Re: [mpls] [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type allocationpolicy
- From: Maarten Vissers <maarten.vissers at huawei.com>
- Date: Mon, 06 Oct 2008 09:39:59 +0200
- Cc: l2vpn at ietf.org, mpls at ietf.org, 'BOCCI Matthew' <Matthew.Bocci at alcatel-lucent.com>, ccamp at ietf.org, mpls-tp at ietf.org, pwe3 at ietf.org, 'BUSI ITALO' <Italo.Busi at alcatel-lucent.it>
- Delivered-to: ietfarch-mpls-web-archive at core3.amsl.com
- Delivered-to: mpls at core3.amsl.com
- In-reply-to: <C50AC39D.C5BD%benjamin.niven-jenkins at bt.com>
- List-archive: <https://www.ietf.org/mailman/private/mpls>
- List-help: <mailto:mpls-request@ietf.org?subject=help>
- List-id: Multi-Protocol Label Switching WG <mpls.ietf.org>
- List-post: <mailto:mpls@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
- Sender: mpls-bounces at ietf.org
- Thread-index: AckkqLTHdNDdblepSIu2W52R3r7OPAAC8OmkALQvDPA=
Ben,
Also in case of a multi-vendor network there should be no issue. The new
functionality is present only in the UNI-N ports (i.e. where the service is
mapped into the PW). When you deploy such new functionality in UNI-N ports
contained in Network Termination devices you can deploy those NT devices
from one vendor. The main network now only has to carry the MS-PW between
the NT devices at the edge of the network. The main network is as such
agnostic to the new functionality.
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
-----Original Message-----
From: pwe3-bounces at ietf.org [mailto:pwe3-bounces at ietf.org] On Behalf Of Ben
Niven-Jenkins
Sent: 02 October 2008 19:30
To: Shahram Davari; Shane Amante
Cc: l2vpn at ietf.org; mpls at ietf.org; BOCCI Matthew; ccamp at ietf.org;
mpls-tp at ietf.org; pwe3 at ietf.org; BUSI ITALO
Subject: Re: [PWE3] [mpls-tp] FW: Changes to PW ACH Channel Type
allocationpolicy
On 02/10/2008 17:05, "Shahram Davari" <davari at tpack.com> wrote:
> From: Shane Amante [mailto:shane at castlepoint.net] Shahram Davari
> wrote:
>> Hi,
>>
>> I also prefer the method that Wishwas proposed. This has many advantages:
>>
>> 1) Allows vendors to not expose their proprietary techniques to their
>> competitors.
>
> From the POV of an operator, this is actually a substantial disadvantage.
>
> [Shahram] OTOH it encourages more innovation and differentiation by
vendors.
Which is fine until you run a multi-vendor network.
Ben
_______________________________________________
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.