Re: [usefor] Issue with ABNF grammar in RFC 5536

Julien ÉLIE <julien@trigofacile.com> Mon, 10 July 2017 19:46 UTC

Return-Path: <julien@trigofacile.com>
X-Original-To: usefor@ietfa.amsl.com
Delivered-To: usefor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF6C1318A0 for <usefor@ietfa.amsl.com>; Mon, 10 Jul 2017 12:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.421
X-Spam-Level:
X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofsqRL_Qip_1 for <usefor@ietfa.amsl.com>; Mon, 10 Jul 2017 12:46:52 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B4881318A3 for <usefor@ietf.org>; Mon, 10 Jul 2017 12:46:51 -0700 (PDT)
Received: from mbpdejulienelie.home ([86.252.120.177]) by mwinf5d81 with ME id j7mp1v0093pkiFq037mpj8; Mon, 10 Jul 2017 21:46:49 +0200
X-ME-Helo: mbpdejulienelie.home
X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg==
X-ME-Date: Mon, 10 Jul 2017 21:46:49 +0200
X-ME-IP: 86.252.120.177
To: usefor@ietf.org
Cc: =?UTF-8?Q?Michael_B=c3=a4uerle?= <michael.baeuerle@stz-e.de>, pkyzivat@alum.mit.edu
References: <15001f4b-477e-1900-6d3b-d0635b9dad94@trigofacile.com> <20170707185914.06cfa0ac@WStation4>
From: =?UTF-8?Q?Julien_=c3=89LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <69036829-918f-2b31-7145-45b8629ef341@trigofacile.com>
Date: Mon, 10 Jul 2017 21:46:49 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170707185914.06cfa0ac@WStation4>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/usefor/6-55b2bCBBlg1U0AHroyqWHeT8I>
Subject: Re: [usefor] Issue with ABNF grammar in RFC 5536
X-BeenThere: usefor@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Ongoing discussion of usefor issues." <usefor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/usefor>, <mailto:usefor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/usefor/>
List-Post: <mailto:usefor@ietf.org>
List-Help: <mailto:usefor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/usefor>, <mailto:usefor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 19:46:54 -0000

Hi Michael,

>> Paul Kyzivat noticed in the IETF Gen-ART mailing-list
>>     https://www.ietf.org/mail-archive/web/gen-art/current/msg14921.html
>> that there is an issue in the ABNF of RFC 5536 (USEFOR).
>>
>>      The following news header fields extend those defined in Section 3.6
>>      of [RFC5322]:
>>
>>        fields        =/ *( approved /
>>                            archive /
>>                            control /
>>                            distribution /
>>                            expires /
>>                            followup-to /
>>                            injection-date /
>>                            injection-info /
>>                            lines /
>>                            newsgroups /
>>                            organization /
>>                            path /
>>                            summary /
>>                            supersedes /
>>                            user-agent /
>>                            xref )
>>
>> to:
>>
>>      The following news header fields are defined by this document:
>>
>>        news-fields    =    approved /
>>                            archive /
>>                            control /
>>                            distribution /
>>                            expires /
>>                            followup-to /
>>                            injection-date /
>>                            injection-info /
>>                            lines /
>>                            newsgroups /
>>                            organization /
>>                            path /
>>                            summary /
>>                            supersedes /
>>                            user-agent /
>>                            xref
>>
>>      The definition of message in Section 3.5 of [RFC5322] is changed to:
>>
>>        message       =   *(fields / obs-fields / news-fields)
>                            ^
>>                          [CRLF body]
> 
> Wouldn't this asterisk introduce the same "infinite loop of empty
> strings" situation as in the erratum noted above?

As "fields" in RFC 5322 amended with erratum 2950 no longer has an 
infinite loop of empty strings, *(fields / obs-fields / news-fields) 
also do not have, don't it?

Note that using 1*(fields / obs-fields / news-fields) is also fine 
because headers are not empty.

I once thought about something like original (fields / obs-fields) 
extended with *news-fields.  The issue is that "fields" and 
"news-fields" are a/ mixed and b/ Netnews specific header fields do not 
appear after all mail header fields.

-- 
Julien ÉLIE

« – Chef ! On vient !
   – On se met en carré ?
   – Non ! En bosquet ! » (Astérix)