Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)
draft-ietf-mmusic-qos-identification-03

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

Lars Eggert (was Discuss) No Objection

Comment (2008-11-05)
No email
send info
Agree with Pasi on the example being invalid.

(Cullen Jennings; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Chris Newman; former steering group member) No Objection

No Objection (2008-11-06 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Agree with comments on ABNF/examples.

(Dan Romascanu; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(David Ward; former steering group member) No Objection

No Objection (2008-11-05 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
agree with other discusses but, will let them carry

(Jari Arkko; former steering group member) (was Discuss, No Objection) No Objection

No Objection (2008-11-06)
No email
send info
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 steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Magnus Westerlund; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Mark Townsley; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Pasi Eronen; former steering group member) No Objection

No Objection (2008-11-04 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
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 steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Tim Polk; former steering group member) No Objection

No Objection (2008-11-04 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
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...