Re: Use of LWSP in ABNF -- consensus call

John Leslie <john@jlc.net> Tue, 15 May 2007 17:16 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho0dX-0004ad-Bs; Tue, 15 May 2007 13:16:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho0dV-0004aR-Vo for ietf@ietf.org; Tue, 15 May 2007 13:16:33 -0400
Received: from mailhost.jlc.net ([199.201.159.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ho0dU-0005S9-N8 for ietf@ietf.org; Tue, 15 May 2007 13:16:33 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104) id D08B923F09B; Tue, 15 May 2007 13:16:32 -0400 (EDT)
Date: Tue, 15 May 2007 13:16:32 -0400
From: John Leslie <john@jlc.net>
To: Paul Overell <paul.overell@thus.net>
Message-ID: <20070515171631.GC70642@verdi>
References: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org> <4648E8CB.3010502@dcrocker.net> <F5C06D62-639B-40CB-803F-6D9E50673768@osafoundation.org> <464926FC.30109@att.com> <jhfVS$CRfXSGFAUB@paulo1-adsl.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <jhfVS$CRfXSGFAUB@paulo1-adsl.demon.co.uk>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: ietf@ietf.org
Subject: Re: Use of LWSP in ABNF -- consensus call
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

Paul Overell <paul.overell@thus.net> wrote:
> In message <464926FC.30109@att.com>, Tony Hansen <tony@att.com> writes
>> Lisa Dusseault wrote:
>> 
>>> 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.
>>
>> LWSP has a valid meaning and use, and its being misapplied somewhere
>> doesn't make that meaning and usage invalid.
> 
> Agreed - well put.
> 
>> I could see a note being
>> added. However, anything more than that is totally inappropriate.
> 
> I would vote against even adding a note.  It seems disproportionate to 
> change a 10 year specification at this late stage on the basis of a 
> single case of a misapplied, but valid, rule in another specification.

   I did some research, and found the following mentions of LWSP:

rfc0733 obs-by rfc0822
rfc0822 defs LWSP-char = SPACE / HTAB   obs-by rfc2822
rfc0987 refs rfc0822   
rfc1138 refs rfc0822
rfc1148 refs rfc0822
rfc1327 refs rfc0822
rfc1486 refs rfc0822
rfc1505 refs rfc0822
rfc1528 refs rfc0822
rfc1848 defs <LWSP-char> ::= SPACE / HTAB
rfc2017 refs rfc0822
rfc2045 refs rfc0822
rfc2046 refs rfc0822   
rfc2110 refs rfc0822
rfc2156 refs rfc0822
rfc2184 refs rfc0822
rfc2231 refs rfc0822
rfc2234 defs LWSP = *(WSP / CRLF WSP)   obs-by rfc4234    
rfc2243 refs rfc0822
rfc2378 defs LWSP-char = SP | TAB
rfc2530 refs rfc2234
rfc2885 defs LWSP = *(WSP / COMMENT / EOL)
rfc3015 defs LWSP = *(WSP / COMMENT / EOL)
rfc3259 defs LWSP = *(WSP / CRLF WSP)
rfc3501 refs rfc2234
rfc3525 defs LWSP = *(WSP / COMMENT / EOL)
rfc3875 defs LWSP = SP | HT | NL
rfc4234 defs LWSP = *(WSP / CRLF WSP)
rfc4646 refs rfc2434

   Based on this, I recommend outright deprecation. The RFC4234
definition is wildly different from the RFC822 usage (which is
substanitally more often referenced): thus any use of it will tend
to confuse. It's also a bit dubious, quite specifically allowing
lines which appear to be blank, but aren't. :^(

   The RFC4234 definition, in fact, is referenced by only 3 RFCs:

RFC2530 Indicating Supported Media Features Using Extensions to DSN and MDN 
RFC3501 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
RFC4646 Tags for Identifying Languages

   The use under RFC2530 is a bit vague ("with LWSP wrapping"); likewise
under RFC3501 ("otherwise treat SP as being equivalent to LWSP"). The
use under RFC4646 has caused known problems.

   This would seem to justify deprecation, IMHO.

   YMMV, of course...

--
John Leslie <john@jlc.net>

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf