Miscellaneous Capabilities Negotiation in the Session Description Protocol (SDP)
RFC 7006
Yes
No Objection
Note: This ballot was opened for revision 06 and is now closed.
(Gonzalo Camarillo; former steering group member) Yes
(Spencer Dawkins; former steering group member) Yes
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?
(Adrian Farrel; former steering group member) No Objection
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.
(Barry Leiba; former steering group member) No Objection
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?
(Benoît Claise; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
(Richard Barnes; former steering group member) No Objection
(Sean Turner; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
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.
(Stewart Bryant; former steering group member) No Objection
(Ted Lemon; former steering group member) No Objection