Dave, I think that the requirements for a successful last call depend on how much review and interest have been demonstrated before the last call. For example, I recently last called draft-housley-cms-fw-wrap. It received no last call comments. What should I do with the draft? Well, in that case, I knew the draft had been reviewed (and changed based on comments) by several people in the S/MIME and security community. I also knew there was work on implementations and specific customers who plan to use the standard if approved. In my judgement as an AD, that was sufficient to justify bringing the document to the IESG even given no support in last call. There might very well be cases wher I'd bring a document to last call wher I was skeptical of the utility of the standard. I'd actually suspect that other tools for judging sufficient support before bringing a document to last call might be better, but last call is certainly a tool for judging support. In such a case, I might conclude that no comments were insufficient support. In conclusion, it seems like the ADs sponsoring documents have significant latitude in this area and that is a reasonable way for things to work. The community can complain that a standard is useless during last call; you can even say things like "I don't see the point; if others don't chime in and say they would use this, please do not publish." In addition, the community has multiple ways of giving feedback if they believe that there are systemic problems in the criteria ADs are using. --Sam _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf