Re: [re-ECN] preliminary draft of problem statement- authors wanted
Bob Briscoe <rbriscoe@jungle.bt.co.uk> Tue, 29 September 2009 01:21 UTC
Return-Path: <rbriscoe@jungle.bt.co.uk>
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 0E93C3A68B0 for <re-ecn@core3.amsl.com>;
Mon, 28 Sep 2009 18:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.583
X-Spam-Level:
X-Spam-Status: No, score=-1.583 tagged_above=-999 required=5 tests=[AWL=-0.066,
BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, 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 edE65bBNEkup for
<re-ecn@core3.amsl.com>; Mon, 28 Sep 2009 18:21:30 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by
core3.amsl.com (Postfix) with ESMTP id 2A7BC3A6809 for <re-ecn@ietf.org>;
Mon, 28 Sep 2009 18:21:29 -0700 (PDT)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 29 Sep 2009 02:22:48 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 29 Sep 2009 02:22:35 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399);
id 1254187354640; Tue, 29 Sep 2009 02:22:34 +0100
Received: from MUT.jungle.bt.co.uk ([10.73.192.22]) by
bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id n8T1MT6X032489;
Tue, 29 Sep 2009 02:22:29 +0100
Message-Id: <200909290122.n8T1MT6X032489@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 29 Sep 2009 02:22:28 +0100
To: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <200909241327.43568.mirja.kuehlewind@ikr.uni-stuttgart.de>
References: <AEDCAF87EEC94F49BA92EBDD49854CC70D1D1EE6@E03MVZ1-UKDY.domain1.systemhost.net>
<4ABA95EB.7090907@informatik.uni-wuerzburg.de>
<AEDCAF87EEC94F49BA92EBDD49854CC70D3160B4@E03MVZ1-UKDY.domain1.systemhost.net>
<200909241327.43568.mirja.kuehlewind@ikr.uni-stuttgart.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 29 Sep 2009 01:22:35.0743 (UTC)
FILETIME=[5373DEF0:01CA40A3]
Cc: re-ecn@ietf.org
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: Tue, 29 Sep 2009 01:21:36 -0000
Mirja, Going back to you posting in this thread a few days ago... The last sentence said, "...implicit[ly] controls a fair capacity sharing" Certainly, I wear out my keyboard telling people that flow rate equality shouldn't be called fairness at all. But we need to avoid implying we have the one and only definition of fair capacity sharing in its place. "...provides a metric that can be used to share capacity under a range of fairness policies likely to be needed in production networks." Bob At 12:27 24/09/2009, Mirja Kuehlewind wrote: >Hi Toby, > >I've tried to fill section 5.3 (see below). I've moved some points form 4. >(Requirements for a Solution) into this section. So I'm not sure if 4. is >still an own section. Might be enough to include on paragraph into the >introduction. >I hope this input helps somehow as a starting point for 5.3 or if this is not >what was meant to be there it may be included in some other part on the >document. > >Mirja > > >----------------------------------------- >5.3. Re-feedback as a potential solution > >To eliminate the asymmetry of information between end-points and network >components it can be supposed to re-insert the congestion feedback signaled >by the receiver into the Internet. Thereby an approximation about how much >congestion needs to be expected over the whole path is given. Having this >information within the network the congestion policing can be enforced before >other users get discriminated by "heavy users". > >Considering the ECN information as the downstream congestion and the >re-feedbacked congestion information as whole-path congestion, the upstream >congestion (or rest-path congestion) can easily be achieved by subtracting >one form the other. That enables network components to be responsive to >congestion instead just rely on the end-hosts. > >The upstream congestion reveals valuable information at ISP borders. On the >one hand the amount of congestion that will be pushed into a domain can >become part of an inter-domain agreement. One the other hand the amount of >the expected upstream congestion might lead to switch to a less congestion >network-domain (what might boost the competition to provide a more reliable >network). > >Summing up, the exposure of downstream, upstream >and the whole-path congestion >can be achieved by re-insertion of congestion notifications and will >establish an information symmetry between users and network providers. This >will open a door for incremental deployment and an evolution to new >congestion responses which are not bounded anymore to an "universal rate >adaptable policy" as the information equilibrium implicit controls a fair >capacity sharing. > > >On Thursday 24 September 2009 10:04:03 toby.moncaster@bt.com wrote: > > 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 > > > > _______________________________________________ > > re-ECN mailing list > > re-ECN@ietf.org > > https://www.ietf.org/mailman/listinfo/re-ecn > > > >-- >------------------------------------------------------------------- >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 >------------------------------------------------------------------- >_______________________________________________ >re-ECN mailing list >re-ECN@ietf.org >https://www.ietf.org/mailman/listinfo/re-ecn ________________________________________________________________ Bob Briscoe, BT Innovate & Design
- [re-ECN] preliminary draft of problem statement- … toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Woundy, Richard
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… João Taveira Araújo
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Mirja Kuehlewind
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Michael Menth
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Mirja Kuehlewind
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Mirja Kuehlewind
- Re: [re-ECN] preliminary draft of problem stateme… Woundy, Richard
- Re: [re-ECN] preliminary draft of problem stateme… Michael Menth
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Matthew Ford
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Woundy, Richard
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Tom Taylor
- Re: [re-ECN] preliminary draft of problem stateme… Mirja Kuehlewind
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Bob Briscoe
- Re: [re-ECN] preliminary draft of problem stateme… Bob Briscoe
- Re: [re-ECN] preliminary draft of problem stateme… Ingemar Johansson S
- Re: [re-ECN] preliminary draft of problem stateme… toby.moncaster
- Re: [re-ECN] preliminary draft of problem stateme… Michael Menth
- Re: [re-ECN] preliminary draft of problem stateme… philip.eardley