[NNTP] AD Evaluation of draft-ietf-nntpext-streaming-05
sah at 428cobrajet.net
Tue May 24 08:38:41 PDT 2005
> -----Original Message-----
> From: Clive D.W. Feather [mailto:clive at demon.net]
> Sent: Tuesday, May 24, 2005 11:17 AM
> To: Scott Hollenbeck
> Cc: ietf-nntp at lists.eyrie.org
> Subject: Re: [NNTP] AD Evaluation of draft-ietf-nntpext-streaming-05
> Scott Hollenbeck said:
> > Section 7.1: Please consider updating the [ABNF] reference to use
> > draft-crocker-abnf-rfc2234bis instead of RFC 2234. The
> IESG recently
> > approved draft-crocker-abnf-rfc2234bis to obsolete 2234.
> It's in the RFC
> > Editor queue.
> Doesn't that risk holding up our publication waiting for it to gain a
> Is there a process for this; in effect "change this reference
> if and only
> if the new version gets RFC status before this document"?
rfc2234bis should pop out of the RFC Editor queue before this one does (the
IESG can make that requirement clear to the RFC Editor if need be), so no, I
don't see a risk of delay. The only "process" to does this without changing
the reference would be to put text in an IESG note to the RFC Editor asking
them to revise the reference if rfc2234bis is available as an RFC before the
WG documents are. It makes more sense to just tell the RFC Editor to
expedite processing of rfc2234bis.
More information about the ietf-nntp