![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
*> From: "Richard Shockey" <richard at shockey.us> *> To: <erosen at cisco.com> *> *> A excellent start... *> *> You forgot $500 for messages on the use of ASCII in RFC's. *> Actually, I believe such messages are useful. They occur infrequently, in short storms at least a year apart, and they provide valuable input from the community. The RFC Editor has always scanned them carefully, looking for (a) a Better (and feasible) Idea, and (b) evidence that there is still a rough consensus in the community that the advantages of plain ASCII outweigh its obvious limitations. [Of course, when the IAOC outsources the RFC Editor to India in 2009, I don't know what effect future such messages will have.] It seems worthwhile to contemplate our editorial navels once in awhile, and does not cost much in the overall message flow. Now, if we could cut down on endless IETF process discussions... Bob Braden _______________________________________________ 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.