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

Dave Crocker <dhc2@dcrocker.net> Thu, 26 June 2008 09:46 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 0B58F28C136; Thu, 26 Jun 2008 02:46:52 -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 69DD928C138; Thu, 26 Jun 2008 02:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_FUTURE_06_12=1.897]
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 EOQKNXgCMGZc; Thu, 26 Jun 2008 02:46:49 -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 41EB628C108; Thu, 26 Jun 2008 02:46:48 -0700 (PDT)
Received: from [192.168.0.3] (adsl-67-127-53-97.dsl.pltn13.pacbell.net [67.127.53.97]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id m5ND7KR0025137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jun 2008 06:07:25 -0700
Message-ID: <486002D3.9030900@dcrocker.net>
Date: Mon, 23 Jun 2008 13:08:51 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
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> <200806231250.m5NCnuGh024638@sbh17.songbird.com>
In-Reply-To: <200806231250.m5NCnuGh024638@sbh17.songbird.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 23 Jun 2008 06:07:25 -0700 (PDT)
Cc: ietf@ietf.org, iesg@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-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


Russ Housley wrote:
> 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.


Hmmm...

Only because it got shot down so quickly and soundly, I'll indulge in some sour 
grapes:  Once upon a time, I suggested that all I-D's be required to specify a 
discussion venue.

What we have here, now, is an example of why that should be a requirement: An 
I-D is for the purpose of discussion. We need to facilitate it's happening.

For rfc2821bis, there was, in fact, an established discussion venue, and it 
long-standing and quite well known to the email community, namely 
ietf-smtp@imc.org.

It could only have helped for that venue to have been known to others, 
particularly if folks wanted to pursue a "community" discussion about a concern 
with the draft.

And especially since rfc2821bis development was, in fact, pursued with exactly 
the same rough consensus process a formally-chartered chartered working group.

But your last sentence probably highlights a basic structural disconnect -- for 
want of a better term -- that we ought to think about fixing:  when an 
individual submission is actually the result of a group process, the group ought 
to be identified and direct dialogue with the group ought to take place, not 
depending upon mediation by an author or proto-shepherd.

d/

-- 

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