Re: Seeking clarification of ABNF "name formation" reference

Philip Guenther <guenther+ietf@sendmail.com> Tue, 22 May 2007 06:29 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 1HqNsX-00077o-3f; Tue, 22 May 2007 02:29:53 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HqNsW-00077f-A6 for discuss-confirm+ok@megatron.ietf.org; Tue, 22 May 2007 02:29:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqNsV-00077T-TI for discuss@apps.ietf.org; Tue, 22 May 2007 02:29:51 -0400
Received: from tls.sendmail.com ([209.246.26.40] helo=foon.sendmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqNsT-0007WU-Gq for discuss@apps.ietf.org; Tue, 22 May 2007 02:29:51 -0400
Received: from [10.201.0.47] (adsl-64-58-1-252.mho.net [64.58.1.252] (may be forged)) (authenticated bits=0) by foon.sendmail.com (Switch-3.2.5/Switch-3.2.0) with ESMTP id l4M6WQbd024771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 23:32:28 -0700
X-DKIM: Sendmail DKIM Filter v0.5.1 foon.sendmail.com l4M6WQbd024771
DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=sendmail.com; s=tls.dkim; t=1179815550; bh=aoLPjSxZAS8yaXcUDDYcGiv8h80=; h=X-DomainKeys: DomainKey-Signature:Date:From:X-X-Sender:To:cc:Subject:In-Reply-To: Message-ID:References:MIME-Version:Content-Type; b=VgoaTjb987BN9PJ/ Zj31faYDVclkf46Z/2qFRKnlX677z6VffiNR3fCToK3uEihJCZ4j4BAKl3IoSqi+yVK EDSPIJN1Nv6uiRYYRb4FzGoXLU3nBpPCTkhXAOcHFGSt/dizH8HoFHqCLMNMn+akutv oKxZeTuqh+K3iLbgHKJ4A=
X-DomainKeys: Sendmail DomainKeys Filter v0.4.1 foon.sendmail.com l4M6WQbd024771
DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:mime-version:content-type; b=fTIaoxJ3ngckJzy/g9wCK7DMmBIr5Q5Ra9g2wBSqI7U24PnN4VwTrK5B6mlD4YXws eGJN09yqSKN5neuxAtGtRB8dpxh6G/JQvXu0/3wrupCD0L0ODu4r5HEIRSI2OpgzE+Y oWacAH3hKMeBAcOZn5n07OCBrsz+wedR1O7KYFg=
Date: Tue, 22 May 2007 00:29:38 -0600
From: Philip Guenther <guenther+ietf@sendmail.com>
X-X-Sender: guenther@skarrin.mho.net
To: dcrocker@bbiw.net
Subject: Re: Seeking clarification of ABNF "name formation" reference
In-Reply-To: <46523D89.70905@dcrocker.net>
Message-ID: <Pine.BSO.4.64.0705220019030.12160@skarrin.mho.net>
References: <46523D89.70905@dcrocker.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: discuss@apps.ietf.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 Mon, 21 May 2007, Dave Crocker wrote:
> In the ABNF document, there is a precedence chart:
>
>> <section title="Operator Precedence">
>>
>>             <t> The various mechanisms described above have the following
>>                precedence, from highest (binding tightest) at the top, to
>>                lowest (loosest) at the bottom: <list>
>>
>>                   <t>Strings, Names formation</t>
>>                   <t>Comment</t>
...
>>                </list>
>>             </t>
>
>
> The reference to "Name formation" has been in this form since RFC 2234.
>
> Oddly, we can't figure out what it is supposed to mean, exactly.
>
> We could make some guesses, but I'd rather check with the group.

My guess was that it's a reference to the 'prose' value form, ala:
 	tag      = 1*<any ASTRING-CHAR except "+">

Inside the angle-brackets, only close-angle-bracket is special, just as 
inside a string, only double-quote is special, so those forms have a 
higher precedence than comment (semicolon isn't special) and repetition 
(asterisk isn't special), and...

So then I looked at the RFC and discovered that the prose value form is 
*only* mentioned in the ABNF definition of ABNF!  Was its prose 
description misplaced and accidentally used to shim a wobbly table?  If 
so, that would explain the dangling reference.


Philip Guenther