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

<toby.moncaster@bt.com> Mon, 26 October 2009 19:11 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 6DABE3A697C for <re-ecn@core3.amsl.com>; Mon, 26 Oct 2009 12:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level:
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=-0.225, 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 V6C1b25XRQCq for <re-ecn@core3.amsl.com>; Mon, 26 Oct 2009 12:11:30 -0700 (PDT)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by core3.amsl.com (Postfix) with ESMTP id 6254C3A68C9 for <re-ecn@ietf.org>; Mon, 26 Oct 2009 12:11:30 -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); Mon, 26 Oct 2009 19:11:41 +0000
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: Mon, 26 Oct 2009 19:11:38 -0000
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70DAA28D0@E03MVZ1-UKDY.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New Version Notification for draft-moncaster-congestion-exposure-problem-03
Thread-Index: AcpWb8t7Ruu1UvwoTGi+MTEE9pxeCQAAAWFw
From: <toby.moncaster@bt.com>
To: <re-ecn@ietf.org>
X-OriginalArrivalTime: 26 Oct 2009 19:11:41.0090 (UTC) FILETIME=[26365020:01CA5670]
Subject: [re-ECN] FW: New Version Notification for draft-moncaster-congestion-exposure-problem-03
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, 26 Oct 2009 19:11:31 -0000

A new version. The main changes are:
* an altered abstract (trying to roughly follow suggestions from John Leslie but with modification - note this still needs work!)
* An improved security considerations section
* The start of a proper Use Cases section

I now I still have comments from a couple of people that will need addressing but I needed to get this submitted before the deadline...

Toby

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: 26 October 2009 19:09
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-03 


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

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

Abstract:
Today's Internet is a product of its history.  TCP is the main
transport protocol responsible for sharing out bandwidth and
preventing a recurrence of congestion collapse while packet drop is
the primary signal of congestion at bottlenecks.  Since packet drop
(and increased delay) impacts all their customers negatively, network
operators would like to be able to distinguish between overly
aggressive congestion control and a confluence of many low-bandwidth,
low-impact flows.  But they are unable to see the actual congestion
signal and thus, they have to implement bandwidth and/or usage limits
based on the only information they can see or measure (the contents
of the packet headers and the rate of the traffic).  Such measures
don't solve the packet-drop problems effectively and are leading to
calls for government regulation (which also won't solve the problem).

We propose congestion exposure as a possible solution.  This allows
packets to carry an accurate prediction of the congestion they expect
to cause downstream thus allowing it to be visible to ISPs and
network operators.  This memo sets out the motivations for congestion
exposure and introduces a strawman protocol designed to achieve
congestion exposure.
                                                                                  


The IETF Secretariat.