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

Matthew Ford <ford@isoc.org> Mon, 28 September 2009 18:50 UTC

Return-Path: <ford@isoc.org>
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 E70023A6A04 for <re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 11:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.199
X-Spam-Level:
X-Spam-Status: No, score=-103.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1, 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 7CtqKKS-yghA for <re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 11:50:04 -0700 (PDT)
Received: from smtp110.iad.emailsrvr.com (smtp110.iad.emailsrvr.com [207.97.245.110]) by core3.amsl.com (Postfix) with ESMTP id B893B3A69F4 for <re-ecn@ietf.org>; Mon, 28 Sep 2009 11:50:04 -0700 (PDT)
Received: from relay31.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay31.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id 10E511B4233; Mon, 28 Sep 2009 14:51:23 -0400 (EDT)
Received: by relay31.relay.iad.mlsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id 2838B1B4266; Mon, 28 Sep 2009 14:51:21 -0400 (EDT)
Message-ID: <4AC105A5.10200@isoc.org>
Date: Mon, 28 Sep 2009 19:51:17 +0100
From: Matthew Ford <ford@isoc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
References: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk>
In-Reply-To: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: re-ECN unIETF list <re-ecn@ietf.org>
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: Mon, 28 Sep 2009 18:50:06 -0000

On 28/09/2009 19:32, Bob Briscoe wrote:
> Can someone suggest a way to decide between the ideas proposed so far
> below, rather than just going round and round on the list?

Pick one ;)

> Expect - EXPosing CongesTion

I like this one - it's not ludicrously contrived, and it's germane to 
the work (as in, you can tell how much congestion to ... expect)

> If we're voting, I vote for CEX (with a soft C of course).

Reminds me of the BT Security Evaluation and Certification Scheme 
(BTSECS) ... *shudder*


Mat

>
>
> 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