Light Reading Mobile – Telecom News, Analysis, Events, and Research
LR Cable News Analysis  

Diving Into Docsis 3.1

October 18, 2012 | Jeff Baumgartner |

ORLANDO -- Cable-Tec Expo -- The big Docsis 3.1 reveal is set to happen here Thursday afternoon as engineers from several cable operators and CableLabs detail the goals and timing of the industry's next-generation IP platform. (See Docsis 3.1 Will Change Cable's Data Channels, Docsis 3.1 to Be Smarter, Faster & Cheaper and Docsis 3.1 to Be Revealed at Cable-Tec Expo.)

We'll have more details on that session soon, but in the meantime, Light Reading Cable has caught up with some of the people tasked with developing those specs and creating the actual equipment.

Jorge Salinger, the VP of access architecture at Comcast Corp., offered his take on the anticipated goals of Docsis 3.1 and when it will become "real," and discussed how cable intends to migrate to the new platform while continuing to support its broad deployment of Docsis 3.1.

Comcast's Jorge Salinger talks about the goals of Docsis 3.1 and how it will be designed to work with previous generations of cable's IP data platform

To gain some insight from the vendor side, we also caught up with Mark Palazzo of Cisco Systems Inc. to ask why the industry is pursuing Docsis 3.1 now, and how the new specs will fit into the company's product roadmap and when. (See Cisco Hints at What Comes After Docsis 3.0.)

Cisco's Mark Palazzo explains how Docsis 3.1 will fit into the company's product roadmap for network equipment and broadband modems

To keep up on news from the show, please visit our Cable-Tec Expo dedicated show site.

— Jeff Baumgartner, Site Editor, Light Reading Cable



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Related Content
Most Popular
Read
White Papers SPONSORED CONTENT
Featured
Resource Library SPONSORED CONTENT
Orthogonal Frequency Division Multiplexing (OFDM)
A modulation scheme where one high-speed signal is split into multiple lower-speed signals