The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)
draft-ietf-bfcpbis-bfcp-websocket-15

Document Type Active Internet-Draft (bfcpbis WG)
Last updated 2017-02-17 (latest revision 2017-02-08)
Replaces draft-pascual-bfcpbis-bfcp-websocket
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Nov 2016 - Draft for BFCP over ... )
Document shepherd Charles Eckel
Shepherd write-up Show (last changed 2016-11-10)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to "Charles Eckel" <eckelcu@cisco.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state MISSREF
BFCPBIS Working Group                                         V. Pascual
Internet-Draft                                                    Oracle
Intended status: Standards Track                                A. Roman
Expires: August 12, 2017                                          Quobis
                                                              S. Cazeaux
                                                   France Telecom Orange
                                                            G. Salgueiro
                                                         R. Ravindranath
                                                                   Cisco
                                                        February 8, 2017

   The WebSocket Protocol as a Transport for the Binary Floor Control
                            Protocol (BFCP)
                  draft-ietf-bfcpbis-bfcp-websocket-15

Abstract

   The WebSocket protocol enables two-way realtime communication between
   clients and servers.  This document specifies the use of Binary Floor
   Control Protocol(BFCP) as a new WebSocket sub-protocol enabling a
   reliable transport mechanism between BFCP entities in new scenarios.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 12, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Pascual, et al.          Expires August 12, 2017                [Page 1]
Internet-Draft      WebSocket as a Transport for BFCP      February 2017

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The WebSocket Protocol  . . . . . . . . . . . . . . . . . . .   3
   4.  The WebSocket BFCP Sub-Protocol . . . . . . . . . . . . . . .   4
     4.1.  Handshake . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  BFCP Encoding . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Transport Reliability . . . . . . . . . . . . . . . . . . . .   5
   6.  SDP Considerations  . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Transport Negotiation . . . . . . . . . . . . . . . . . .   6
     6.2.  SDP Media Attributes  . . . . . . . . . . . . . . . . . .   6
   7.  SDP Offer/Answer Procedures . . . . . . . . . . . . . . . . .   7
     7.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.2.  Example Usage of 'websocket-uri' SDP Attribute  . . . . .   7
   8.  Authentication  . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Registration of the WebSocket BFCP Sub-Protocol  . . . .  10
     10.2.  Registration of the 'TCP/WS/BFCP' and 'TCP/WSS/BFCP' SDP
            'proto' Values . . . . . . . . . . . . . . . . . . . . .  11
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     12.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The WebSocket(WS) [RFC6455] protocol enables two-way message exchange
   between clients and servers on top of a persistent TCP connection,
   optionally secured with Transport Layer Security (TLS) [RFC5246].
Show full document text