[bfcpbis] RFC 8857 on The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)

rfc-editor@rfc-editor.org Tue, 19 January 2021 22:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B2E3A1DE2; Tue, 19 Jan 2021 14:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.922
X-Spam-Level:
X-Spam-Status: No, score=-0.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEd-0Dd4lxWB; Tue, 19 Jan 2021 14:57:53 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4764E3A1A42; Tue, 19 Jan 2021 14:56:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D4A7F40780; Tue, 19 Jan 2021 14:56:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bfcpbis@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210119225620.0D4A7F40780@rfc-editor.org>
Date: Tue, 19 Jan 2021 14:56:20 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/te2t5H7k1NcBjohNgyVnX0ah1YE>
Subject: [bfcpbis] =?utf-8?q?RFC_8857_on_The_WebSocket_Protocol_as_a_Tran?= =?utf-8?q?sport_for_the_Binary_Floor_Control_Protocol_=28BFCP=29?=
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 22:58:01 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8857

        Title:      The WebSocket Protocol as a 
                    Transport for the Binary Floor Control 
                    Protocol (BFCP) 
        Author:     V. Pascual,
                    A. Román,
                    S. Cazeaux,
                    G. Salgueiro,
                    R. Ravindranath
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    victor.pascual_avila@nokia.com,
                    anton.roman@quobis.com,
                    stephane.cazeaux@orange.com,
                    gsalguei@cisco.com,
                    rmohanr@cisco.com
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bfcpbis-bfcp-websocket-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8857

        DOI:        10.17487/RFC8857

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

This document is a product of the Binary Floor Control Protocol Bis Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC