<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>QoS vs QoE</title><link>http://blogs.technet.com/markdea/archive/2008/01/30/qos-vs-qoe.aspx</link><description>I have been meaning to write my thoughts about this for quite some time as its one of those conversations I have with both partners and customers on a regular basis. After having a really interesting conversation with Simon Horrocks at Psytechnics and</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: QoS vs QoE</title><link>http://blogs.technet.com/markdea/archive/2008/01/30/qos-vs-qoe.aspx#2803034</link><pubDate>Thu, 31 Jan 2008 14:03:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2803034</guid><dc:creator>MarkSummerson</dc:creator><description>&lt;p&gt;Hi Mark,&lt;/p&gt;
&lt;p&gt;To continue your analogy....what you actually need is somebody to oversee you, your colleagues and the rest of the general public’s journey home and take into account both the cars, the quality of driver and the importance of the journey....and then manipulate the traffic and the size of the road according to those factors....only then can you guarantee that every driver/rider will have a faultless stress free journey home.&lt;/p&gt;
&lt;p&gt;....which is why we developed our Application Assured Infrastructure approach, where we can deploy the apps and then monitor and manage performance across our network within thresholds, by the application performance, not just the packet performance....perfect for UC&lt;/p&gt;
&lt;p&gt;And my pitch here is done ;-)&lt;/p&gt;</description></item></channel></rss>