Re: [apps-discuss] Review of: draft-yevstifeyev-abnf-separated-lists-02

Julian Reschke <julian.reschke@gmx.de> Sat, 11 December 2010 11:09 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B9A83A6D0F for <apps-discuss@core3.amsl.com>; Sat, 11 Dec 2010 03:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.492
X-Spam-Level:
X-Spam-Status: No, score=-104.492 tagged_above=-999 required=5 tests=[AWL=-1.893, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9LOAgoNjTOO6 for <apps-discuss@core3.amsl.com>; Sat, 11 Dec 2010 03:09:10 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 1B0B33A6AC1 for <apps-discuss@ietf.org>; Sat, 11 Dec 2010 03:09:09 -0800 (PST)
Received: (qmail invoked by alias); 11 Dec 2010 11:10:41 -0000
Received: from p508FB594.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.181.148] by mail.gmx.net (mp066) with SMTP; 11 Dec 2010 12:10:41 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18F0rJ2hFIFFqW5Isl8lOENSRvZgn1xEioDJ7AQns Pbi0GgeosvjiRV
Message-ID: <4D035C28.6070804@gmx.de>
Date: Sat, 11 Dec 2010 12:10:32 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Dave CROCKER <dcrocker@bbiw.net>
References: <4D028FE0.20906@bbiw.net>
In-Reply-To: <4D028FE0.20906@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Mykyta Yevstifeyev <evnikita2@gmail.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Review of: draft-yevstifeyev-abnf-separated-lists-02
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Dec 2010 11:09:11 -0000

On 10.12.2010 21:38, Dave CROCKER wrote:
> ...
> Given continuance of the old "#" form, I wonder whether it might be
> worth assembling whatever ABNF enhancements are out in the wild into an
> Informational document, so that they stand on their own and are easily
> citable? Should anyone have need of one or another of these, they can
> simply invoke it rather than having to (once again) specify it.
> ...

Indeed, that would be a good idea.

Some more thoughts:

- Please don't mess with RFC 5234 until those extensions are well 
understood and *in use*.

- Specifying is not sufficient; the few parsing and validation tools 
need to be extended. (*)

- I'm not sure why a new list production that is inspired by "#" can't 
have the same name.

Best regards, Julian

(*) In HTTPbis, we extended Bill Fenner's ABNF parser ("BAP") to accept 
the list production and re-serialize it in plain RFC 5234; this is what 
we're using to produce the 5234-style ABNF. See 
<http://trac.tools.ietf.org/wg/httpbis/trac/browser/abnfparser/bap>.