Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis

John C Klensin <john@jck.com> Mon, 23 June 2008 19:59 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 1B9563A69D5; Mon, 23 Jun 2008 12:59:56 -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 81B7C3A69D5; Mon, 23 Jun 2008 12:59:55 -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 0bBT2qwQPsxu; Mon, 23 Jun 2008 12:59:54 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 833353A6948; Mon, 23 Jun 2008 12:59:54 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1KAsCU-0006gW-2m; Mon, 23 Jun 2008 15:59:42 -0400
Date: Mon, 23 Jun 2008 15:59:41 -0400
From: John C Klensin <john@jck.com>
To: Russ Housley <housley@vigilsec.com>, dcrocker@bbiw.net
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
Message-ID: <698F71BEE6ECCFF2C1348D8F@p3.JCK.COM>
In-Reply-To: <20080623195128.419ED3A694C@core3.amsl.com>
References: <8832006D4D21836CBE6DB469@klensin-asus.vbn.inter-touch.net> <485590E2.3080107@gmail.com> <p06250116c47c330c7dd0@[75.145.176.242]> <4856DE3A.3090804@gmail.com> <C122F91B-59B0-49AC-ABBC-6752217C4E47@NOKIA.COM> <20080619024147.9146C3A6938@core3.amsl.com> <485A353B.30403@dcrocker.net> <20080619175645.0CA443A68C2@core3.amsl.com> <485FCAAF.9070808@dcrocker.net> <20080623195128.419ED3A694C@core3.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: ietf@ietf.org, iesg@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-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


--On Monday, 23 June, 2008 14:19 -0400 Russ Housley
<housley@vigilsec.com> wrote:

> Dave:
> 
>>>> If you feel that group was rogue, please explain.  If you
>>>> do not,  what is the basis for your view that its
>>>> considerations were  sufficiently faulty to warrant being
>>>> overridden?
>>> Prior to the appeal, this aspect of John's rationale was not 
>>> raised.  It was not raised by John, the document PROTO
>>> shepherd, or  the IESG member sponsoring the document.
>> 
>> Again, I hope we do not find ourselves in a he said/no he
>> didn't  exchange.  I'll
>> merely suggest that had the Discuss been immediately taken to
>> the  public mailing
>> list, it seems pretty likely that salient details would
>> quickly have been put forward.
> 
> This is an individual submission, not a WG document.  So,
> there is no charter that lists the appropriate mail list for
> such a discussion.  That said, John did take the issue to a
> mail list.  I know this because someone forward his posting to
> me.  John did not CC me on the posting, which I interpret as
> not seeking dialogue at that point.

Russ, that note was sent to the mailing list after I received
your "change the document or appeal" note.   I believed that
note from you closed the door on any further dialogue with you
(or the IESG).  The note to the SMTP list was simply to collect
opinions on which of the two choices you gave me to adopt.

If you intended the "change the document or appeal" note to be
interpreted in any other way, I apologize for not copying you on
the question to the list, but I really could not figure out any
other way to read it (and cannot to this day).

best,
   john


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