<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
It does appear presumptive to suggest that a codec that hasn't completed a standardization process be made "mandatory to implement."<br><br>Since there have been some large judgments over use of
allegedly "free" codecs, the lesson is that codecs that are claimed to
be "free of encumbrance" may in time be discovered not to be. The IETF process can potentially be useful in helping to clarify the IPR status of codecs. However, those wheels grind slowly. <br><br><hr id="stopSpelling">From: Markus.Isomaki@nokia.com<br>To: peter.musgrave@magorcorp.com; harald@alvestrand.no<br>Date: Tue, 21 Dec 2010 21:38:42 +0000<br>CC: rtc-web@alvestrand.no; dispatch@ietf.org; ted.ietf@gmail.com<br>Subject: Re: [RTW] [dispatch] Fwd: New Version Notification for draft-alvestrand-dispatch-rtcweb-protocols-00<br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
<style>
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.ecxMsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass pre
{margin-bottom:.0001pt;font-size:10.0pt;font-family:'Courier New';}
.ExternalClass span.ecxHTMLPreformattedChar
{font-family:Consolas;}
.ExternalClass span.ecxEmailStyle19
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;}
.ExternalClass div.ecxWordSection1
{page:WordSection1;}
</style>
<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);">Hi Peter, all,</span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);"> </span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);">About the video codec: Are there any arguments on why VP8 would
not have IPR issues? It is available as an open source implementation, but that
does not mean there are no IPR against it. My understanding is that the IPR
situation wrt. VP8 is still unclear and thus risky. The other issue with VP8 is,
as far as I know, the lack of a clear spec out of which independent interoperable
implementations can be created.</span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);"> </span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);">So I don’t at least buy the argument that we should choose
VP8 as mandatory to implement video codec because of IPR reasons.</span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);"> </span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);">I’m working on a separate review on Harald’s drafts
(thanks for putting them together) and will come back to the codec issue there in
more detail, but just wanted to respond to Peter’s point here.</span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);"> </span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);">Regards,</span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);"> Markus
</span></p>
<p class="ecxMsoNormal"><span style="font-size: 11pt; font-family: 'Calibri','sans-serif'; color: rgb(31, 73, 125);"> </span></p>
<div style="border-width: medium medium medium 1.5pt; border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; padding: 0cm 0cm 0cm 4pt;">
<div>
<div style="border-right: medium none; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0cm 0cm;">
<p class="ecxMsoNormal"><b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span style="font-size: 10pt; font-family: 'Tahoma','sans-serif';"> dispatch-bounces@ietf.org
[mailto:dispatch-bounces@ietf.org] <b>On Behalf Of </b>ext Peter Musgrave<br>
<b>Sent:</b> 17 December, 2010 13:48<br>
<b>To:</b> Harald Alvestrand<br>
<b>Cc:</b> rtc-web@alvestrand.no; dispatch@ietf.org; Ted Hardie<br>
<b>Subject:</b> Re: [dispatch] Fwd: New Version Notification for
draft-alvestrand-dispatch-rtcweb-protocols-00</span></p>
</div>
</div>
<p class="ecxMsoNormal"> </p>
<div>
<p class="ecxMsoNormal">I'd also like to echo Alan's thanks for these drafts. </p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">The protocol doc is very clear. [If you read only one
dispatch draft this Christmas, make it this one. ;-) ]</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">One observation to the group. The mandatory to implement
video CODEC is VP8 (presumably since it does not have IPR issues - which some
other choices would have). </p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">Regards, </p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal">Peter Musgrave</p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 9pt; font-family: 'Helvetica','sans-serif';">Nits</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 9pt; font-family: 'Helvetica','sans-serif';">Introduction</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 9pt; font-family: 'Helvetica','sans-serif';">s/</span><span style="font-size: 10pt; font-family: Courier;">veichle/vehicle/</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">Section 2
Para "Within each.."</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">s/implementaiton/implementation/</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">Section 4
Para1</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">"such
as" (something missing here?)</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">Section 5
Para2</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">"There
is no third mandatory to implement" </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span style="font-size: 10pt; font-family: Courier;">? Was
there a mention of a third before. Not sure why this statement is there.</span></p>
</div>
</div>
<div>
<p class="ecxMsoNormal"> </p>
</div>
<p class="ecxMsoNormal"> </p>
<div>
<div>
<p class="ecxMsoNormal">On 2010-11-10, at 6:34 AM, Harald Alvestrand wrote:</p>
</div>
<p class="ecxMsoNormal"><br>
<br>
</p>
<div>
<p class="ecxMsoNormal">This is the overview document for the IETF-related RTC-WEB
work.<br>
<br>
-------- Original Message -------- </p>
<table class="ecxMsoNormalTable" border="0" cellpadding="0" cellspacing="0">
<tbody><tr>
<td style="padding: 0cm;" nowrap="nowrap" valign="top">
<p class="ecxMsoNormal" style="text-align: right;" align="right"><b>Subject: </b></p>
</td>
<td style="padding: 0cm;">
<p class="ecxMsoNormal">New Version Notification for
draft-alvestrand-dispatch-rtcweb-protocols-00</p>
</td>
</tr>
<tr>
<td style="padding: 0cm;" nowrap="nowrap" valign="top">
<p class="ecxMsoNormal" style="text-align: right;" align="right"><b>Date: </b></p>
</td>
<td style="padding: 0cm;">
<p class="ecxMsoNormal">Wed, 10 Nov 2010 03:31:05 -0800 (PST)</p>
</td>
</tr>
<tr>
<td style="padding: 0cm;" nowrap="nowrap" valign="top">
<p class="ecxMsoNormal" style="text-align: right;" align="right"><b>From: </b></p>
</td>
<td style="padding: 0cm;">
<p class="ecxMsoNormal">IETF I-D Submission Tool <a href="mailto:idsubmission@ietf.org"><idsubmission@ietf.org></a></p>
</td>
</tr>
<tr>
<td style="padding: 0cm;" nowrap="nowrap" valign="top">
<p class="ecxMsoNormal" style="text-align: right;" align="right"><b>To: </b></p>
</td>
<td style="padding: 0cm;">
<p class="ecxMsoNormal"><a href="mailto:harald@alvestrand.no">harald@alvestrand.no</a></p>
</td>
</tr>
</tbody></table>
<p class="ecxMsoNormal" style="margin-bottom: 12pt;"> </p>
<pre>A new version of I-D, draft-alvestrand-dispatch-rtcweb-protocols-00.txt has been successfully submitted by Harald Alvestrand and posted to the IETF repository.</pre><pre> </pre><pre>Filename: draft-alvestrand-dispatch-rtcweb-protocols</pre><pre>Revision: 00</pre><pre>Title: Overview: Real Time Protocols for Brower-based Applications</pre><pre>Creation_date: 2010-11-11</pre><pre>WG ID: Independent Submission</pre><pre>Number_of_pages: 9</pre><pre> </pre><pre>Abstract:</pre><pre>This document gives an overview of a protocol suite intended for use</pre><pre>with real-time applications that can be deployed in browsers - "real</pre><pre>time communication on the Web".</pre><pre> </pre><pre>It intends to serve as a starting and coordination point to make sure</pre><pre>all the parts that are needed to achieve this goal are findable, and</pre><pre>that the parts that belong in the Internet protocol suite are fully</pre><pre>specified and on the right publication track.</pre><pre> </pre><pre>This work is an attempt to synthesize the input of many people, but</pre><pre>makes no claims to fully represent the views of any of them. All</pre><pre>parts of the document should be regarded as open for discussion.</pre><pre> </pre><pre> </pre><pre> </pre><pre>The IETF Secretariat.</pre><pre> </pre><pre> </pre><pre> </pre></div>
<p class="ecxMsoNormal">_______________________________________________<br>
dispatch mailing list<br>
<a href="mailto:dispatch@ietf.org">dispatch@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/dispatch</p>
</div>
<p class="ecxMsoNormal"> </p>
</div>
</div>
<br>_______________________________________________
RTC-Web mailing list
RTC-Web@alvestrand.no
http://www.alvestrand.no/mailman/listinfo/rtc-web </body>
</html>