2015-02-18 20:13 GMT+01:00 Maxime Marchand <
maxime.a...@gmail.com>:
> BFCP is part of the SDP and signalling handshake.
Not entirely true. BFCP is defined as a standalone protocol. The fact
that its data (floor IDs, etc) can be transmitted via SIP+SDP is just
an "usage" of BFCP. But remember that WebRTC is not about SIP.
> I would need an SDP that
> can support an "m=application <port> TCP/BFCP" line along with the
> associated "a" lines.
Yes. You can mangle and parse your SDP in order to add and retrieve
the BFCP stream:
https://www.npmjs.com/package/sdp-transform
The browser's WebRTC engine should just ignore/reject the BFCP media
stream (by setting its port to 0). That should work, and if not, it
should be reported to the browser vendor.
Anyhow, the fact that WebRTC uses SDP does not mean that it must
implement any SDP based stream.
> I believe this should be part of the WebRTC implementation if we want WebRTC
> to be part of the IMS world and support that aspect of conferencing.
I don't think we really want WebRTC to be part of the IMS world.
That's not the purpose of WebRTC.
> Is it confirmed that BFCP will NOT be part of WebRTC?
For sure.