Re: Call for review of proposed update to ID-Checklist

Dave Crocker <dhc2@dcrocker.net> Sun, 10 August 2008 15:38 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9C833A6953; Sun, 10 Aug 2008 08:38:13 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E57653A6953 for <ietf@core3.amsl.com>; Sun, 10 Aug 2008 08:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11]
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 X7kc1GlLrGRg for <ietf@core3.amsl.com>; Sun, 10 Aug 2008 08:38:12 -0700 (PDT)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id 57FF53A6879 for <ietf@ietf.org>; Sun, 10 Aug 2008 08:38:09 -0700 (PDT)
Received: from [192.168.0.3] (adsl-67-127-53-187.dsl.pltn13.pacbell.net [67.127.53.187]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id m7AFc546027733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Aug 2008 08:38:06 -0700
Message-ID: <489F0B5D.5070406@dcrocker.net>
Date: Sun, 10 Aug 2008 08:38:05 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Subject: Re: Call for review of proposed update to ID-Checklist
References: <97789FA162BD4EEA9E668BD21E372BAD@BertLaptop> <489DC3E0.3000202@dcrocker.net> <46FE4022D7A994D15EA0F360@p3.JCK.COM> <0CDF1105EE0F431B9B8D0D6B8D9AFC7A@BertLaptop>
In-Reply-To: <0CDF1105EE0F431B9B8D0D6B8D9AFC7A@BertLaptop>
X-Virus-Scanned: ClamAV 0.92/7999/Sun Aug 10 04:05:47 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 10 Aug 2008 08:38:06 -0700 (PDT)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


Bert Wijnen (IETF) wrote:
> I think that both of you (and some others) arwe looking at the ID_Checklist
> too much as if it is part of our (rigid) process. Our processes 
> are described in formally approved BCP documents.


Bert,

I am trying to distinguish between what the Checklist "is intended to be" from 
the competing views of what it actually is, as discussed in this thread 8-11 
July.  That thread made clear that a variety of serious and thoughtful people 
have very different views on the actuality.

This sort of debate is never resolved by abstract exchanges. It needs hard data.

I think your previous note correctly listed what the document was (and probably 
is) *intended* to be.  I think the thread made clear there is a strong case that 
the document has become more than that. I think it also made clear that the 
basis for its becoming more is fuzzy.

So my suggestion is not seeking to directly resolve the matter, but rather to 
provide a tool for discussion.  Simply put, it adds an audit trail to the 
document's content that should help folks by providing some relatively objective 
information that makes clear what is and is not based on rules defined elsewhere.

Hence, I am hoping that detailed attention to John's note following-up my own 
suggestion comes later, since I read it as possibly seeking to resolve things 
directly. More probably, he was merely trying to help make the case for why the 
document needs substantiation of its particulars.

I suggested that you perform the audit exercise partly because you are the one 
modifying the document and partly because you are friendly to the document's 
current form.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf