Re: Cross-area review (was Meeting rotation)

Dave Crocker <dhc@dcrocker.net> Tue, 22 December 2015 04:53 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE9B1A00D5 for <ietf@ietfa.amsl.com>; Mon, 21 Dec 2015 20:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FrEoNBRv6G8p for <ietf@ietfa.amsl.com>; Mon, 21 Dec 2015 20:52:59 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53F8A1A00CC for <ietf@ietf.org>; Mon, 21 Dec 2015 20:52:59 -0800 (PST)
Received: from [192.168.1.99] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id tBM4quYm007936 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 21 Dec 2015 20:52:57 -0800
Subject: Re: Cross-area review (was Meeting rotation)
To: John C Klensin <john-ietf@jck.com>, Ralph Droms <rdroms.ietf@gmail.com>
References: <CAC8QAcf=yAAGVN35tUCpX38y6_qGstGhK4iYuyhK94LVWrz-+A@mail.gmail.com> <CAHw9_iL+eAFtGHKXVWMHaqi=3mGO9H1CfE4e=yZCekE9UzPR6A@mail.gmail.c om> <E7D065D8-CADC-4A65-8AC7-6ECE9CF63D4F@ecs.soton.ac.uk> <7A7519D5-FD9B-4F4D-A7E5-AC047F684623@netapp.com> <EMEW3|02dedadbe5e65aac9732e9359a7c2dberBHGjK03tjc|ecs.soton.ac.uk|E7D065D8-CADC-4A65-8AC7-6ECE9CF63D4F@ecs.soton.ac.uk> <CAHw9_iKtck6ZSp6ofNFKLRj7-o3_UR42McTNQqsqCXfcduxAeA@mail.gmail.c om> <5674460C.1000107@krsek.cz> <4B81FA54-F79C-42CB-8024-1C653B0C9406@cisco.com> <20151218233645.GG3294@mx2.yitter.info> <56749EA4.6040801@gmail.com> <20151219000743.GH3294@mx2.yitter.info> <5676EBE9.8050304@dcrocker.net> <970B54F5-2422-4588-A95A-63E5144A8D35@gmail.com> <56789BBB.7020709@dcrocker.net> <4AE6DC68FC9B8CA113CBCDFA@JcK-HP8200.jck.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5678D728.2080404@dcrocker.net>
Date: Mon, 21 Dec 2015 20:52:56 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <4AE6DC68FC9B8CA113CBCDFA@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 21 Dec 2015 20:52:58 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/X1CVD1m5byCKiAkXMqwU-WqZBYw>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Dec 2015 04:53:00 -0000

On 12/21/2015 5:59 PM, John C Klensin wrote:
> I'm not certain we are getting to "good enough" quite often
> enough.  Moreover, what was "good enough" when the expectation
> was that people would not deploy Proposed Standards in products,
> at least without understanding that was a risk and treating it
> as such, may not be "good enough" when Proposed Standards are
> not only deployed but the community's attitude seems to be that


This nicely summarizes a common bit of mythology in the IETF.

First it presumes that folk out there in develop-and-deploy land have no 
ability to assess what they are developing and deploying.

Second is that it presumes that there has been some sort of major change 
in the way IETF specs are processed pre- and post- Proposed status 
assignment.

Both are fundamentally wrong.

The IETF is a collaborative community venture, not a grand parental 
oversight commission.  Folk out their in product-land have been able to 
deal with immature, flakey and changing IETF specs productively for more 
than 25 years.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net