<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: royalty free codecs at the IETF</title>
	<atom:link href="http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/</link>
	<description>I wuv you.</description>
	<lastBuildDate>Tue, 09 Mar 2010 08:03:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Franck Martin</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-206562</link>
		<dc:creator>Franck Martin</dc:creator>
		<pubDate>Tue, 04 Aug 2009 01:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-206562</guid>
		<description>IETF is all about passing the barriers and joining the group. It is a resistance path. It makes great specifications because blood(?!) and sweat has gone into them.

Keep steady, you&#039;ll get there.</description>
		<content:encoded><![CDATA[<p>IETF is all about passing the barriers and joining the group. It is a resistance path. It makes great specifications because blood(?!) and sweat has gone into them.</p>
<p>Keep steady, you&#8217;ll get there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Monty</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-206484</link>
		<dc:creator>Monty</dc:creator>
		<pubDate>Mon, 03 Aug 2009 18:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-206484</guid>
		<description>oops; looks ike angle bracketsdon&#039;t get escaped. &#039;foo; in &quot;I don&#039;t work for &#039;foo&#039;&quot;  above is missing the foo because I put it in brackets....</description>
		<content:encoded><![CDATA[<p>oops; looks ike angle bracketsdon&#8217;t get escaped. &#8216;foo; in &#8220;I don&#8217;t work for &#8216;foo&#8217;&#8221;  above is missing the foo because I put it in brackets&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Monty</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-206483</link>
		<dc:creator>Monty</dc:creator>
		<pubDate>Mon, 03 Aug 2009 18:29:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-206483</guid>
		<description>That... was an exhausting conference.

To answer a few questions, Ericsson had 39 registered employees attending, but that didn&#039;t count independent contractors that work for the company in reality but aren&#039;t official employees.  &quot;I don&#039;t work for , I am from a little company&quot; is apparently a whole category of running joke at the IETF.

Also, there is no formal vorting, but there are the &#039;hum votes&#039; as mentioned.  They&#039;re not binding, but they do matter.  In our the telcos in attendance hummed as a block unanimously against and everyone was fully aware that would happen.  The truly damning thing would have been had they hummed unanimously against and there had not been sufficient perceived support for the WG.

As it was, we obviously lost the hum vote, but by a surprisingly small margin; things were solidly against but not overwhelmingly so.  We made our case, stood our ground during questioning, and now things go back to the mailing lists to address at least one obvious mistake in preparation--- I intend to blog about this myself in a great deal more detail in a day or two.  

There was no quick victory as we hoped, and that was an urealistic hope, but we came surprisingly close.  In every way our &#039;failure&#039; moved us forward and we may even be close enough that we&#039;ll not need to re-BoF in Hiroshima (IETF76).  Hope hope, these trips are exhausting.</description>
		<content:encoded><![CDATA[<p>That&#8230; was an exhausting conference.</p>
<p>To answer a few questions, Ericsson had 39 registered employees attending, but that didn&#8217;t count independent contractors that work for the company in reality but aren&#8217;t official employees.  &#8220;I don&#8217;t work for , I am from a little company&#8221; is apparently a whole category of running joke at the IETF.</p>
<p>Also, there is no formal vorting, but there are the &#8216;hum votes&#8217; as mentioned.  They&#8217;re not binding, but they do matter.  In our the telcos in attendance hummed as a block unanimously against and everyone was fully aware that would happen.  The truly damning thing would have been had they hummed unanimously against and there had not been sufficient perceived support for the WG.</p>
<p>As it was, we obviously lost the hum vote, but by a surprisingly small margin; things were solidly against but not overwhelmingly so.  We made our case, stood our ground during questioning, and now things go back to the mailing lists to address at least one obvious mistake in preparation&#8212; I intend to blog about this myself in a great deal more detail in a day or two.  </p>
<p>There was no quick victory as we hoped, and that was an urealistic hope, but we came surprisingly close.  In every way our &#8216;failure&#8217; moved us forward and we may even be close enough that we&#8217;ll not need to re-BoF in Hiroshima (IETF76).  Hope hope, these trips are exhausting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mardeg</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-205034</link>
		<dc:creator>Mardeg</dc:creator>
		<pubDate>Thu, 30 Jul 2009 02:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-205034</guid>
		<description>What would be good is if Xiph actually released Speex 1.2 final or all OSes, since the latest RC1 has been at http://downloads.xiph.org/releases/speex/ since 24-Jul-2008</description>
		<content:encoded><![CDATA[<p>What would be good is if Xiph actually released Speex 1.2 final or all OSes, since the latest RC1 has been at <a href="http://downloads.xiph.org/releases/speex/" rel="nofollow">http://downloads.xiph.org/releases/speex/</a> since 24-Jul-2008</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @F1LT3R</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-204935</link>
		<dc:creator>@F1LT3R</dc:creator>
		<pubDate>Thu, 30 Jul 2009 00:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-204935</guid>
		<description>Such a breath of fresh air to hear this is happening, thanks for the info Chris! Two big names like these with the skill and the scalability to make something happen is a great hope for the future of the Internet.</description>
		<content:encoded><![CDATA[<p>Such a breath of fresh air to hear this is happening, thanks for the info Chris! Two big names like these with the skill and the scalability to make something happen is a great hope for the future of the Internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franck Martin</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-204926</link>
		<dc:creator>Franck Martin</dc:creator>
		<pubDate>Thu, 30 Jul 2009 00:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-204926</guid>
		<description>It is interesting. If I recall the SIP specification attributes a few parameters to some standard codec (like g723) and allows extension for other codecs (like iLBC). I suspect IANA could start a list of reference numbers and codec to be used in various protocols.
Also IETF has not an obligation of opensource, but requires all people writing RFC to disclose if they know if any technology is under any patent. To avoid someone push a standard and then later come back and claim royalties.
Finally SIP is as much about audio codec as video codecs and there are more people looking at streaming TV. IETF is the right place when you want to bring some technology, increase its robustness and standardize it. And may be at the difference of W3C, anything is a standard if at least 2 independent operable system has been built. You don&#039;t need to wait for the others to agree, and the others can do their own standard too. At the end, it is the user that votes by using.</description>
		<content:encoded><![CDATA[<p>It is interesting. If I recall the SIP specification attributes a few parameters to some standard codec (like g723) and allows extension for other codecs (like iLBC). I suspect IANA could start a list of reference numbers and codec to be used in various protocols.<br />
Also IETF has not an obligation of opensource, but requires all people writing RFC to disclose if they know if any technology is under any patent. To avoid someone push a standard and then later come back and claim royalties.<br />
Finally SIP is as much about audio codec as video codecs and there are more people looking at streaming TV. IETF is the right place when you want to bring some technology, increase its robustness and standardize it. And may be at the difference of W3C, anything is a standard if at least 2 independent operable system has been built. You don&#8217;t need to wait for the others to agree, and the others can do their own standard too. At the end, it is the user that votes by using.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Petit-Huguenin</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/07/royalty-free-codecs-at-the-ietf/comment-page-1/#comment-204922</link>
		<dc:creator>Marc Petit-Huguenin</dc:creator>
		<pubDate>Thu, 30 Jul 2009 00:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1346#comment-204922</guid>
		<description>I do not see how Ericsson can pack the meeting with 40-100 people, as there is only 39 Ericsson employees registered to attend the IETF meeting (https://www.ietf.org/registration/ietf75/attendance.py?sortkey=3&amp;login=).  Also there is no such thing as a vote at the IETF.  Closest thing is a hum that will need to be confirmed on the mailing-list.</description>
		<content:encoded><![CDATA[<p>I do not see how Ericsson can pack the meeting with 40-100 people, as there is only 39 Ericsson employees registered to attend the IETF meeting (<a href="https://www.ietf.org/registration/ietf75/attendance.py?sortkey=3&amp;login=" rel="nofollow">https://www.ietf.org/registration/ietf75/attendance.py?sortkey=3&amp;login=</a>).  Also there is no such thing as a vote at the IETF.  Closest thing is a hum that will need to be confirmed on the mailing-list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
