![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
John,
* There is, as far as I know, no precedent for an IETF-related body to announce a public comment period on a document, make a series of "interim decisions" and announce them five days before the end of that period, and then leave the comment period termination date in place rather than restarting the review on the revised document.For a purely practical point of view: When I'm asked to review a document, and before I start, the author realizes that a section needs to be modified, then this is something I'd like to know. That saves me the time to review something that is known to be changed anyway.Sure. And the period of time you get to make the review starts when you get the changed version. That is why I believe this review period is, in practice, only five days long.
I'd think it is still 30 days. N changes were proposed, on comments
made in the first days, it was clear that one of them wasn't a good
idea, so it was dropped. No review is necessary for that, for the
other N-1 changes, there is still a 30 day period ongoing.
Henk
------------------------------------------------------------------------------
Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre http://www.xs4all.nl/~henku
P.O.Box 10096 Singel 258 Phone: +31.20.5354414
1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445
The Netherlands The Netherlands Mobile: +31.6.55861746
------------------------------------------------------------------------------
Belgium: an unsolvable problem, discussed in endless meetings, with no
hope for a solution, where everybody still lives happily.
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.