![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Scott, > rfc 2026 says what must be done in some cases - it does not say what > can not be done in the cases it does not cover - specifically, RFC 2026 > in no way would block a 4-week last call for an informational RFC > - note that RFC 2026 does not require any last call for informationals > Right, I didn't mean to imply there was an upper limit. Its always a judgment call. > fwiw - I agree with John - this doc warents a longer last call because > it does impact how part of the IETF process will work and the draft > did not get vetted in a normal working group process > That's a fair statement. I believe Brian just told us that he's not in a rush, so he's not cutting the discussion off too early. But its his call if he officially changes the last call period. Jari _______________________________________________ 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.