RFC 4582: The Binary Floor Control Protocol (BFCP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8855.
Current version: RFC 8855 — The Binary Floor Control Protocol (BFCP)
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4582
- Published
- November 2006
- Authors
- G. Camarillo; J. Ott; K. Drage
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 65
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 1890RTP Profile for Audio and Video Conferences with Minimal ControlObsoleted
January 1996
- RFC 6464A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level IndicationCurrent
December 2011
- RFC 6465A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level IndicationCurrent
December 2011
- RFC 9071RTP-Mixer Formatting of Multiparty Real-Time TextCurrent
July 2021
- RFC 4585Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)Updated
July 2006
- RFC 4579Session Initiation Protocol (SIP) Call Control - Conferencing for User AgentsCurrent
August 2006
- RFC 4587RTP Payload Format for H.261 Video StreamsCurrent
August 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?