Miscellaneous Capabilities Negotiation in the Session Description Protocol (SDP)
draft-ietf-mmusic-sdp-miscellaneous-caps-07

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

(Gonzalo Camarillo) Yes

(Spencer Dawkins) Yes

Comment (2013-06-21 for -06)
No email
send info
I was able to guess at bcap and ccap, but not at icap (title), and I had to scan for a while to decode that. The 4th occurrence of "title" finally said "*media* title" capability - that helped. 

Could you consider moving "media title" to the first occurrence of "title" in the doc?

(Jari Arkko) No Objection

(Richard Barnes) No Objection

(Stewart Bryant) No Objection

(Benoît Claise) No Objection

(Adrian Farrel) No Objection

Comment (2013-06-27 for -06)
No email
send info
I think it would be helpful to add a reminder of how legacy
implementations and those that do not support the new capability 
negotiations will react when they are attempted. This is probably just
a simple one line statement and a reference.

(Stephen Farrell) No Objection

Comment (2013-06-26 for -06)
No email
send info
Are these possibly missing security considerations?

- The bandwidth capability could be used as part of
a DoS if reservations are made based on bad values.
For example, if Alice gets lots of bandwidth reserved
then Bob might not be able to do stuff.

- A premium-rate number could be included in the 
PSTN thingy.

Barry Leiba No Objection

Comment (2013-06-21 for -06)
No email
send info
As I read the internationalization paragraph in Section 3.1.3, I find that I would appreciate an example that shows two titles for the same content, in different character sets.  Can you add such an example?

(Ted Lemon) No Objection

(Pete Resnick) No Objection

(Martin Stiemerling) No Objection

(Sean Turner) No Objection