<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for bradyvolpe.com</title>
	
	<link>http://bradyvolpe.com</link>
	<description>Explore</description>
	<lastBuildDate>Thu, 09 Feb 2012 02:31:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForBradyvolpecom" /><feedburner:info uri="commentsforbradyvolpecom" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Comment on DOCSIS 3.0 Tutorial – Upstream Channel Bonding by Ravi</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/rK4ci8GPf2k/</link>
		<dc:creator>Ravi</dc:creator>
		<pubDate>Thu, 09 Feb 2012 02:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=997#comment-22728</guid>
		<description>Thank You so much Brady for your valuable time and as usual spot on resoponse</description>
		<content:encoded><![CDATA[<p>Thank You so much Brady for your valuable time and as usual spot on resoponse</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/rK4ci8GPf2k" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/comment-page-1/#comment-22728</feedburner:origLink></item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial – Upstream Channel Bonding by Brady</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/CK1nSkqBTVs/</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Wed, 08 Feb 2012 19:13:11 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=997#comment-22711</guid>
		<description>I don't have a good reference other than DOCSIS specification itself.  Section D of the &lt;a href="http://bradyvolpe.com/library/CM-SP-MULPIv3.0-I13-100611.pdf" title="DOCSIS 3.0 MULPI Specification" target="_blank" rel="nofollow"&gt;DOCSIS 3.0 MULPI Specification&lt;/a&gt;, which starts on page 596 of the document, has a very detailed explanation of every section of the configuration file.  This is really the place to start in order to understand configuration files.

The CVC pertains to secure downloads of firmware to cable modems.  To understand this, you will want to read the &lt;a href="http://bradyvolpe.com/library/CM-SP-BPI+-C01-081104.pdf" title="DOCSIS Baseline Privacy Specification" target="_blank" rel="nofollow"&gt;BPI specification&lt;/a&gt;, starting on section 9.1, page 77.

Sorry that I don't have primers on these yet.  I've guess you've given me a number of topics to write on, however I'm deep into a downstream and upstream bonding impairment research that I hope to get a few articles out on soon.

-Brady</description>
		<content:encoded><![CDATA[<p>I don&#8217;t have a good reference other than DOCSIS specification itself.  Section D of the <a href="http://bradyvolpe.com/library/CM-SP-MULPIv3.0-I13-100611.pdf" title="DOCSIS 3.0 MULPI Specification" target="_blank" rel="nofollow">DOCSIS 3.0 MULPI Specification</a>, which starts on page 596 of the document, has a very detailed explanation of every section of the configuration file.  This is really the place to start in order to understand configuration files.</p>
<p>The CVC pertains to secure downloads of firmware to cable modems.  To understand this, you will want to read the <a href="http://bradyvolpe.com/library/CM-SP-BPI+-C01-081104.pdf" title="DOCSIS Baseline Privacy Specification" target="_blank" rel="nofollow">BPI specification</a>, starting on section 9.1, page 77.</p>
<p>Sorry that I don&#8217;t have primers on these yet.  I&#8217;ve guess you&#8217;ve given me a number of topics to write on, however I&#8217;m deep into a downstream and upstream bonding impairment research that I hope to get a few articles out on soon.</p>
<p>-Brady</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/CK1nSkqBTVs" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/comment-page-1/#comment-22711</feedburner:origLink></item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial – Upstream Channel Bonding by Brady</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/tpEZGHW9A7s/</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Wed, 08 Feb 2012 18:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=997#comment-22708</guid>
		<description>Hi Ravi,

DOCSIS 2.0 and 3.0 did add additional modulations to the upstream.  You will now find 8-PSK, 32-QAM, 64-QAM and 128-QAM with Trellis Code Modulation (TCM).  8-PSK, 32-QAM and 128-QAM w/TCM are rarely used because they do not offer substantial data increases over the standard modulation of 16- and 64-QAM.

A lot of plants have migrated to 16-QAM successfully and are in the process of determining if the RF plant can support 64-QAM.  There are a number of factors to look at including noise, group delay, micro-reflections, laser clipping, etc.

Keep in mind that 16-QAM only need 18 dB MER while 64-QAM needs 24 dB MER.  So the plant must be in a lot better shape.

-Brady</description>
		<content:encoded><![CDATA[<p>Hi Ravi,</p>
<p>DOCSIS 2.0 and 3.0 did add additional modulations to the upstream.  You will now find 8-PSK, 32-QAM, 64-QAM and 128-QAM with Trellis Code Modulation (TCM).  8-PSK, 32-QAM and 128-QAM w/TCM are rarely used because they do not offer substantial data increases over the standard modulation of 16- and 64-QAM.</p>
<p>A lot of plants have migrated to 16-QAM successfully and are in the process of determining if the RF plant can support 64-QAM.  There are a number of factors to look at including noise, group delay, micro-reflections, laser clipping, etc.</p>
<p>Keep in mind that 16-QAM only need 18 dB MER while 64-QAM needs 24 dB MER.  So the plant must be in a lot better shape.</p>
<p>-Brady</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/tpEZGHW9A7s" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/comment-page-1/#comment-22708</feedburner:origLink></item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial – Upstream Channel Bonding by Ravi</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/iZ07Mb1Nwm0/</link>
		<dc:creator>Ravi</dc:creator>
		<pubDate>Wed, 08 Feb 2012 06:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=997#comment-22663</guid>
		<description>Thanks for answering my previous query.

Wanted to understand the reason behind having QPSK or 16QAM only for Upstream while we have 64 or 256 QAM for Downstream channels.

Also it would be great iof you could point me to an article which explains all the fields of a CM configuration file.
I need to understand significance of fileds like MIC, QoS, CVC data etc..</description>
		<content:encoded><![CDATA[<p>Thanks for answering my previous query.</p>
<p>Wanted to understand the reason behind having QPSK or 16QAM only for Upstream while we have 64 or 256 QAM for Downstream channels.</p>
<p>Also it would be great iof you could point me to an article which explains all the fields of a CM configuration file.<br />
I need to understand significance of fileds like MIC, QoS, CVC data etc..</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/iZ07Mb1Nwm0" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/comment-page-1/#comment-22663</feedburner:origLink></item>
	<item>
		<title>Comment on DOCSIS 3.0 Tutorial – Upstream Channel Bonding by Ravi</title>
		<link>http://feedproxy.google.com/~r/CommentsForBradyvolpecom/~3/2TGdmd9_TLg/</link>
		<dc:creator>Ravi</dc:creator>
		<pubDate>Wed, 08 Feb 2012 02:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=997#comment-22653</guid>
		<description>Thanks Brady. You answered it well.

One more query,

Why do we have only QPSK or 16 QAM for upstream when we are using 64 or 256 QAM for downstream.

Can you also point me to an article/link which explains each field in CM configuration file....</description>
		<content:encoded><![CDATA[<p>Thanks Brady. You answered it well.</p>
<p>One more query,</p>
<p>Why do we have only QPSK or 16 QAM for upstream when we are using 64 or 256 QAM for downstream.</p>
<p>Can you also point me to an article/link which explains each field in CM configuration file&#8230;.</p>
<img src="http://feeds.feedburner.com/~r/CommentsForBradyvolpecom/~4/2TGdmd9_TLg" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/comment-page-1/#comment-22653</feedburner:origLink></item>
</channel>
</rss><!-- Dynamic page generated in 1.357 seconds. --><!-- Cached page generated by WP-Super-Cache on 2012-02-09 01:04:43 --><!-- Compression = gzip -->

