Re: [re-ECN] Congestion Exposure BOF approved

Bob Briscoe <rbriscoe@jungle.bt.co.uk> Mon, 28 September 2009 18:20 UTC

Return-Path: <rbriscoe@jungle.bt.co.uk>
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 0A76B28C0DC for <re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 11:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, 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 tXOmbtXK11Gv for <re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 11:20:24 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by core3.amsl.com (Postfix) with ESMTP id F0C633A6958 for <re-ecn@ietf.org>; Mon, 28 Sep 2009 11:20:23 -0700 (PDT)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Sep 2009 19:21:41 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Sep 2009 19:21:41 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1254162100518; Mon, 28 Sep 2009 19:21:40 +0100
Received: from MUT.jungle.bt.co.uk ([10.215.130.87]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id n8SILbEa024617; Mon, 28 Sep 2009 19:21:37 +0100
Message-Id: <200909281821.n8SILbEa024617@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 28 Sep 2009 19:21:34 +0100
To: Lars Eggert <lars.eggert@nokia.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <75BDC13D-1877-4B57-BA06-B5B5F10F3CB0@nokia.com>
References: <0BE56D2A-15FC-4BE4-9BCD-850E91564D36@nokia.com> <200909281643.n8SGhF89022989@bagheera.jungle.bt.co.uk> <75BDC13D-1877-4B57-BA06-B5B5F10F3CB0@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 28 Sep 2009 18:21:41.0327 (UTC) FILETIME=[86A5CDF0:01CA4068]
Cc: re-ECN unIETF list <re-ecn@ietf.org>
Subject: Re: [re-ECN] Congestion Exposure BOF approved
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:20:30 -0000

Lars,

At 18:06 28/09/2009, Lars Eggert wrote:
>Hi,
>
>On 2009-9-28, at 19:43, Bob Briscoe wrote:
>>>I'll work with the proponents on detailing the BOF agenda
>>
>>Presumably primarily on this list.
>
>yes.

OK let's get going again with this on the list.


>>>One bit of feedback from the I* is that the
>>>proposed charter is lengthy but light on actual proposed work. We
>>>need
>>>a crisper BOF agenda and proposed WG charter.
>>
>>I'd be wary of adding more work (as there's a lot in each item
>>listed), but if you mean more info is needed on each item, certainly
>>can do.
>
>I probably shouldn't have said "light" but "unclear". What exactly the
>proposed work items are needs to still become more to-the-point
>understandable.

Understood.


>>What's the process (including deadlines and who has to approve it)
>>for:
>>- defining a BoF announcement (the one linked from the IETF agenda)?
>>- defining a draft charter?
>
>Both of these are what you (the plural you) and me need to work on and
>agree on. Soon.

OK - another two item to get back to working on, on this list.


>>Before getting down to candidate acronyms, what's behind the "bit too
>>generic" comment? Was that feedback from the I* or a personal view?
>>
>>Is there concern about:
>>- needing a name for a protocol in the title?
>>- or needing more about motivation in the title?
>
>My personal view. Basically, "CE" as an BOF/WG acronym is a bit too
>short IMO. If we can find something a bit more mnemonic, that'd be nice.
>
>(Note that I think the BOF long name is fine - this is about the
>acronym.)

I don't think we proposed CE. There was a bit of a thread a while ago 
where loads of suggestions came out, but we seemed to be diverging rather.

I proposed CEX, which either stands for Congestion EXposure or 
Congestion Exposure eXperiments. [Or perhaps CExEx thinking about it 
now.] Remember, you can never have an excess of CEX.

Some agreed, some didn't.

I'll re-post the last posting on this, and get this going again.


>>>PS: Secretariat (BCC'ed), please earmark an agenda slot for the BOF,
>>>but wait with the allocation until we know what acronym we'll go
>>>with.
>>
>>When do we have to say how long a slot we need?
>
>Now. I'm guessing you want at least 2h?

Yup. Definitely IMO.


Bob


>Lars

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design