Re: [PWE3] Mandatory Control Word
Eric Gray <eric.gray@ericsson.com> Wed, 27 October 2010 06:53 UTC
Return-Path: <eric.gray@ericsson.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 87D163A68CE for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 23:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.122
X-Spam-Level:
X-Spam-Status: No, score=-2.122 tagged_above=-999 required=5 tests=[AWL=0.477, 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 dyIRSNCtJ6fk for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 23:53:57 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 50AEC3A6819 for <pwe3@ietf.org>; Tue, 26 Oct 2010 23:53:57 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o9R6tK1N028579 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 27 Oct 2010 01:55:20 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.213]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 27 Oct 2010 02:55:19 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Wed, 27 Oct 2010 02:55:16 -0400
Thread-Topic: [PWE3] Mandatory Control Word
Thread-Index: Act1MpjAXrQAFXgyRvCiFrt6jyxxdwAbxQJQ
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F10929F4068B@EUSAACMS0701.eamcs.ericsson.se>
References: <4CC70E97.7000100@cisco.com>
In-Reply-To: <4CC70E97.7000100@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 27 Oct 2010 06:53:58 -0000
Stewart, I agree with your suggested limitations to new PW types and suggestion to recommend its use for existing PW types. However, the observation about deployed systems - when taken together with what appears to be a growing impression that use of the control word with all PW types may be a good idea - seems to argue that we would (eventually) need a BCP that specifies use of the control word, and possibly we may even have to publish a "non-use of PW control word considered dangerous" RFC. I don't see a way to avoid this, assuming that is where we are headed, but it might be good to be clear on whether or not that _is_ where we are headed. It also causes me to wonder if there are implementations deployed in the field where use of the control word is not a configurable capability. Certainly, if deployed equipment is all capable of being configured to always use control words, then it is not unrealistic to suggest that configuring things that way would simplify future implementations. -- Eric -----Original Message----- From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Stewart Bryant Sent: Tuesday, October 26, 2010 1:24 PM To: pwe3 Subject: [PWE3] Mandatory Control Word 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] Mandatory Control Word Stewart Bryant
- Re: [PWE3] Mandatory Control Word Thomas Nadeau
- Re: [PWE3] Mandatory Control Word Shah, Himanshu
- Re: [PWE3] Mandatory Control Word Ignacio Goyret
- Re: [PWE3] Mandatory Control Word Eric Gray
- Re: [PWE3] Mandatory Control Word Stewart Bryant
- Re: [PWE3] Mandatory Control Word Delregno, Christopher N (Nick DelRegno)
- Re: [PWE3] Mandatory Control Word Thomas Nadeau
- Re: [PWE3] Mandatory Control Word Giles Heron
- Re: [PWE3] Mandatory Control Word Ben Niven-Jenkins
- Re: [PWE3] Mandatory Control Word Greg Mirsky