<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: OpenID: A possible identity mechanism for VoIP?</title>
	<atom:link href="http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/feed/" rel="self" type="application/rss+xml" />
	<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/</link>
	<description>A daily round table on the tech industry with experts and callers from all over the globe. Join us as we pick apart the news and get to the meat of what\'s happening out there.</description>
	<lastBuildDate>Sat, 13 Mar 2010 16:12:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: VoIP Man</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-202750</link>
		<dc:creator>VoIP Man</dc:creator>
		<pubDate>Wed, 18 Apr 2007 09:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-202750</guid>
		<description>Yes, I think that OpenID is a cool idea for VoIP applications.</description>
		<content:encoded><![CDATA[<p>Yes, I think that OpenID is a cool idea for VoIP applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VoIP User</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-130956</link>
		<dc:creator>VoIP User</dc:creator>
		<pubDate>Mon, 19 Feb 2007 16:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-130956</guid>
		<description>&lt;strong&gt;SIP Doesn&#039;t Need openID&lt;/strong&gt;

We do have identification problems, but what we need to resolve those is authentication on a server to server level within a multi-lateral peered &quot;supernet&quot; environment.</description>
		<content:encoded><![CDATA[<p><strong>SIP Doesn&#8217;t Need openID</strong></p>
<p>We do have identification problems, but what we need to resolve those is authentication on a server to server level within a multi-lateral peered &#8220;supernet&#8221; environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The PhoneBoy Blog &#187; Eating My Words on OpenID</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-78217</link>
		<dc:creator>The PhoneBoy Blog &#187; Eating My Words on OpenID</dc:creator>
		<pubDate>Thu, 14 Dec 2006 19:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-78217</guid>
		<description>[...] Between a private email from Aswath and other posts on OpenID, I have reconsidered my opinion on this. It may not be such a bad thing after all. [...]</description>
		<content:encoded><![CDATA[<p>[...] Between a private email from Aswath and other posts on OpenID, I have reconsidered my opinion on this. It may not be such a bad thing after all. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Louis Seguineau</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-78163</link>
		<dc:creator>Jean-Louis Seguineau</dc:creator>
		<pubDate>Thu, 14 Dec 2006 17:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-78163</guid>
		<description>As a matter of fact this may be also of interest http://openid.xmpp.za.net/</description>
		<content:encoded><![CDATA[<p>As a matter of fact this may be also of interest <a href="http://openid.xmpp.za.net/" rel="nofollow">http://openid.xmpp.za.net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog by Kveton &#187; OpenID + VoIP == Good?</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-78152</link>
		<dc:creator>Blog by Kveton &#187; OpenID + VoIP == Good?</dc:creator>
		<pubDate>Thu, 14 Dec 2006 17:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-78152</guid>
		<description>[...] Update: Discussions continue all over the place on this.  Share and Enjoy:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</description>
		<content:encoded><![CDATA[<p>[...] Update: Discussions continue all over the place on this.  Share and Enjoy:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Louis Seguineau</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-78135</link>
		<dc:creator>Jean-Louis Seguineau</dc:creator>
		<pubDate>Thu, 14 Dec 2006 16:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-78135</guid>
		<description>There is a Wordpress OpenID implementation available ;)

Anything that de-couple authentification/authorization from the address handle used in the communication potocol is welcome. 
The slight drawback I would see today is the binding to HTTP in the negotiation... This is very web oriented.

In short, the principle of OpenID is definitivly interesting, but may need to ba adapted to communication protocols. That should not be difficult.</description>
		<content:encoded><![CDATA[<p>There is a Wordpress OpenID implementation available ;)</p>
<p>Anything that de-couple authentification/authorization from the address handle used in the communication potocol is welcome.<br />
The slight drawback I would see today is the binding to HTTP in the negotiation&#8230; This is very web oriented.</p>
<p>In short, the principle of OpenID is definitivly interesting, but may need to ba adapted to communication protocols. That should not be difficult.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Kveton</title>
		<link>http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/comment-page-1/#comment-78132</link>
		<dc:creator>Scott Kveton</dc:creator>
		<pubDate>Thu, 14 Dec 2006 16:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/12/14/openid-a-possible-identity-mechanism-for-voip/#comment-78132</guid>
		<description>VoIP with OpenID is a great idea.  We keep seeing new applications for it that solve really specific problems for different verticals.  Its amazing what an extremely thin layer of identity (in OpenID&#039;s case, really just authentication) can do for so many different applications.

As for the WordPress plugin, there is a great one here:

http://verselogic.net/projects/wordpress/wordpress-openid-plugin/

Although the site appears to be down at the moment.  I&#039;m using it on a few sites and its just great.  FYI.</description>
		<content:encoded><![CDATA[<p>VoIP with OpenID is a great idea.  We keep seeing new applications for it that solve really specific problems for different verticals.  Its amazing what an extremely thin layer of identity (in OpenID&#8217;s case, really just authentication) can do for so many different applications.</p>
<p>As for the WordPress plugin, there is a great one here:</p>
<p><a href="http://verselogic.net/projects/wordpress/wordpress-openid-plugin/" rel="nofollow">http://verselogic.net/projects/wordpress/wordpress-openid-plugin/</a></p>
<p>Although the site appears to be down at the moment.  I&#8217;m using it on a few sites and its just great.  FYI.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
