Voice over IP (VoIP) SIP Peering Use Cases
draft-ietf-speermint-voip-consolidated-usecases-19
Yes
(Cullen Jennings)
(Gonzalo Camarillo)
No Objection
(Lars Eggert)
(Lisa Dusseault)
(Robert Sparks)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
Note: This ballot was opened for revision 19 and is now closed.
Cullen Jennings Former IESG member
Yes
Yes
()
Unknown
Gonzalo Camarillo Former IESG member
Yes
Yes
()
Unknown
Alexey Melnikov Former IESG member
No Objection
No Objection
(2009-10-03)
Unknown
RFC 4366 is not referenced in the text, so it should be deleted.
Dan Romascanu Former IESG member
(was Discuss)
No Objection
No Objection
(2009-10-09)
Unknown
Section 5.6 is surprisingly lean as compared to the various static use cases. That may be because it is hard to describe in general terms, but I was expecting a lot more detail there.
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Ralph Droms Former IESG member
No Objection
No Objection
(2009-10-06)
Unknown
Is there a specific intended purpose for these use cases: requirements development, guidance to developers/deployers, ??? Sorry for the minor rant, but the phrase "attempts to 'do something useful'" is a hot button for me. So, I'm going to indulge my inner pedant here. In the Introduction: This document attempts to capture Voice over IP (VoIP) use cases for Session Initiation Protocol (SIP) [RFC3261] based peering. "Attempts to capture" probably isn't a useful result. How about "describes important Voice over IP (VoIP) use cases, as determined by the SPEERMINT working group, ..." And, s/SPEERMING/SPEERMINT" in the header...
Robert Sparks Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown