Re: [re-ECN] BoF Proposal for wider IETF
"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Fri, 18 September 2009 22:46 UTC
Return-Path: <richard_woundy@cable.comcast.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 57F7C3A689A for <re-ecn@core3.amsl.com>;
Fri, 18 Sep 2009 15:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.327
X-Spam-Level:
X-Spam-Status: No, score=-6.327 tagged_above=-999 required=5 tests=[AWL=1.536,
BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,
J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_HI=-8]
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 hQ52mScx4wmk for
<re-ecn@core3.amsl.com>; Fri, 18 Sep 2009 15:46:06 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com
[24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 336653A657C for
<re-ecn@ietf.org>; Fri, 18 Sep 2009 15:46:06 -0700 (PDT)
Received: from ([10.52.116.31]) by pacdcimo01.cable.comcast.com with ESMTP id
5503620.54033265; Fri, 18 Sep 2009 18:46:55 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by
PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 18 Sep 2009 18:46:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Sep 2009 18:46:55 -0400
Message-ID: <8A82D1BFEDDE7E4597978355239BBBCB2A236A@PACDCEXCMB06.cable.comcast.com>
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70D1D1FDF@E03MVZ1-UKDY.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] BoF Proposal for wider IETF
Thread-Index: AcoyD73dw04VGBGmR9mjfdVL/IIMGwAE9ixfAAdjWMABgtA2kAAP76vg
References: <8A82D1BFEDDE7E4597978355239BBBCB05A348@PACDCEXCMB06.cable.comcast.com>
<8A82D1BFEDDE7E4597978355239BBBCB2A1B75@PACDCEXCMB06.cable.comcast.com>
<AEDCAF87EEC94F49BA92EBDD49854CC70D1D1FDF@E03MVZ1-UKDY.domain1.systemhost.net>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: <toby.moncaster@bt.com>, <lars.eggert@nokia.com>,
<rbriscoe@jungle.bt.co.uk>
X-OriginalArrivalTime: 18 Sep 2009 22:46:56.0176 (UTC)
FILETIME=[EC818B00:01CA38B1]
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] BoF Proposal for wider IETF
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: Fri, 18 Sep 2009 22:46:07 -0000
Looking at the recommended steps in http://tools.ietf.org/html/rfc5434#section-2, here's my opinion of some items our group should focus on. >From step 4: "getting agreement on the problem statement". Toby Moncaster has made some progress towards a draft already; we should be assisting him and contributing text. >From step 6 (note: after the BoF is approved): "identifying areas of agreement and areas of disagreement". The most fundamental disagreement (i.e. keeping flow-rate fairness) is probably captured in RFC 5290, http://tools.ietf.org/html/rfc5290. Has anyone identified any candidate protocols or approaches other than re-ECN? >From step 7: "produce a proposed charter and iterate on it on the mailing list". We might be able to start with the BoF proposal. >From step 8: "decide what questions will be asked during the BOF itself". This is somewhat different than the questions captured in the FAQ that Bob and John Leslie worked on. The questions are really about agreement with the charter, agreement with the problem statement, should a WG be formed yet, etc. See http://tools.ietf.org/html/rfc5434#section-4. We don't have to be a slave to RFC 5434, but it does provide pretty helpful advice. -- Rich -----Original Message----- From: toby.moncaster@bt.com [mailto:toby.moncaster@bt.com] Sent: Friday, September 18, 2009 6:44 AM To: Woundy, Richard; lars.eggert@nokia.com; rbriscoe@jungle.bt.co.uk Cc: re-ecn@ietf.org Subject: RE: [re-ECN] BoF Proposal for wider IETF Just in case people are interested, it looks as though the IESG will make their decisions on which BoFs to accept next Friday (25th). By that time it would be nice to have started some of the preliminary work that will need to be done if we do get approval... One of the key things we need to think about is suitable people to chair the BoF. I believe Rich has already expressed an interest and so we would need to find A.N.Other... Toby > -----Original Message----- > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On > Behalf Of Woundy, Richard > Sent: 10 September 2009 19:06 > To: lars.eggert@nokia.com; Briscoe,RJ,Bob,XVR9 BRISCORJ R > Cc: re-ecn@ietf.org > Subject: Re: [re-ECN] BoF Proposal for wider IETF > > I think I found my own answer (yes, officially), per > http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#Transport. > > -- Rich > > -----Original Message----- > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On > Behalf > Of Woundy, Richard > Sent: Thursday, September 10, 2009 10:33 AM > To: lars.eggert@nokia.com; rbriscoe@jungle.bt.co.uk > Cc: re-ecn@ietf.org > Subject: Re: [re-ECN] BoF Proposal for wider IETF > > >you need to have submitted a BOF proposal by the deadline. See > RFC5434, > Section 2, Step 5. > > Did we make the deadline? > > -- Rich > _______________________________________________ > 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
- [re-ECN] BoF Proposal for wider IETF Bob Briscoe
- Re: [re-ECN] BoF Proposal for wider IETF Lars Eggert
- Re: [re-ECN] BoF Proposal for wider IETF Woundy, Richard
- Re: [re-ECN] BoF Proposal for wider IETF Woundy, Richard
- Re: [re-ECN] BoF Proposal for wider IETF Bob Briscoe
- Re: [re-ECN] BoF Proposal for wider IETF toby.moncaster
- Re: [re-ECN] BoF Proposal for wider IETF Tom Taylor
- Re: [re-ECN] BoF Proposal for wider IETF Woundy, Richard
- Re: [re-ECN] BoF Proposal for wider IETF Woundy, Richard