RFC 4376: Requirements for Floor Control Protocols
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 defines the requirements for a floor control protocol for multiparty conferences in the context of an existing framework. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4376
- Published
- February 2006
- Authors
- P. Koskelainen; J. Ott; H. Schulzrinne; X. Wu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4375Emergency Telecommunications Services (ETS) Requirements for a Single Administrative DomainCurrent
January 2006
- RFC 4396RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed TextCurrent
February 2006
- RFC 4355IANA Registration for Enumservices email, fax, mms, ems, and smsUpdated
January 2006
- RFC 4353A Framework for Conferencing with the Session Initiation Protocol (SIP)Current
February 2006
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4351Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio StreamCurrent
January 2006
- RFC 4348Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio CodecUpdated
January 2006
- RFC 4411Extending the Session Initiation Protocol (SIP) Reason Header for Preemption EventsCurrent
February 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?