RFC 4583: Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8856.
Current version: RFC 8856 — Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
In plain English — editorial summary, not part of the RFC
This document specifies how to describe Binary Floor Control Protocol (BFCP) streams in Session Description Protocol (SDP) descriptions. User agents using the offer/answer model to establish BFCP streams use this format in their offers and answers. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4583
- Published
- November 2006
- Authors
- G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 8856
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4574The Session Description Protocol (SDP) Label AttributeCurrent
August 2006
- RFC 4572Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)Obsoleted
July 2006
- RFC 4570Session Description Protocol (SDP) Source FiltersCurrent
July 2006
- RFC 4568Session Description Protocol (SDP) Security Descriptions for Media StreamsCurrent
July 2006
- RFC 4567Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)Current
July 2006
- RFC 4566SDP: Session Description ProtocolObsoleted
July 2006
- RFC 4686Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)Current
September 2006
- RFC 4473Requirements for Internet Media Guides (IMGs)Current
May 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?