Voice over IP (VoIP) SIP Peering Use Cases
RFC 6405

Note: This ballot was opened for revision 19 and is now closed.

(Gonzalo Camarillo) Yes

(Cullen Jennings) Yes

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Ralph Droms) No Objection

Comment (2009-10-06 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
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...

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

(Russ Housley) No Objection

Alexey Melnikov No Objection

Comment (2009-10-03 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
RFC 4366 is not referenced in the text, so it should be deleted.

(Dan Romascanu) (was Discuss) No Objection

Comment (2009-10-09)
No email
send info
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.

(Robert Sparks) (was Discuss) No Objection