RFC 8285 on A General Mechanism for RTP Header Extensions
rfc-editor@rfc-editor.org Thu, 26 October 2017 00:23 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 A6C1B13F4F9; Wed, 25 Oct 2017 17:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 XKWGcVc4W1P3; Wed, 25 Oct 2017 17:23:35 -0700 (PDT)
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 BD8F513F501; Wed, 25 Oct 2017 17:23:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 20626B80E0D; Wed, 25 Oct 2017 17:23:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8285 on A General Mechanism for RTP Header Extensions
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, avt@ietf.org
Message-Id: <20171026002317.20626B80E0D@rfc-editor.org>
Date: Wed, 25 Oct 2017 17:23:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8GGzIHfdXWSbOYB0E1_V4VIMF_0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 26 Oct 2017 00:23:43 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8285
Title: A General Mechanism for RTP
Header Extensions
Author: D. Singer,
H. Desineni,
R. Even, Ed.
Status: Standards Track
Stream: IETF
Date: October 2017
Mailbox: singer@apple.com,
h3dnvb@gmail.com,
roni.even@huawei.com
Pages: 25
Characters: 54893
Obsoletes: RFC 5285
I-D Tag: draft-ietf-avtcore-rfc5285-bis-14.txt
URL: https://www.rfc-editor.org/info/rfc8285
DOI: 10.17487/RFC8285
This document provides a general mechanism to use the header
extension feature of RTP (the Real-time Transport Protocol). It
provides the option to use a small number of small extensions in each
RTP packet, where the universe of possible extensions is large and
registration is decentralized. The actual extensions in use in a
session are signaled in the setup information for that session. This
document obsoletes RFC 5285.
This document is a product of the Audio/Video Transport Core Maintenance 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