draft-ietf-rtcweb-audio-02.txt   draft-ietf-rtcweb-audio-03.txt 
Network Working Group JM. Valin Network Working Group JM. Valin
Internet-Draft Mozilla Internet-Draft Mozilla
Intended status: Standards Track C. Bran Intended status: Standards Track C. Bran
Expires: February 03, 2014 Plantronics Expires: April 18, 2014 Plantronics
August 02, 2013 October 15, 2013
WebRTC Audio Codec and Processing Requirements WebRTC Audio Codec and Processing Requirements
draft-ietf-rtcweb-audio-02 draft-ietf-rtcweb-audio-03
Abstract Abstract
This document outlines the audio codec and processing requirements This document outlines the audio codec and processing requirements
for WebRTC client application and endpoint devices. for WebRTC client application and endpoint devices.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 03, 2014. This Internet-Draft will expire on April 18, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 33 skipping to change at page 2, line 33
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Codec Requirements 3. Codec Requirements
To ensure a baseline level of interoperability between WebRTC To ensure a baseline level of interoperability between WebRTC
clients, a minimum set of required codecs are specified below. While clients, a minimum set of required codecs are specified below. If
this section specifies the codecs that will be mandated for all other suitable audio codecs are available for the browser to use, it
WebRTC client implementations, it leaves the question of supporting is RECOMMENDED that they are also be included in the offer in order
additional codecs to the will of the implementer. to maximize the possibility to establish the session without the need
for audio transcoding.
WebRTC clients are REQUIRED to implement the following audio codecs. WebRTC clients are REQUIRED to implement the following audio codecs.
o Opus [RFC6716], with the payload format specified in [Opus-RTP] o Opus [RFC6716], with the payload format specified in [Opus-RTP]
and any ptime value up to 120 ms and any ptime value up to 120 ms
o G.711 PCMA and PCMU with one channel, a rate of 8000 Hz and a o G.711 PCMA and PCMU with one channel, a rate of 8000 Hz and a
ptime of 20 - see section 4.5.14 of [RFC3551] ptime of 20 - see section 4.5.14 of [RFC3551]
o Telephone Event - [RFC4733] o Telephone Event - [RFC4733]
 End of changes. 4 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/