<?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>Quality of Experience (QoE) paper published</title><link>http://blogs.technet.com/chlacy/archive/2007/08/20/quality-of-experience-qoe-paper-published.aspx</link><description>Tom has posted about the QoE paper that has been published. Please read it at: http://blogs.technet.com/toml/archive/2007/07/27/quality-of-experience-qoe-paper-published.aspx?CommentPosted=true#commentmessage</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Quality of Experience (QoE) paper published</title><link>http://blogs.technet.com/chlacy/archive/2007/08/20/quality-of-experience-qoe-paper-published.aspx#1905010</link><pubDate>Thu, 06 Sep 2007 02:38:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1905010</guid><dc:creator>chris dalby</dc:creator><description>&lt;P&gt;Hi Chad&lt;/P&gt;
&lt;P&gt;Beleive it or not, I've been waiting for this to come out. &amp;nbsp;I only wish one less acronym had been introduced and a consistency with QoS had been established. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm still no wiser whether QoE is a lower or higher benchmark, or a completely different bench. Hope I'm not killing the messenger here, but I think QoE is one step too far.&lt;/P&gt;</description></item><item><title>re: Quality of Experience (QoE) paper published</title><link>http://blogs.technet.com/chlacy/archive/2007/08/20/quality-of-experience-qoe-paper-published.aspx#1938643</link><pubDate>Tue, 11 Sep 2007 16:38:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1938643</guid><dc:creator>chlacy</dc:creator><description>&lt;p&gt;Hi Chris,&lt;/p&gt;
&lt;p&gt;I understand your comments about QoS v. QoE. There is a difference between the two. Simply put, QoS only focuses on the network and its relative health. Cisco and the other network infrastructure vendors have done a very good job at promoting QoS as a means to deliver &amp;quot;valuable&amp;quot; packets to their destination. However, QoS does not address the problem of what happens if the destination isn't ready for the packet. I wouldn't expect these vendors to address this either. So, this isn't a dig at them. They control the network and they are doing everything within their power to make the network the best it can be. &lt;/p&gt;
&lt;p&gt;QoE on the other hand takes into account not only the network, but processor consumption, memory usage, disk utilization. In other words, QoE is an attempt to look at any bottleneck within the infrastructure that may affect the quality of hte voice taffic.&lt;/p&gt;
</description></item><item><title>re: Quality of Experience (QoE) paper published</title><link>http://blogs.technet.com/chlacy/archive/2007/08/20/quality-of-experience-qoe-paper-published.aspx#1946567</link><pubDate>Wed, 12 Sep 2007 23:30:56 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1946567</guid><dc:creator>Chris Dalby</dc:creator><description>&lt;P&gt;Thanks for the explanation for that Chad. &amp;nbsp;I see what you are saying. &amp;nbsp;My feeling at the moment is that router and firewall vendors in general publish quite confusing documentation in their manuals regarding QoS. &amp;nbsp;This was a big headache for me. &amp;nbsp;Getting clear and simple QoE info in vendor manuals would be a major plus.&lt;/P&gt;</description></item><item><title>re: Quality of Experience (QoE) paper published</title><link>http://blogs.technet.com/chlacy/archive/2007/08/20/quality-of-experience-qoe-paper-published.aspx#2576034</link><pubDate>Wed, 28 Nov 2007 00:59:32 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2576034</guid><dc:creator>Mark Knepper</dc:creator><description>&lt;p&gt;My client is looking delploy this in their enterprise, but are concerned about the overhead that the QMS may introduce into the network. &amp;nbsp;Are there any stats on how much load, bandwidth, etc. will be placed on the network as it monitors QoE? &amp;nbsp;We certainly don't want to degrade the QoE by measuring it!&lt;/p&gt;</description></item></channel></rss>