RFC 8864 on Negotiation Data Channels Using the Session Description Protocol (SDP)

rfc-editor@rfc-editor.org Wed, 20 January 2021 00:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E6D3A09EF; Tue, 19 Jan 2021 16:21:22 -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 1pR0HdF5mli8; Tue, 19 Jan 2021 16:21:20 -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 A0ABF3A09EC; Tue, 19 Jan 2021 16:21:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CDE1F4075A; Tue, 19 Jan 2021 16:21:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4NjQgb24gTmVnb3RpYXRpb24gRGF0YSBDaGFubmVscyBVc2luZyB0aGUgU2Vzc2lvbiBEZXNjcmlwdGlvbiBQcm90b2NvbCAoU0RQKQ==?=
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, mmusic@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210120002104.4CDE1F4075A@rfc-editor.org>
Date: Tue, 19 Jan 2021 16:21:04 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/duc4ISsKTuovI9Z3Nd1B4KCzyvE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2021 00:21:22 -0000

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

        
        RFC 8864

        Title:      Negotiation Data Channels Using the 
                    Session Description Protocol (SDP) 
        Author:     K. Drage,
                    M. Makaraju,
                    R. Ejzak,
                    J. Marcon,
                    R. Even, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    drageke@ntlworld.com,
                    mmraju@gmail.com,
                    richard.ejzak@gmail.com,
                    jeromee.marcon@free.fr,
                    ron.even.tlv@gmail.com
        Pages:      24
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mmusic-data-channel-sdpneg-28.txt

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

        DOI:        10.17487/RFC8864

Data channel setup can be done using either the in-band Data Channel
Establishment Protocol (DCEP) or some out-of-band non-DCEP protocol. 
This document specifies how the SDP (Session Description Protocol)
offer/answer exchange can be used to achieve an out-of-band non-DCEP
negotiation for establishing a data channel.

This document is a product of the Multiparty Multimedia Session Control 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