[codec] RFC 8486 on Ambisonics in an Ogg Opus Container

rfc-editor@rfc-editor.org Mon, 29 October 2018 19:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B46BB13106F; Mon, 29 Oct 2018 12:17:40 -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 MMUTVTxexgj1; Mon, 29 Oct 2018 12:17:39 -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 66D091252B7; Mon, 29 Oct 2018 12:17:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A9D89B822BC; Mon, 29 Oct 2018 12:17:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, codec@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20181029191732.A9D89B822BC@rfc-editor.org>
Date: Mon, 29 Oct 2018 12:17:32 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/codec/ysUb_UeavQfk0rl3i15BX3s0YD4>
Subject: [codec] =?utf-8?q?RFC_8486_on_Ambisonics_in_an_Ogg_Opus_Containe?= =?utf-8?q?r?=
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codec/>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Oct 2018 19:17:41 -0000

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

        
        RFC 8486

        Title:      Ambisonics in an Ogg Opus Container 
        Author:     J. Skoglund,
                    M. Graczyk
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2018
        Mailbox:    jks@google.com, 
                    michael@mgraczyk.com
        Pages:      10
        Characters: 22832
        Updates:    RFC 7845

        I-D Tag:    draft-ietf-codec-ambisonics-10.txt

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

        DOI:        10.17487/RFC8486

This document defines an extension to the Opus audio codec to
encapsulate coded Ambisonics using the Ogg format.  It also contains
updates to RFC 7845 to reflect necessary changes in the description
of channel mapping families.

This document is a product of the Internet Wideband Audio Codec 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