Re: Use of LWSP in ABNF -- consensus call

Lisa Dusseault <lisa@osafoundation.org> Tue, 15 May 2007 00:35 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hnl1A-000241-K8; Mon, 14 May 2007 20:35:56 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hnl18-00023q-Ab for discuss-confirm+ok@megatron.ietf.org; Mon, 14 May 2007 20:35:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hnl18-00023d-0N for discuss@apps.ietf.org; Mon, 14 May 2007 20:35:54 -0400
Received: from laweleka.osafoundation.org ([204.152.186.98]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hnl17-00024J-J6 for discuss@apps.ietf.org; Mon, 14 May 2007 20:35:53 -0400
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 27C37142201; Mon, 14 May 2007 17:35:53 -0700 (PDT)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3m2fsvMDxgT; Mon, 14 May 2007 17:35:51 -0700 (PDT)
Received: from [192.168.1.101] (unknown [74.95.2.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 20CE81421FF; Mon, 14 May 2007 17:35:49 -0700 (PDT)
In-Reply-To: <4648E8CB.3010502@dcrocker.net>
References: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org> <4648E8CB.3010502@dcrocker.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F5C06D62-639B-40CB-803F-6D9E50673768@osafoundation.org>
Content-Transfer-Encoding: 7bit
From: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: Use of LWSP in ABNF -- consensus call
Date: Mon, 14 May 2007 17:35:46 -0700
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: Apps Discuss <discuss@apps.ietf.org>, Paul Overell <paul.overell@thus.net>, IETF General Discussion Mailing List <ietf@ietf.org>, ietf-dkim@mipassoc.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

On May 14, 2007, at 3:55 PM, Dave Crocker wrote:

>
> Lisa Dusseault wrote:
>> The IESG reviewed <http://www.ietf.org/internet-drafts/draft- 
>> crocker-rfc4234bis-00.txt> for publication as Internet Standard  
>> and would like to know if there is consensus to recommend against  
>> the use of LWSP in future specifications,
>
> 1   This issue was initially raised in the IESG by Chris Newman,  
> who changed
> his Discuss, with a statement that he recommended inserting a  
> comment, along
> the lines that others are also recommending.  Unless I've misread  
> the record,
> all other votes on advancing ABNF from Draft to Full are positive  
> or neutral,.
> except for your own Discuss.  Is this correct?


The issue was initially raised by Frank Ellerman or by various in the  
DKIM WG depending on how you look at it -- Frank explicitly suggested  
possible changes to the draft, in his posting to the IETF list.

You're right about the voting situation but here's the background: I  
took on the DISCUSS myself as a placeholder for an issue that the  
IESG had consensus to investigate further (consensus to investigate  
what the consensus is).   I could have asked somebody else to hold  
the DISCUSS but this seemed most convenient as long as the rest of  
the IESG trusted me to investigate.

>
> 2.  The ABNF is a candidate for moving from Draft to Full.  Will  
> removing a
> rule (that is already in use?) or otherwise changing the semantics  
> of the
> specification, at this point, still permit the document to  
> advance?  I had the
> impression that moving to Full was based on some serious beliefs  
> about a
> specification's being quite stable.  Making this kind of change,  
> this late in
> the game, would seem to run counter to that.

Moving to Internet Standard is indeed something we do carefully, and  
of course that means investigating proposed changes to make sure  
they're appropriate, and setting a high bar for accepting them.  I  
believe that's what we're doing here, investigating carefully.

I share your concerns about removing rules that are already in use --  
that would generally be a bad thing.  However I'm interested in the  
consensus around whether a warning or a deprecation statement would  
be a good thing.

Thanks,
Lisa