Re: [re-ECN] preliminary draft of problem statement- authors wanted

<toby.moncaster@bt.com> Mon, 28 September 2009 15:28 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 276543A69BC for <re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 08:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.961
X-Spam-Level:
X-Spam-Status: No, score=-2.961 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, J_CHICKENPOX_91=0.6, 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 A2T4YBwFoMwa for <re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 08:28:02 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 325223A69B8 for <re-ecn@ietf.org>; Mon, 28 Sep 2009 08:28:02 -0700 (PDT)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.61]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 28 Sep 2009 16:29:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 28 Sep 2009 16:29:18 +0100
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70D417C1A@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <200909281722.31029.mirja.kuehlewind@ikr.uni-stuttgart.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] preliminary draft of problem statement- authors wanted
Thread-Index: AcpAT3+VN751M5fDS/C0FmGKtkFP+gAADnWg
References: <AEDCAF87EEC94F49BA92EBDD49854CC70D1D1EE6@E03MVZ1-UKDY.domain1.systemhost.net> <4ABBFA12.5070806@informatik.uni-wuerzburg.de> <AEDCAF87EEC94F49BA92EBDD49854CC70D390B86@E03MVZ1-UKDY.domain1.systemhost.net> <200909281722.31029.mirja.kuehlewind@ikr.uni-stuttgart.de>
From: <toby.moncaster@bt.com>
To: <mirja.kuehlewind@ikr.uni-stuttgart.de>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 28 Sep 2009 15:29:20.0121 (UTC) FILETIME=[72CEFE90:01CA4050]
Subject: Re: [re-ECN] preliminary draft of problem statement- authors wanted
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 15:28:04 -0000

Hi Mirja,

Thanks for the comments, I know the text is a bit of a mess! Hopefully things will get tidied up over the coming week (as we now know this BoF is going ahead for certain...) 

Currently the text is very much a mix of rough notes, blocks of text from various contributors and some edited stuff from me. As I said in the email I haven't myself read through the whole thing - I just wanted to get something out before the weekend for anyone who had some spare time :)

I am intending to devote a whole day this week to tidying things up and hopefully getting rid of any glaring inconsistencies. My intention is to concentrate on better explaining the problem, highlighting that congestion exposure seems to give a nice solution and show that re-feedback (in the more general case e.g. not re-ECN specifically) is a possible embodiment of congestion exposure...

Toby

> -----Original Message-----
> From: Mirja Kuehlewind [mailto:mirja.kuehlewind@ikr.uni-stuttgart.de]
> Sent: 28 September 2009 16:23
> To: re-ecn@ietf.org
> Cc: Moncaster,T,Toby,DER3 R
> Subject: Re: [re-ECN] preliminary draft of problem statement- authors
> wanted
> 
> Hi Toby,
> 
> two comments for my side so far:
> 
> Regarding the requirements, I'm not sure if their are understandable
> for somebody who don't know the re-ECN ideas. Although another ordering
> might help. And at this point of the document upstream and downstream
> congestion needs to be explained first.
> 
> In 5.2 I don't see why you are referring to re-ECN in the first
> paragraph while remaining very general in the rest of the section. I
> would prefer to move the reference to re-ECN to the end of the section.
> Where else a direct mention of ECN as a mechanism giving feedback would
> make the idea of re-feedback more clear to me.
> Btw. why has ECN been kicked out completely?
> 
> Mirja
> 
> 
> On Friday 25 September 2009 14:13:03 toby.moncaster@bt.com wrote:
> > Here is what I have done so far. I haven't yet incorporated one of
> > Michael's abstracts and I still haven't added in the proper list of
> > authors. I have heavily edited several sections but have to admit I
> > haven't tried to read through to see if it makes any sense.
> >
> > I am going to leave this now for a couple of days, probably until
> Tuesday.
> > Anyone wanting to edit it in the meantime please feel free!
> >
> > Toby
> >
> > ____________________________________________________________________
> > Toby Moncaster, Senior Researcher, Network Infrastructure Practise
> > B54/70 Adastral Park, Ipswich, IP53RE, UK.  +44 7918 901170
> >
> > > -----Original Message-----
> > > From: Michael Menth [mailto:menth@informatik.uni-wuerzburg.de]
> > > Sent: 25 September 2009 00:01
> > > To: Moncaster,T,Toby,DER3 R
> > > Cc: re-ecn@ietf.org
> > > Subject: Re: [re-ECN] preliminary draft of problem statement-
> > > authors wanted
> > >
> > > Hi Toby,
> > >
> > > here is some text for the abstract.
> > >
> > > >    We need to add an abstract summarising the problem and
> pointing
> > > >
> > > >    towards congestion exposure as an answer...
> > >
> > > I like it short:
> > >
> > > The idea of congestion exposure means that a flow reveals an
> > > estimate of the congestion it causes on its remaining downstream
> > > path. It makes policing or other actions depending on downstream
> > > congestion in the Internet more effective and leads thereby to a
> > > more efficient and fairer Internet. This document motivates the
> need
> > > for congestion exposure and illustrates its usefulness in different
> > > use cases. Therefore, actions should be taken to implement a simple
> > > form of congestion exposure in the Internet.
> > >
> > > However, an enumeration for what congestion exposure may be useful
> > > can help to catch the reader's interest:
> > >
> > > The idea of congestion exposure means that a flow reveals an
> > > estimate of the congestion it causes on its remaining downstream
> > > path. Congestion exposure may be useful for various purposes, e.g.,
> > > meaningful policing at network ingresses, congestion-based
> > > accounting between ISPs, fairer bandwidth sharing among users,
> > > increased trust in the congestion-responsiveness of end-systems,
> and
> > > possibly congestion-dependent load balancing and routing.
> Therefore,
> > > congestion exposure leads to a more efficient and fairer Internet.
> > > This document motivates the need for congestion exposure and
> > > illustrates its usefulness in different use cases. Therefore,
> > > actions should be taken to implement a simple form of congestion
> > > exposure in the Internet.
> > >
> > > The abstract may also contain a summary of the problem (I don't
> find
> > > it's necessary in the abstract) and be placed before the text
> above:
> > >
> > > The Internet relies on TCP's congestion control algorithm and saved
> > > it from a major congestion collapse since its adoption. However,
> TCP
> > > is applied on a voluntary base and the bandwidth is fairly shared
> > > among flows instead of users. This is problematic so that ISPs take
> > > simple or advanced policing actions on some sorts of traffic.
> > > However, since congestion on the downstream path of a flow is not
> > > visible, these approaches possibly hit users unnecessarily and are
> > > not effective enough.
> > >
> > >
> > > Regards,
> > >
> > >     Michael
> > >
> > > toby.moncaster@bt.com schrieb:
> > > > Hi Michael,
> > > >
> > > > Thanks for the useful feedback. Clearly this document is still in
> > > > its very early stages. I will try and produce a new version by
> end
> > > > of the week  which will hopefully address some of your comments.
> > > >
> > > > Meanwhile I am still keen to get volunteers willing to contribute
> > >
> > > chunks
> > >
> > > > of text for any of the sections.
> > > >
> > > > Toby
> > > >
> > > >> -----Original Message-----
> > > >> From: Michael Menth [mailto:menth@informatik.uni-wuerzburg.de]
> > > >> Sent: 23 September 2009 22:41
> > > >> To: Moncaster,T,Toby,DER3 R
> > > >> Cc: re-ecn@ietf.org
> > > >> Subject: Re: [re-ECN] preliminary draft of problem statement-
> > >
> > > authors
> > >
> > > >> wanted
> > > >>
> > > >> Hi Toby,
> > > >>
> > > >> I read the whole document and still it is unclear in many parts.
> > > >> I marked them in the attached doc-file. I hope this helps to
> > > >> improve
> > >
> > > its
> > >
> > > >> clarity.
> > > >>
> > > >> Regards,
> > > >>
> > > >>     Michael
> > > >>
> > > >> toby.moncaster@bt.com schrieb:
> > > >>> Hi All,
> > > >>>
> > > >>> As promised here is a new draft of the problem statement with a
> > > >>> bit
> > > >>
> > > >> more meat on the bones. There is still an awful lot of work to
> be
> > >
> > > done
> > >
> > > >> on this and not too much time to do it. Our absolute deadline to
> > > >> get something in is October 19th - only just over 3 weeks
> away...
> > > >>
> > > >>> As before I would welcome any contributions of text or general
> > > >>
> > > >> comments. When I have a bit more time I will do proper xml2rfc
> > >
> > > author
> > >
> > > >> entries for everyone that has contributed... For political
> > > >> reasons I want it to be clear that this is a document that has
> > > >> been worked on from people across the whole range of the IETF
> community.
> > > >>
> > > >>> Toby
> > >
> > >
> ____________________________________________________________________
> > >
> > > >>> Toby Moncaster, Senior Researcher, Network Infrastructure
> > > >>> Practise B54/70 Adastral Park, Ipswich, IP53RE, UK.  +44 7918
> > > >>> 901170
> > > >
> > > > -----------------------------------------------------------------
> -
> > > > ---
> > > >
> > > >> -
> > > >>
> > > >>> --
> > > >>>
> > > >>> _______________________________________________
> > > >>> re-ECN mailing list
> > > >>> re-ECN@ietf.org
> > > >>> https://www.ietf.org/mailman/listinfo/re-ecn
> > > >>
> > > >> --
> > > >> Dr. Michael Menth, Assistant Professor University of Wuerzburg,
> > > >> Institute of Computer Science Am Hubland,
> > >
> > > D-
> > >
> > > >> 97074 Wuerzburg, Germany, room B206
> > > >> phone: (+49)-931/31-86644 (new), fax: (+49)-931/888-6632
> > > >> mailto:menth@informatik.uni-wuerzburg.de
> > > >> http://www3.informatik.uni-wuerzburg.de/research/ngn
> > >
> > > --
> > > Dr. Michael Menth, Assistant Professor University of Wuerzburg,
> > > Institute of Computer Science Am Hubland, D-97074 Wuerzburg,
> > > Germany, room B206
> > > phone: (+49)-931/31-86644 (new), fax: (+49)-931/888-6632
> > > mailto:menth@informatik.uni-wuerzburg.de
> > > http://www3.informatik.uni-wuerzburg.de/research/ngn
> 
> 
> 
> --
> -------------------------------------------------------------------
> Dipl.-Ing. Mirja Kühlewind
> Institute of Communication Networks and Computer Engineering (IKR)
> University of Stuttgart, Germany Pfaffenwaldring 47, D-70569 Stuttgart
> 
> web: www.ikr.uni-stuttgart.de
> email: mirja.kuehlewind@ikr.uni-stuttgart.de
> tel: +49(0)711/685-67973
> -------------------------------------------------------------------