RFC 8858 on Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)

rfc-editor@rfc-editor.org Tue, 19 January 2021 00:46 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 7539F3A0D3E; Mon, 18 Jan 2021 16:46:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 5Sni9KgOAfIw; Mon, 18 Jan 2021 16:46:23 -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 E84D03A0B37; Mon, 18 Jan 2021 16:46:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2F75BF40794; Mon, 18 Jan 2021 16:46:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4NTggb24gSW5kaWNhdGluZyBFeGNsdXNpdmUgU3VwcG9ydCBvZiBSVFAgYW5kIFJUUCBDb250cm9sIFByb3RvY29sIChSVENQKSBNdWx0aXBsZXhpbmcgVXNpbmcgdGhlIFNlc3Npb24gRGVzY3JpcHRpb24gUHJvdG9jb2wgKFNEUCk=?=
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: <20210119004606.2F75BF40794@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:46:06 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MULirZloLgBcCb6Kj6SwDlw3jdg>
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: Tue, 19 Jan 2021 00:46:26 -0000

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

        
        RFC 8858

        Title:      Indicating Exclusive Support of RTP and
                    RTP Control Protocol (RTCP) Multiplexing 
                    Using the Session Description Protocol (SDP) 
        Author:     C. Holmberg
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    christer.holmberg@ericsson.com
        Pages:      9
        Updates:    RFC 5761

        I-D Tag:    draft-ietf-mmusic-mux-exclusive-12.txt

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

        DOI:        10.17487/RFC8858

This document defines a new Session Description Protocol (SDP)
media-level attribute, 'rtcp-mux-only', that can be used by an
endpoint to indicate exclusive support of RTP and RTP Control
Protocol (RTCP) multiplexing. The document also updates RFC 5761 by
clarifying that an offerer can use a mechanism to indicate that it is
not able to send and receive RTCP on separate ports.

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