<?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"
	>
<channel>
	<title>Comments on: WS-Federation TC roundup and thoughts</title>
	<atom:link href="http://www.xmlgrrl.com/blog/archives/2007/04/04/ws-federation-tc-roundup-and-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xmlgrrl.com/blog/archives/2007/04/04/ws-federation-tc-roundup-and-thoughts/</link>
	<description>XML, identity, crafting, and other tangled musings</description>
	<pubDate>Mon, 13 Oct 2008 14:14:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Eve</title>
		<link>http://www.xmlgrrl.com/blog/archives/2007/04/04/ws-federation-tc-roundup-and-thoughts/#comment-56611</link>
		<dc:creator>Eve</dc:creator>
		<pubDate>Sat, 14 Apr 2007 22:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.xmlgrrl.com/blog/archives/2007/04/04/ws-federation-tc-roundup-and-thoughts/#comment-56611</guid>
		<description>Hi, James. :-)

Seriously, I hadn't seen it yet, but I think the point about working with a knowledgeable counterpart in each of the other domains you're federating with is an important deployment consideration, both initially and in an ongoing fashion -- as certificates expire, for example.  (However, I don't think this is the top barrier to federation.)

Where everybody could probably do a much better job is in planning for the long term in such a relationship, so that there's an understanding of regular maintenance and hygiene rather than dealing with fire drills all the time. This problem isn't unique to identity federation, but there's no doubt a special list of tasks that would be involved compared to other IT activities.</description>
		<content:encoded><![CDATA[<p>Hi, James. :-)</p>
<p>Seriously, I hadn&#8217;t seen it yet, but I think the point about working with a knowledgeable counterpart in each of the other domains you&#8217;re federating with is an important deployment consideration, both initially and in an ongoing fashion &#8212; as certificates expire, for example.  (However, I don&#8217;t think this is the top barrier to federation.)</p>
<p>Where everybody could probably do a much better job is in planning for the long term in such a relationship, so that there&#8217;s an understanding of regular maintenance and hygiene rather than dealing with fire drills all the time. This problem isn&#8217;t unique to identity federation, but there&#8217;s no doubt a special list of tasks that would be involved compared to other IT activities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: curious</title>
		<link>http://www.xmlgrrl.com/blog/archives/2007/04/04/ws-federation-tc-roundup-and-thoughts/#comment-56586</link>
		<dc:creator>curious</dc:creator>
		<pubDate>Sat, 14 Apr 2007 19:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.xmlgrrl.com/blog/archives/2007/04/04/ws-federation-tc-roundup-and-thoughts/#comment-56586</guid>
		<description>Curious if you have seen http://duckdown.blogspot.com/2007/04/federated-identity-and-industry.html</description>
		<content:encoded><![CDATA[<p>Curious if you have seen <a href="http://duckdown.blogspot.com/2007/04/federated-identity-and-industry.html" rel="nofollow">http://duckdown.blogspot.com/2007/04/federated-identity-and-industry.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
