[re-ECN] VIability issue #2
Leslie Daigle <leslie@thinkingcat.com> Thu, 05 November 2009 06:06 UTC
Return-Path: <leslie@thinkingcat.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 76E003A6951 for <re-ecn@core3.amsl.com>;
Wed, 4 Nov 2009 22:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599]
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 VY+zR1-D1yFB for
<re-ecn@core3.amsl.com>; Wed, 4 Nov 2009 22:06:35 -0800 (PST)
Received: from zeke.ecotroph.net (zeke.ecotroph.net [70.164.19.155]) by
core3.amsl.com (Postfix) with ESMTP id AE65C3A6781 for <re-ecn@ietf.org>;
Wed, 4 Nov 2009 22:06:35 -0800 (PST)
Received: from beethoven.local ([::ffff:72.254.105.208]) (AUTH: PLAIN leslie,
SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp;
Thu, 05 Nov 2009 01:06:55 -0500 id 015B0093.4AF26B7F.00002C88
Message-ID: <4AF26B76.7090308@thinkingcat.com>
Date: Thu, 05 Nov 2009 01:06:46 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: re-ecn@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [re-ECN] VIability issue #2
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 06:06:36 -0000
[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 #2
The expectation is that congestion exposure information will be carried
in IP packet headers. Is there really enough room to do that
effectively (in IPv4)?
For discussion:
This assumes tight timing -- that feedback is received and acted upon
such that subsequent flows will experience the same or similar network
state. What are the implications (or likelihood) of different paths?
Or, are there other network state changes that will (could) change in
that timeframe (now or in future developments).
Leslie.
--
-------------------------------------------------------------------
"Reality:
Yours to discover."
-- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------
- [re-ECN] VIability issue #2 Leslie Daigle
- Re: [re-ECN] VIability issue #2 toby.moncaster
- Re: [re-ECN] VIability issue #2 João Taveira Araújo
- Re: [re-ECN] VIability issue #2 HeinerHummel
- Re: [re-ECN] VIability issue #2 toby.moncaster
- Re: [re-ECN] VIability issue #2 HeinerHummel
- Re: [re-ECN] VIability issue #2 HeinerHummel
- Re: [re-ECN] VIability issue #2 Tom Taylor
- Re: [re-ECN] VIability issue #2 John Leslie
- Re: [re-ECN] VIability issue #2 HeinerHummel
- Re: [re-ECN] VIability issue #2 Woundy, Richard
- Re: [re-ECN] VIability issue #2 toby.moncaster