Re: [PWE3] Mandatory Control Word
Ignacio Goyret <i.goyret@alcatel-lucent.com> Tue, 26 October 2010 20:34 UTC
Return-Path: <i.goyret@alcatel-lucent.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 5EE513A679C for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 13:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.216
X-Spam-Level:
X-Spam-Status: No, score=-102.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2MNIYlJbgDE3 for <pwe3@core3.amsl.com>; Tue, 26 Oct 2010 13:34:31 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 4B38B3A6405 for <pwe3@ietf.org>; Tue, 26 Oct 2010 13:34:30 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id o9QKaFUk014869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 26 Oct 2010 15:36:15 -0500 (CDT)
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [135.140.53.169]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o9QKaCuH015252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Oct 2010 15:36:14 -0500
Received: from igoyret-c1.alcatel-lucent.com (dhcp-135-140-27-184 [135.140.27.184]) by cliff.eng.ascend.com (8.13.1/8.13.1) with ESMTP id o9QKaA5Y010383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Oct 2010 13:36:11 -0700
Message-Id: <201010262036.o9QKaA5Y010383@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 26 Oct 2010 13:36:04 -0700
To: pwe3 <pwe3@ietf.org>
From: Ignacio Goyret <i.goyret@alcatel-lucent.com>
In-Reply-To: <B281F185E514BB4CB7EF182F9CA158BE018510E5@mdmxm05.ciena.com >
References: <4CC70E97.7000100@cisco.com> <54983C49-782C-4A96-AA2B-BE8A434B1195@lucidvision.com> <B281F185E514BB4CB7EF182F9CA158BE018510E5@mdmxm05.ciena.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: stbryant@cisco.com
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 20:34:32 -0000
+1 At 02:35 PM 10/26/2010 -0400, Shah, Himanshu wrote: >I do kind of agree with Stuart's assessment, AD or not... :-) > >IMHO, >/himanshu > >-----Original Message----- >From: Thomas Nadeau > > 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] 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