Identification of Communications Services in the Session Initiation Protocol (SIP)
draft-ietf-sipping-service-identification-04

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

Lars Eggert No Objection

(Cullen Jennings; former steering group member) Yes

(Robert Sparks; former steering group member) Yes

(Adrian Farrel; former steering group member) No Objection

Well written and easy to read, thanks.

To me, the recommendations in Section 7 are very important. I was hoping I would find them. I think you could usefully note in the Abstract and the Introduction that the document does make recommendations, and possibly you could include a "management summary" of those recommendations in the Introduction. (Note that the final paragraph of the Introduction lists the other sections but is too shy to mention the recommendations!)

(Alexey Melnikov; former steering group member) No Objection

4.3.  Network Quality of Service Authorization

   The IP network can provide differing levels of Quality of Service
   (QoS) to IP packets.  This service can include guaranteed throughput,
   latency, or loss characteristics.  Typically, the user agent will
   make some kind of QoS request, either using explicit signaling
   protocols (such as RSVP) or through marking of Diffserv value in

I think this needs an informative reference to RSVP RFC.

   packets.  The network will need to make a policy decision based on

(Dan Romascanu; former steering group member) No Objection

(Jari Arkko; former steering group member) No Objection

(Lisa Dusseault; former steering group member) No Objection

(Magnus Westerlund; former steering group member) No Objection

(Ralph Droms; former steering group member) No Objection

(Ron Bonica; former steering group member) No Objection

(Russ Housley; former steering group member) (was Discuss) No Objection

(Tim Polk; former steering group member) No Objection