Re: [re-ECN] BoF Proposal for wider IETF
"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Fri, 18 September 2009 18:12 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 1D67A3A6B85 for <re-ecn@core3.amsl.com>;
Fri, 18 Sep 2009 11:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level:
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=-2.654,
BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,
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 f+OEmIpzhuoW for
<re-ecn@core3.amsl.com>; Fri, 18 Sep 2009 11:12:10 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com
[208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id E9C6F3A6B81 for
<re-ecn@ietf.org>; Fri, 18 Sep 2009 11:12:09 -0700 (PDT)
Received: from ([10.52.116.30]) by paoakoavas10.cable.comcast.com with ESMTP
id KP-TDCH7.69302528; Fri, 18 Sep 2009 14:12:48 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by
PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 18 Sep 2009 14:12:48 -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 14:12:47 -0400
Message-ID: <8A82D1BFEDDE7E4597978355239BBBCB2A22F4@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/IIMGwAE9ixfAAdjWMABgtA2kAAOjgOA
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 18:12:48.0869 (UTC)
FILETIME=[A125A950:01CA388B]
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 18:12:11 -0000
>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... Yes, I have expressed interest in being a BoF co-chair, and I've had some prior experience that might be helpful here. But I don't think we should not be campaigning for co-chairs on IETF mailing lists -- in fact, I don't think there should be any IETF position campaigning at all. That's why I sent a *private* email to Bob Briscoe (as the most active BoF organizer) and to Lars Eggert (as one of the responsible ADs per http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#Transport). The other responsible AD is Jari Arkko. I would recommend that other folks interested in a potential BoF co-chair role should also communicate privately to Lars and Jari -- although right now they are probably more focused on whether this should be an approved BoF for Hiroshima than whom they should pick for co-chairs. Certainly the deeper pool of candidates they have to choose from, the better for this group. In any case, I'll spend more time working on <Re-ECN or whatever> regardless of my personal role in this group. Here is some helpful advice from http://tools.ietf.org/html/rfc5434#section-7.1: BOF organizers often assume that they will be chairing a BOF (and the eventual WG). Neither assumption is always true. ADs need to ensure that a BOF runs smoothly and is productive. For some topics, it is a given that the BOF will be contentious. In such cases, ADs may want to have a more experienced person chairing or co-chairing the BOF. Also, those interested in organizing the BOF often are the most interested in driving a particular technology (and may have strongly held views about what direction an effort should take). Working Groups are often more effective when passionately involved parties are allowed to focus on the technical work, rather than on managing the WG itself. Thus, do not be surprised (or offended!) if the AD wants to pick one or more co-chairs for either the BOF or a follow-on WG. -- 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