[mpls] Question for clarification (was RE: Poll on renaming of EXP field)
"Eric Gray" <eric.gray@ericsson.com> Tue, 19 August 2008 14:42 UTC
Return-Path: <mpls-bounces@ietf.org>
X-Original-To: mpls-archive@megatron.ietf.org
Delivered-To: ietfarch-mpls-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD51F3A6938; Tue, 19 Aug 2008 07:42:26 -0700 (PDT)
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA7813A6A4F for <mpls@core3.amsl.com>; Tue, 19 Aug 2008 07:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.654
X-Spam-Level:
X-Spam-Status: No, score=-6.654 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 iHJjLQQof7Od for <mpls@core3.amsl.com>; Tue, 19 Aug 2008 07:42:23 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 9484B3A69CC for <mpls@ietf.org>; Tue, 19 Aug 2008 07:42:23 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m7JEgSnL001856; Tue, 19 Aug 2008 09:42:29 -0500
Received: from eusrcmw721.eamcs.ericsson.se ([138.85.77.21]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Aug 2008 09:42:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Aug 2008 09:42:26 -0500
Message-ID: <941D5DCD8C42014FAF70FB7424686DCF039AFD07@eusrcmw721.eamcs.ericsson.se>
In-Reply-To: <C4CF528C.612B%swallow@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Question for clarification (was RE: [mpls] Poll on renaming of EXP field)
Thread-Index: AckBcE00i7UqvG1jEd2DSgAewhIyZgAlsH4Q
References: <C4CF528C.612B%swallow@cisco.com>
From: Eric Gray <eric.gray@ericsson.com>
To: George Swallow <swallow@cisco.com>, Loa Andersson <loa@pi.nu>
X-OriginalArrivalTime: 19 Aug 2008 14:42:28.0563 (UTC) FILETIME=[CDB08A30:01C90209]
Cc: mpls@ietf.org
Subject: [mpls] Question for clarification (was RE: Poll on renaming of EXP field)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
George/Loa, I am concerned that we may be signing ourselves up for a slew of RFC revisions/replacements in making this name change. Just to make things clearer - is it the intention that we're creating a single RFC that explains the change and will then be listed as "updating" all RFCs that currently use the term "EXP", or are we in fact signing up to replace a number of RFCs? It's one thing to decide that the field name "CoS" is not worse than the name "EXP"; it is quite another thing to sign up for churning a number of RFCs to replace a term - because it is "nor worse than" the existing term. Another thing to consider is that - even if we plan only to list this new RFC as "updating" all of the RFCs that currently refer to the field name "EXP" - we may be setting a record for the number of RFCs "updated" by a single new RFC. Given the number of people who still refer to RFC 2547 VPNs, it is not all that clear what difference an RFC that proposes to change a field name from "EXP bits" to "CoS bits" will really have. However, if we don't even list this RFC as "updating" these other RFCs, then it is very likely that the new RFC will have even less impact on usage (possibly having no effect what-so-ever over the long run) - since a person reading any of these existing RFCs will have no particular reason to know about this new one. In my opinion, a better use of everybody's time would be to write an RFC that simply explains the way the IETF's use of the term "Experimental" actually works (i.e. - you do not get to pick experimental values, or define symantic meanings for a set of values, for use in the Internet scope without obtaining a specific value (or values) from a number space manager, such as IANA). Such a thing would be quite a reasonable thing to do as a simple process BCP. -- Eric Gray Principal Engineer Ericsson > -----Original Message----- > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On > Behalf Of George Swallow > Sent: Monday, August 18, 2008 4:24 PM > To: mpls@ietf.org > Subject: [mpls] Poll on renaming of EXP field > > During the last call on "EXP field" renamed to "CoS Field" > draft-ietf-mpls-cosfield-def-04.txt, there were comments on > alternatives to the name COS. > > This message initiates a two week poll on whether the name COS > is good enough, or if some other name is needed. The poll closes > 23:59 Sept 1 GMT. > > Please answer with a simple yes or no. You may send any > additional comment > in a separate message (with a different subject line). > > ...George > > _______________________________________________ > mpls mailing list > mpls@ietf.org > https://www.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls
- [mpls] Poll on renaming of EXP field George Swallow
- Re: [mpls] Poll on renaming of EXP field Santiago Alvarez (saalvare)
- [mpls] discussion (was Re: Poll on renaming of EX… Mikael Abrahamsson
- Re: [mpls] Poll on renaming of EXP field Huub van Helvoort
- Re: [mpls] Poll on renaming of EXP field Rajiv Asati (rajiva)
- Re: [mpls] discussion (was Re: Poll on renaming o… George Swallow
- Re: [mpls] Poll on renaming of EXP field Shane Amante
- Re: [mpls] Poll on renaming of EXP field Cao Wei
- Re: [mpls] Poll on renaming of EXP field HENDERICKX Wim
- Re: [mpls] Poll on renaming of EXP field Harshith Shetty
- Re: [mpls] Poll on renaming of EXP field jordan.britnell
- Re: [mpls] Poll on renaming of EXP field Jiang Yuan-long
- Re: [mpls] Poll on renaming of EXP field Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls] Poll on renaming of EXP field Matthew Meyer
- Re: [mpls] Poll on renaming of EXP field Tomohiro Otani
- Re: [mpls] Poll on renaming of EXP field Santanu.Ganguly
- Re: [mpls] Poll on renaming of EXP field Phil Bedard
- Re: [mpls] Poll on renaming of EXP field BOCCI Matthew
- Re: [mpls] discussion (was Re: Poll on renaming o… Shahram Davari
- [mpls] Question for clarification (was RE: Poll o… Eric Gray
- Re: [mpls] Poll on renaming of EXP field Eric Gray
- Re: [mpls] Poll on renaming of EXP field phani bandaru
- Re: [mpls] Question for clarification (was RE: Po… Diego Caviglia
- Re: [mpls] Poll on renaming of EXP field buyukkoc
- Re: [mpls] Poll on renaming of EXP field Francois Le Faucheur IMAP
- Re: [mpls] Question for clarification (was RE: Po… Shahram Davari
- Re: [mpls] Poll on renaming of EXP field Shahram Davari
- [mpls] "Traffic Management" (was Re: Poll on rena… Francois Le Faucheur IMAP
- Re: [mpls] Poll on renaming of EXP field Peter Tomsu
- Re: [mpls] "Traffic Management" (was Re: Poll on … Eric Gray
- Re: [mpls] Poll on renaming of EXP field John Kenney
- Re: [mpls] "Traffic Management" (was Re: Poll on … John Kenney
- [mpls] FW: Poll on renaming of EXP field Howard Green
- Re: [mpls] "Traffic Management" (was Re: Poll on … Shah, Himanshu
- Re: [mpls] "Traffic Management" (was Re: Poll on … Huub van Helvoort
- Re: [mpls] "Traffic Management" (was Re: Poll on … George Swallow
- Re: [mpls] "Traffic Management" (was Re: Poll on … David Allan
- Re: [mpls] "Traffic Management" (was Re: Poll on … Peng He
- Re: [mpls] "Traffic Management" (was Re: Poll on … Eric Gray
- Re: [mpls] "Traffic Management" (was Re: Poll on … Eric Gray
- Re: [mpls] Poll on renaming of EXP field Mach Chen
- Re: [mpls] Poll on renaming of EXP field Vijayanand C
- Re: [mpls] Poll on renaming of EXP field Tom Petch
- Re: [mpls] "Traffic Management" (was Re: Poll on … Francois Le Faucheur IMAP
- Re: [mpls] "Traffic Management" (was Re: Poll on … Francois Le Faucheur IMAP
- Re: [mpls] Poll on renaming of EXP field Alexander Vainshtein
- Re: [mpls] "Traffic Management" (was Re: Poll on … Alexander Vainshtein
- Re: [mpls] Poll on renaming of EXP field Daniele Ceccarelli
- [mpls] Discuss of EXP field Adrian Farrel
- Re: [mpls] Discuss of EXP field Alexander Vainshtein
- Re: [mpls] "Traffic Management" (was Re: Poll on … Eric Gray
- Re: [mpls] Poll on renaming of EXP field Moshe Ashkenazi
- Re: [mpls] Poll on renaming of EXP field Vullo, Anthony D (Tony)
- Re: [mpls] FW: Poll on renaming of EXP field Vadali, Somayajulu (Somu)
- [mpls] Poll on renaming of EXP field mushaoxing 63008
- Re: [mpls] Poll on renaming of EXP field saquib khan
- Re: [mpls] Poll on renaming of EXP field Annamaria Fulignoli
- Re: [mpls] Poll on renaming of EXP field Zafar Ali (zali)
- Re: [mpls] Poll on renaming of EXP field Andrew Sergeev
- Re: [mpls] Poll on renaming of EXP field Michael Lyngbøl
- Re: [mpls] Poll on renaming of EXP field Ben Niven-Jenkins
- Re: [mpls] Poll on renaming of EXP field Andrew G. Malis
- Re: [mpls] Poll on renaming of EXP field Don Fedyk