High-Level Requirements for Internet Voice Mail
draft-ietf-vpim-ivm-goals-06
Yes
(Scott Hollenbeck)
No Objection
(Allison Mankin)
(David Kessens)
(Russ Housley)
(Steven Bellovin)
(Ted Hardie)
Note: This ballot was opened for revision 06 and is now closed.
Scott Hollenbeck Former IESG member
Yes
Yes
()
Unknown
Allison Mankin Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Harald Alvestrand Former IESG member
(was Discuss)
No Objection
No Objection
(2004-04-02)
Unknown
Reviewed by Spencer Dawkins, Gen-ART. Complete review available from http://www.alvestrand.no/ietf/gen/reviews/draft-ietf-vpim-ivm-goals-06-dawkins.txt This could very easily have been a DISCUSS. But the -ivm document is completed, so this document is "documenting the thinking of the group" rather than telling other people what the requirements are. That limits the value of making the goals document better. High points: The biggest "open issue" is that this requirements document has some really vague "MUSTs" that need to be spelled out in more detail. For example, "and MUST gracefully handle the case where a legacy receiving system does not support the IVM codecs" - if the working group is going to use this document as a filter for proposals that don't meet the MUSTs, how would anyone know whether a proposal meets this MUST? In general, the requirements that include the words "specifically, this includes" are fine. It's the ones that don't include these words that have problems! My impression is that most of the people who have provided comments on the draft probably understand the context, which is fine for the working group but not-so-fine for reviewers outside the working group.
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Steven Bellovin Former IESG member
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown