Hi Alexey,
The question is: in the meantime, what to do about this draft? By
default I guess I will simply restate the issue in my genart telechat
review and leave it for the IESG discuss it.
As per my comments above, I think we should acknowledge that there is a
subtle issue with ABNF in RFC 5536. I think the best way forward is to
approve some fix to your erratum and let
draft-baeuerle-netnews-cancel-lock be reviewed by IESG. At this moment
it is not clear to me that work on RFC 5536 will happen any time soon,
so I don't think we should hold this draft hostage.
No work on RFC 5536 is scheduled in a near future.
The next revision will probably be when we deal with Netnews
internationalization (UTF-8 newsgroup names, UTF-8 distributions...).
It may be in a separate RFC or in a rewrite of RFC 5536 (in case RFC
5322 is also rewritten).
Also, the USEFOR WG began a BCP for Netnews but the WG concluded before
the task finished. That is the next consequent work to do.
https://datatracker.ietf.org/doc/draft-ietf-usefor-useage/
--
Julien ÉLIE
« De mourir, ça ne me fait rien. Mais ça me fait peine de quitter la
vie. » (Marcel Pagnol)
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
