Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
Note: This ballot was opened for revision 03 and is now closed.
(Allison Mankin) Yes
(Brian Carpenter) No Objection
(Margaret Cullen) No Objection
(Bill Fenner) (was Discuss) No Objection
(Ted Hardie) No Objection
(Sam Hartman) (was Discuss) No Objection
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) No Objection
(Russ Housley) (was Discuss) No Objection
(David Kessens) No Objection
(Jon Peterson) No Objection
(Mark Townsley) No Objection
(Bert Wijnen) No Objection
Comment (2005-09-01 for -)
This document has a normative reference:  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?