From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Mon Apr 04 2005 - 20:55:29 EDT
Hi,
RFC 2234 (ABNF) has been superseded by an IESG approved I-D
(not yet published in a new RFC).
This affects WIMS and essentially all other PWG protocol specs.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
-----Original Message-----
From: ltru-bounces@lists.ietf.org [mailto:ltru-bounces@lists.ietf.org]On
Behalf Of Randy Presuhn
Sent: Monday, April 04, 2005 6:32 PM
To: LTRU Working Group
Subject: [Ltru] Fw: Protocol Action: 'Augmented BNF for Syntax
Specifications: ABNF' to Draft Standard
Hi -
forwarded for your information....
The references in the registry i-d should be changed accordingly.
Randy
----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: "Internet Architecture Board" <iab@iab.org>; "RFC Editor"
<rfc-editor@rfc-editor.org>
> Sent: Monday, April 04, 2005 1:35 PM
> Subject: Protocol Action: 'Augmented BNF for Syntax Specifications: ABNF'
to Draft Standard
>
> The IESG has approved the following document:
>
> - 'Augmented BNF for Syntax Specifications: ABNF '
> <draft-crocker-abnf-rfc2234bis-00.txt> as a Draft Standard
>
> This document has been reviewed in the IETF but is not the product of an
> IETF Working Group.
>
> The IESG contact person is Scott Hollenbeck.
>
> Technical Summary
>
> Internet technical specifications often need to define a format
> syntax. Over the years a modified version of Backus-Naur Form (BNF),
> called Augmented BNF (ABNF), has been popular among many Internet
> specifications. The current specification documents ABNF. It
> balances compactness and simplicity, with reasonable representational
> power. The differences between standard BNF and ABNF involve naming
> rules, repetition, alternatives, order-independence, and value
> ranges. This specification also supplies additional rule definitions
> and encoding for a core lexical analyzer of the type common to
> several Internet specifications.
>
> This document obsoletes RFC 2234.
>
> Working Group Summary
>
> This document is the work of individual submitters. It was produced
> to address comments received from the IESG when the IESG was asked
> to elevate RFC 2234 to Draft Standard status. An IETF last call on
> the request to elevate RFC 2234 was completed in June 2004.
>
> Protocol Quality
>
> Harald Alvestrand, Bill Fenner, and Scott Hollenbeck evaluated this
> specification for the IESG.
>
> RFC Editor Note:
>
> Abstract and Section 1, first sentence:
> OLD:
> "Internet technical specifications often need to define a format"
> ^^^^^^
>
> NEW:
> "Internet technical specifications often need to define a formal"
> (change "format" to "formal")
>
> Section 1:
> OLD:
> "Changes in the latest version of this Internet Draft:"
>
> NEW:
> "Changes Since RFC 2234:"
>
> Section 3.1:
> OLD:
> NOTE:
>
> NOTE: This specification for ABNF does not provide for implicit
> specification of linear white space.
>
> NEW:
> NOTE: This specification for ABNF does not provide for implicit
> specification of linear white space.
> (remove frist instance of "NOTE")
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Ltru mailing list
Ltru@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru
This archive was generated by hypermail 2.1.4 : Thu Apr 16 2009 - 10:55:40 EDT