Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)
draft-ietf-mmusic-qos-identification-03
Yes
(Cullen Jennings)
No Objection
(Dan Romascanu)
(Jon Peterson)
(Magnus Westerlund)
(Mark Townsley)
(Ross Callon)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 03 and is now closed.
Cullen Jennings Former IESG member
Yes
Yes
()
Unknown
Chris Newman Former IESG member
No Objection
No Objection
(2008-11-06)
Unknown
Agree with comments on ABNF/examples.
Dan Romascanu Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
David Ward Former IESG member
No Objection
No Objection
(2008-11-05)
Unknown
agree with other discusses but, will let them carry
Jari Arkko Former IESG member
(was Discuss, No Objection)
No Objection
No Objection
(2008-11-06)
Unknown
As an implementor of an application on a host acting as a, say, a SIP phone I do not not understand how these mechanisms are going to help me at all. First, how do I know if the underlying OS version supports NSIS, for instance? And even if I do know that, that says *nothing* about the support in the one place that truly needs it, namely in the routers in between. So all this appears to do is negotiation of mechanisms between two parties who have no clue about what mechanisms are available. Are there significant enough RSVP, NSIS, etc. deployments where specialized applications can actually make use of this?
Jon Peterson Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
(was Discuss)
No Objection
No Objection
(2008-11-05)
Unknown
Agree with Pasi on the example being invalid.
Magnus Westerlund Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Pasi Eronen Former IESG member
No Objection
No Objection
(2008-11-04)
Unknown
The example at end of Section 3 doesn't actually match the ABNF syntax (it's missing a space after the colon).
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
No Objection
No Objection
(2008-11-04)
Unknown
I don't think the following BNF in section 3 is quite right: qos-mech = rsvp / nsis / extension-mech extension-mech = token since rsvp and nsis are actually tokens according to the IANA Considerations. The intent is clear enough, so this is just a comment...