<?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: Lippis Report Issue 82: Securing Unified Communications Infrastructure</title>
	<atom:link href="http://lippisreport.com/2007/05/lippis-report-issue-82-securing-unified-communications-infrastructure/feed/" rel="self" type="application/rss+xml" />
	<link>http://lippisreport.com/2007/05/lippis-report-issue-82-securing-unified-communications-infrastructure/</link>
	<description>Resources for Network / IT Business Decision Makers</description>
	<lastBuildDate>Mon, 21 May 2012 12:58:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Uvyehhps</title>
		<link>http://lippisreport.com/2007/05/lippis-report-issue-82-securing-unified-communications-infrastructure/comment-page-1/#comment-122259</link>
		<dc:creator>Uvyehhps</dc:creator>
		<pubDate>Sat, 13 Dec 2008 17:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/2007/05/07/lippis-report-issue-82-securing-unified-communications-infrastructure/#comment-122259</guid>
		<description>Thanks!,</description>
		<content:encoded><![CDATA[<p>Thanks!,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: artr</title>
		<link>http://lippisreport.com/2007/05/lippis-report-issue-82-securing-unified-communications-infrastructure/comment-page-1/#comment-27767</link>
		<dc:creator>artr</dc:creator>
		<pubDate>Tue, 03 Jul 2007 15:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://lippisreport.com/2007/05/07/lippis-report-issue-82-securing-unified-communications-infrastructure/#comment-27767</guid>
		<description>While security and reliability are indeed considerations in network design for unified communications, the bottom line for accommodating traffic is capacity planning. One of the challenges for converging all forms of communications traffic under UC is that such traffic will change dynamically from the past. Voice messages will become email text messages, IM contacts will become conversational voice connections, and two-party calls can extend to &quot;instant&quot; multi-party voice or video contacts. (We have already had telephone calls that become voice messages.)

In planning for this kind of dynamically-changing activity, it would seem appropriate for network designers to enable activity data to be collected for operational analysis on a  &quot;unified&quot; basis. This  would enable &quot;people contact&quot; activity to be tracked across modalities of communication (&quot;transmodal&quot;) in order to project overall traffic demands. Clearly, there will be differences in network needs between an IM connection, asynchronous messaging, conversational voice, and video, and in escalating from one modality to the other, network capacity needs will be constantly shifting. 

In effect, it is not enough to track messages and phone call activity, but also to track &quot;multimodal&quot;  contacts.

Respectfully,

Art Rosenberg
The Unified-View</description>
		<content:encoded><![CDATA[<p>While security and reliability are indeed considerations in network design for unified communications, the bottom line for accommodating traffic is capacity planning. One of the challenges for converging all forms of communications traffic under UC is that such traffic will change dynamically from the past. Voice messages will become email text messages, IM contacts will become conversational voice connections, and two-party calls can extend to &#8220;instant&#8221; multi-party voice or video contacts. (We have already had telephone calls that become voice messages.)</p>
<p>In planning for this kind of dynamically-changing activity, it would seem appropriate for network designers to enable activity data to be collected for operational analysis on a  &#8220;unified&#8221; basis. This  would enable &#8220;people contact&#8221; activity to be tracked across modalities of communication (&#8220;transmodal&#8221;) in order to project overall traffic demands. Clearly, there will be differences in network needs between an IM connection, asynchronous messaging, conversational voice, and video, and in escalating from one modality to the other, network capacity needs will be constantly shifting. </p>
<p>In effect, it is not enough to track messages and phone call activity, but also to track &#8220;multimodal&#8221;  contacts.</p>
<p>Respectfully,</p>
<p>Art Rosenberg<br />
The Unified-View</p>
]]></content:encoded>
	</item>
</channel>
</rss>

