One document matched: draft-marjou-rtcweb-video-codec-00.xml

<?xml version='1.0' ?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [      
  <!ENTITY RFC2119 PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
]>

<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?> 
<rfc ipr='trust200811' category='info'>
<?rfc toc='yes'?>
<?rfc compact='yes'?>
<?rfc sortrefs='yes'?>

<front>
	<title abbrev='Video codec for WebRTC'>
     Video codec for WebRTC. 
	</title>
	
	<author initials='X.' surname='Marjou' fullname='Xavier Marjou'>
	<organization>France Telecom Orange</organization>
	<address>
		<postal>
			<street>2, avenue Pierre Marzin</street>
			<city>Lannion</city> 
			<code>22307</code>
			<country>France</country>
		</postal> 
      <email>xavier.marjou@orange.com</email>
	</address>
	</author>
	

<author initials='P.' surname='Philippe' fullname='Pierrick Philippe'>
	<organization>France Telecom Orange</organization>
	<address>
		<postal>
			<street>2, avenue Pierre Marzin</street>
			<city>Lannion</city> 
			<code>22307</code>
			<country>France</country>
		</postal> 
      <email>pierrick.philippe@orange.com</email>
	</address>
	</author>
	
	<date month='October' year='2012' />
	
	<area>Real-time Applications and Infrastructure Area</area>
	<keyword>video</keyword>
       <keyword>codec</keyword>

	<abstract>
		<t>
In the context of WebRTC, there is currently no consensus on the video codec(s) that need to be mandatory to implement.
This draft gives some arguments in favor of H.264.
</t>
	</abstract>
</front>

<middle>

  <section title="Introduction">

  <t>In the context of WebRTC, there is currently no consensus on the video
 codec(s) that need to be mandatory to implement.</t>

<t>In order to reach a consensus, the RTCWEB  chairs have solicited internet-drafts
naming proposed mandatory-to-implement video codecs 
(c.f. <xref target="rtcweb-mail" />).</t>

<t>This draft gives some arguments in favor of H.264.</t>

</section>
 
	<section title="Terminology">
      
	<t> In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" are to be interpreted as described in RFC 2119 <xref target="RFC2119" />.</t>
  
	</section>



	<section title="Rationale and Position">

		<t>
Many videoconferencing systems exist today (e.g. fact sheets of services at <xref target="h264-ftob" />), mainly for professional services but also 
for individual consumers.</t> 
<t>
We believe that WebRTC, when used as a mean to interconnect 
Web browsers to these existing services, can be a driver 
for enabling more users to access them.
</t>
<t>
As an example, all Orange video conferencing systems operate using the H.264/AVC technology. 
H.264/AVC benefits from many available implementations, tuned for different 
architectures, and has clear licensing conditions. VP8 has no footprint in this market, 
independent implementations are rare, licensing conditions are not yet clarified 
(free license offered from one patent owner while MPEG LA operates a Patent Pool with at
least 12 members (c.f. <xref target="press-article" />)). 
</t>
<t>
With this current status, it is believed that incorporating the mandatory to implement
video codec having the bigger footprint will permit a better adoption and 
interconnection of WebRTC to existing services leading to a successful standard.
</t>
<t>
Hence we strongly support H.264/AVC to be part of the mandatory to implement codecs.
</t>


 
	</section>
		


    
	<section title="Security Considerations">
  
		<t>None.</t>

	</section>


	<section title="IANA Considerations">

	
		<t>None.</t>


	</section> 


	<section title="Acknowledgements">

		<t></t>

	</section> 


  
</middle>

<back>

<references title="Normative references">

	&RFC2119;
 
</references>

<references title="Informative references">




<reference anchor="rtcweb-mail">
	<front>
		<title>http://www.ietf.org/mail-archive/web/rtcweb/current/msg05070.html</title>
		<author>
			<organization>IETF</organization>
		</author>
		<date year=""></date>
	</front>
</reference>	



<reference anchor="h264-ftob">
	<front>
		<title>http://www.orange-business.com/en/mnc2/collaboration/conferencing/index.jsp</title>
		<author>
			<organization>Orange</organization>
		</author>
		<date year=""></date>
	</front>
</reference>	

<reference anchor="press-article">
	<front>
		<title>http://www.streamingmedia.com/Articles/Editorial/Featured-Articles/WebM-Patent-Fight-Ahead-for-Google-76781.aspx</title>
		<author>
			<organization>streamingmedia.com</organization>
		</author>
		<date year=""></date>
	</front>
</reference>	
  
</references>

</back>

</rfc>