We knew the issue was a contractual one, between Netflix and content owners. They did not have the rights to stream to MSO hardware. But it seems the issue was specifically with Starz, and now that Netflix and Starz have parted ways that obstacle is gone. Well, maybe. No one is sure if the Starz deal was the only obstacle, or if there are similar clauses in contracts with other rights owners, and Netflix isn’t commenting. But there is some hope:

The Starz deal was why RCN Corp. was unable to offer Netflix on TiVo boxes when the cable operator launched its TiVo offering in May 2010, RCN Senior Director of Video Product and Video Network Operations Jason Nealis tells Light Reading Cable. He says he’s eager to reopen the dialogue with Netflix now that that Starz deal has expired.

I suppose if anyone would have inside information it’d be Jason, since he’s the point man for RCN’s TiVo implementation.

Of course, TiVo could always implement DLNA, which would open the door to work arounds. Which is how ARRIS gets Netflix on their MSO Moxi units, via PlayOn running on a user’s computer, as stated in this video:

Or, when TiVo publishes their SDK, perhaps PlayOn could create an app for TiVo.

Given TiVo’s working relationship with Comcast, and their integration of Comcast’s XFINITY On Demand into retail units, I have to wonder if we might see support for Comcast’s Streampix streaming service land on TiVo as well. That’s something I certainly would not expect to see supported on units provided by other MSOs, but it would be a welcome addition to retail units. And it would make sense, seeing as Comcast’s deal is for support or retail units and I’d expect them to be happy to have their streaming service on those boxes.

Via Light Reading Cable.

But it seems it has fallen apart, and CableOne has pulled Aria out of trials, as reported by Light Reading. But what is bad news for EchoStar could be good news for TiVo:

CableOne’s interest in EchoStar, Charlie Ergen’s technology and set-top box outfit, goes back a bit. EchoStar and TiVo Inc. were among the companies the MSO was looking at in mid-2010, when CableOne was mulling its next-gen video service strategy. TiVo has once again emerged as “a very strong candidate” for that business, a source says. Motorola Mobility Inc. remains CableOne’s primary digital set-top and security vendor.

Things have changed since mid-2010, TiVo now has a proven track record with deployments at RCN, Suddenlink, Grande Communications, and Charter. Including the ability to rapidly deploy with a new operator, proven with the short turn around time on the Grande deal. CableOne falls right between RCN and Suddenlink in size, so it would be right in TiVo’s sweet spot.

Via Light Reading.

They were very cagey in their responses, largely due to the legal issues of the pending merger and the limitations on what the two companies can do together until the merger is complete. But it certainly sounds like they’re looking at Android, probably in a form similar to Google TV, as Motorola’s new STB platform. This is exactly what I talked about in August when the merger was first announced. The buyout, or merger if you prefer, is about more than phones and patents. It seems like most of the press surrounding the merger continues to focus on just phones and patents, but Google is playing a much bigger game. Motorola only has 4% of the global smartphone market, but they’re the dominant player in the US cable STB market. Google also has SageTV, which was asked about int he videos but they declined to talk about it, and we still don’t know how it will be used. But it seems logical that it will play a role in the future of the Google TV platform and/or a related STB OS.

There are a lot questions and the answers could have a major impact on the industry. Android runs primarily on ARM core chips. Google TV launched on Intel chips, but it is moving to ARM. Cable STBs tend to use embedded chips using MIPS cores. Could Motorola STBs shift to ARM for Android? That would be a huge change for traditional STB chip vendors, and a huge opportunity for ARM vendors. A chip like a Tegra 2 or Tegra 3 would make for quite a powerful STB. Consider that today’s high end smartphones have far more processing power, graphics power, and protocol support than pretty much any cable STB on the market. And MVPDs are increasingly looking to OTT features to enhance their services and attract and retain customers.

But I’m extrapolating a bit, certainly reading into some of the things that were said, or not said, in the videos. There are a lot of interesting points in the videos. The first is primarily about the cable business and the second discusses tablets and if MSOs might start offering tablets as a part of their service, just like leasing an STB.

Here are the videos, see what you think:

The user still has to request specific recordings, and a separate copy is kept for every user. If you and ten of your neighbors record the same program, eleven copies are kept on the head end. While this is inefficient and, frankly, stupid, from a technical standpoint, it is due to legal requirements. Cablevision is deploying nDVRs in some of their territories in NY and CT. They were sued by content providers over the nDVR – and won. But the ruling hinges on the fact that the nDVR works just like a ‘normal’ DVR with each user recording their own content. The functionality is the same, only the storage has moved from the customer’s home to the central office. Making one copy and providing access to multiple users would be redistribution, legally, and is a no-no. Hopefully someday the law will catch up to reality, but I’m not holding my breath.

There is one point in the Light Reading article reporting on this that I’m not sure I agree with:

That means EchoStar’s system will be built to store the individual programs a given customer sets to record, and won’t back up that data. So if a hard drive fails, all of the recorded content on that drive goes poof.

My understanding is that, while the ruling does require separate recordings for each user and would not allow backups, it doesn’t forbid using modern storage technology such as RAID. Indeed, there are some home DVRs that use RAID today. For the non-geeks, RAID is Redundant Array of Independent Drives. To over-simplify, picture to physical hard drives acting as one logical drive, with two copies of everything – one copy per drive. You only have the storage capacity of one drive, but you have redundancy – if one physical drive fails you don’t lose any data, it is safely on the other drive. And you can swap out the dead drive, copy everything over, and restore redundancy with nothing being lost. Since I’m sure EchoStar’s system will be using commercial grade storage arrays at the central office I’d be a bit surprised if they didn’t use some form of RAID or the equivalent.

Beyond the possibility of offering some form of redundancy, there are also economies of scale. Since a storage array will be shared across many users, even with redundant recordings the total raw storage space required to support a number of users, for the same number of recordings, is less than with individual drives in every home. It just works out to be a more efficient distribution with less wasted space. The environment in a data center is likely to be better for the drives than the average home too – clean, reliable power, good environmental controls, minimal vibration, etc. And since the recordings are already in the ‘cloud’, and EchoStar is of course the owner of placeshifting pioneer Sling Media, I would expect them to include the ability to stream your recordings to other devices. And that would be without requiring you to buy a Slingbox or use your broadband connection to send the data out of your home.

EchoStar says they’ll deliver the nDVR to their first customer by the end of 2012. While sister company Dish Network normally gets first dibs on new EchoStar products, I’m not sure that will be true this time. The problem with nDVRs is that they require sending different streams, possibly multiple streams, to every home. Imagine watching one show in the living room, while three other household members watch other recordings in other rooms. That’s four data streams into your home. Now all of your neighbors are doing the same. Satellite doesn’t do this well, it is best suited for sending the same content into multiple homes because of the fixed number of transponders. Even satellite data systems are more bandwidth limited than cable, fiber, or even DSL systems. They could have something tricky up their sleeves, like a wireless data play for delivery, but I think it is more likely that this will show up with a cable MSO. Very likely a second tier MSO looking for a technical edge, much as RCN & Suddenlink have turned to TiVo.

And speaking of TiVo, many view the nDVR as a threat to TiVo as their business has been built around placing ‘conventional’ DVRs into homes. But I disagree. TiVo’s main selling point is their UI, not the fact that the hard drive is in the STB. TiVo could just as easily split their product and create an nDVR. In fact, something like the TiVo Preview could easily be the STB client for an nDVR system. Right now it is designed to stream from a DVR in the home, but that data stream could just as easily be delivered into the home from remote storage. Exactly the same way OTT content is delivered to TiVo today. If demand for nDVRs takes off I’m sure we’ll see an nDVR from TiVo. The Virgin Media TiVo in the UK already has a DOCSIS modem and it looks like the upcoming 16.x software includes DOCSIS support, which could be hinting at future US products as well. And there is MoCA as well, which could communicate with an MSO gateway unit. Saying ‘data is data’ is a bit simplistic, but not too far off the mark.

In any case, it will be interesting to see if EchoStar gets more traction with their nDVR than they’ve achieved with their SlingLoaded cable products to date.

Via Light Reading.

As Light Reading reports:

In addition to giving Entropic an undisclosed stake in privately held Zenverge, the money will go toward the development of products aimed at MSOs and other service providers that convert incoming video signals into formats that can be displayed on PCs, tablets and smartphones that are within reach of a home’s Wi-Fi network — akin to what a Slingbox does today, but without the out-of-home access element.

The companies initially will focus on a video-transcoding “sidecar” product that will connect to set-top boxes. Future implementations will be baked into network-attached storage (NAS) devices and set-tops or video gateways, says Vinay Gokhale, Entropic’s SVP of marketing and business development.

Place shifting is perhaps the key feature still missing in TiVo’s products. I think it is becoming increasingly important as MVPDs introduce direct streaming services that bypass the STB, delivering their content directly to PCs, tablets, and smartphones. There is also competitive pressure from Echostar’s SlingLoaded efforts and other products like DirecTV’s upcoming Nomad and Comcast’s Televation box, both of which use Entropic’s silicon for MoCA, but ViXS chips for the transcoding. I think TiVo needs to provide a way to stream content to remain competitive, both in retail and for their MSO partners.

The inability to stream video from a TiVo to a portable device is most painfully evident in TiVo’s iPad and iPhone apps. You can fling content from the app to view on your TiVo, and you can setup recordings, see what is on the TiVo, and manage them – pretty much everything except watch them. The real issue is that TiVo recordings are high-bandwidth MPEG-2, that’s what digital cable and ATSC OTA broadcasts both use. But the high bandwidth makes it less than ideal for streaming to mobile devices. And, even if that weren’t an issue, most mobile devices aren’t designed to handle MPEG-2. The standard for mobile devices is MPEG-4/H.264, and maybe support for other modern codecs like VC-1, DivX, and/or WebM. To stream content to an iPad, for example, TiVo really needs hardware to transcode it to H.264 first, just like a Slingbox.

One possibility is a solution along the lines of the Sling Adapter for the Dish Network ViP 722 DVR. It is a simple USB hardware dongle which handles the transcoding. The video signal is fed to the box via USB, transcoded to the proper codec, resolution, framerate, etc., for the destination device, and then fed back over the USB to the DVR. All of the network communication is handled by the DVR, as is the real intelligence. TiVo could create a transcoding dongle like this for their hardware. Now that EchoStar, Sling’s parent company, and TiVo are no longer beating on each other in court, perhaps they could even license the Sling Adapter wholesale and simply implement the required support in the TiVo software. The advantage is that Sling is the place shifting market leader and they have clients for a number of platforms. It wouldn’t be hard for TiVo to build support into their apps either.

The Nomad and Televation boxes take a different approach, the same one Entropic is apparently pursuing with Zenverge. Instead of a USB sidecar dedicated to one DVR, these are network sidecars, kind of like network attached storage. They live on the MoCA network and thus can theoretically be shared by multiple DVRs in the home. Just like the Sling Adapter does via USB, these units take a data stream of the encoded video in over MoCA, do the necessary transcoding, and feed the data back to the DVR via MoCA. The DVR then handles the intelligence for routing the transcoded video to the client device over whichever network connection is appropriate. Since the new TiVo Premiere Q and Premiere Elite will have MoCA, this would also be a viable solution for them. Older TiVo units, like the Premiere, could use the devices via Ethernet as long as there was an ECB (Ethernet Coaxial Bridge) into the MoCA network.

Given the existing supplier relationship between Entropic and TiVo, and the competitive pressure on TiVo to add place shifting, this could possibly be how TiVo gets there. This is all speculation, of course.

As for the statement that it is for streaming within the home only, that may be true for the initial plans. However, once you have the transcoding working and a solid client, extending it to streaming outside of the home is the easy part. That’s all basic network routing. If you can ever everything else working, adding that is a snap.

Via Light Reading.

I’ve seen other sites reporting that this means MSO’s will not need to allow CableCARD self-installs until November 1st – but that’s not accurate. The original rule making was that MSOs which allow any form of self-install, such as a cable box or cable modem, must allow CableCARD self-installs as of August 1st – that date is now August 8th. It also required MSOs which did not allow self-installs to begin allowing CableCARD self-installs as of November 1st – and that date remains. Since nearly all MSOs allow some self-installs the August 8th date applies to them. Here’s the details right out of the FCC rule making – with emphasis added by me:

The rules adopted in the Order are effective on August 8, 2011, with two exceptions. First, Section 76.640(b)(4)(iii), which requires cable operators to include a home networking output on high-definition set-top boxes (except for unidirectional, non-recording settop boxes), has an effective date of December 1, 2012. Second, and only with respect to operators that did not previously offer self install for leased boxes or cable modems and needed time to establish the necessary customer support infrastructure, Section 76.1205(b)(1)’s requirement that cable operators provide the means to allow subscribers to self-install CableCARDs becomes effective on November 1, 2011.

So August 8th is the new date for when most cable customers should be able to self-install their own CableCARDs and not pay for a truck roll.

Via Light Reading.

We are rolling out TiVo beyond the Boston market test, where things are going quite well and we are going to be introducing other cities, probably starting with Chicago in the first quarter next year

This isn’t too surprising as Chicago is one of two cities where Comcast has rolled out tru2way support (the other being Denver – maybe they’ll be next?), and, as Light Reading’s Cable Digital News points out, it is another territory where Comcast uses Motorola hardware. Still no word on when Comcast and TiVo will complete the work to being the software to Cisco/Scientific Atlanta DVRs.

Comcast is also running a new TV spot to advertise the TiVo software:

However, even if consumers can get their hands on the sets, there is no guarantee that they’ll be able to access tru2way content immediately. The cable industry has pledged to implement tru2way across their networks by July 1, 2009 – except for Charter which has until July 1, 2010. So early adopters may wish to check with their local MSO to see if tru2way support is available before jumping on these sets, or they may find themselves stuck with unidirectional CableCARD features until tru2way support is rolled out.

From Light Reading’s Cable Digital News.

The MOU refers to the ‘Founders’ repeatedly – these are the cable MSOs: Comcast Cable, Time Warner Cable, Cox Communications, Bright House Networks, Charter Communications, and Cablevision. New two-way devices are referred to as Interactive Digital Cable Products (IDCP), in contrast to the one-way Unidirectional Digital Cable Products (UDCP). Under the terms of the MOU, the Founders agree to support tru2way on all of their digital cable networks by July 1, 2009 – except for Charter which has until July 1, 2010 to complete their roll-out. The MOU also codifies that the tru2way specifications will be the sole means for IDCPs to access interactive cable services.

While consumer electronics adopters must adhere to the tru2way specifications and license, innovative features that are not specified but that are consistent with the specs and license ‘are allowed and encouraged’. That seems to leave room for innovation, but it remains to be seen how narrowly ‘consistent’ is evaluated. To help ensure solid support for tru2way the cable MSOs have to eat their own dog food, as it were. After July 1, 2009 (again, July 1, 2010 for Charter) the Founders agree that at least 20% of their STBs will support tru2way. That holds until they’ve deployed at least ten million tru2way-enabled STBs. This is to ensure a sufficient install base that the Founders will have a vested interest in ensuring solid support.

Since tru2way is largely a firmware specification, and specifications can evolve, the Founders agree to support any given version of the tru2way Middleware used by an Adopter’s product for five years from the date of that version’s first certification. So, in effect, that should guarantee a minimum product life of five years. Of course, it could easily be longer as Adopter’s products could receive firmware updates, and the Founders could support a Middleware version for longer than five years. Clearly it would be up to the Adopter, the CE vendor, to provide updates to newer tru2way Middleware versions, which is only fair. And to help ensure that is possible, there is an equal access provision in the MOU. Any given tru2way Middleware revision will be available to Adopters at the same time it is available to Founders. So the MSO’s won’t have any unfair advantage in being able to bring newer features to market first.

As for guide data, which was long a bone of contention over OCAP, any Founder’s digital cable system which carriers a CBS broadcast signal (which is pretty much all of them) which contains the Gemstar-TV Guide EPG data and where that Founder has an agreement covering the Gemstar data, must not block or remove said data from the CBS signal. In English? Well, Gemstar-TV Guide has an agreement with CBS to carry their EPG data. This data is used by a number of TVs, VCRs, DVRs, DVD Recorders, etc, to provide a simple on-screen EPG. The data is carried in the VBI, the vertical blanking interval, and are not part of the video itself. This has been an issue in the past as some cable MSOs have stripped out this data from the broadcast when processing the network feed for redistribution, hence making it inaccessible to CE devices that rely on it for their EPG.

So this agreement means that the Founder agree to not block or strip the data, when it is carried by the local CBS affiliate and they can legally do so, of course. This provides CE vendors with a data source for a ‘native’ EPG, as opposed to relying on the tru2way MSO-provided EPG, or a out-of-band EPG downloaded separately, as in a TiVo. The broadcast EPG does generally lack the full level of detail found in a downloaded EPG, or even the MSOs EPG, but it has the advantage of being readily available in the received signal and gives the CE vendor the ability to process and use the data as they wish, unlike the tru2way guide which comes as-is.

While the agreement seems to treat tru2way as the primary means of navigation, Adopters are free to overlay their own ‘native’ navigation with four prerequisites: 1. It must be initiated by the user each time (such as through a remote action), 2. it must be only for navigation (no ads, etc), 3. It must be transitory (sounds like once the action is complete it should return to tru2way-mode), and 4. it must appear the same on all channels. So no special ABC navigation screen that isn’t used on NBC, etc.

There is a ‘sunset’, or exit clause for the MOU. Starting July 1, 2009, if fewer than 500,000 new retail IDCPs are connected to the Founders’ networks within any given 24 month period then the Founders are no longer bound by the MOU. Basically, if the Adopters, the CE vendors, don’t hold up their end of the bargin and produce enough IDCP devices, then the cable MSOs are no longer bound to spend their money supporting tru2way on their networks and they’re free to stop, try something else, etc. Considering the number of TVs, DVRs, etc, sold at retail in this country each year, this shouldn’t be a problem – if and only if the CE vendors step up and start tru2way-enabling a sufficient number of device models. So the ball is in their court.

Licensing for the IDCPs will be under the existing CableLabs licenses, with some amendments. Certification of devices will be through CableLabs IDCP testing. Once a vendor has had five mutually agreed upon devices certified by CableLabs, then they are eligible to self-certify future devices. This is one of the compromises in the agreement. CE vendors didn’t want the expense and hassle of going through CableLabs for each new product, while the cable industry didn’t want the potential havoc caused by bad devices being connected to their networks. So now once a vendor has proven their competence level through CableLabs certification, they can be free of that requirement.

Under the MOU CableLabs will establish a Founders Advisory Board (FAB) which will apparently serve as a kind of arbitration group when changes to the tru2way hardware specification are proposed. As the board is currently specified there are nine votes – one for each of the Founders, and one for the CE Adopters as a block, one for the IT Adopters as a block, and one for the content providers as a block. That means that, should they vote in unison, the cable MSOs would always carry a majority. And you’d actually need two MSOs to break ranks and vote with the other blocks to swing the majority. But the vote is also only advisory and non-binding, so I’m not sure what it is in aid of other than as an opinion poll for the parties involved. And, of course, the FCC still has final say in the end.

CableLabs also agrees to approve or disapprove any new digital output system or content protection system within 180 days of the proposal being submitted by an Adopter, on a ‘reasonable and nondiscriminatory basis’. This will probably come into play with technologies akin to TiVo’s TiVoGuard, which protects TiVoToGo transfers. As CE vendors look to innovate and develop whole home distribution systems, etc, there may be new technologies developed to satisfy the rights holders that their content is being protected. And if CableLabs disapproves the technology, or simply fails to act within 180 days, then the Adopter can appeal to the FCC which is expected to handle the appeal in a 90-day process. Remember that a while back the NFL and MPAA tried to block TiVoGuard and TivoToGo, but the FCC approved it.

But there’s another way to get a new technology approved. If four members of the MPAA agree that the new system provides adequate content protection, then that technology will be automatically approved by CableLabs.

If tru2way is sunset and CableLabs defines a successor to CableCARD or tru2way (such as DCAS) then Adopters who are party to the MOU may participate in the development of the successor.

The definitions have some interesting tidbits. Under the MOU, ‘Digital Cable System’ only covers systems with one or more QAM channels, operating with a capacity of 750MHz or higher and with a minimum of 5,000 basic cable subscribers.

Not a lot of information, really, but it is clearly a compromise with some give and take by both the cable MSOs and the consumer electronics vendors, which is what we needed to un-roadblock two-way cable development. It is interesting that Charter gets an extra year to complete their tru2way roll-out, compared to the other five Founder MSOs. I guess Charter must be further behind in their progress than the others. Of course, I just happen to currently reside in Charter territory. Note though that the dates are for completion of deployment, some areas already have tru2way support and many more will before the year is out.

In many ways the Sezmi architecture reminds me of XStreamHD‘s plans, only where XStreamHD uses satellite Sezmi uses terrestrial broadcast. The terrestrial component seems, on its face, to be very similar to the now defunct Moviebeam system. Where moviebeam used ‘spare’ NTSC bandwidth, usually piggybacked on PBS stations, Sezmi will be ATSC to broadcast their digital signals. Broadband will be used to distribute additional content. The plans to partner with 3G providers seems to indicate that they could use 3G, or the forthcoming 4G networks, such as WiMax for distribution as well. The recently auctioned 700MHz spectrum would be perfect for this kind of use.

The Sezmi system uses a main receiver in the home, which acts as a DVR with 1TB of storage. It will also have eSATA and USB ports for storage expansion. While client boxes attached to TVs in the home provide access to the content. Sezmi is looking to offer a ‘TV 2.0′ experience, with personalization for five different users in the home. Each person will see a customized menu of their own selected program. The Sezmi system will also be able to record OTA ATSC content, and access web video from sites such as YouTube.

Frankly, I just don’t see how this will succeed. Terrestrial frequency availability is limited, and even if they used H.264 they’d only get maybe 4-6 HD channels per frequency, to get more would mean highly compressing them. Providing SD content instead of HD would allow for several times as many channels, but the market is shifting to HD. And most broadband services lack sufficient bandwidth to provide a full channel lineup. I’m guessing they’ll do something like cable systems using SDV. The broadcast will be used for high demand content that is needed by more users, while the broadband will be used for content on demand – so if a user requests a specific program that isn’t ‘mainstream’ it will come over broadband. That would allow them to avoid sending the majority of the lineup into each home all the time.

But it remains to be seen what content licenses Sezmi will be able to obtain, to offer a lineup competitive to cable and satellite. As well as the pricing, which will have to be highly competitive to get users to convert. And it will only work for those who have solid ATSC reception, and it seems like broadband will be required as well.

From a technical perspective it is interesting, but as a consumer I don’t see the appeal in what they’ve announced to date.

For more information see PC Magazine, Light Reading’s Cable Digital News, and U.S. News & World Report.

The agreement also allows CE vendors to formally participate in CableLabs processes and includes a license to use the tru2way trademark. The new agreement consolidates and simplifies two separate licenses, the CableCARD Host Licensing Agreement (Chila) and the OpenCable Application Platform Implementer Agreement. Formerly both were required for any CE vendor who wished to implement tru2way in their devices.

Via Multichannel News and Light Reading’s Cable Digital News.

Like Motorola’s MTR700, Cisco’s STA1520 will be demo’d at the upcoming Cable Show, and it will be part of the Wave 60 certification process with CableLabs, so it too could be available by early July.

Via Light Reading’s Cable Digital News.

However, it seems it was just delayed a bit. Jeff Baumgartner at Light Reading has a sharp eye and he caught something in a press release from CableLabs about the upcoming Cable Show. (I see something about Sling Media in there too…) One of the products they announced that will be on display is the Digeo Moxi HD DVR 3012. CableLabs says:

Digeo will showcase its latest DVR for cable, the Moxi HD DVR 3012. Digeo will be showing the Emmy Award-winning user interface, dual digital tuning capability, and integrated CableCARD. This new DVR includes a streamlined processor and increased hard drive.

Over at Zatz Not Funny, reader ‘cableric’ left a comment with some industry insider information on the new box, which doesn’t sound all that encouraging really.

Oh, and this is what I spotted about Sling:

EchoStar Technologies LLC will demonstrate SlingModem™, the first DOCSIS® cable modem that fully integrates the place-shifting capabilities pioneered in the original Slingbox™. With the SlingModem, customers can easily watch and control their TV programming on any Internet-connected computing device just as they would in front of the living room television. The SlingModem provides the cable customer with both a broadband connection as well as the place-shifting functionality made famous by the Slingbox.

I’ve covered the SlingModem before, most recently from CES in January.

And they also mention Motorola’s SDV Tuning Resolver, the MTR700, which will be demo’d using a TiVo:

Motorola will demonstrate its MTR700 Tuning Adapter which connects unidirectional UDCPs (including a TiVo device, in specific) to a cable network, accessing multimedia content in the cable network’s switched digital video (SDV) tier. Seamless tuning of the TiVo device across both broadcast and SDV tiers will be shown. Motorola will also demonstrate its Integrated CMTS (I-CMTS) and SURFboard® cable modems, in a DOCSIS 3.0 setting using the traditional Motorola 2:8 DS/US Module and new TX32 high-density Decoupled Downstream Module.

That’s very good news, as it means TiVo must have their software well along, which means a summer release will probably happen as planned.

It sounds like there will be a lot of SDV & tru2way demos at The Cable Show, I wish I was going.

Picked up via Zatz Not Funny.