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

John C Klensin <john-ietf@jck.com> Sat, 09 August 2008 19:58 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 EAAC73A683E; Sat, 9 Aug 2008 12:58:07 -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 C6A693A63D3 for <ietf@core3.amsl.com>; Sat, 9 Aug 2008 12:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 FA7WyoZXvvll for <ietf@core3.amsl.com>; Sat, 9 Aug 2008 12:58:06 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id DEEA33A683E for <ietf@ietf.org>; Sat, 9 Aug 2008 12:58:05 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1KRuZg-000EL1-EV; Sat, 09 Aug 2008 15:58:04 -0400
Date: Sat, 09 Aug 2008 15:58:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Bert Wijnen \\(IETF\\)" <bertietf@bwijnen.net>, dcrocker@bbiw.net
Subject: Re: Call for review of proposed update to ID-Checklist
Message-ID: <EFB863C6392FD44E6F24541C@p3.JCK.COM>
In-Reply-To: <0CDF1105EE0F431B9B8D0D6B8D9AFC7A@BertLaptop>
References: <97789FA162BD4EEA9E668BD21E372BAD@BertLaptop> <489DC3E0.3000202@dcrocker.net> <46FE4022D7A994D15EA0F360@p3.JCK.COM> <0CDF1105EE0F431B9B8D0D6B8D9AFC7A@BertLaptop>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


--On Saturday, 09 August, 2008 20:52 +0200 "Bert Wijnen
\\(IETF\\)" <bertietf@bwijnen.net> wrote:

> John and Dave,
> 
> 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 aredescribed
> in formally approved BCP documents.
> 
> The ID-Checklist is intended (or at least that is how it
> started, and as far
> as I am concerned that is still the intention) to help in a
> few areas:

Bert,

We are in complete and utter agreement with each other about the
appropriate role of the ID_Checklist.  For better or worse, the
IESG apparently does not agree, as evidenced most recently in
their response to my appeal about turning a suggestion from the
original version of the Checklist into a firm rule without
having that explicitly confirmed by the community.

We also agree that revising the Checklist into a document that
is suitable for use as part of a package of firm rules is a
rather different job than updating it while being consistent
with its original purpose.

So I withdraw my suggestion and comments but strongly suggest
that you make sure that your intentions for the document and
those of the IESG are in synch before proceeding much further.

regards,
    john

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf