Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
draft-ietf-mmusic-sdp-bfcp-03
Yes
(Allison Mankin)
No Objection
(Alex Zinin)
(Bill Fenner)
(Brian Carpenter)
(David Kessens)
(Jon Peterson)
(Margaret Cullen)
(Mark Townsley)
(Russ Housley)
(Scott Hollenbeck)
(Ted Hardie)
Note: This ballot was opened for revision 03 and is now closed.
Allison Mankin Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Bert Wijnen Former IESG member
No Objection
No Objection
(2005-09-01)
Unknown
This document has a normative reference:
[9] Levin, O. and G. Camarillo, "The SDP (Session Description
Protocol) Label Attribute",
draft-levin-mmmusic-sdp-media-label-00 (work in progress),
July 2004.
and that document is an individual Internet-Draft, that also has expired.
So what impact does this have?
Bill Fenner Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
No Objection
No Objection
()
Unknown
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
(was Discuss)
No Objection
No Objection
(2005-08-31)
Unknown
I'm not sure I see a way that a server can offer both a TLS and non-TLS stream using this media type. If clients end up being required to support TLS tihs probably doesn't matter. However it may be an issue if clients are not required to support TLS. Perhaps I'm missing some information about how offer/answer works. It definitely seems that two m lines would be wrong because then a client could accept both of them.
Scott Hollenbeck Former IESG member
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown