<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>TOS and DSCP</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx</link><description>Some weeks ago I described 802.1p . It's a way to color traffic on your local network segment. If you have network equipment aware of this tag, you can get strict prioritization at these hops. Still, the tag is at layer-2 and not layer-3; your average</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: TOS and DSCP</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#579647</link><pubDate>Thu, 20 Apr 2006 09:55:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:579647</guid><dc:creator>pankaj </dc:creator><description>How the SGW supports &amp;nbsp;DSCP/ToS bits value in the IP packets header differently for voice, data and signaling traffic.</description></item><item><title>re: TOS and DSCP</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#594995</link><pubDate>Thu, 11 May 2006 03:40:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:594995</guid><dc:creator>wndpteam</dc:creator><description>Regarding &amp;quot;How does the gateway support DSCP/TOS value in the IP packet header differently for voice, data, and signalling traffic?&amp;quot;: This is really implementation specific; there is no short answer. First, the device must implement a prioritization scheme (queue servicing algorithm for example) that differentiates traffic based on DSCP. Home standards also differ from those focused on enterprise or access networks. For example, in the enterprise, there are RFCs that clearly describe per-hop behaviors (PHB) that directly answer your question. these PHBs can be implemented in most enterprise class routers. In the home, there is no specific standard that defines device behavior. The WiFi WMM (wireless multimedia) specification defines which DSCP values must be used for four categories of traffic (background, best effort, video, and voice), but the MAC implementation really dictates the behavior of traffic in each of these categories. All that said, if a device implements some notion of priority, it is better than nothing. We're seeing many more consumer grade devices that implement priority schemes based on DSCP that enable streaming of high definition (HD) video. In fact, Microsoft requires a good implementation for premium router/gateway/AP devices to receive a Designed for Windows logo. For more information on this, see the whitepaper here: &lt;a rel="nofollow" target="_new" href="http://www.microsoft.com/whdc/device/network/homenet/WAP_reqs.mspx"&gt;http://www.microsoft.com/whdc/device/network/homenet/WAP_reqs.mspx&lt;/a&gt;&lt;br&gt;&lt;br&gt;</description></item><item><title>WiFi QoS Support in Windows Vista: WMM</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#650375</link><pubDate>Thu, 29 Jun 2006 05:34:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:650375</guid><dc:creator>Windows Network Development</dc:creator><description>In Windows Vista, a great deal of effort has gone into making it simple for network applications to take...</description></item><item><title>WiFi QoS Support in Windows Vista, part 2</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#652006</link><pubDate>Fri, 30 Jun 2006 11:29:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:652006</guid><dc:creator>Windows Network Development</dc:creator><description>My previous post on WiFi QoS (WMM) discussed the four access classes (BG, BE, VI, and VO) available for...</description></item><item><title>WiFi QoS Support in Windows Vista: WMM part 2</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#652018</link><pubDate>Fri, 30 Jun 2006 11:36:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:652018</guid><dc:creator>Windows Network Development</dc:creator><description>My previous post on WiFi QoS (WMM) discussed the four access classes (BG, BE, VI, and VO) available for...</description></item><item><title>Deprecating old QoS APIs</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#657206</link><pubDate>Wed, 05 Jul 2006 23:46:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:657206</guid><dc:creator>Windows Network Development</dc:creator><description>A while back I wrote about the fundamentals of networking Quality of Service (QoS) including 802.1p and...</description></item><item><title>How to find consumer network gear that rocks: part 2 (QoS)</title><link>http://blogs.msdn.com/wndp/archive/2006/03/23/559656.aspx#1632549</link><pubDate>Fri, 09 Feb 2007 10:08:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1632549</guid><dc:creator>Windows Core Networking</dc:creator><description>&lt;p&gt;The “Certified for Windows Vista” logo is comprised of requirements for myriad networking features and&lt;/p&gt;
</description></item></channel></rss>