Re: [PWE3] Mandatory Control Word

"Shah, Himanshu" <hshah@ciena.com> Tue, 26 October 2010 18:36 UTC

Return-Path: <hshah@ciena.com>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1116D3A6943 for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 11:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[AWL=0.610, 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 zk31Z0n12I-S for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 11:36:00 -0700 (PDT)
Received: from ripley.ciena.com (ripley.ciena.com [63.118.34.24]) by core3.amsl.com (Postfix) with ESMTP id 819823A682A for <pwe3@ietf.org>; Tue, 26 Oct 2010 11:34:59 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Oct 2010 14:35:49 -0400
Message-ID: <B281F185E514BB4CB7EF182F9CA158BE018510E5@mdmxm05.ciena.com>
In-Reply-To: <54983C49-782C-4A96-AA2B-BE8A434B1195@lucidvision.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] Mandatory Control Word
Thread-Index: Act1NRHCl032huMbTtWTp4Nch1ETPQAByxuA
References: <4CC70E97.7000100@cisco.com> <54983C49-782C-4A96-AA2B-BE8A434B1195@lucidvision.com>
From: "Shah, Himanshu" <hshah@ciena.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>, stbryant@cisco.com
Cc: pwe3 <pwe3@ietf.org>
Subject: Re: [PWE3] Mandatory Control Word
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2010 18:36:05 -0000

I do kind of agree with Stuart's assessment, AD or not... :-)

IMHO,
/himanshu

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
Thomas Nadeau
Sent: Tuesday, October 26, 2010 1:42 PM
To: stbryant@cisco.com
Cc: pwe3
Subject: Re: [PWE3] Mandatory Control Word


	Is this your personal opinion speaking as a vendor with lots of
said equipment, or as an AD?

	--Tom



> From
> 
> draft-delregno-pwe3-mandatory-control-word/
> 
> =======
> 2.  Mandatory Control Word
> 
>   The Control Word SHALL be mandatory for all PWE3 encapsulations.
The
>   use of the sequence number remains OPTIONAL.
> 
>   As a result of the Control Word being Mandatory, all implementations
>   of the PWE3 encapsulations SHALL follow Section 6.1 of [RFC4447]
>   wherein the "PWs MUST have c=1".  This requirement SHALL remain
until
>   such time, if ever, RFC4447 is superceded and the support for
Control
>   Word negotiation is removed as a result of this mandate.
> 
> ======
> 
> Given the reality of network deployments I do not see how we can
> talk about removing the requirement to negotiate the CW in any
> realistic time frame.
> 
> It's fine to require the CW for all new PW types, and it's
> probably OK to RECOMMEND operation with the CW, but it's
> unrealistic to remove the option given the extent of the deployed
> systems.
> 
> - Stewart
> 
> 
> 
> _______________________________________________
> 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