Two things in response to the issue of waiting to deal with the revised NOMCOM document.
First, as a practical matter, I'm not inclined to believe there's a significant issue. If the timetable as specified in RFC2727 is completed on schedule, the NOMCOM will be done in less than 3 weeks. Even if they run over they'll be done before the Spring IETF and that's only 7 weeks away. The NOMCOM should be well on its way to completing its task and barring anything exceptional I'm having trouble believing you're going to learn anything about the process in the remaining 7 weeks that you have not already learned. And I say that based on having met with every NOMCOM or some set of NOMCOM members after every NOMCOM since this document was started. Second, having said all that, I suspect in the best case this document could be completed coincident with the NOMCOM completing its task at hand. If there really is a last minute issue or some issue that someone really does not want to talk about until NOMCOM closes, folks can tell me privately if necessary. It's been done before and you probably never noticed, right? In any case, I'm certainly not going to force the document to close if there's something that needs discussing. Honestly, there's no particular required timeframe for being done, although it would be nice to be done before Minneapolis or in the worst case before the next NOMCOM starts this summer. Also, I don't think there's anything particularly contentious on the list of issues ... but I could be wrong. :-) Jim -- James M. Galvin <[EMAIL PROTECTED]>
