[bfcpbis] RFC 8855 on The Binary Floor Control Protocol (BFCP)

rfc-editor@rfc-editor.org Tue, 19 January 2021 22:55 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 A72973A18CD; Tue, 19 Jan 2021 14:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 LQCbvAgTwVxc; Tue, 19 Jan 2021 14:55:38 -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 5A9113A1999; Tue, 19 Jan 2021 14:55:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 22A2EF40763; Tue, 19 Jan 2021 14:54:53 -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: <20210119225453.22A2EF40763@rfc-editor.org>
Date: Tue, 19 Jan 2021 14:54:53 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/Bm6IMnwj8FmNy87PpWy2w6Y53Ss>
Subject: [bfcpbis] =?utf-8?q?RFC_8855_on_The_Binary_Floor_Control_Protoco?= =?utf-8?q?l_=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:55:46 -0000

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

        
        RFC 8855

        Title:      The Binary Floor Control Protocol (BFCP) 
        Author:     G. Camarillo,
                    K. Drage,
                    T. Kristensen,
                    J. Ott,
                    C. Eckel
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    gonzalo.camarillo@ericsson.com,
                    drageke@ntlworld.com,
                    tom.kristensen@jotron.com,
                    ott@in.tum.de,
                    eckelcu@cisco.com
        Pages:      87
        Obsoletes:  RFC 4582

        I-D Tag:    draft-ietf-bfcpbis-rfc4582bis-16.txt

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

        DOI:        10.17487/RFC8855

Floor control is a means to manage joint or exclusive access to
shared resources in a (multiparty) conferencing environment. Thereby,
floor control complements other functions -- such as conference and
media session setup, conference policy manipulation, and media
control -- that are realized by other protocols.

This document specifies the Binary Floor Control Protocol (BFCP).
BFCP is used between floor participants and floor control servers,
and between floor chairs (i.e., moderators) and floor control
servers.

This document obsoletes RFC 4582.

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