[NNTP] [Errata Rejected] RFC3977 (2004)
Julien ÉLIE
julien at trigofacile.com
Mon May 14 14:28:39 PDT 2012
Hi all,
[Russ]
>>> Yes, please. We would clearly want to fix this in any revision of RFC
>>> 3977. Personally, I would recommend that any implementor use 423 as
>>> described in Julien's analysis despite the wording of RFC 3977.
[Barry]
>> RFC Editor, will you please switch errata #2004 from "rejected" to
>> "hold for document update"? Thanks.
[Alice]
> The status has been changed as requested:
> http://www.rfc-editor.org/errata_search.php?eid=2004
And also [Clive] of course, thanks to all of you!
The "hold for document update" status is pretty fine.
[Charles]
> a revision [of RFC3977] is unlikely in the foreseeeable future. Is there
> any mechanism whereby a NOTE can be added as an erratum pointing out
> that "With hindsight it might have been better to ..., and this
> should be revisited in any revision of this document"? As least that
> would alert people to the issue and hint that they might want to
> reconsider how to cope with it in their implementation.
I do not believe such a mechanism exists. Unfortunately.
One has to go to the HTML version of the IETF site:
http://tools.ietf.org/html/rfc3977
and pay attention to the two red words "Errata Exist". Then, carefully
read through all the submitted errata.
--
Julien ÉLIE
« Mieux vaut allumer une bougie que maudire les ténèbres. » (Lao
Zi)
More information about the ietf-nntp
mailing list