Re: [re-ECN] Congestion Exposure BOF approved
Lars Eggert <lars.eggert@nokia.com> Mon, 28 September 2009 17:06 UTC
Return-Path: <lars.eggert@nokia.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 A77AE3A6885 for <re-ecn@core3.amsl.com>;
Mon, 28 Sep 2009 10:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599]
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 EZPTrMjwWRXx for
<re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 10:06:27 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by
core3.amsl.com (Postfix) with ESMTP id 847873A6828 for <re-ecn@ietf.org>;
Mon, 28 Sep 2009 10:06:27 -0700 (PDT)
Received: from pc-a80034.wlan.inet.fi (pc-a80034.wlan.inet.fi [194.111.80.34])
(authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id
n8SH5kPu075854 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
Mon, 28 Sep 2009 20:07:37 +0300 (EEST) (envelope-from lars.eggert@nokia.com)
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <200909281643.n8SGhF89022989@bagheera.jungle.bt.co.uk>
Date: Mon, 28 Sep 2009 20:06:53 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <75BDC13D-1877-4B57-BA06-B5B5F10F3CB0@nokia.com>
References: <0BE56D2A-15FC-4BE4-9BCD-850E91564D36@nokia.com>
<200909281643.n8SGhF89022989@bagheera.jungle.bt.co.uk>
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.1076)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3
(mail.fit.nokia.com [195.148.124.194]); Mon, 28 Sep 2009 20:07:38 +0300 (EEST)
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 17:06:31 -0000
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. > >> and >> assigning some BOF chairs. > > Presumably off list initially. Yes. >> 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. > 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. > 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.) >> 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? Lars
- [re-ECN] Congestion Exposure BOF approved Lars Eggert
- Re: [re-ECN] Congestion Exposure BOF approved Bob Briscoe
- Re: [re-ECN] Congestion Exposure BOF approved Lars Eggert
- Re: [re-ECN] Congestion Exposure BOF approved Bob Briscoe