<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<title>Re: [dispatch] Fwd: New Version Notification for
draft-alvestrand-dispatch-rtcweb-protocols-00</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The good thing about Opus codec is that as it has been developed
through the IETF process, the ownership and change control issues are clear. This
makes referencing and even mandating it by IETF or W3C more comfortable.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Markus<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ext Henry Sinnreich
[mailto:henry.sinnreich@gmail.com] <br>
<b>Sent:</b> 22 December, 2010 04:32<br>
<b>To:</b> Isomaki Markus (Nokia-CIC/Espoo); peter.musgrave@magorcorp.com;
harald@alvestrand.no; codec@ietf.org<br>
<b>Cc:</b> rtc-web@alvestrand.no; dispatch@ietf.org; ted.ietf@gmail.com<br>
<b>Subject:</b> Re: [dispatch] Fwd: New Version Notification for
draft-alvestrand-dispatch-rtcweb-protocols-00<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:13.0pt;
font-family:"Calibri","sans-serif"'>It is interesting, almost funny (or sad
depending on the perspective) how the reaction to a _God Forbid_ IP-free video
codec is mirroring the opposition to the Internet audio codec. That opposition
proved eventually futile and we have now a CODEC WG.<br>
I hope the AD’s will have now the same fortitude as was shown when the
Internet audio codec WG was formed. <br>
<br>
I have taken the liberty to copy the CODEC WG and hope they can participate now
in the video codec discussion as well.<br>
My apology for the double posting.<br>
<br>
Thanks, Henry <br>
<br>
<br>
On 12/21/10 3:38 PM, "<a href="Markus.Isomaki@nokia.com">Markus.Isomaki@nokia.com</a>"
<<a href="Markus.Isomaki@nokia.com">Markus.Isomaki@nokia.com</a>> wrote:</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Peter, all,<br>
<br>
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.<br>
<br>
So I don’t at least buy the argument that we should choose VP8 as
mandatory to implement video codec because of IPR reasons.<br>
<br>
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.<br>
<br>
Regards,<br>
Markus
<br>
<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href="dispatch-bounces@ietf.org">dispatch-bounces@ietf.org</a> [<a
href="mailto:dispatch-bounces@ietf.org">mailto:dispatch-bounces@ietf.org</a>] <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> <a href="rtc-web@alvestrand.no">rtc-web@alvestrand.no</a>; <a
href="dispatch@ietf.org">dispatch@ietf.org</a>; Ted Hardie<br>
<b>Subject:</b> Re: [dispatch] Fwd: New Version Notification for
draft-alvestrand-dispatch-rtcweb-protocols-00<br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span>I'd also like to echo Alan's thanks for these drafts. <br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span>The protocol doc is very clear. [If you read only one dispatch draft
this Christmas, make it this one. ;-) ]<br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span>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). <br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span>Regards, <br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span>Peter Musgrave<br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif"'>Nits<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif"'>Introduction<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif"'>s/</span><span
style='font-size:10.0pt;font-family:Courier'>veichle/vehicle/<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'><br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>Section 2 Para
"Within each.."<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>s/implementaiton/implementation/<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'><br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>Section 4 Para1<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>"such as"
(something missing here?)<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'><br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>Section 5 Para2<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>"There is no
third mandatory to implement" <br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:Courier'>? Was there a mention
of a third before. Not sure why this statement is there.<br>
</span><span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><br>
<br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span>On 2010-11-10, at 6:34 AM, Harald Alvestrand wrote:<br>
<br>
<br>
This is the overview document for the IETF-related RTC-WEB work.<br>
<br>
-------- Original Message -------- <br>
<span style='font-size:13.0pt;font-family:"Calibri","sans-serif"'><br>
</span><o:p></o:p></p>
</div>
</div>
</body>
</html>