<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.marjou-rtcweb-audio-codecs-for-interop" target="https://datatracker.ietf.org/doc/html/draft-marjou-rtcweb-audio-codecs-for-interop-01">
   <front>
      <title>WebRTC audio codecs for interoperability with legacy networks.</title>
      <author initials="X." surname="Marjou" fullname="Xavier Marjou">
         <organization>France Telecom Orange</organization>
      </author>
      <author initials="S." surname="Proust" fullname="Stephane Proust">
         <organization>France Telecom Orange</organization>
      </author>
      <author initials="K." surname="Bogineni" fullname="Kalyani Bogineni">
         <organization>Verizon Wireless</organization>
      </author>
      <author initials="R." surname="Jesske" fullname="Roland Jesske">
         <organization>Deutsche Telekom AG</organization>
      </author>
      <author initials="M." surname="Lei" fullname="Miao Lei">
         <organization>Huawei</organization>
      </author>
      <author initials="E." surname="Marocco" fullname="Enrico Marocco">
         <organization>Cisco</organization>
      </author>
      <author initials="E." surname="Berger" fullname="Espen Berger">
         <organization>Cisco</organization>
      </author>
      <date month="February" day="25" year="2013" />
      <abstract>
	 <t>   This document presents use-cases underlining why WebRTC needs AMR-WB,
   AMR and G.722 as additional relevant voice codecs to satisfactorily
   ensure interoperability with existing systems.  It also presents a
   way forward that takes into consideration the concerns expressed
   against the addition of codecs besides Opus and G.711.

   It is especially recognized that unjustified additional costs on
   browsers must be avoided.  Therefore, the proposed solution intends
   to fully rely on the codecs already supported on the devices
   implementing the browsers and for which license and implementation
   costs have been already paid.

   It is expected that this way forward will significantly limit the
   costs and technical impacts on browsers while greatly improving
   interoperability with legacy systems and overall quality.  It intents
   to be considered as a good compromise beneficial to all parties and
   to the whole industry: the user quality experience will be optimized
   as a whole at limited additional costs without incurring high costs
   for both networks to support transcoding and browsers to support
   additional codecs.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-marjou-rtcweb-audio-codecs-for-interop-01" />
   
</reference>
