[rtcweb] RFC 7874 on WebRTC Audio Codec and Processing Requirements

rfc-editor@rfc-editor.org Wed, 25 May 2016 23:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DDDF12DE3F; Wed, 25 May 2016 16:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 3CInYKlMzYYC; Wed, 25 May 2016 16:48:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6912E12DE2F; Wed, 25 May 2016 16:48:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9C0FD180006; Wed, 25 May 2016 16:48:04 -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
Message-Id: <20160525234804.9C0FD180006@rfc-editor.org>
Date: Wed, 25 May 2016 16:48:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/OrwpiU_9K3ds61MOLFJDThugzpI>
Cc: rtcweb@ietf.org, rfc-editor@rfc-editor.org
Subject: [rtcweb] RFC 7874 on WebRTC Audio Codec and Processing Requirements
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 23:48:43 -0000

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

        
        RFC 7874

        Title:      WebRTC Audio Codec and Processing 
                    Requirements 
        Author:     JM. Valin, C. Bran
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    jmvalin@jmvalin.ca, 
                    cary.bran@plantronics.com
        Pages:      7
        Characters: 16160
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-audio-11.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7874

This document outlines the audio codec and processing requirements
for WebRTC endpoints.

This document is a product of the Real-Time Communication in WEB-browsers 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