In the interest of moving faster, we should choose *not* to discuss purely editorial issues and leave them to the editors to resolve at their discretion. Peter -----Original Message----- From: ltru-bounces at ietf.org [mailto:ltru-bounces at ietf.org] On Behalf Of Randy Presuhn Sent: Wednesday, May 27, 2009 11:27 AM To: LTRU Working Group Subject: [Ltru] In the interest of moving faster... Hi - As someone who's been doing IETF stuff for a long long time, rather than as co-chair or as a technical contributor... At this stage of the process, the fastest way to resolve review comments is to look carefully at the proposed resolution. If it's something you could live with, just say "ok" and make no further comment. If the reviewer doesn't make a specific proposal, propose minimal-change text that *directly* addresses the thrust of the comment. The next-quickest path is to say "no, we already considered this alternative and rejected it." Word-smithing the proposal will slow things down, and should only be done if there's significant problems with the proposal (ambiguities or lack of clarity). If you want to bring things to a grinding halt, drag in peripheral issues not directly raised by the review comment. Ironically, total silence also slows things down. Don't forget that after we're finished with it, the RFC editor gets a chance to fix English usage, punctuation, etc. Randy _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.