BFCP floor control signalling over Data Channels
draft-schwarz-mmusic-bfcp-usage-data-channel-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Keith Drage , Juergen Stoetzer-Bradler , Albrecht Schwarz | ||
| Last updated | 2016-10-06 (Latest revision 2016-04-04) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies how the Binary Floor Control Protocol (BFCP) can be instantiated as a data channel sub-protocol, using the SDP offer/answer exchange-based external negotiation defined in [I- D.ietf-mmusic-data-channel-sdpneg]. Two network configurations are documented: a WebRTC end-to-end configuration (connecting two BFCP over data channel endpoints), and a gateway configuration (connecting an BFCP over data channel endpoint with an BFCP over (TLS)/TCP/IP (or over (DTLS)/UDP/IP) endpoint).
Authors
Keith Drage
Juergen Stoetzer-Bradler
Albrecht Schwarz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)