[NNTP] Re: GenART reviews of draft-ietf-nntpext-tls-nntp-07 and
draft-ietf-nntpext-authinfo-09
Clive D.W. Feather
clive at demon.net
Mon Jul 25 03:04:17 PDT 2005
Russ Allbery said:
> For informative references, I believe it's fine to just reference the
> draft and let the RFC Editor deal with it. The concern with referencing
> drafts was additional hold-up at the publishing stage when we don't
> actually care whether we go with the current reference or the later
> reference, but my understanding is that that this concern doesn't apply to
> informative references.
I handled all this through a note to the RFC Editor:
The normative reference to RFC 2234 [RFC2234] and the informative
reference to RFC 2629 [RFC2629] may be replaced by
draft-crocker-abnf-rfc2234bis and draft-mrose-writing-rfcs
respectively should either or both of those documents reach RFC
status before this one.
The informative references to [NNTP-AUTH], [NNTP-STREAM], and [NNTP-
TLS] are documents which are expected to be published simultaneously
with this one and so can be replaced by references to the resulting
RFCs.
--
Clive D.W. Feather | Work: <clive at demon.net> | Tel: +44 20 8495 6138
Internet Expert | Home: <clive at davros.org> | Fax: +44 870 051 9937
Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc | |
More information about the ietf-nntp
mailing list