Re: [re-ECN] Viability issue #3

<toby.moncaster@bt.com> Thu, 05 November 2009 12:51 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 BB5CB3A6AB6 for <re-ecn@core3.amsl.com>; Thu, 5 Nov 2009 04:51:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.263
X-Spam-Level:
X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=0.336, 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 GuZlQl9u4nx5 for <re-ecn@core3.amsl.com>; Thu, 5 Nov 2009 04:51:41 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id BFAB03A68D1 for <re-ecn@ietf.org>; Thu, 5 Nov 2009 04:51:40 -0800 (PST)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.61]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 5 Nov 2009 12:51:59 +0000
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: Thu, 5 Nov 2009 12:50:53 -0000
Message-ID: <AEDCAF87EEC94F49BA92EBDD49854CC70DCB16FD@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <4AF26B98.5040005@thinkingcat.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Viability issue #3
Thread-Index: Acpd3kQ3iUq14mRsRR+8k6gcx+UgTAAN+4yA
References: <4AF26B98.5040005@thinkingcat.com>
From: <toby.moncaster@bt.com>
To: <leslie@thinkingcat.com>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 05 Nov 2009 12:51:59.0122 (UTC) FILETIME=[C33B5F20:01CA5E16]
Subject: Re: [re-ECN] Viability issue #3
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, 05 Nov 2009 12:51:41 -0000

> -----Original Message-----
> From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On
> Behalf Of Leslie Daigle
> Sent: 05 November 2009 06:07
> To: re-ecn@ietf.org
> Subject: [re-ECN] Viability issue #3
> 
> 
> [This attempts to outline an issue that could be perceived as
> challenging the viability of congestion exposure work.  The goal is to
> capture the issue, as well as itemize reasonable supporting arguments
> (for viability) and remaining questions to be addressed.  Please
> respond
> with suggestions as needed for each section.  ]
> 
> Viability Issue #3
> 
> Does this scale to the whole Internet?

Yes... It just may not give the same degree of accuracy everywhere

> 
> Suggested:
> 
> 1/ Discussions of working with ECN-enabled and non-ECN enabled routers
> begins to address this.

WE will need to do a proper survey of ECN-readiness. Arguably responding
to drop coming from a RED queue should give very similar results, it
just doesn't allow intermediate nodes to work out the downstream
congestion (and we need to set out the full implications of that)

> 
> 
> Questions:
> 
> 2/ Are there any issues with scale (processing, state) in core
routers?

I hope not as in general it is only border devices that are expected to
change in response to this (aside from any issues of ECN-capability).

> 
> 
> Leslie.
> 
> --
> 
> -------------------------------------------------------------------
> "Reality:
>       Yours to discover."
>                                  -- ThinkingCat
> Leslie Daigle
> leslie@thinkingcat.com
> -------------------------------------------------------------------
> _______________________________________________
> re-ECN mailing list
> re-ECN@ietf.org
> https://www.ietf.org/mailman/listinfo/re-ecn