![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Brian E Carpenter <brian.e.carpenter at gmail.com> wrote: > On 2008-01-30 10:35, Cullen Jennings wrote: >> >> The process for publishing them has many bottlenecks and delays... > > I couldn't agree more... > perhaps people should focus on whether the class of documents > available at http://www.ietf.org/IESG/content/ions.html > is useful, not on the mechanics of writing and posting them. I firmly believe these are useful, and that given more time we'll fill in some of the gaps. (I most sincerely hope the IESG isn't even considering discarding the IONs we already have.) I'd like to suggest that many of the RFC2026 diffs that Brian put in his Internet Draft might be put in IONs, to the extent they merely document current practice which already reflects IESG consensus. (Running those through a WG process seems pointless...) -- John Leslie <john at jlc.net> _______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.