Re: [re-ECN] Acronym for BoF / w-g?

<toby.moncaster@bt.com> Tue, 29 September 2009 09:09 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 A813E3A6890 for <re-ecn@core3.amsl.com>; Tue, 29 Sep 2009 02:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.964
X-Spam-Level:
X-Spam-Status: No, score=-2.964 tagged_above=-999 required=5 tests=[AWL=0.035, 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 cbxgBsb3fvg0 for <re-ecn@core3.amsl.com>; Tue, 29 Sep 2009 02:08:59 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id 2281B28C0E7 for <re-ecn@ietf.org>; Tue, 29 Sep 2009 02:08:58 -0700 (PDT)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.61]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 29 Sep 2009 10:10:18 +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:10:16 +0100
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70D418041@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70D417FCE@E03MVZ1-UKDY.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Acronym for BoF / w-g?
Thread-Index: AcpAaiJZGeifKBQ7Qc+ZHLqrZX+iowAd2d7gAACQFcA=
References: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk> <AEDCAF87EEC94F49BA92EBDD49854CC70D417FCE@E03MVZ1-UKDY.domain1.systemhost.net>
From: <toby.moncaster@bt.com>
To: <toby.moncaster@bt.com>, <rbriscoe@jungle.bt.co.uk>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 29 Sep 2009 09:10:18.0350 (UTC) FILETIME=[AA11E0E0:01CA40E4]
Subject: Re: [re-ECN] Acronym for BoF / w-g?
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:09:00 -0000

And one more:

TECI - Timely Exposure of Congestion Information - pronounced "techy"

The main thing this adds is the idea that it is important WHEN this info is exposed...

However I am mindful of the extremely sound advice in RFC5434 which tells us that a common pitfall for BoFs is 

" - giving the BOF a "cute" but unintuitive name (or acronym),
    preventing people from realizing that it would be of interest to
    them."

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:50
> To: Briscoe,RJ,Bob,XVR9 BRISCORJ R; re-ecn@ietf.org
> Subject: Re: [re-ECN] Acronym for BoF / w-g?
> 
> Just one more suggestion (a variation really...):
> 
> Context - CONgestion EXposed (with "ext" = "ex'ed")
> 
> > -----Original Message-----
> > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On
> > Behalf Of Bob Briscoe
> > Sent: 28 September 2009 19:32
> > To: re-ECN unIETF list
> > Subject: [re-ECN] Acronym for BoF / w-g?
> >
> > 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
> _______________________________________________
> re-ECN mailing list
> re-ECN@ietf.org
> https://www.ietf.org/mailman/listinfo/re-ecn