Re: [re-ECN] "Is a standard required?"

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 29 April 2010 10:53 UTC

Return-Path: <dromasca@avaya.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 609C63A6C66 for <re-ecn@core3.amsl.com>; Thu, 29 Apr 2010 03:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level:
X-Spam-Status: No, score=-2.089 tagged_above=-999 required=5 tests=[AWL=0.510, 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 B7+qwl5Jc8+B for <re-ecn@core3.amsl.com>; Thu, 29 Apr 2010 03:53:09 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 9A07D3A6C59 for <re-ecn@ietf.org>; Thu, 29 Apr 2010 03:53:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,294,1270440000"; d="scan'208";a="13700599"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 29 Apr 2010 06:52:54 -0400
X-IronPort-AV: E=Sophos;i="4.52,294,1270440000"; d="scan'208";a="468846031"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Apr 2010 06:52:53 -0400
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, 29 Apr 2010 12:52:38 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04021457E3@307622ANEX5.global.avaya.com>
In-Reply-To: <20100429102934.GE14169@verdi>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] "Is a standard required?"
Thread-Index: AcrnhuIYu0XHI3rRQz2wcN0ILPuKnAAAeEkw
References: <4BD6F2DD.3040202@cisco.com><EE00404438E9444D90AEA84210DC4067A3740C@pacdcexcmb05.cable.comcast.com><046e01cae754$bb3bd490$0600a8c0@china.huawei.com><4BD94573.6060007@cisco.com> <20100429102934.GE14169@verdi>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: John Leslie <john@jlc.net>, Stewart Bryant <stbryant@cisco.com>
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] "Is a standard required?"
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, 29 Apr 2010 10:53:10 -0000

 

> -----Original Message-----
> From: re-ecn-bounces@ietf.org 
> [mailto:re-ecn-bounces@ietf.org] On Behalf Of John Leslie

> 
>    Instead, we define standards so that customers can ask 
> their vendors for a feature which is well-enough-defined to 
> be implemented by the vendors with a high probability that it 
> will interoperate.

Yes (but this is not the only condition - that feature should also be in
answer to a real functional need or operational problem in the Internet,
and the solution should be implementable, deployable, and compatible
with the existing deployed technology) 

> It's quite normal for us to design standards that never see 
> implementation by multiple vendors.
> 

Is this true? Beyond going into the discussion of what is 'normal' I
would observe that an RFC that cannot prove the existence of two
independent implementations cannot be advanced from Proposed to Draft. 

>    I can understand how you might see that as wasteful and 
> want to change it, but I seriously advise that new IESG 
> members _not_ set out to change the way IETF operates.
> 

I do not think that the new IESG members are asking questions that were
not asked before. The IETF does not have infinite resources, this is
something that is not that new. 

Dan