[bfcpbis] RFC 8856 on Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
rfc-editor@rfc-editor.org Tue, 19 January 2021 22:56 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 23E253A1C84; Tue, 19 Jan 2021 14:56:59 -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 QvSElxJwX6iC; Tue, 19 Jan 2021 14:56:57 -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 CF3543A1B59; Tue, 19 Jan 2021 14:55:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9E15AF4076A; Tue, 19 Jan 2021 14:55:40 -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: <20210119225540.9E15AF4076A@rfc-editor.org>
Date: Tue, 19 Jan 2021 14:55:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/peL6lshPT16t6pUueBHr8ktvZgM>
Subject: [bfcpbis] RFC 8856 on Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams
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:57:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8856
Title: Session Description Protocol (SDP) Format
for Binary Floor Control Protocol (BFCP)
Streams
Author: G. Camarillo,
T. Kristensen,
C. Holmberg
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: gonzalo.camarillo@ericsson.com,
tom.kristensen@jotron.com,
tomkri@ifi.uio.no,
christer.holmberg@ericsson.com
Pages: 22
Obsoletes: RFC 4583
I-D Tag: draft-ietf-bfcpbis-rfc4583bis-27.txt
URL: https://www.rfc-editor.org/info/rfc8856
DOI: 10.17487/RFC8856
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.
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