Re: [re-ECN] Conex charter - now in External Review

Stewart Bryant <stbryant@cisco.com> Thu, 29 April 2010 08:39 UTC

Return-Path: <stbryant@cisco.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 4693028C22C for <re-ecn@core3.amsl.com>; Thu, 29 Apr 2010 01:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.442
X-Spam-Level:
X-Spam-Status: No, score=-10.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 SRCG+4QKb0xa for <re-ecn@core3.amsl.com>; Thu, 29 Apr 2010 01:39:02 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 2CC6028C231 for <re-ecn@ietf.org>; Thu, 29 Apr 2010 01:38:30 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAILi2EtAZnwN/2dsb2JhbACdC3GiVIFhCwGYLYUQBA
X-IronPort-AV: E=Sophos;i="4.52,294,1270425600"; d="scan'208";a="106355667"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 29 Apr 2010 08:38:16 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o3T8cFRq029755; Thu, 29 Apr 2010 08:38:15 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id o3T8cB627686; Thu, 29 Apr 2010 09:38:12 +0100 (BST)
Message-ID: <4BD94573.6060007@cisco.com>
Date: Thu, 29 Apr 2010 09:38:11 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <4BD6F2DD.3040202@cisco.com> <20100427151601.GF16203@verdi><EE00404438E9444D90AEA84210DC406793D9DB@pacdcexcmb05.cable.comcast.com><A8B8C5AF-37C2-4DD6-BDDB-760FC616BE8F@g11.org.uk><EE00404438E9444D90AEA84210DC406793DC75@pacdcexcmb05.cable.comcast.com><20100428152122.GB14169@verdi><68FC2CFB-2F16-4B2C-8DA8-D8EED6DC81FC@g11.org.uk> <EE00404438E9444D90AEA84210DC4067A3740C@pacdcexcmb05.cable.comcast.com> <046e01cae754$bb3bd490$0600a8c0@china.huawei.com>
In-Reply-To: <046e01cae754$bb3bd490$0600a8c0@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "'Woundy, Richard'" <Richard_Woundy@cable.comcast.com>, re-ecn@ietf.org
Subject: Re: [re-ECN] Conex charter - now in External Review
X-BeenThere: re-ecn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
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, 29 Apr 2010 08:39:03 -0000

> I think the biggest questions regarding CONEX so far are:
> "Is this at the point where standardization is required, or is this
> research?"
> "Is a standard required because there are multiple vendors getting
> demand from multiple operators for this type of solution to the stated
> problem?"
>    
These are the key questions that initiated the search for additional 
information during the review.

Normally you do not need standards unless you are going to get 
multi-vendor deployments in live networks - hence my questions to the 
list about who was likely to deploy and in which type of network.

I am not for a moment suggesting that the IxTF should not do the IPv6 
experimental demonstration of the use of the technology,  but the 
question arose as to whether we needed an IETF  WG to do that.

If there are  IANA policy issues associated with the IPv6 codepoints 
needed to run the experiment, we can run a much lighter weight process 
to get experimental codepoints than to set up and manage a WG.

If the experimentally work (which can run a lot faster without the 
overhead of standardization) demonstrates that CONEX technology is an 
economic benefit to providers, or to the owners of enterprise networks, 
re-running the BOF to set up a WG and create a standard will be pushing 
on an open door.

- Stewart