<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: QoS: Quality of Suppression</title>
	<atom:link href="http://www.saunderslog.com/2006/05/17/qos-quality-of-suppression/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.saunderslog.com/2006/05/17/qos-quality-of-suppression/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=qos-quality-of-suppression</link>
	<description>An outcome-driven leader, proven technology product developer, and  marketer with over 20 years of hands-on experience including start-up, small and large business environments, and the board room. This is my blog.</description>
	<lastBuildDate>Thu, 26 Jan 2012 17:15:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alec</title>
		<link>http://www.saunderslog.com/2006/05/17/qos-quality-of-suppression/#comment-2203</link>
		<dc:creator>Alec</dc:creator>
		<pubDate>Wed, 17 May 2006 11:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/05/17/qos-quality-of-suppression/#comment-2203</guid>
		<description>It&#039;s funny Frank, but the QoS I&#039;ve used really successfully at home has been pretty brute force.  My Linksys WRT54GS router has the ability to prioritize traffic from individual MAC addresses high.  I simply told it that the ATA devices got priority over everything else.  Boom!  Great quality... it&#039;s not courteous, but it works. 
 
I&#039;m not sure whether painting packets, or whatever else, is the right way to do this.  But I don&#039;t think it&#039;s hard if the parties with vested interests can get to the table.  Or, as the article points out, maybe that isn&#039;t their intent. </description>
		<content:encoded><![CDATA[<p>It&#039;s funny Frank, but the QoS I&#039;ve used really successfully at home has been pretty brute force.  My Linksys WRT54GS router has the ability to prioritize traffic from individual MAC addresses high.  I simply told it that the ATA devices got priority over everything else.  Boom!  Great quality&#8230; it&#039;s not courteous, but it works. </p>
<p>I&#039;m not sure whether painting packets, or whatever else, is the right way to do this.  But I don&#039;t think it&#039;s hard if the parties with vested interests can get to the table.  Or, as the article points out, maybe that isn&#039;t their intent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Miller</title>
		<link>http://www.saunderslog.com/2006/05/17/qos-quality-of-suppression/#comment-2202</link>
		<dc:creator>Frank Miller</dc:creator>
		<pubDate>Wed, 17 May 2006 09:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/05/17/qos-quality-of-suppression/#comment-2202</guid>
		<description>Its been interesting to watch the progression of QoS implementations over the last 15 years.  The bottom line is that you just need to identify the high priority traffic somehow and handle is more quickly than other traffic.  Diffserv works for this but nobody does it and when they do, there&#039;s no agreement on the actual painting of packets.  The only thing that has worked has been some kind of &quot;segregation&quot; of traffic in an arbitrary way.  This means separate timeslots in a T-1 or PVC or SVC in an ATM network, essentially, reserved bandwidth. 
 
The real problem is, if we can&#039;t get devices (and their users) to be &quot;curteous&quot; about sharing their bandwidth, you&#039;re really left with traffic segregation as the only means to really make sure it works.  As soon as you start talking about segregation, you&#039;ve introduced overhead and overhead needs to be paid for.  I guess my point is, I don&#039;t see this as some kind of conspiracy.  The telcos may be capitalizing on the problem, but the underlying problem is real and the solution they&#039;re using is really the best way to solve the problem.  Unfortunate, not a conspiracy. </description>
		<content:encoded><![CDATA[<p>Its been interesting to watch the progression of QoS implementations over the last 15 years.  The bottom line is that you just need to identify the high priority traffic somehow and handle is more quickly than other traffic.  Diffserv works for this but nobody does it and when they do, there&#039;s no agreement on the actual painting of packets.  The only thing that has worked has been some kind of &quot;segregation&quot; of traffic in an arbitrary way.  This means separate timeslots in a T-1 or PVC or SVC in an ATM network, essentially, reserved bandwidth. </p>
<p>The real problem is, if we can&#039;t get devices (and their users) to be &quot;curteous&quot; about sharing their bandwidth, you&#039;re really left with traffic segregation as the only means to really make sure it works.  As soon as you start talking about segregation, you&#039;ve introduced overhead and overhead needs to be paid for.  I guess my point is, I don&#039;t see this as some kind of conspiracy.  The telcos may be capitalizing on the problem, but the underlying problem is real and the solution they&#039;re using is really the best way to solve the problem.  Unfortunate, not a conspiracy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

