<?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/"
		>
<channel>
	<title>Comments on: DOCSIS 3.0 Tutorial &#8211; CMTS Architecture</title>
	<atom:link href="http://volpefirm.com/blog/docsis-3-0/docsis3_architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://volpefirm.com/docsis-3-0/docsis3_architecture/</link>
	<description>A Technical Communications Company</description>
	<lastBuildDate>Wed, 16 May 2012 06:51:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Branco</title>
		<link>http://volpefirm.com/docsis-3-0/docsis3_architecture/#comment-231</link>
		<dc:creator>Branco</dc:creator>
		<pubDate>Wed, 21 Dec 2011 09:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=360#comment-231</guid>
		<description>Hi Cable Guys,

Great tutorial Brady ! Thanks a lot, your website helps me so much.
In Europe, I see that a French Cable Operator begins to deploy the RF spanning option with MC20x20 instead of rolling new MC3G60 linecards out .
By using one DSport per Linecard to spreading four QAM channels over the other four DSports, we have at last 8 Downstream frequencies, but 4 primary downstreams only and 4 serving groups...

So what does this RF spanning solution stand for ? 

It will be better to roll MC3G60 out. I understand that there is a cost-effective choice for the cable operator but the QoS for subscribers won&#039;t be great...</description>
		<content:encoded><![CDATA[<p>Hi Cable Guys,</p>
<p>Great tutorial Brady ! Thanks a lot, your website helps me so much.<br />
In Europe, I see that a French Cable Operator begins to deploy the RF spanning option with MC20x20 instead of rolling new MC3G60 linecards out .<br />
By using one DSport per Linecard to spreading four QAM channels over the other four DSports, we have at last 8 Downstream frequencies, but 4 primary downstreams only and 4 serving groups&#8230;</p>
<p>So what does this RF spanning solution stand for ? </p>
<p>It will be better to roll MC3G60 out. I understand that there is a cost-effective choice for the cable operator but the QoS for subscribers won&#8217;t be great&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agnet</title>
		<link>http://volpefirm.com/docsis-3-0/docsis3_architecture/#comment-230</link>
		<dc:creator>Agnet</dc:creator>
		<pubDate>Tue, 13 Jul 2010 02:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=360#comment-230</guid>
		<description>We like I-CMTS for new introdution.</description>
		<content:encoded><![CDATA[<p>We like I-CMTS for new introdution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Slimjim100</title>
		<link>http://volpefirm.com/docsis-3-0/docsis3_architecture/#comment-229</link>
		<dc:creator>Slimjim100</dc:creator>
		<pubDate>Tue, 22 Jun 2010 13:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=360#comment-229</guid>
		<description>Brady,

    I have had the pleasure to work with I-CMTS, M-CMTS, &amp; hybrid-CMTS. I think that all the different designs have there place and uses and it can come down to many things that will decide your deployment. I know MSO&#039;s that deploy M-CMTS &amp; I-CMTS in the same systems and the reason being is capacity in some hub sites over others. I personally like the M-CMTS due to the raw number of QAM’s I have to combine with and the fact I can easily add more QAM’s without setting up more chassis&#039;s and this can be a space saver in a crowded head-end. I even have seen customer go the hybrid route where they started with an I-CMTS and added M-CMTS to the CMTS to run additional QAM for other services.  It’s not just about cable modems anymore there are so many different services running over the DOCSIS plant you need flexibility. At the end of the day it comes down to needs, budget, and design.

-Brian (Slimjim100)</description>
		<content:encoded><![CDATA[<p>Brady,</p>
<p>    I have had the pleasure to work with I-CMTS, M-CMTS, &amp; hybrid-CMTS. I think that all the different designs have there place and uses and it can come down to many things that will decide your deployment. I know MSO&#8217;s that deploy M-CMTS &amp; I-CMTS in the same systems and the reason being is capacity in some hub sites over others. I personally like the M-CMTS due to the raw number of QAM’s I have to combine with and the fact I can easily add more QAM’s without setting up more chassis&#8217;s and this can be a space saver in a crowded head-end. I even have seen customer go the hybrid route where they started with an I-CMTS and added M-CMTS to the CMTS to run additional QAM for other services.  It’s not just about cable modems anymore there are so many different services running over the DOCSIS plant you need flexibility. At the end of the day it comes down to needs, budget, and design.</p>
<p>-Brian (Slimjim100)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brady</title>
		<link>http://volpefirm.com/docsis-3-0/docsis3_architecture/#comment-228</link>
		<dc:creator>Brady</dc:creator>
		<pubDate>Tue, 22 Jun 2010 12:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=360#comment-228</guid>
		<description>Stewart,

Thanks for feedback on your experience with I-CMTS vs. M-CMTS architectures.  I would appreciate this type of feedback from users in live networks.  I have experience in networks where trouble occurs and much more in the traditional 6-foot plant.  The real test comes from those of you who are living the day-in day-out trials of these architectures in a production environment.  So please continue to provide feedback.

-Brady</description>
		<content:encoded><![CDATA[<p>Stewart,</p>
<p>Thanks for feedback on your experience with I-CMTS vs. M-CMTS architectures.  I would appreciate this type of feedback from users in live networks.  I have experience in networks where trouble occurs and much more in the traditional 6-foot plant.  The real test comes from those of you who are living the day-in day-out trials of these architectures in a production environment.  So please continue to provide feedback.</p>
<p>-Brady</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stewart</title>
		<link>http://volpefirm.com/docsis-3-0/docsis3_architecture/#comment-227</link>
		<dc:creator>stewart</dc:creator>
		<pubDate>Tue, 22 Jun 2010 09:17:24 +0000</pubDate>
		<guid isPermaLink="false">http://bradyvolpe.com/?p=360#comment-227</guid>
		<description>Brady,
I&#039;ve had experience of both, although not naming vendors. When the idea of a M-CMTS was mooted, I didn&#039;t fancy it. I still don&#039;t. The idea was sold on the basis you could take some of the components and bunch them together-with only the RF parts being in the remote hubsites. This hasn&#039;t happened-edge QAM&#039;s for VOD are still being used for VOD, and the same is true for DOCSIS. I haven&#039;t seen the over lap-yet.
I&#039;m not saying the DOCSIS 3.0 I-CMTS is foolproof either-but I think that is down to the ever increasing tech that goes into these boxes. DOCSIS 1.0 was very simple when you look back at it-but insecure and easily hackable as well-that&#039;s progress, I suppose :-)
When I worked in telco circuit switches, the thing that always screwed you up were the external timing sources-drift will always be a problem-whereas if everything is on the same physical backplane, the problem goes away.
Everybody to their own-different vendors will do it different ways but I find it interesting a certain vendor has gone back on it&#039;s promise not to build DOCSIS 3.0 cards for its &quot;pizza box&quot; chassis-all down to customer pressure. The easy upgrade path for D1 to D3, definetly, but not as lucrative for the sales people ;-)</description>
		<content:encoded><![CDATA[<p>Brady,<br />
I&#8217;ve had experience of both, although not naming vendors. When the idea of a M-CMTS was mooted, I didn&#8217;t fancy it. I still don&#8217;t. The idea was sold on the basis you could take some of the components and bunch them together-with only the RF parts being in the remote hubsites. This hasn&#8217;t happened-edge QAM&#8217;s for VOD are still being used for VOD, and the same is true for DOCSIS. I haven&#8217;t seen the over lap-yet.<br />
I&#8217;m not saying the DOCSIS 3.0 I-CMTS is foolproof either-but I think that is down to the ever increasing tech that goes into these boxes. DOCSIS 1.0 was very simple when you look back at it-but insecure and easily hackable as well-that&#8217;s progress, I suppose <img src='http://volpefirm.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
When I worked in telco circuit switches, the thing that always screwed you up were the external timing sources-drift will always be a problem-whereas if everything is on the same physical backplane, the problem goes away.<br />
Everybody to their own-different vendors will do it different ways but I find it interesting a certain vendor has gone back on it&#8217;s promise not to build DOCSIS 3.0 cards for its &#8220;pizza box&#8221; chassis-all down to customer pressure. The easy upgrade path for D1 to D3, definetly, but not as lucrative for the sales people <img src='http://volpefirm.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

