Re: [re-ECN] Acronym for BoF / w-g? DCP
<toby.moncaster@bt.com> Tue, 29 September 2009 09:00 UTC
Return-Path: <toby.moncaster@bt.com>
X-Original-To: re-ecn@core3.amsl.com
Delivered-To: re-ecn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id DA4913A6844 for <re-ecn@core3.amsl.com>;
Tue, 29 Sep 2009 02:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.963
X-Spam-Level:
X-Spam-Status: No, score=-2.963 tagged_above=-999 required=5 tests=[AWL=0.036,
BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1]
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 XIOvShw3ita3 for
<re-ecn@core3.amsl.com>; Tue, 29 Sep 2009 02:00:41 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by
core3.amsl.com (Postfix) with ESMTP id 1354B3A677E for <re-ecn@ietf.org>;
Tue, 29 Sep 2009 02:00:40 -0700 (PDT)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.61]) by
smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 29 Sep 2009 10:02:00 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 29 Sep 2009 10:01:58 +0100
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70D418008@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70D417FF3@E03MVZ1-UKDY.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Acronym for BoF / w-g? DCP
Thread-Index: AcpA3/XVwzfDVktaT/eLPkVmEWfvrgAAfXyQAABS7DA=
References: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk><4AC1C235.90704@informatik.uni-wuerzburg.de><4AC1C6DB.7040704@informatik.uni-wuerzburg.de>
<AEDCAF87EEC94F49BA92EBDD49854CC70D417FF3@E03MVZ1-UKDY.domain1.systemhost.net>
From: <toby.moncaster@bt.com>
To: <toby.moncaster@bt.com>, <menth@informatik.uni-wuerzburg.de>,
<rbriscoe@jungle.bt.co.uk>
X-OriginalArrivalTime: 29 Sep 2009 09:02:00.0672 (UTC)
FILETIME=[816E3E00:01CA40E3]
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Acronym for BoF / w-g? DCP
X-BeenThere: re-ecn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: re-inserted explicit congestion notification <re-ecn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>,
<mailto:re-ecn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/re-ecn>
List-Post: <mailto:re-ecn@ietf.org>
List-Help: <mailto:re-ecn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>,
<mailto:re-ecn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Sep 2009 09:00:42 -0000
Perhaps an alternative name for re-ECN itself could be: INSPECT - Insertion of predicted congestion Toby > -----Original Message----- > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On > Behalf Of toby.moncaster@bt.com > Sent: 29 September 2009 09:58 > To: menth@informatik.uni-wuerzburg.de; Briscoe,RJ,Bob,XVR9 BRISCORJ R > Cc: re-ecn@ietf.org > Subject: Re: [re-ECN] Acronym for BoF / w-g? DCP > > I am not convinced that prediction is quite right. To me it implies a > particular approach (namely re-ECN) and I am keen that any WG is given > the freedom to eventually explore other possible approaches. > > Having said that I am also not completely convinced by "expose" or > "Exposure" (preferring instead transparency with its associated > economic context). However, as Bob said in an earlier email we seem to > have converged that as being the word that causes least confusion. > > Sadly whatever you choose to call something is always open to > misinterpretation... > > Toby > > > -----Original Message----- > > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On > > Behalf Of Michael Menth > > Sent: 29 September 2009 09:36 > > To: Briscoe,RJ,Bob,XVR9 BRISCORJ R > > Cc: re-ECN unIETF list > > Subject: Re: [re-ECN] Acronym for BoF / w-g? DCP > > > > Hi again, > > > > as I said already before, I like Richard's "prediction" quite much as > > the "inserted re-feedback" is just an estimate for the congestion on > > the > > path. Another adjective to describe the congestion prediction would > be > > nice to sound good, e.g., downstream congestion prediction (DCP) > which > > also implies that proxies may insert re-feedback. Maybe another > > adjective is better? > > > > Regards, > > > > Michael > > > > Michael Menth schrieb: > > > Hi all, > > > > > > I am not happy with all the acronyms. Regarding the meaning, I like > > > Richard's "congestion prediction" most as the returned ECN feedback > > is > > > just a hint to predict the congestion on the path. But I feel that > > the > > > term "exposure" has already quite some consensus. Another option > > which > > > is in line with CEX, CEEX, etc. would be > > > > > > Explicit Congestion Exposure (ECE) > > > > > > It can be seen in contrast to or as a complement to Explicit > > > Congestion Notification (ECN). We already have Pre-Congestion > > > Notification (PCN) as another variant in this style. > > > > > > Regards, > > > > > > Michael > > > > > > Bob Briscoe schrieb: > > >> Hi Congestion Exposers (or should that be ex-posers?), > > >> > > >> Lars & Jari need an acronym. > > >> > > >> Can someone suggest a way to decide between the ideas proposed so > > far > > >> below, rather than just going round and round on the list? > > >> > > >> Context - CONgestion EXposed Truthfully > > >> Counted - COngestion {UNiversally Truthfully} ExposeD > > >> Exact - EXposing All CongesTion > > >> Expect - EXPosing CongesTion > > >> ExCeTra (pronounced etc.) - EXposing Congestion TRAnsparently > > >> CEX - Congestion EXposure or Congestion Exposure eXperiments > > >> ConEx - Congestion Exposure > > >> re-ECN - re-inserted Explicit Congestion Notification (or receiver > > >> aligned) > > >> re-con - Reinserted Congestion? Also alluding to military > > reconnaissance > > >> Trac - Transport with accountabiliy > > >> Travis or Tracvis - Transport with congestion visiblity > > >> > > >> I've removed a couple the original proposer didn't really like, to > > >> try to start converging. > > >> > > >> If we're voting, I vote for CEX (with a soft C of course). > > >> > > >> > > >> Bob > > >> > > >> > > >>> Subject: RE: [re-ECN] Name for BoF? > > >>> Date: Tue, 8 Sep 2009 11:01:43 +0100 > > >>> From: <toby.moncaster@bt.com> > > >>> To: <toby.moncaster@bt.com>om>, <rbriscoe@jungle.bt.co.uk>uk>, > > >>> <re-ecn@ietf.org> > > >>> Cc: <ingemar.s.johansson@ericsson.com> > > >>> > > >>> 6 more suggestions: > > >>> > > >>> Connexion - CONgestioN EXposure InformatiON > > >>> Context - CONgestion EXposed Truthfully > > >>> Convex - CONgestion Voluntarily EXposed > > >>> Counted - COngestion {UNiversally Truthfully} ExposeD > > >>> Exact - EXposing All CongesTion > > >>> Expect - EXPosing CongesTion > > >>> > > >>> Of these I think I prefer exact, counted and context as the words > > >>> convey something of what we mean. > > >>> > > >>> Toby > > >>> > > >>> > > >>> > -----Original Message----- > > >>> > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] > On > > >>> > Behalf Of toby.moncaster@bt.com > > >>> > Sent: 08 September 2009 09:20 > > >>> > To: Briscoe,RJ,Bob,XVR9 BRISCORJ R; re-ecn@ietf.org > > >>> > Cc: ingemar.s.johansson@ericsson.com > > >>> > Subject: Re: [re-ECN] Name for BoF? > > >>> > > > >>> > If you want to go for something catchy I had been thinking on > the > > >>> lines > > >>> > of: > > >>> > > > >>> > ExCeTra (pronounced etc.) - EXposing Congestion TRAnsparently > > >>> > > > >>> > I am exactly split between Congestion Transparency and > Congestion > > >>> > Exposure. Congestion Visibility is weak... > > >>> > > > >>> > Toby > > >>> > > > >>> > PS - glad we got something out in time for the deadline. Let's > > >>> hope it > > >>> > proves suitable to get us to the starting gate in Hiroshima... > > >>> > > > >>> > > -----Original Message----- > > >>> > > From: re-ecn-bounces@ietf.org [mailto:re-ecn- > bounces@ietf.org] > > On > > >>> > > Behalf Of Bob Briscoe > > >>> > > Sent: 08 September 2009 09:03 > > >>> > > To: re-ECN unIETF list > > >>> > > Cc: Ingemar Johansson S > > >>> > > Subject: Re: [re-ECN] Name for BoF? > > >>> > > > > >>> > > Folks, > > >>> > > > > >>> > > More views welcome? > > >>> > > > > >>> > > Summary of 'votes' so far... > > >>> > > > > >>> > > At 00:08 08/09/2009, João Taveira Araújo wrote: > > >>> > > >Bob Briscoe wrote: > > >>> > > >>Folks, > > >>> > > >> > > >>> > > >>One important issue I never raised - the name. > > >>> > > >> > > >>> > > >>Congestion Exposure > > >>> > > >>Congestion Visibility > > >>> > > >>Congestion Transparency > > >>> > > > > >>> > > Congestion Exposure seems to get everyone's approval > > >>> > > > > >>> > > > > >>> > > >>And a short form: > > >>> > > >>CEX? > > >>> > > >>re-ECN? > > >>> > > > > >>> > > Everyone agrees on what it shouldn't be: Not re-ECN > > >>> > > Less agreement on a replacement: > > >>> > > > > >>> > > CEX > > >>> > > ConEx > > >>> > > re-con > > >>> > > Also, one vote for "Wait until later." > > >>> > > > > >>> > > > > >>> > > I'm not so keen on including "Con" for obvious > > >>> > > reasons :) Choosing something like that can come back and > bite > > you. > > >>> > > It also sounds somehow as much like config as congestion. > > >>> > > > > >>> > > Some time ago, Toby came up with a clever one: > > >>> > > C-IT (pron. "See it") for Congestion Information > > >>> > Transparency. > > >>> > > not so useful if we're not calling it transparency tho. > > >>> > > > > >>> > > Hey, I've just had a thought, the flag (or > > >>> > > codepoint) for rest-of-path congestion could be > > >>> > > called CEX (Congestion Expected), rather > > >>> > > ambiguous with ECN's "Congestion Experienced (CE)" tho. > > >>> > > > > >>> > > > > >>> > > Bob > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > ________________________________________________________________ > > >>> > > Bob Briscoe, Networks Research Centre, BT > > Research > > >>> > > > > >>> > > _______________________________________________ > > >>> > > re-ECN mailing list > > >>> > > re-ECN@ietf.org > > >>> > > https://www.ietf.org/mailman/listinfo/re-ecn > > >>> > _______________________________________________ > > >>> > re-ECN mailing list > > >>> > re-ECN@ietf.org > > >>> > https://www.ietf.org/mailman/listinfo/re-ecn > > >> > > >> ________________________________________________________________ > > >> Bob Briscoe, BT Innovate & Design > > >> _______________________________________________ > > >> re-ECN mailing list > > >> re-ECN@ietf.org > > >> https://www.ietf.org/mailman/listinfo/re-ecn > > > > > > > -- > > Dr. Michael Menth, Assistant Professor > > University of Wuerzburg, Institute of Computer Science > > Am Hubland, D-97074 Wuerzburg, Germany, room B206 > > phone: (+49)-931/31-86644 (new), fax: (+49)-931/888-6632 > > mailto:menth@informatik.uni-wuerzburg.de > > http://www3.informatik.uni-wuerzburg.de/research/ngn > > > > _______________________________________________ > > re-ECN mailing list > > re-ECN@ietf.org > > https://www.ietf.org/mailman/listinfo/re-ecn > _______________________________________________ > re-ECN mailing list > re-ECN@ietf.org > https://www.ietf.org/mailman/listinfo/re-ecn
- [re-ECN] Acronym for BoF / w-g? Bob Briscoe
- Re: [re-ECN] Acronym for BoF / w-g? Matthew Ford
- Re: [re-ECN] Acronym for BoF / w-g? Scott Brim
- Re: [re-ECN] Acronym for BoF / w-g? Kwok Ho Chan
- Re: [re-ECN] Acronym for BoF / w-g? Fred Baker
- Re: [re-ECN] Acronym for BoF / w-g? Bob Briscoe
- Re: [re-ECN] Acronym for BoF / w-g? Bob Briscoe
- Re: [re-ECN] Acronym for BoF / w-g? Fred Baker
- Re: [re-ECN] Acronym for BoF / w-g? Bob Briscoe
- Re: [re-ECN] Acronym for BoF / w-g? Fred Baker
- Re: [re-ECN] Acronym for BoF / w-g? Richard Bennett
- Re: [re-ECN] Acronym for BoF / w-g? Fred Baker
- [re-ECN] Congestion is relative (was: Re: Acronym… Bob Briscoe
- Re: [re-ECN] Acronym for BoF / w-g? ECE Michael Menth
- Re: [re-ECN] Acronym for BoF / w-g? DCP Michael Menth
- Re: [re-ECN] Acronym for BoF / w-g? toby.moncaster
- Re: [re-ECN] Acronym for BoF / w-g? DCP toby.moncaster
- Re: [re-ECN] Acronym for BoF / w-g? DCP toby.moncaster
- Re: [re-ECN] Acronym for BoF / w-g? toby.moncaster
- Re: [re-ECN] Acronym for BoF / w-g? DCP Tina TSOU
- Re: [re-ECN] Acronym for BoF / w-g? Lars Eggert
- Re: [re-ECN] Acronym for BoF / w-g? toby.moncaster
- [re-ECN] Draft Agenda toby.moncaster
- Re: [re-ECN] Acronym for BoF / w-g? DCE Michael Menth
- Re: [re-ECN] Draft Agenda Leslie Daigle
- Re: [re-ECN] Draft Agenda toby.moncaster
- Re: [re-ECN] Draft Agenda Mirja Kuehlewind
- Re: [re-ECN] Draft Agenda toby.moncaster
- Re: [re-ECN] Draft Agenda Woundy, Richard
- Re: [re-ECN] Draft Agenda Leslie Daigle
- Re: [re-ECN] Draft Agenda toby.moncaster
- [re-ECN] BOF e-ECN Demo (was RE: Draft Agenda) alan.p.smith
- Re: [re-ECN] Draft Agenda Woundy, Richard
- Re: [re-ECN] Draft Agenda Woundy, Richard
- Re: [re-ECN] Draft Agenda alan.p.smith
- Re: [re-ECN] Draft Agenda Lars Eggert
- Re: [re-ECN] Draft Agenda Woundy, Richard
- Re: [re-ECN] Draft Agenda Matt Mathis