[re-ECN] Draft Agenda
<toby.moncaster@bt.com> Tue, 29 September 2009 09:57 UTC
Return-Path: <toby.moncaster@bt.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 B15DA3A6864 for <re-ecn@core3.amsl.com>;
Tue, 29 Sep 2009 02:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.261
X-Spam-Level:
X-Spam-Status: No, score=-3.261 tagged_above=-999 required=5 tests=[AWL=0.338,
BAYES_00=-2.599, 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 vhiQTnzp6EDq for
<re-ecn@core3.amsl.com>; Tue, 29 Sep 2009 02:57:18 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by
core3.amsl.com (Postfix) with ESMTP id A64A13A6765 for <re-ecn@ietf.org>;
Tue, 29 Sep 2009 02:57:18 -0700 (PDT)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.61]) by
smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 29 Sep 2009 10:58:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
x-cr-hashedpuzzle: BMA= A0ig A8Qk ChH2 DH3k DThe Dx8z EHkz ETEX EaDD EvfH GfN4
HSlP HphN IV4O JO4L; 1; cgBlAC0AZQBjAG4AQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7;
{F6F8AC39-1FD6-4A01-B84F-99FDDAB1E175};
dABvAGIAeQAuAG0AbwBuAGMAYQBzAHQAZQByAEAAYgB0AC4AYwBvAG0A;
Tue, 29 Sep 2009 09:58:30 GMT; RAByAGEAZgB0ACAAQQBnAGUAbgBkAGEA
x-cr-puzzleid: {F6F8AC39-1FD6-4A01-B84F-99FDDAB1E175}
Content-class: urn:content-classes:message
Date: Tue, 29 Sep 2009 10:58:30 +0100
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70D41814F@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <B56BB2A2-AECD-43F0-98D0-1457C86F1FA9@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Draft Agenda
Thread-Index: AcpA5cInrrLYt8F6Tum1HePydtkH3AAApoJA
References: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk>
<AEDCAF87EEC94F49BA92EBDD49854CC70D417FCE@E03MVZ1-UKDY.domain1.systemhost.net>
<AEDCAF87EEC94F49BA92EBDD49854CC70D418041@E03MVZ1-UKDY.domain1.systemhost.net>
<B56BB2A2-AECD-43F0-98D0-1457C86F1FA9@nokia.com>
From: <toby.moncaster@bt.com>
To: <re-ecn@ietf.org>
X-OriginalArrivalTime: 29 Sep 2009 09:58:37.0712 (UTC)
FILETIME=[6A396900:01CA40EB]
Subject: [re-ECN] Draft Agenda
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: Tue, 29 Sep 2009 09:57:19 -0000
As promised, here is the start of a discussion on the draft agenda for the BoF... This is making the assumption that we will get 2 hours of meeting time. I personally feel 2 hours is plenty - if we got more than that the risk is that we will lose the focus (and lose our audience). 5 mins administrivia 10 mins introduction by chairs 20 mins the problem 15 mins towards a solution 10 mins demonstration 40 mins discussion 10 mins sumnmary 10 mins questions and hums Details: "The problem" will give the background to why we want to do this work, and why now. It will probably be split into two halves - the general problem for the Internet and the specific problem as seen by an operator. It should largely cover the first half of the problem statement document we are jointly working on. "towards a solution" will cover the second half of the problem statement document. It will describe an overview of re-feedback and show how this can allow congestion to be exposed by end-users. It WON'T have details of re-ECN itself, however it could explain briefly the concept of policing to a congestion rate. The "demonstration" should really take 5 mins, but allowing 10 mins allows for things going wrong. At the moment the plan is to show a simple re-ECN system where a series of different size files are transferred across a link. At the BoF end there is a monitor that will display the congestion level. We will be able to insert extra congestion and show that the monitor can give you the congestion upstream and downstream. The idea is to show that this is not just research but that it is ready for the IETF - we aren't trying to impose our solution, we just need to show that there is a solution possible... The "discussion" will need to be led by the chairs to prevent it going off into protocol details or other dead-ends. The key thing is to work towards getting agreement that the CONCEPT of exposing congestion (and thus correcting the information asymmetry) is a good thing, and that it is the starting point towards a more open and transparent means of controlling the use of the Internet by monitoring the one thing that actually impacts all users... One of the key things here will be to show there is already an active community working in this area. "summary" just needs to bring together any loose ends from the discussion and try and leave people with a clear set of messages, for instance: congestion is a key metric, currently congestion is hidden from the layer that needs to know about it, revealing this congestion will correct the information asymmetry and lead to better control of the Internet, etc "The questions" will need a whole email thread of their own, but that can wait till a bit nearer the day. The key thing is to have very clear closed questions- that is questions that only have a yes or no answer... Toby
- [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