Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
RFC 8856
| Document | Type |
RFC - Proposed Standard
(January 2021; No errata)
Obsoletes RFC 4583
|
||||
|---|---|---|---|---|---|---|
| Authors | Gonzalo Camarillo , Tom Kristensen , Christer Holmberg | |||||
| Last updated | 2021-01-19 | |||||
| Stream | Internent Engineering Task Force (IETF) | |||||
| Formats | plain text html xml pdf htmlized (tools) htmlized bibtex | |||||
| Reviews | ||||||
| Additional Resources |
|
|||||
| Stream | WG state | Submitted to IESG for Publication | ||||
| Document shepherd | Mary Barnes | |||||
| Shepherd write-up | Show (last changed 2018-08-29) | |||||
| IESG | IESG state | RFC 8856 (Proposed Standard) | ||||
| Action Holders |
(None)
|
|||||
| Consensus Boilerplate | Yes | |||||
| Telechat date | ||||||
| Responsible AD | Adam Roach | |||||
| Send notices to | (None) | |||||
| IANA | IANA review state | Version Changed - Review Needed | ||||
| IANA action state | RFC-Ed-Ack | |||||
Internet Engineering Task Force (IETF) G. Camarillo
Request for Comments: 8856 Ericsson
Obsoletes: 4583 T. Kristensen
Category: Standards Track Jotron
ISSN: 2070-1721 C. Holmberg
Ericsson
January 2021
Session Description Protocol (SDP) Format for Binary Floor Control
Protocol (BFCP) Streams
Abstract
This document defines the Session Description Protocol (SDP) offer/
answer procedures for negotiating and establishing Binary Floor
Control Protocol (BFCP) streams.
This document obsoletes RFC 4583.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8856.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction
2. Conventions
3. Floor Control Roles
4. Fields in the "m=" Line
5. SDP Attributes
5.1. SDP 'floorctrl' Attribute
5.2. SDP 'confid' Attribute
5.3. SDP 'userid' Attribute
5.4. SDP 'floorid' Attribute
5.5. SDP 'bfcpver' Attribute
6. Multiplexing Considerations
7. BFCP Connection Management
7.1. TCP Connection Management
8. TLS/DTLS Considerations
9. ICE Considerations
10. SDP Offer/Answer Procedures
10.1. Generating the Initial SDP Offer
10.2. Generating the SDP Answer
10.3. Offerer Processing of the SDP Answer
10.4. Modifying the Session
11. Examples
12. Security Considerations
13. IANA Considerations
13.1. Registration of SDP 'proto' Values
13.2. Registration of the SDP 'floorctrl' Attribute
13.3. Registration of the SDP 'confid' Attribute
13.4. Registration of the SDP 'userid' Attribute
13.5. Registration of the SDP 'floorid' Attribute
13.6. Registration of the SDP 'bfcpver' Attribute
14. Changes from RFC 4583
15. References
15.1. Normative References
15.2. Informative References
Acknowledgements
Authors' Addresses
1. Introduction
As discussed in the BFCP (Binary Floor Control Protocol)
specification [RFC8855], a given BFCP client needs a set of data in
order to establish a BFCP connection to a floor control server. This
data includes the transport address of the server, the conference
identifier, and the user identifier.
One way for clients to obtain this information is to use a Session
Description Protocol (SDP) offer/answer exchange [RFC3264]. This
document specifies how to encode this information in the SDP session
descriptions that are part of such an offer/answer exchange.
User agents typically use the offer/answer model to establish a
number of media streams of different types. Following this model, a
BFCP connection is described as any other media stream by using an
SDP "m=" line, possibly followed by a number of SDP lines that also
apply to the BFCP connection.
Section 4 defines how the field values in an "m=" line representing a
BFCP connection are set.
Section 5 defines SDP attributes that are used when negotiating a
BFCP connection.
Section 6 defines multiplexing considerations for a BFCP connection.
Section 7 defines procedures for managing a BFCP connection.
Section 8 defines TLS and DTLS considerations when negotiating a BFCP
connection.
Section 9 defines considerations regarding Interactive Connectivity
Establishment (ICE) [RFC8445] when negotiating a BFCP connection.
Section 10 defines the SDP offer/answer procedures for negotiating a
BFCP connection.
This document obsoletes RFC 4583 [RFC4583]. Section 14 summarizes
Show full document text