[re-ECN] FW: New Version Notification for draft-moncaster-congestion-exposure-problem-01

<toby.moncaster@bt.com> Thu, 15 October 2009 16:09 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 DC27F28C11E for <re-ecn@core3.amsl.com>; Thu, 15 Oct 2009 09:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 U0hUn0f+Unb0 for <re-ecn@core3.amsl.com>; Thu, 15 Oct 2009 09:09:25 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by core3.amsl.com (Postfix) with ESMTP id BCDD328C0FE for <re-ecn@ietf.org>; Thu, 15 Oct 2009 09:09:24 -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); Thu, 15 Oct 2009 17:09:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Thu, 15 Oct 2009 17:08:29 +0100
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70D82E734@E03MVZ1-UKDY.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New Version Notification for draft-moncaster-congestion-exposure-problem-01
Thread-Index: AcpNsJOu/FQOW4lxTzqUkBhD5+YNRAAAAlQA
From: <toby.moncaster@bt.com>
To: <re-ecn@ietf.org>
X-OriginalArrivalTime: 15 Oct 2009 16:09:27.0310 (UTC) FILETIME=[DEA0A2E0:01CA4DB1]
Subject: [re-ECN] FW: New Version Notification for draft-moncaster-congestion-exposure-problem-01
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: Thu, 15 Oct 2009 16:09:26 -0000

As promised a new version of the problem statement. There have been extensive changes in this version trying to take into account comments from a number of people. The structure has changed slightly and I have removed an awful lot of the text about economics. I am possibly tempted to put some of that back in as an appendix but only if people think it actually adds significantly to the problem statement.

Overall I hope this is now clearer at identifying the problem (lack of congestion information) an effect of this problem (ISPs unable to tell which traffic is a problem) and then shows how congestion exposure might be the solution.

One glaring omission is a change log between this and version 00...

I have uploaded the XML version for those of you that use xml2rfc. In theory it should be in the same directory as the txt version. I have included any non-standard references "inline" in the xml which makes it messy but self-contained.

Big gaps still needing work are:

Section 7 on Use Cases. I would like to concentrate on just 1 or 2 here as examples...

Section 9 Security. This should concentrate on direct attacks on congestion exposure (DoS and dishonest declaration).

Section 4 is also a little weak.

I am going to have to concentrate on other things now at least until late next week so any volunteers to take the editing token?

Toby

____________________________________________________________________ 
Toby Moncaster, Senior Researcher, Network Infrastructure Practice
B54/70 Adastral Park, Ipswich, IP53RE, UK.  +44 7918 901170 



-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: 15 October 2009 17:00
To: Moncaster,T,Toby,DEE1 R
Cc: Krug,AL,Louise,DES3 R; menth@informatik.uni-wuerzburg.de; j.araujo@ee.ucl.ac.uk; sblake@extremenetworks.com; richard_woundy@cable.comcast.com
Subject: New Version Notification for draft-moncaster-congestion-exposure-problem-01 


A new version of I-D, draft-moncaster-congestion-exposure-problem-01.txt has been successfuly submitted by T Moncaster and posted to the IETF repository.

Filename:	 draft-moncaster-congestion-exposure-problem
Revision:	 01
Title:		 The Need for Congestion Exposure in the Internet
Creation_date:	 2009-10-15
WG ID:		 Independent Submission
Number_of_pages: 15

Abstract:
The success of the Internet is largely down to the elegant manner in
which it shares capacity amongst all users while avoiding congestion
collapse.  However this relies on the cooperation of all end users to
work efficiently.  Increasingly a small minority of users are able to
grab larger and larger shares of the network leading ISPs to impose
arbitrary controls on traffic.  These controls set ISPs on a direct
collision course with their customers and the regulators.

The root of the problem lies in the fact the ISPs are unable to see
the most important information about the traffic - namely the amount
of congestion that traffic is going to cause in the network.  We
propose congestion exposure as a possible solution.  Every packet
will carry an accurate prediction of the congestion it expects to
cause downstream.  This memo sets out the motivations for congestion
exposure and introduces a strawman protocol designed to achieve
congestion exposure.
                                                                                  


The IETF Secretariat.