| rfc8857v5.txt | rfc8857.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) V. Pascual | Internet Engineering Task Force (IETF) V. Pascual | |||
| Request for Comments: 8857 Nokia | Request for Comments: 8857 Nokia | |||
| Category: Standards Track A. Román | Category: Standards Track A. Román | |||
| ISSN: 2070-1721 Quobis | ISSN: 2070-1721 Quobis | |||
| S. Cazeaux | S. Cazeaux | |||
| Orange | Orange | |||
| G. Salgueiro | G. Salgueiro | |||
| R. Ravindranath | R. Ravindranath | |||
| Cisco | Cisco | |||
| May 2020 | January 2021 | |||
| The WebSocket Protocol as a Transport for the Binary Floor Control | The WebSocket Protocol as a Transport for the Binary Floor Control | |||
| Protocol (BFCP) | Protocol (BFCP) | |||
| Abstract | Abstract | |||
| The WebSocket protocol enables two-way real-time communication | The WebSocket protocol enables two-way real-time communication | |||
| between clients and servers. This document specifies the use of | between clients and servers. This document specifies the use of | |||
| Binary Floor Control Protocol (BFCP) as a new WebSocket subprotocol | Binary Floor Control Protocol (BFCP) as a new WebSocket subprotocol | |||
| enabling a reliable transport mechanism between BFCP entities in new | enabling a reliable transport mechanism between BFCP entities in new | |||
| skipping to change at line 40 ¶ | skipping to change at line 40 ¶ | |||
| received public review and has been approved for publication by the | received public review and has been approved for publication by the | |||
| Internet Engineering Steering Group (IESG). Further information on | Internet Engineering Steering Group (IESG). Further information on | |||
| Internet Standards is available in Section 2 of RFC 7841. | Internet Standards is available in Section 2 of RFC 7841. | |||
| Information about the current status of this document, any errata, | Information about the current status of this document, any errata, | |||
| and how to provide feedback on it may be obtained at | and how to provide feedback on it may be obtained at | |||
| https://www.rfc-editor.org/info/rfc8857. | https://www.rfc-editor.org/info/rfc8857. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2021 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at line 106 ¶ | skipping to change at line 106 ¶ | |||
| Modern web browsers include a WebSocket client stack complying with | Modern web browsers include a WebSocket client stack complying with | |||
| the WebSocket API [WS-API] as specified by the W3C. It is expected | the WebSocket API [WS-API] as specified by the W3C. It is expected | |||
| that other client applications (those running in personal computers | that other client applications (those running in personal computers | |||
| and devices such as smartphones) will also make a WebSocket client | and devices such as smartphones) will also make a WebSocket client | |||
| stack available. This document extends the applicability of | stack available. This document extends the applicability of | |||
| [RFC8855] and [RFC8856] to enable the usage of BFCP in these | [RFC8855] and [RFC8856] to enable the usage of BFCP in these | |||
| scenarios. | scenarios. | |||
| The transport over which BFCP entities exchange messages depends on | The transport over which BFCP entities exchange messages depends on | |||
| how the clients obtain information to contact the floor control | how the clients obtain information to contact the floor control | |||
| server (e.g., using an Session Description Protocol (SDP) offer/ | server (e.g., using a Session Description Protocol (SDP) offer/answer | |||
| answer exchange per [RFC8856] or the procedure described in RFC 5018 | exchange per [RFC8856] or the procedure described in RFC 5018 | |||
| [RFC5018]). [RFC8855] defines two transports for BFCP: TCP and UDP. | [RFC5018]). [RFC8855] defines two transports for BFCP: TCP and UDP. | |||
| This specification defines a new WebSocket subprotocol (as defined in | This specification defines a new WebSocket subprotocol (as defined in | |||
| Section 1.9 of [RFC6455]) for transporting BFCP messages between a | Section 1.9 of [RFC6455]) for transporting BFCP messages between a | |||
| WebSocket client and server. This subprotocol provides a reliable | WebSocket client and server. This subprotocol provides a reliable | |||
| and boundary-preserving transport for BFCP when run on top of TCP. | and boundary-preserving transport for BFCP when run on top of TCP. | |||
| Since WebSocket provides a reliable transport, the extensions defined | Since WebSocket provides a reliable transport, the extensions defined | |||
| in [RFC8855] for sending BFCP over unreliable transports are not | in [RFC8855] for sending BFCP over unreliable transports are not | |||
| applicable. | applicable. | |||
| 2. Terminology | 2. Terminology | |||
| skipping to change at line 467 ¶ | skipping to change at line 467 ¶ | |||
| Subprotocol Definition: RFC 8857 | Subprotocol Definition: RFC 8857 | |||
| 10.2. Registration of the 'TCP/WS/BFCP' and 'TCP/WSS/BFCP' SDP "proto" | 10.2. Registration of the 'TCP/WS/BFCP' and 'TCP/WSS/BFCP' SDP "proto" | |||
| Values | Values | |||
| This document defines two new values for the SDP "proto" subregistry | This document defines two new values for the SDP "proto" subregistry | |||
| within the "Session Description Protocol (SDP) Parameters" registry. | within the "Session Description Protocol (SDP) Parameters" registry. | |||
| The resulting entries are shown in Table 1: | The resulting entries are shown in Table 1: | |||
| +--------------+-----------+ | +==============+===========+ | |||
| | Value | Reference | | | Value | Reference | | |||
| +==============+===========+ | +==============+===========+ | |||
| | TCP/WS/BFCP | RFC 8857 | | | TCP/WS/BFCP | RFC 8857 | | |||
| +--------------+-----------+ | +--------------+-----------+ | |||
| | TCP/WSS/BFCP | RFC 8857 | | | TCP/WSS/BFCP | RFC 8857 | | |||
| +--------------+-----------+ | +--------------+-----------+ | |||
| Table 1: Values for the | Table 1: Values for the | |||
| SDP "proto" Field | SDP "proto" Field | |||
| skipping to change at line 518 ¶ | skipping to change at line 518 ¶ | |||
| Description Protocol (SDP) WebSocket Connection URI | Description Protocol (SDP) WebSocket Connection URI | |||
| Attribute", RFC 8124, DOI 10.17487/RFC8124, March 2017, | Attribute", RFC 8124, DOI 10.17487/RFC8124, March 2017, | |||
| <https://www.rfc-editor.org/info/rfc8124>. | <https://www.rfc-editor.org/info/rfc8124>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| [RFC8855] Camarillo, G., Drage, K., Kristensen, T., Ott, J., and C. | [RFC8855] Camarillo, G., Drage, K., Kristensen, T., Ott, J., and C. | |||
| Eckel, "The Binary Floor Control Protocol (BFCP)", | Eckel, "The Binary Floor Control Protocol (BFCP)", | |||
| RFC 8855, DOI 10.17487/RFC8855, May 2020, | RFC 8855, DOI 10.17487/RFC8855, January 2021, | |||
| <https://www.rfc-editor.org/info/rfc8855>. | <https://www.rfc-editor.org/info/rfc8855>. | |||
| [RFC8856] Camarillo, G., Kristensen, T., and C. Holmberg, "Session | [RFC8856] Camarillo, G., Kristensen, T., and C. Holmberg, "Session | |||
| Description Protocol (SDP) Format for Binary Floor Control | Description Protocol (SDP) Format for Binary Floor Control | |||
| Protocol (BFCP) Streams", RFC 8856, DOI 10.17487/RFC8856, | Protocol (BFCP) Streams", RFC 8856, DOI 10.17487/RFC8856, | |||
| May 2020, <https://www.rfc-editor.org/info/rfc8856>. | January 2021, <https://www.rfc-editor.org/info/rfc8856>. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265, | [RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265, | |||
| DOI 10.17487/RFC6265, April 2011, | DOI 10.17487/RFC6265, April 2011, | |||
| <https://www.rfc-editor.org/info/rfc6265>. | <https://www.rfc-editor.org/info/rfc6265>. | |||
| [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer | |||
| Protocol (HTTP/1.1): Message Syntax and Routing", | Protocol (HTTP/1.1): Message Syntax and Routing", | |||
| RFC 7230, DOI 10.17487/RFC7230, June 2014, | RFC 7230, DOI 10.17487/RFC7230, June 2014, | |||
| End of changes. 6 change blocks. | ||||
| 7 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||