<?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: A-IMS from Verizon and Buddies: A Good thing as I see it</title>
	<atom:link href="http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/</link>
	<description>Commentary on Mobile technologies, VoIP, SIP, IMS, Web 2.0 and Technology</description>
	<lastBuildDate>Mon, 02 Aug 2010 14:27:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Arjun</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-48</link>
		<dc:creator>Arjun</dc:creator>
		<pubDate>Fri, 28 Sep 2007 23:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-48</guid>
		<description>You noticed correctly. However, I have no interest ,gain, nor loss in either mentioning or not mentioning Cisco. Looks like I just missed mentioning their name. Sorry I couldn&#039;t offer a more climactic response. I am glad you appreciate Cisco&#039;s role in this.</description>
		<content:encoded><![CDATA[<p>You noticed correctly. However, I have no interest ,gain, nor loss in either mentioning or not mentioning Cisco. Looks like I just missed mentioning their name. Sorry I couldn&#8217;t offer a more climactic response. I am glad you appreciate Cisco&#8217;s role in this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-47</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 27 Sep 2007 17:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-47</guid>
		<description>I notice that Cisco notoriously absent from mention in your article as one of the partners developing this solution for VzW, aside from the snide remark about the old Cisco IAD. Since Cisco is first in the &quot;Acknowlegements&quot; section of the A-IMS Architecture doc (June 2006) I can only assume this is intentional.&lt;br/&gt;&lt;br/&gt;In reality, Cisco is responsible for implementation of the Bearer Manager portion of the solution that you seem to like so well.&lt;br/&gt;&lt;br/&gt;And thank God that Cisco is involved - otherwise A-IMS would wind up with same problems, shortfalls, and oversights as IMS. Because that is what happens when telecom network people try to write a data spec.</description>
		<content:encoded><![CDATA[<p>I notice that Cisco notoriously absent from mention in your article as one of the partners developing this solution for VzW, aside from the snide remark about the old Cisco IAD. Since Cisco is first in the &#8220;Acknowlegements&#8221; section of the A-IMS Architecture doc (June 2006) I can only assume this is intentional.</p>
<p>In reality, Cisco is responsible for implementation of the Bearer Manager portion of the solution that you seem to like so well.</p>
<p>And thank God that Cisco is involved &#8211; otherwise A-IMS would wind up with same problems, shortfalls, and oversights as IMS. Because that is what happens when telecom network people try to write a data spec.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjun</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-46</link>
		<dc:creator>Arjun</dc:creator>
		<pubDate>Sat, 24 Feb 2007 05:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-46</guid>
		<description>Unfortunately not. It seems Verizon and partners keep the specs close to their heart, so to speak.</description>
		<content:encoded><![CDATA[<p>Unfortunately not. It seems Verizon and partners keep the specs close to their heart, so to speak.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-45</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 22 Feb 2007 23:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-45</guid>
		<description>Does Verizon give any details about the policy manager ? Are there any standard docs available in this regard, just curious</description>
		<content:encoded><![CDATA[<p>Does Verizon give any details about the policy manager ? Are there any standard docs available in this regard, just curious</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-44</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 22 Feb 2007 23:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-44</guid>
		<description>Does Verizon give any details about the policy manager ? Are there any standard docs available in this regard, just curious</description>
		<content:encoded><![CDATA[<p>Does Verizon give any details about the policy manager ? Are there any standard docs available in this regard, just curious</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-43</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 25 Oct 2006 08:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-43</guid>
		<description>Interesting indeed.  I think it is generous of Verizon to publish their internal implementation spec, and brave of all those vendors to tell us what they are going to do, since that has to be based on implementation plans and gives all the other guys in Standards an advance warning to allow them to take pot shots at it (sorry, thats how standards works).  What I find most interesting is that a lot of what A-IMS defines is actually NOT about IMS at all, but about the bits that reside around the edge of IMS.  These same functions (policy, authentication, bandwidth management) can be applied to any Service Enabling architecture, including access to the internet for a vertical third party service.  &lt;br/&gt;&lt;br/&gt;I also find it interesting that A-IMS seems to be a rip off of a lot of stuff that MSF are doing (which Verizon are members of).  It&#039;s easy to innovate (sic.) when you nicjk someone else&#039;s ideas.</description>
		<content:encoded><![CDATA[<p>Interesting indeed.  I think it is generous of Verizon to publish their internal implementation spec, and brave of all those vendors to tell us what they are going to do, since that has to be based on implementation plans and gives all the other guys in Standards an advance warning to allow them to take pot shots at it (sorry, thats how standards works).  What I find most interesting is that a lot of what A-IMS defines is actually NOT about IMS at all, but about the bits that reside around the edge of IMS.  These same functions (policy, authentication, bandwidth management) can be applied to any Service Enabling architecture, including access to the internet for a vertical third party service.  </p>
<p>I also find it interesting that A-IMS seems to be a rip off of a lot of stuff that MSF are doing (which Verizon are members of).  It&#8217;s easy to innovate (sic.) when you nicjk someone else&#8217;s ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curro</title>
		<link>http://blog.roychowdhury.org/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/comment-page-1/#comment-42</link>
		<dc:creator>Curro</dc:creator>
		<pubDate>Fri, 06 Oct 2006 11:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/09/22/a-ims-from-verizon-and-buddies-a-good-thing-as-i-see-it/#comment-42</guid>
		<description>Hi&lt;br/&gt;&lt;br/&gt;Great post and very interesting analysis. I&#039;m afraid that IMS is becoming a chaos, due to all interoperability issues and propietary solutions at the edges. All the vendors want to evolve their own platforms to be 3GPP compliant... with their own products, as you say.&lt;br/&gt;&lt;br/&gt;Interesting the multi-level authentication. One of the most challenges when heterogeneous access networks are used is the delay due to new authentication. Also in handovers. Have you found in the document data about latency time or related to this issue?&lt;br/&gt;&lt;br/&gt;Thanks!</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>Great post and very interesting analysis. I&#8217;m afraid that IMS is becoming a chaos, due to all interoperability issues and propietary solutions at the edges. All the vendors want to evolve their own platforms to be 3GPP compliant&#8230; with their own products, as you say.</p>
<p>Interesting the multi-level authentication. One of the most challenges when heterogeneous access networks are used is the delay due to new authentication. Also in handovers. Have you found in the document data about latency time or related to this issue?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
