<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Joe's Thoughts on Software Architecture : IP Multimedia Subsystem</title><link>http://blogs.msdn.com/joe_hofstader/archive/tags/IP+Multimedia+Subsystem/default.aspx</link><description>Tags: IP Multimedia Subsystem</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Communications as a Service (CaaS)</title><link>http://blogs.msdn.com/joe_hofstader/archive/2007/11/14/communications-as-a-service.aspx</link><pubDate>Wed, 14 Nov 2007 22:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6222660</guid><dc:creator>hofstader</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/joe_hofstader/comments/6222660.aspx</comments><wfw:commentRss>http://blogs.msdn.com/joe_hofstader/commentrss.aspx?PostID=6222660</wfw:commentRss><description>Communications as a Service (CaaS) is an architecture for communications applications. CaaS extends the principles of a Software as a Service (SaaS) architecture by adding a control layer based on the Session Initiation Protocol (SIP), The ability to...(&lt;a href="http://blogs.msdn.com/joe_hofstader/archive/2007/11/14/communications-as-a-service.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=6222660" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/SIP/default.aspx">SIP</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/IP+Multimedia+Subsystem/default.aspx">IP Multimedia Subsystem</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/Session+Initiation+Protocol/default.aspx">Session Initiation Protocol</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/IMS/default.aspx">IMS</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/CaaS/default.aspx">CaaS</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/Communications+as+a+Service/default.aspx">Communications as a Service</category></item><item><title>An Introduction to the Blog...</title><link>http://blogs.msdn.com/joe_hofstader/archive/2007/09/10/an-introduction-to-the-blog.aspx</link><pubDate>Mon, 10 Sep 2007 23:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4856732</guid><dc:creator>hofstader</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/joe_hofstader/comments/4856732.aspx</comments><wfw:commentRss>http://blogs.msdn.com/joe_hofstader/commentrss.aspx?PostID=4856732</wfw:commentRss><description>Writing about architecting communications solutions is like catching a tiger by the tail – narrowing down the amount of detailed information and background material required to provide a cohesive description on how to architect communications software...(&lt;a href="http://blogs.msdn.com/joe_hofstader/archive/2007/09/10/an-introduction-to-the-blog.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=4856732" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/SIP/default.aspx">SIP</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/Communications+Services/default.aspx">Communications Services</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/IP+Multimedia+Subsystem/default.aspx">IP Multimedia Subsystem</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/Session+Initiation+Protocol/default.aspx">Session Initiation Protocol</category><category domain="http://blogs.msdn.com/joe_hofstader/archive/tags/IMS/default.aspx">IMS</category></item></channel></rss>