<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bfcpbis-rfc4582bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-bfcpbis-rfc4582bis-16">
   <front>
      <title>The Binary Floor Control Protocol (BFCP)</title>
      <author initials="G." surname="Camarillo" fullname="Gonzalo Camarillo">
         <organization>Ericsson</organization>
      </author>
      <author initials="K." surname="Drage" fullname="Keith Drage">
         <organization>Alcatel-Lucent</organization>
      </author>
      <author initials="T." surname="Kristensen" fullname="Tom Kristensen">
         <organization>Cisco</organization>
      </author>
      <author initials="J." surname="Ott" fullname="Joerg Ott">
         <organization>Aalto University</organization>
      </author>
      <author initials="C." surname="Eckel" fullname="Charles Eckel">
         <organization>Cisco</organization>
      </author>
      <date month="November" day="13" year="2015" />
      <abstract>
	 <t>Floor control is a means to manage joint or exclusive access to shared resources in a (multiparty) conferencing environment. Thereby, floor control complements other functions -- such as conference and media session setup, conference policy manipulation, and media control -- that are realized by other protocols.

 This document specifies the Binary Floor Control Protocol (BFCP). BFCP is used between floor participants and floor control servers, and between floor chairs (i.e., moderators) and floor control servers.

 This document obsoletes RFC 4582.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bfcpbis-rfc4582bis-16" />
   
</reference>
