RFC 5018: Connection Establishment in the Binary Floor Control Protocol (BFCP)
In plain English — editorial summary, not part of the RFC
This document specifies how a Binary Floor Control Protocol (BFCP) client establishes a connection to a BFCP floor control server outside the context of an offer/answer exchange. Client and server authentication are based on Transport Layer Security (TLS). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5018
- Published
- September 2007
- Authors
- G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
- Updated by:
- RFC 8996
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 4934Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
May 2007
- RFC 4169Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2Current
November 2005
- RFC 3749Transport Layer Security Protocol Compression MethodsUpdated
May 2004
- RFC 3734Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
March 2004
- RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted
June 2003
- RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated
December 2002
- RFC 3268Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)Obsoleted
July 2002
- RFC 2817Upgrading to TLS Within HTTP/1.1Updated
May 2000
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?