Last Call: <draft-ietf-rtcweb-audio-codecs-for-interop-05.txt> (Additional WebRTC audio codecs for interoperability.) to Informational RFC

The IESG <> Wed, 24 February 2016 21:32 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 1CD3F1B2D0D; Wed, 24 Feb 2016 13:32:03 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-rtcweb-audio-codecs-for-interop-05.txt> (Additional WebRTC audio codecs for interoperability.) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Wed, 24 Feb 2016 13:32:03 -0800
Archived-At: <>
Cc:,,, Cullen Jennings <>,
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 24 Feb 2016 21:32:03 -0000

The IESG has received a request from the Real-Time Communication in
WEB-browsers WG (rtcweb) to consider the following document:
- 'Additional WebRTC audio codecs for interoperability.'
  <draft-ietf-rtcweb-audio-codecs-for-interop-05.txt> as Informational

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-03-09. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   To ensure a baseline level of interoperability between WebRTC
   endpoints, a minimum set of required codecs is specified.  However,
   to maximize the possibility to establish the session without the need
   for audio transcoding, it is also recommended to include in the offer
   other suitable audio codecs that are available to the browser.

   This document provides some guidelines on the suitable codecs to be
   considered for WebRTC endpoints to address the most relevant
   interoperability use cases.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.