[rfc-i] ABNF (RFC2234)

shollenbeck at verisign.com (Hollenbeck, Scott) Wed, 06 April 2005 11:02 UTC

From: "shollenbeck at verisign.com"
Date: Wed, 06 Apr 2005 07:02:16 -0400
Subject: [rfc-i] ABNF (RFC2234)
Message-ID: <046F43A8D79C794FA4733814869CDF0759AA5D@dul1wnexmb01.vcorp.ad.vrsn.com>

> -----Original Message-----
> From: rfc-interest-bounces at rfc-editor.org 
> [mailto:rfc-interest-bounces at rfc-editor.org] On Behalf Of Bruce Lilly
> Sent: Tuesday, April 05, 2005 7:32 PM
> To: rfc-interest at rfc-editor.org
> Subject: Re: [rfc-i] ABNF (RFC2234)
> 
> 
> >  Date: 2005-04-03 21:17
> >  From: Bob Braden <braden at isi.edu>
> 
> > ? *> Somebody (one of 2234's authors) should probably 
> instruct the RFC Editor
> > ? *> to elide the "erratum" which purports to change the 
> technical content of
> > ? *> 2234...
> > 
> > I must admit to having lost track of this discussion. ?Is the above
> > statement correct, oh wise people? ?If so, will someone 
> tell us exactly
> > what to put in the erratum?
> 
> My opinion, based on the discussion, but with the caveat that I am
> neither one of the RFC's authors nor one of the cognizant Area
> Directors, is that there are two parts of the first erratum message
> which are objectionable:
> 
> 1. " / c-wsp"
> 2. ", possibly multiline"

...and with the recent IESG approval of draft-crocker-abnf-rfc2234bis (which obsoletes RFC 2234), the erratum for RFC 2234 become irrelevent.

-Scott-