Re: [re-ECN] "Is a standard required?"
John Leslie <john@jlc.net> Thu, 29 April 2010 14:37 UTC
Return-Path: <john@jlc.net>
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 B3EB73A6998 for <re-ecn@core3.amsl.com>; Thu, 29 Apr 2010 07:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level:
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=0.701, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
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 6O-k1Z1Uf5L1 for <re-ecn@core3.amsl.com>; Thu, 29 Apr 2010 07:37:47 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id 424FA3A696C for <re-ecn@ietf.org>; Thu, 29 Apr 2010 07:37:47 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 4B28133C2B; Thu, 29 Apr 2010 10:37:33 -0400 (EDT)
Date: Thu, 29 Apr 2010 10:37:33 -0400
From: John Leslie <john@jlc.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-ID: <20100429143733.GI14169@verdi>
References: <20100429102934.GE14169@verdi> <EDC652A26FB23C4EB6384A4584434A04021457E3@307622ANEX5.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04021457E3@307622ANEX5.global.avaya.com>
User-Agent: Mutt/1.4.1i
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 14:37:48 -0000
Romascanu, Dan (Dan) <dromasca@avaya.com> wrote: > [John Leslie wrote:] >> >> 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) True... and WGs are quite properly charged to meet those criteria. > > 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. As we both know, the percentage of RFCs that progress from Proposed to Draft has been minuscule. >> 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. I have no objection to asking such questions (though I have some reservations about posing such questions to only an off-list audience). I meant only to suggest that requiring "satisfactory" answers to questions about deployment before chartering a WG strikes me as a change from historical practice. > The IETF does not have infinite resources, this is something that is > not that new. I well understand that watching WGs drag on for years without producing something "implementable, deployable, and compatible with the existing deployed technology" is discouraging. But I would urge you (and all IESG members) not to insist that it be accomplished _before_ chartering the WG. -- John Leslie <john@jlc.net>
- [re-ECN] New draft Conex charter - for rapid comm… philip.eardley
- Re: [re-ECN] New draft Conex charter - for rapid … Ingemar Johansson S
- Re: [re-ECN] New draft Conex charter - for rapid … Mcdysan, David E
- Re: [re-ECN] New draft Conex charter - for rapid … philip.eardley
- Re: [re-ECN] New draft Conex charter - for rapid … philip.eardley
- Re: [re-ECN] New draft Conex charter - for rapid … ken carlberg
- Re: [re-ECN] New draft Conex charter - for rapid … philip.eardley
- Re: [re-ECN] New draft Conex charter - for rapid … Mirja Kühlewind
- Re: [re-ECN] New draft Conex charter - for rapid … Leslie Daigle
- Re: [re-ECN] New draft Conex charter - for rapid … Mcdysan, David E
- Re: [re-ECN] New draft Conex charter - for rapid … Georgios Karagiannis
- Re: [re-ECN] New draft Conex charter - for rapid … Ingemar Johansson S
- Re: [re-ECN] New draft Conex charter - for rapid … Alissa Cooper
- [re-ECN] FW: New draft Conex charter - for rapid … philip.eardley
- Re: [re-ECN] FW: New draft Conex charter - for ra… ken carlberg
- Re: [re-ECN] FW: New draft Conex charter - for ra… philip.eardley
- Re: [re-ECN] New draft Conex charter - for rapid … philip.eardley
- Re: [re-ECN] FW: New draft Conex charter - for ra… Alissa Cooper
- Re: [re-ECN] FW: New draft Conex charter - for ra… Bob Briscoe
- Re: [re-ECN] FW: New draft Conex charter - for ra… Lars Eggert
- Re: [re-ECN] FW: New draft Conex charter - for ra… John Leslie
- Re: [re-ECN] FW: New draft Conex charter - for ra… philip.eardley
- Re: [re-ECN] FW: New draft Conex charter - for ra… John Leslie
- Re: [re-ECN] FW: New draft Conex charter - for ra… Bob Briscoe
- Re: [re-ECN] FW: New draft Conex charter - for ra… Leslie Daigle
- Re: [re-ECN] FW: New draft Conex charter - for ra… Lars Eggert
- [re-ECN] Conex charter - now in External Review John Leslie
- Re: [re-ECN] Conex charter - now in External Revi… Stewart Bryant
- Re: [re-ECN] Conex charter - now in External Revi… John Leslie
- Re: [re-ECN] Conex charter - now in External Revi… Woundy, Richard
- Re: [re-ECN] Conex charter - now in External Revi… ken carlberg
- Re: [re-ECN] Conex charter - now in External Revi… Woundy, Richard
- Re: [re-ECN] Conex charter - now in External Revi… John Leslie
- Re: [re-ECN] Conex charter - now in External Revi… ken carlberg
- Re: [re-ECN] Conex charter - now in External Revi… Woundy, Richard
- Re: [re-ECN] Conex charter - now in External Revi… Leslie Daigle
- Re: [re-ECN] Conex charter - now in External Revi… David Harrington
- Re: [re-ECN] Conex charter - now in External Revi… Stewart Bryant
- Re: [re-ECN] Conex charter - now in External Revi… Stewart Bryant
- Re: [re-ECN] Conex charter - now in External Revi… ken carlberg
- [re-ECN] "Is a standard required?" John Leslie
- Re: [re-ECN] "Is a standard required?" Romascanu, Dan (Dan)
- Re: [re-ECN] "Is a standard required?" John Leslie
- Re: [re-ECN] Conex charter - now in External Revi… Woundy, Richard
- Re: [re-ECN] Conex charter - now in External Revi… Bob Briscoe
- Re: [re-ECN] Conex charter - now in External Revi… John Leslie
- Re: [re-ECN] Conex charter - now in External Revi… Woundy, Richard
- Re: [re-ECN] Conex charter - now in External Revi… Mcdysan, David E
- Re: [re-ECN] Conex charter - now in External Revi… Leslie Daigle
- Re: [re-ECN] Conex charter - now in External Revi… Kevin Mason