Re: draft-klensin-rfc2821bis-10: ABNF discuss

John C Klensin <john+smtp@jck.com> Tue, 08 July 2008 22:15 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m68MFJeP091342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Jul 2008 15:15:19 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m68MFJCv091341; Tue, 8 Jul 2008 15:15:19 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m68MFGhB091333 for <ietf-smtp@imc.org>; Tue, 8 Jul 2008 15:15:17 -0700 (MST) (envelope-from john+smtp@jck.com)
Received: by core3.amsl.com (Postfix, from userid 0) id 213FF28C37C; Tue, 8 Jul 2008 15:15:04 -0700 (PDT)
X-Original-To: iesg@core3.amsl.com
Delivered-To: iesg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D06A3A690C for <iesg@core3.amsl.com>; Thu, 3 Jul 2008 12:12:33 -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 a2PP1U1sXnWD for <iesg@core3.amsl.com>; Thu, 3 Jul 2008 12:12:32 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 633A23A6774 for <iesg@ietf.org>; Thu, 3 Jul 2008 12:12:32 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1KEUEP-0008xO-TN; Thu, 03 Jul 2008 15:12:38 -0400
Date: Thu, 03 Jul 2008 15:12:37 -0400
From: John C Klensin <john+smtp@jck.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
cc: ietf-smtp@imc.org, IESG <iesg@ietf.org>
Subject: Re: draft-klensin-rfc2821bis-10: ABNF discuss
Message-ID: <1CE1E244C179B83FC705AB8C@p3.JCK.COM>
In-Reply-To: <486D1D5D.7010201@ericsson.com>
References: <4869EB38.4010106@ericsson.com> <5F1B835C0E2B6CC3133CC589@p3.JCK.COM> <486D1D5D.7010201@ericsson.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

--On Thursday, 03 July, 2008 20:41 +0200 Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:

>> The "not discussed at all" issue is one that could open up yet
>> another whole discussion of the information the tracker gives
>> to authors, editors, mailing lists, etc., and just what the
>> expectations are of both IESG members and document shepherds.
>> Since those topics are probably as controversial as the ones
>> associated with the pending appeal, I'm going to try to avoid
>> them here and hope that, if people do want to raise them, they
>> will at least change the subject line.
> 
> I only tried to express that if one tries to resolve a discuss
> one needs
> to involve the Discuss holding AD somehow. And I have
> personally not
> heard a single beep from anyone until a week ago about this
> part of the discuss.

Understood.

Part of the problem here is similar to one that the RFC Editor
discovered and fixed some years ago. 

Because "DISCUSS" can mean, among other things:

	* I want to think about this for a while
	
	* I want to discuss it with other IESG members and find
	out what they think
	
	* I am expecting further input from the developers of
	the document

it is a little bit too easy for the third case to get lost.  It
obviously did in this case, for which I apologize.  On the other
hand, it would be, IMO, very helpful if the IESG cleaned that
situation up.

I'll let others comment on the substance of your note -- you
have probably heard enough from me.

regards,
    john