Re: Use of LWSP in ABNF -- consensus call

Dave Crocker <dcrocker@bbiw.net> Sat, 22 September 2007 16:43 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 1IZ84L-0001jz-Qx; Sat, 22 Sep 2007 12:43:01 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IZ84K-0001gn-0i for discuss-confirm+ok@megatron.ietf.org; Sat, 22 Sep 2007 12:43:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IZ84J-0001eo-Fu for discuss@apps.ietf.org; Sat, 22 Sep 2007 12:42:59 -0400
Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IZ848-0001jx-7M for discuss@apps.ietf.org; Sat, 22 Sep 2007 12:42:54 -0400
Received: from [192.168.0.2] (adsl-67-127-57-71.dsl.pltn13.pacbell.net [67.127.57.71]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l8MGgF8Q016848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Sep 2007 09:42:15 -0700
Message-ID: <46F545F1.1010806@bbiw.net>
Date: Sat, 22 Sep 2007 09:42:25 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Apps Discuss <discuss@apps.ietf.org>
Subject: Re: Use of LWSP in ABNF -- consensus call
X-Priority: 2 (High)
References: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org>
In-Reply-To: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: Paul Overell <paul.overell@thus.net>
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 5/14/2007 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, 
> as it has caused problems recently in DKIM and could cause problems in 
> other places.
> 
> Some discussion on this point already:
>  - http://www1.ietf.org/mail-archive/web/ietf/current/msg46048.html
>  - http://www1.ietf.org/mail-archive/web/discuss/current/msg00463.html
>  - http://mipassoc.org/pipermail/ietf-dkim/2007q1/007295.html
>  - 
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_comment&id=66440  
> (in this tracker comment, Chris Newman recommended to remove LWSP, but 
> for backward-compatibility it's probably better to keep it and recommend 
> against use)


Folks,

The current situation with elevating the ABNF document to full Internet 
Standard is that Lisa has a Discuss hold on it, on behalf of an IESG view that 
a warning note should be attached.

Acting as an individual contributor, Chris Newman has offered the following 
change to the document, as a possible means of resolving things:


> OLD:
>         LWSP           =  *(WSP / CRLF WSP)
>                        ; linear white space (past newline)
> NEW:
>         LWSP           =  *(WSP / CRLF WSP)
>                        ; Use of this linear-white-space rule permits
>                        ; lines containing only white space that are no
>                        ; longer legal in mail headers and have caused
>                        ; interoperability problems in other contexts.
>                        ; Do not use when defining mail headers and use
>                        ; with caution in other contexts.


The nature of the IETF process is such that there are no guarantees for what 
will resolve a Discuss, but the signs are good that a consensus on this list, 
for a note of this type, will suffice.

The premise is that the discussion on this list, last May, had consensus to 
retain the LWSP construct and consensus to add a warning.  The text that Chris 
is suggesting seems to accomplish this.

In spite of saying "Do not use", the comment is non-normative, in formal IETF 
specification terms.  Yet it does seem to adequately describe the problem and 
the way to deal with it.



           So, I'm going to ask for a consensus call on this
           modification, where the assumption is that the text
           is acceptable.

           All that is needed is for folk who *object* to speak up
           and state their reasons.

           If there is consensus *against* this change, we'll have to
           try something else.

           Absent a consensus *against* the wording change, we will
           propose it to Lisa and see if that resolves her Discuss.

           This consensus call closes on Sunday, 30 September.


Thanks.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net