Re: [re-ECN] Complete draft Charter for proposed CONEX WG

<philip.eardley@bt.com> Tue, 08 December 2009 18:40 UTC

Return-Path: <philip.eardley@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 004103A6841 for <re-ecn@core3.amsl.com>; Tue, 8 Dec 2009 10:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.074
X-Spam-Level:
X-Spam-Status: No, score=-3.074 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, J_CHICKENPOX_72=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 Xo6Q+dj9ADFo for <re-ecn@core3.amsl.com>; Tue, 8 Dec 2009 10:40:33 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id F05153A6830 for <re-ecn@ietf.org>; Tue, 8 Dec 2009 10:40:32 -0800 (PST)
Received: from E03MVB1-UKBR.domain1.systemhost.net ([193.113.197.107]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 8 Dec 2009 18:40:20 +0000
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: Tue, 8 Dec 2009 18:36:16 -0000
Message-ID: <4A916DBC72536E419A0BD955EDECEDEC06363B6D@E03MVB1-UKBR.domain1.systemhost.net>
In-Reply-To: <200912081647.29883.mkuehle@ikr.uni-stuttgart.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Complete draft Charter for proposed CONEX WG
Thread-Index: Acp4HcQVIb2V0rD9QEacc0YPb18bPwAF3Y9A
From: <philip.eardley@bt.com>
To: <mirja.kuehlewind@ikr.uni-stuttgart.de>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 08 Dec 2009 18:40:20.0204 (UTC) FILETIME=[E4E122C0:01CA7835]
Subject: Re: [re-ECN] Complete draft Charter for proposed CONEX WG
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, 08 Dec 2009 18:40:34 -0000

Thanks Mirja - both changes work for me
phil

> -----Original Message-----
> From: Mirja Kühlewind [mailto:mirja.kuehlewind@ikr.uni-stuttgart.de] 
> Sent: 08 December 2009 15:47
> To: re-ecn@ietf.org
> Cc: Eardley,PL,Philip,DEE1 R
> Subject: Re: [re-ECN] Complete draft Charter for proposed CONEX WG
> 
> 
> Hi,
> 
> see below
> 
> > The purpose of the CONEX working group is to develop a mechanism to 
> > allow senders to inform the network of the level of congestion they 
> > expect their packets to encounter. This information is 
> currently only 
> > visible at the transport layer.
> I would add the end systems here: "This information is 
> currently only visible 
> at the transport layer in the end systems."
> 
> > With the output of CONEX, it will be
> > possible to provide sufficient information in each IP 
> datagram so that
> > any node in the network can see the expected rest-of-path 
> congestion.
> > Once any node can see the impact it causes (and suffers) by 
> sending or
> > forwarding packets, it will be possible to hold senders and whole
> > networks accountable for the congestion they cause downstream. Tools
> > that exploit the CONEX output could be used for mitigating 
> distributed
> > denial of service (DDoS); simplifying differentiation of quality of
> > service (QoS); policing compliance to congestion control; and so on.
> Maybe change the order here: "Tools that exploit the CONEX 
> output could be 
> used for simplifying differentiation of quality of service 
> (QoS); policing 
> compliance to congestion control; mitigating distributed 
> denial of service 
> (DDoS); and so on."
> 
> BR,
> Mirja
> 
>