Re: [PWE3] Mandatory Control Word

Thomas Nadeau <tnadeau@lucidvision.com> Tue, 26 October 2010 17:39 UTC

Return-Path: <tnadeau@lucidvision.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 209353A69D2 for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 10:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level:
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154, 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 LPZS+DX8jrCK for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 10:39:56 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 2D1B83A69C1 for <pwe3@ietf.org>; Tue, 26 Oct 2010 10:39:56 -0700 (PDT)
Received: from [192.168.1.133] (unknown [72.71.250.36]) by lucidvision.com (Postfix) with ESMTP id 76C7217A1FFD; Tue, 26 Oct 2010 13:41:43 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <4CC70E97.7000100@cisco.com>
Date: Tue, 26 Oct 2010 13:41:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <54983C49-782C-4A96-AA2B-BE8A434B1195@lucidvision.com>
References: <4CC70E97.7000100@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1081)
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 17:39:57 -0000

	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
>