[re-ECN] Viability issue #1

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 19BB53A6951 for <re-ecn@core3.amsl.com>; Wed, 4 Nov 2009 22:06:04 -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=[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 gsMU8cAc06zl for <re-ecn@core3.amsl.com>; Wed, 4 Nov 2009 22:06:03 -0800 (PST)
Received: from zeke.ecotroph.net (zeke.ecotroph.net [70.164.19.155]) by core3.amsl.com (Postfix) with ESMTP id 5F6D63A679C for <re-ecn@ietf.org>; Wed, 4 Nov 2009 22:06:03 -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:24 -0500 id 015B0094.4AF26B60.00002C19
Message-ID: <4AF26B57.3030601@thinkingcat.com>
Date: Thu, 05 Nov 2009 01:06:15 -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 #1
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:04 -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 #1

What are the points in favour of/against congestion exposure as an 
architecturally sound technique to specify for the Internet?  (NB -- 
this is about congestion exposure, as constrained in the agreed 
principles, not any particular proposal)?

Suggested:

1/ This is about network flows, not applications or services, so it will 
serve future network uses (application types).

2/ Congestion exposure provides mechanisms to declare awareness of 
whole-path congestion WITHOUT prescribing behaviours.

3/ This is also network agnostic in the sense that no pre-existing 
agreements or interpretations need be in place to make the congestion 
exposure work.  (*Accounting* for it is a separate matter, but that's okay).


Questions:

4/ To what extent is this dependent on an assumed network architecture 
where the major sources of content (and congestion) traverse transit 
networks, as opposed to being CDNs connected directly to access networks 
(for business purposes)?



-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
leslie@thinkingcat.com
-------------------------------------------------------------------