Re: [re-ECN] Revised agenda theory
Leslie Daigle <leslie@thinkingcat.com> Sun, 25 October 2009 22:06 UTC
Return-Path: <leslie@thinkingcat.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 921C93A69E9 for <re-ecn@core3.amsl.com>;
Sun, 25 Oct 2009 15:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level:
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093,
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 1bJI9wcSv3Q1 for
<re-ecn@core3.amsl.com>; Sun, 25 Oct 2009 15:06:15 -0700 (PDT)
Received: from zeke.ecotroph.net (zeke.ecotroph.net [70.164.19.155]) by
core3.amsl.com (Postfix) with ESMTP id A030A3A6856 for <re-ecn@ietf.org>;
Sun, 25 Oct 2009 15:06:15 -0700 (PDT)
Received: from beethoven.local ([::ffff:173.71.204.217]) (AUTH: PLAIN leslie,
SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp;
Sun, 25 Oct 2009 18:06:27 -0400 id 015B0061.4AE4CBE3.00001BAF
Message-ID: <4AE4CBDB.4030806@thinkingcat.com>
Date: Sun, 25 Oct 2009 18:06:19 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
References: <4AE26E9B.8060205@thinkingcat.com>
<200910242327.n9ONRbZt023456@bagheera.jungle.bt.co.uk>
In-Reply-To: <200910242327.n9ONRbZt023456@bagheera.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Matt MATHIS <mathis@psc.edu>, re-ecn@ietf.org
Subject: Re: [re-ECN] Revised agenda theory
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: Sun, 25 Oct 2009 22:06:21 -0000
Hi Bob,
I do take your point about viability (of mechanisms for congestion
exposure, btw, not re-ECN specifically) being a challenge, but I also
don't think we'll get to discussing chartering a working group if we
don't take a whack at it. "Focus" will be the watch-word.
I'm happy to discuss how to make sure that discussion _is_ focused. I
actually think your smiley-table (mail to Fred) is a reasonable starting
point for at least some aspect of illustrating this.
I should also say -- I don't think the BoF can determine that congestion
exposure is The One True Way to better Internet health. I'm not even
particularly convinced a WG can do that. I'm hoping the bar is set at
demonstrating that it is a useful and important step to pursue, even as
others are pursue elsewhere.
A few more points, in-line:
Bob Briscoe wrote:
> Leslie,
>
> This looks good, but see below about the viability item, wherein lie
> monsters. Also, a couple of thoughts before that:
>
> 1/ I've been thinking... We should add an item to the many purposes list:
> - evolution path beyond TCP (running out of dynamic range)
Which is pretty cool, but on the bof agenda might lead to some ratholing
on whether we're just bashing TCP, no?
>
> 2/ I think it would be cool to have a brief session on the community
> around this; what people are doing in this space, why, etc. This could
> be structured:
> - either as one of the chairs reporting all this (requiring people to
> have told you in advance what they're doing - plus scraping the list
> archive for what people said when they introduced their interest recently),
> - or as a vox pop.
>
> It would also be a chance to report on some of the activity that has
> been going on to ensure the commercial & public policy community would
> be happy with such a change to the Internet (e.g. the GIIC thing you
> went to, and any ISOC activities you're planning).
I'm happy to have _a_ slide pointing out there's a lot of stuff going on
in the world, because, as you note, it does communicate that this is
getting broad airtime in the world at large. But for the purpose of the
BoF, I think the major emphasis should be on making sure the people in
the room have enough information to determine whether they think there
is an IETF activity here.
The latter is the theory behind "the problem" item on the agenda. If
there's a better way to handle that piece of it, happy to take sugestions.
And, I'll be sure to announce the ISOC activity here, when it's, errr,
announced. :)
>
> 3/ On the "discussion of viability" it occurs to me that the BoF can't
> really discuss how viable it might be to deploy re-ECN without also
> considering the viability of alternative approaches to solve each of the
> problems we claim to be able to solve (or even whether alternatives exist).
>
> How otherwise are we going to
> - side-step the net neutrality problem?
> - simplify inter-domain e2e QoS?
> - move beyond TCP which is running out of dynamic range?
> - and so on?
>
> Taking evolution beyond TCP as an example...
>
> In the IRTF ICCRG, Matt Mathis has proposed that moving to 1/p
> congestion controls (rather than 1/sqrt(p) like TCP) would allow
> congestion control to scale indefinitely, by maintaining a high
> congestion information rate as flow rates & link rates scale. Whereas if
> we stick with TCP-friendly, the information rate per window is already
> becoming stupidly low (hours between loss signals) as rates increase
> over the next few years. To put it bluntly, as carriers deploy more
> capacity, we'll be held back by the e2e protocols, which aren't able to
> use it.
>
> Widespread re-ECN deployment would allow us to relax the TCP-friendly
> requirement, so we can bless 1/p controls and shift onto a sounder
> evolution path.
>
> The alternative seems to be changing every router (and every LSR and
> every ethernet switch) in the Internet to do RCP (which still aims for
> flow-rate-fairness so it still drives ISPs into net neutrality issues,
> yada yada).
>
> ____
> Do you see my point about trying to talk about the viability of re-ECN
> in isolation from wider debate on the viability of the alternatives? But
> such a session would require a lot of cluefulness in the audience to
> understand it. You might recall the p2pi workshop, which covered just a
> small part of this space. It was a selected set of participants, but
> even then the cluefulness factor from each specialist about a each
> related area was painfully low.
>
> I'm not saying we shouldn't try to talk about viability, but it will be
> a complicated session to do justice to the debate.
And, the sad reality is, we will not do it justice. What we need to do
is hit the high points to illustrate that there is viability here, and
it's worth chartering an IETF activity to delve into it in more depth.
One refinement to the agenda text occurs to me:
CONEX
5 mins administrivia
5 mins introduction by chairs
Background
40 mins the problem
context/motivation [Rich Woundy]
technical problem [Mark Handley]
10 mins constraints [Philip Eardley]
30 mins towards a solution
overview of re-ECN [Bob Briscoe]
Discussion of potential IETF work
40 mins discussion of viability of congestion exposure
20 mins draft charter discussion
10 mins questions and hums
Leslie.
>
>
> Bob
>
> At 04:03 24/10/2009, Leslie Daigle wrote:
>
>> Hi,
>>
>> We need to get an agenda posted. Subject to suggested changes, and/or
>> absent howls of dissent, we'll post the following. Note that I have
>> expanded it to allow more discussion of the specific viability of the
>> approach.
>>
>> We'll work on framing up some discussion for that part of the agenda
>> during the next week, or so.
>>
>> Leslie.
>>
>>
>>
>> Congestion Exposure (ConEx) is a proposed new IETF activity to enable
>> congestion to be exposed along the forwarding path of the Internet. By
>> revealing expected congestion in the IP header of every packet,
>> congestion exposure provides a generic network capability which allows
>> greater freedom over how capacity is shared. Such information could be
>> used for many purposes, including congestion policing, accountability
>> and inter-domain SLAs. It may also open new approaches to QoS and
>> traffic engineering.
>>
>> The purpose of the BoF is to explore the support for and viability of
>> pursuing an IETF activity to define a basic protocol to expose the
>> expected rest-of-path congestion in the IP header. Any such protocol
>> should work with minimal changes to the existing network, in particular
>> it should work with unmodified routers. There is already one existing
>> proposal that builds on ECN to provide rest-of-path congestion
>> information in every IP header and other proposals may come forward.
>>
>> More detail is available at:
>> http://trac.tools.ietf.org/area/tsv/trac/wiki/re-ECN
>>
>> BoF Co-Chairs:
>>
>> Leslie Daigle <leslie@thinkingcat.com>
>> Philip Eardley <philip.eardley@bt.com>
>>
>>
>> Agenda
>>
>> 5 mins administrivia
>> 5 mins introduction by chairs
>> 40 mins the problem
>> context/motivation [Rich Woundy]
>> technical problem [Mark Handley]
>> 10 mins constraints [Philip Eardley]
>> 30 mins towards a solution
>> overview of re-ECN [Bob Briscoe]
>> 40 mins discussion of viability
>> 20 mins draft charter discussion
>> 10 mins questions and hums
>>
>>
>> N.B.: This assumes our current 160min agenda space (check my math!).
>> If the BoF moves, we'll have to re-think.
>>
>>
>> --
>>
>> -------------------------------------------------------------------
>> "Reality:
>> Yours to discover."
>> -- ThinkingCat
>> Leslie Daigle
>> leslie@thinkingcat.com
>> -------------------------------------------------------------------
>> _______________________________________________
>> re-ECN mailing list
>> re-ECN@ietf.org
>> https://www.ietf.org/mailman/listinfo/re-ecn
>
> ________________________________________________________________
> Bob Briscoe, BT Innovate & Design
--
-------------------------------------------------------------------
"Reality:
Yours to discover."
-- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------
- [re-ECN] Revised agenda theory Leslie Daigle
- Re: [re-ECN] Revised agenda theory Bob Briscoe
- Re: [re-ECN] Revised agenda theory Leslie Daigle
- Re: [re-ECN] Revised agenda theory toby.moncaster
- Re: [re-ECN] Revised agenda theory Bob Briscoe
- [re-ECN] TCP's "Dynamic Range" John Leslie
- Re: [re-ECN] TCP's "Dynamic Range" Bob Briscoe
- Re: [re-ECN] TCP's "Dynamic Range" Leslie Daigle
- Re: [re-ECN] TCP's "Dynamic Range" Matt Mathis
- Re: [re-ECN] TCP's "Dynamic Range" Leslie Daigle
- Re: [re-ECN] TCP's "Dynamic Range" John Leslie
- [re-ECN] re-echo of drop (was: Re: TCP's "Dynamic… Bob Briscoe
- Re: [re-ECN] re-echo of drop João Taveira Araújo
- Re: [re-ECN] TCP's "Dynamic Range" philip.eardley
- [re-ECN] re-echo of drop Matt Mathis
- Re: [re-ECN] re-echo of drop (was: Re: TCP's "Dyn… Matt Mathis
- Re: [re-ECN] re-echo of drop (was: Re: TCP's "Dyn… Bob Briscoe
- Re: [re-ECN] re-echo of drop João Taveira Araújo
- Re: [re-ECN] re-echo of drop Bob Briscoe