RFC 7587 on RTP Payload Format for the Opus Speech and Audio Codec
rfc-editor@rfc-editor.org Tue, 30 June 2015 23:36 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D47131B2A68; Tue, 30 Jun 2015 16:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 S_XsEBv44GHs; Tue, 30 Jun 2015 16:36:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4281B2A60; Tue, 30 Jun 2015 16:36:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A955D18046B; Tue, 30 Jun 2015 16:33:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7587 on RTP Payload Format for the Opus Speech and Audio Codec
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150630233317.A955D18046B@rfc-editor.org>
Date: Tue, 30 Jun 2015 16:33:17 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/TJBAB9ES3RldIk8z87cEifAa_ko>
Cc: drafts-update-ref@iana.org, payload@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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, 30 Jun 2015 23:36:30 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7587
Title: RTP Payload Format for the
Opus Speech and Audio Codec
Author: J. Spittka, K. Vos, JM. Valin
Status: Standards Track
Stream: IETF
Date: June 2015
Mailbox: jspittka@gmail.com,
koenvos74@gmail.com,
jmvalin@jmvalin.ca
Pages: 18
Characters: 41770
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-rtp-opus-11.txt
URL: https://www.rfc-editor.org/info/rfc7587
DOI: http://dx.doi.org/10.17487/RFC7587
This document defines the Real-time Transport Protocol (RTP) payload
format for packetization of Opus-encoded speech and audio data
necessary to integrate the codec in the most compatible way. It also
provides an applicability statement for the use of Opus over RTP.
Further, it describes media type registrations for the RTP payload
format.
This document is a product of the Audio/Video Transport Payloads 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/rfc.html
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