![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Sorry. No it does not make any changes. Our practices remain the same.
Russ
Hi, Russ,
Spencer:
This document is intended to set expectations. It does not make any normative changes to RFC 2026.
Russ
Got that part.
I'm actually asking whether the ION makes any changes in the expectations set in the 02 version of the now-dead IESG draft, which the IESG has been referencing in conversations about DISCUSS ballot positions for a while now - doesn't look like it, but wanted to make sure what you guys think.
Thanks,
Spencer
At 01:08 PM 8/27/2007, Spencer Dawkins wrote:Hi, Russ,
A quick comparison with version 02 of this draft (from 2006, currently listed in DEAD state) is showing minor typo corrections and a million format changes, but the criteria haven't changed in any meaningful way. Is this your understanding also?
Thanks,
Spencer
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ 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.