>>>>> "Henning" == Henning Schulzrinne <hgs@xxxxxxxxxxxxxxx> writes:
Henning> Putting all comments, including DISCUSS, into a
Henning> document-specific issue tracker would be most
Henning> helpful. (It would be helpful even beyond publication of
Henning> an RFC, as we have found for the SIP documents, as they
Henning> can be used to gather issues that a future "bis" effort
Agreed provided that it is simple for me to open a new issue from my
email client, turn an email discussion into an issue, resolve and
issue using email, etc. Also, I need to be able to update multiple
issues in an email message, etc etc. Basically, I'm OK with an issue
tracker provided that it does not increase the complexity for those
doing cross-area review who want to open up a bunch of issues and
manipulate them. Especially using a web based issue tracker is a
non-starter from that standpoint. (You do probably want a web
interface to any issue tracker; you just don't want to destroy the
existing interface.)
It is possible to meet these requirements in an issue tracker design.
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf