Re: [re-ECN] Expired re-ECN Internet Drafts
<toby.moncaster@bt.com> Tue, 22 September 2009 09:25 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 28F5B3A67A8 for <re-ecn@core3.amsl.com>;
Tue, 22 Sep 2009 02:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.214
X-Spam-Level:
X-Spam-Status: No, score=-3.214 tagged_above=-999 required=5 tests=[AWL=0.385,
BAYES_00=-2.599, 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 3kzZhSatKBdM for
<re-ecn@core3.amsl.com>; Tue, 22 Sep 2009 02:25:07 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by
core3.amsl.com (Postfix) with ESMTP id 1CBB93A68C4 for <re-ecn@ietf.org>;
Tue, 22 Sep 2009 02:25:06 -0700 (PDT)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.64]) by
smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 22 Sep 2009 10:26:09 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Sep 2009 10:25:17 +0100
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70D26259B@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <C9BB98B434D19544A9D39022083A558E04F2B0EC@E03MVB1-UKBR.domain1.systemhost.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Expired re-ECN Internet Drafts
Thread-Index: Aco4W+DlG398Nb7JTW29xVpJ1GbPGgDChu8w
References: <C9BB98B434D19544A9D39022083A558E04F2B0EC@E03MVB1-UKBR.domain1.systemhost.net>
From: <toby.moncaster@bt.com>
To: <alan.p.smith@bt.com>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 22 Sep 2009 09:26:09.0161 (UTC)
FILETIME=[B7E7DF90:01CA3B66]
Subject: Re: [re-ECN] Expired re-ECN Internet Drafts
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, 22 Sep 2009 09:25:08 -0000
Out of interest could people let the list know if they have tried to read either of these documents and if so whether they found them intelligible or not? In particular I am looking for feedback on the protocol document which I suspect has become almost impenetrably dense over the past 8 revisions by 4 different people... If people are struggling it may be worth releasing a lightweight overview of the protocol before the BoF for non-experts to have a starting point... Toby > -----Original Message----- > From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On > Behalf Of alan.p.smith@bt.com > Sent: 18 September 2009 13:31 > To: re-ecn@ietf.org > Subject: [re-ECN] Expired re-ECN Internet Drafts > > There are 2 Internet Drafts for re-ECN, which have recently expired. > These are a description of the protocol: > http://tools.ietf.org/html/draft-briscoe-tsvwg-re-ecn-tcp-07 and one > described as a "motivation" for re-ECN: > http://tools.ietf.org/html/draft-briscoe-tsvwg-re-ecn-tcp-motivation-00 > which is actually more of an architecture for re-ECN or a framework for > using the protocol. > > These 2 documents do need a re-write. I would hope that if the BOF goes > ahead then members of the community would want to shape these new > documents, be they direct replacements or entirely new documents. At > the > very least we need a draft that properly documents the motivation for > congestion awareness. > > In the meantime the expired drafts can be updated only as a keep-alive. > I would like to take the opportunity to re-name the motivation to > something more accurate, so propose renaming it to "A Framework for > adding Congestion Accountability to TCP/IP". > > Is there anyone who wants to contribute to new documents? It could be > with providing content, editing, scoping, etc. > > Alan > > _______________________________________________ > re-ECN mailing list > re-ECN@ietf.org > https://www.ietf.org/mailman/listinfo/re-ecn
- [re-ECN] Expired re-ECN Internet Drafts alan.p.smith
- Re: [re-ECN] Expired re-ECN Internet Drafts toby.moncaster
- Re: [re-ECN] Expired re-ECN Internet Drafts Ingemar Johansson S
- Re: [re-ECN] Expired re-ECN Internet Drafts Mirja Kuehlewind