[rfc-dist] RFC 6716 on Definition of the Opus Audio Codec

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Sep 10 17:15:25 PDT 2012

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

        RFC 6716

        Title:      Definition of the Opus Audio Codec 
        Author:     JM. Valin, K. Vos,
                    T. Terriberry
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2012
        Mailbox:    jmvalin at jmvalin.ca, 
                    koenvos74 at gmail.com, 
                    tterriberry at mozilla.com
        Pages:      326
        Characters: 977743
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-codec-opus-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6716.txt

This document defines the Opus interactive speech and audio codec.
Opus is designed to handle a wide range of interactive audio
applications, including Voice over IP, videoconferencing, in-game
chat, and even live, distributed music performances.  It scales from
low bitrate narrowband speech at 6 kbit/s to very high quality stereo
music at 510 kbit/s.  Opus uses both Linear Prediction (LP) and the
Modified Discrete Cosine Transform (MDCT) to achieve good compression
of both speech and music.  [STANDARDS-TRACK]

This document is a product of the Internet Wideband Audio Codec Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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 at 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

More information about the rfc-dist mailing list