Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consensus call

John C Klensin <john-ietf@jck.com> Fri, 18 May 2007 01:14 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 1Hor34-0007Ai-D1; Thu, 17 May 2007 21:14:26 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hor33-0007AY-H0 for discuss-confirm+ok@megatron.ietf.org; Thu, 17 May 2007 21:14:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hor33-0007AQ-7I for discuss@apps.ietf.org; Thu, 17 May 2007 21:14:25 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hor31-0006PZ-T3 for discuss@apps.ietf.org; Thu, 17 May 2007 21:14:25 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1Hor30-000Bq7-Cg; Thu, 17 May 2007 21:14:22 -0400
Date: Thu, 17 May 2007 21:14:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consensus call
Message-ID: <4512BF1B1B2C8C4A9487E733@p3.JCK.COM>
In-Reply-To: <CF36D27A6AC084536D6D8F24@[192.168.1.119]>
References: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org> <4648E8CB.3010502@dcrocker.net> <F5C06D62-639B-40CB-803F-6D9E50673768@osafoundation.org> <4649FA12.30909@alvestrand.no> <4649FB9A.9000107@bbiw.net> <1504A69099CF1B62F66FE576@p3.JCK.COM> <tsllkfnwgfb.fsf@mit.edu> <E09D6916A9D19A52976E4567@p3.JCK.COM> <tsl7ir7utz8.fsf@mit.edu> <CF36D27A6AC084536D6D8F24@[192.168.1.119]>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Apps Discuss <discuss@apps.ietf.org>, 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 Thursday, 17 May, 2007 21:52 +0200 Harald Tveit Alvestrand
<harald@alvestrand.no> wrote:

> I don't agree with the meaning I get from this statement. The
> problem is that the construct that ABNF calls "LWSP" causes
> problems in protocols that use it.
> This problem is independent of the name of the construct; the
> problem is in defining a grammar where the sequence
> <CRLF><CRLF> has a different meaning than <CRLF><SPACE><CRLF>.
>...

Interesting.  I don't think that is a problem with the grammar,
and think it would be rather hard to define a grammar that would
not permit that situation.   After all
    <CRLF> Thing <SPACE><CRLF> could case similar problems if
some construction permitted it and defining a grammar that would
prohibit any <SPACE><CRLF> construction isn't easy in ABNF for
reasons that have nothing to do with LWSP.

Instead, I see the problem as using the grammar to define
situations equivalent to 
    LWSP [ optional-stuff ] CRLF
as compared to 
    LWSP AtLeastOneRequiredThing CRLF
or
    [ LWSP optional-stuff ] CRLF

I don't see either of the latter as problematic.

      john