Re: Seeking clarification of ABNF "name formation" reference

Dave Crocker <dhc@dcrocker.net> Wed, 23 May 2007 21:16 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 1HqyC7-0008AI-0c; Wed, 23 May 2007 17:16:31 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1HqyC5-0008AD-ED for discuss-confirm+ok@megatron.ietf.org; Wed, 23 May 2007 17:16:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqyC5-0008A5-4X for discuss@apps.ietf.org; Wed, 23 May 2007 17:16:29 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqyC3-0005lG-Nk for discuss@apps.ietf.org; Wed, 23 May 2007 17:16:29 -0400
Received: from [192.168.0.4] (adsl-68-122-125-236.dsl.pltn13.pacbell.net [68.122.125.236]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l4NLGEMl025238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <discuss@apps.ietf.org>; Wed, 23 May 2007 14:16:15 -0700
Message-ID: <4654AEEC.80503@dcrocker.net>
Date: Wed, 23 May 2007 14:15:24 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: discuss@apps.ietf.org
Subject: Re: Seeking clarification of ABNF "name formation" reference
References: <46523D89.70905@dcrocker.net> <20070523084651.GB57435@finch-staff-1.thus.net> <465429B2.8030006@gmx.de>
In-Reply-To: <465429B2.8030006@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Clean
X-Songbird-From: dhc@dcrocker.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
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

Folks,

I think we figured out what this was about.  The 'name formation' meant the 
aggregation of characters that form a rulename.

The revised precedence list reads:

 > >                  <t>Rule name, prose-val, Terminal value<t>
 > >                  <t>Comment</t>
 > >                  <t>Value range</t>
 > >                  <t>Repetition</t>
 > >                  <t>Grouping, Optional</t>
 > >                  <t>Concatenation</t>
 > >                  <t>Alternative</t>


We believe that each item on the first line is explained with existing 
definitions or text.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net