<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.schwarz-mmusic-bfcp-usage-data-channel" target="https://datatracker.ietf.org/doc/html/draft-schwarz-mmusic-bfcp-usage-data-channel-02">
   <front>
      <title>BFCP floor control signalling over Data Channels</title>
      <author initials="K." surname="Drage" fullname="Keith Drage">
         <organization>Nokia</organization>
      </author>
      <author initials="J." surname="Stoetzer-Bradler" fullname="Juergen Stoetzer-Bradler">
         <organization>Nokia</organization>
      </author>
      <author initials="A." surname="Schwarz" fullname="Albrecht Schwarz">
         <organization>Nokia</organization>
      </author>
      <date month="April" day="4" year="2016" />
      <abstract>
	 <t>   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).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-schwarz-mmusic-bfcp-usage-data-channel-02" />
   
</reference>
