RFC 8852 on RTP Stream Identifier Source Description (SDES)
rfc-editor@rfc-editor.org Tue, 19 January 2021 22:54 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 7C6E53A1925; Tue, 19 Jan 2021 14:54:28 -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=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 GPAV4sYGmzOg; Tue, 19 Jan 2021 14:54:24 -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 BD83A3A18D2; Tue, 19 Jan 2021 14:54:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 832D7F40764; Tue, 19 Jan 2021 14:53:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8852 on RTP Stream Identifier Source Description (SDES)
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, avtext@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210119225355.832D7F40764@rfc-editor.org>
Date: Tue, 19 Jan 2021 14:53:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/uWh4CL5BVHehIRDxX49AmzqwwQQ>
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 22:54:34 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8852
Title: RTP Stream Identifier Source Description (SDES)
Author: A.B. Roach,
S. Nandakumar,
P. Thatcher
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: adam@nostrum.com,
snandaku@cisco.com,
pthatcher@gmail.com
Pages: 8
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avtext-rid-09.txt
URL: https://www.rfc-editor.org/info/rfc8852
DOI: 10.17487/RFC8852
This document defines and registers two new Real-time Transport
Control Protocol (RTCP) Stream Identifier Source Description (SDES)
items. One, named RtpStreamId, is used for unique identification of
RTP streams. The other, RepairedRtpStreamId, can be used to identify
which stream is to be repaired using a redundancy RTP stream.
This document is a product of the Audio/Video Transport Extensions 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