Re: [re-ECN] Acronym for BoF / w-g?
Kwok Ho Chan <khchan@huawei.com> Mon, 28 September 2009 19:34 UTC
Return-Path: <khchan@huawei.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 6D5F43A69B4 for <re-ecn@core3.amsl.com>;
Mon, 28 Sep 2009 12:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.744
X-Spam-Level:
X-Spam-Status: No, score=-1.744 tagged_above=-999 required=5 tests=[AWL=0.255,
BAYES_00=-2.599, J_CHICKENPOX_72=0.6]
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 trnkippRzYs1 for
<re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 12:34:12 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by
core3.amsl.com (Postfix) with ESMTP id 752353A6862 for <re-ecn@ietf.org>;
Mon, 28 Sep 2009 12:34:12 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com
(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id
<0KQP000CG535DB@usaga02-in.huawei.com> for re-ecn@ietf.org;
Mon, 28 Sep 2009 12:35:30 -0700 (PDT)
Received: from K73911.huawei.com ([10.192.21.57]) by usaga02-in.huawei.com
(iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPSA id
<0KQP000GU534JB@usaga02-in.huawei.com> for re-ecn@ietf.org;
Mon, 28 Sep 2009 12:35:29 -0700 (PDT)
Date: Mon, 28 Sep 2009 15:35:27 -0400
From: Kwok Ho Chan <khchan@huawei.com>
In-reply-to: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk>
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Message-id: <0KQP000GW535JB@usaga02-in.huawei.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Content-type: text/plain; charset=iso-8859-1; format=flowed
Content-transfer-encoding: quoted-printable
References: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk>
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 19:34:13 -0000
I am worried the use of CEX and Exposure may
generate too much traffic for the list.
It may also trigger some censorship with some jurisdictions and organizations.
What do you tell the immigration officer who checks your passport when he asks
you what convention/meeting you are attending
before he lets you into the country?
We may have too many people attending our meetings.
I like C-IT (See It) for Congestion Information Transparency
I like Transparency more than Exposure, as
Transparency hints at trust, while Exposure
hints at unwanted disclosure (like the publishing of movie star private info).
-- Kwok --
At 02:32 PM 9/28/2009, Bob Briscoe wrote:
>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] 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