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

Russ Housley <housley@vigilsec.com> Mon, 23 June 2008 19:51 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 584183A6991; Mon, 23 Jun 2008 12:51:30 -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 3EECB3A69E1 for <ietf@core3.amsl.com>; Mon, 23 Jun 2008 12:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.682
X-Spam-Level:
X-Spam-Status: No, score=-100.682 tagged_above=-999 required=5 tests=[AWL=1.917, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 l5JD-a9PqQ6S for <ietf@core3.amsl.com>; Mon, 23 Jun 2008 12:51:28 -0700 (PDT)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 419ED3A694C for <ietf@ietf.org>; Mon, 23 Jun 2008 12:51:28 -0700 (PDT)
Received: (qmail 9705 invoked by uid 0); 23 Jun 2008 19:51:20 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (72.66.14.12) by woodstock.binhost.com with SMTP; 23 Jun 2008 19:51:20 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Jun 2008 14:19:26 -0400
To: dcrocker@bbiw.net
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
In-Reply-To: <485FCAAF.9070808@dcrocker.net>
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>
Mime-Version: 1.0
Message-Id: <20080623195128.419ED3A694C@core3.amsl.com>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

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 

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