idnits 2.17.1 draft-cbran-rtcweb-codec-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(ii) Publication Limitation clause. If this document is intended for submission to the IESG for publication, this constitutes an error. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 29, 2011) is 4562 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- No information found for draft-ekr-security-considerations-for-rtc-web - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'I-D.ekr-security-considerations-for-rtc-web' -- No information found for draft-webm - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'I-D.webm' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Bran 3 Internet-Draft Plantronics 4 Intended status: Standards Track C. Jennings 5 Expires: May 1, 2012 Cisco 6 October 29, 2011 8 WebRTC Codec and Media Processing Requirements 9 draft-cbran-rtcweb-codec-01 11 Abstract 13 This document outlines the codec and media processing requirements 14 for WebRTC client application and endpoint devices. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. This document may not be modified, 20 and derivative works of it may not be created, and it may not be 21 published except as an Internet-Draft. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on May 1, 2012. 35 Copyright Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. Codec Requirements . . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Audio Codec Requirements . . . . . . . . . . . . . . . . . 3 56 3.2. Video Codec Requirements . . . . . . . . . . . . . . . . . 3 57 4. WebRTC Client Requirements . . . . . . . . . . . . . . . . . . 4 58 5. Legacy VoIP Interoperability . . . . . . . . . . . . . . . . . 5 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 61 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 62 9. Normative References . . . . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 65 1. Introduction 67 An integral part of the success and adoption of the Web Real Time 68 Communications (WebRTC) will be the voice and video interoperability 69 between WebRTC applications. This specification will outline the 70 media processing and codec requirements for WebRTC client 71 implementations. 73 2. Terminology 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 77 document are to be interpreted as described in RFC 2119 [RFC2119]. 79 3. Codec Requirements 81 This section covers the audio and video codec requirements for WebRTC 82 client applications. To ensure a baseline level of interoperability 83 between WebRTC clients, a minimum set of required codecs are 84 specified below. While this section specifies the codecs that will 85 be mandated for all WebRTC client implementations, it leaves the 86 question of supporting additional codecs to the will of the 87 implementer. 89 3.1. Audio Codec Requirements 91 WebRTC clients are REQUIRED to implement the following audio codecs. 93 o PCMA/PCMU - 1 channel with a rate of 8000 Hz and a ptime of 20 - 94 see section 4.5.14 of [RFC3551] 96 o Telephone Event - [RFC4734] 98 o Opus [draft-ietf-codec-opus] 100 3.2. Video Codec Requirements 102 If the MPEG-LA issues an intent to offer H.264 baseline profile on a 103 royalty free basis for use in browsers before March 15, 2012, then 104 the REQUIRED video codecs will be H.264 baseline. If this does not 105 happen by that the date, then the REQUIRED video codec will be VP8 106 [I-D.webm]. 108 The following feature list applies to all required video codecs. 110 Required video codecs: 112 o MUST support at least 10 frames per second (fps) and SHOULD 113 support 30 fps 115 o If VP8, then MUST support a the bilinear and none reconstruction 116 filters 118 o OPTIONALLY offer support for additional color spaces 120 o MUST support a minimum resolution of 320X240 122 o SHOULD support resolutions of 1280x720, 720x480, 1024x768, 123 800x600, 640x480, 640 x 360 , 320x240 125 4. WebRTC Client Requirements 127 It is plausible that the dominant near to mid-term WebRTC usage model 128 will be people using the interactive audio and video capabilities to 129 communicate with each other via web browsers running on a notebook 130 computer that has built-in microphone and speakers. The notebook-as- 131 communication-device paradigm presents challenging echo cancellation 132 and audio gain problems, the specific remedy of which will not be 133 mandated here. However, while no specific algorithm or standard will 134 be required by WebRTC compatible clients, functionality such as 135 automatic gain control, echo cancellation, headset detection and 136 passing call control events to connected devices will improve the 137 user experience and should be implemented by the endpoint device. 139 To address the problems outlined above, suitable implementations of 140 the functionality listed below SHOULD be available within an RTC-Web 141 endpoint device. 143 o Automatic gain control 145 o Ability to override automatic gain control to manually set gain 147 o Auto-adjustments to gain control and echo cancellation algorithms 148 based on if a headset or internal speakers/microphone is being 149 used 151 o Echo cancellation, including acoustic echo cancellation 153 o Headset detection 155 o Call control event notification to connected devices such as 156 headsets 158 5. Legacy VoIP Interoperability 160 The codec requirements above will ensure, at a minimum, voice 161 interoperability capabilities between WebRTC client applications and 162 legacy phone systems. 164 Video interoperability will be dependent upon the MPEG-LA decision 165 regarding H.264 baseline. 167 6. IANA Considerations 169 This document makes no request of IANA. 171 Note to RFC Editor: this section may be removed on publication as an 172 RFC. 174 7. Security Considerations 176 The codec requirements have no additional security considerations 177 other than those captured in 178 [I-D.ekr-security-considerations-for-rtc-web]. 180 8. Acknowledgements 182 This draft incorporates ideas and text from various other drafts. In 183 particularly we would like to acknowledge, and say thanks for, work 184 we incorporated from Harald Alvestrand. 186 9. Normative References 188 [I-D.ekr-security-considerations-for-rtc-web] 189 Rescorla, E., "Security Considerations for RTC-Web", 190 May 2011. 192 [I-D.webm] 193 Google, Inc., "VP8 Data Format and Decoding Guide", 194 July 2010. 196 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 197 Requirement Levels", BCP 14, RFC 2119, March 1997. 199 [RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and 200 Video Conferences with Minimal Control", STD 65, RFC 3551, 201 July 2003. 203 [RFC4734] Schulzrinne, H. and T. Taylor, "Definition of Events for 204 Modem, Fax, and Text Telephony Signals", RFC 4734, 205 December 2006. 207 Authors' Addresses 209 Cary Bran 210 Plantronics 211 345 Encinial Street 212 Santa Cruz, CA 95060 213 USA 215 Phone: +1 206 661-2398 216 Email: cary.bran@plantronics.com 218 Cullen Jennings 219 Cisco 220 170 West Tasman Drive 221 San Jose, CA 95134 222 USA 224 Phone: +1 408 421-9990 225 Email: fluffy@cisco.com