10 Fun Facts about our Film The Near Future. Ready for Anything.

Eric Klassen
Executive Producer and Innovation Project Engineer

Aug 9, 2018

"Ideas without execution are a hobby, and true innovators are not in the hobby business." -- Phil McKinney

This week at our Summer Conference we released a short a film titled The Near Future. Ready for Anything. The third in our Near Future series focusing on virtual reality and AI, the film highlights how our broadband networks and increased connectivity will play a crucial role in the innovations of the future in the field of education.

  1. To cast the lead role, a casting agency started with 50 young women. The producers listened to readings from the top 25 and Callbacks were done for the top 10, 5, 3, 2 and finally, the star of the film, Violet Hicks, was chosen for the role of Millie.
  2. The video-wall scene was created by constructing two separate classrooms next to each other with a large glass pane for the shared wall. After the scene was shot, both classrooms were torn down, including carpet, walls, and window tint, all in the same day.
  3. The rainbow cut-outs on the school wall were actual school art projects. All other classroom items on the walls, including the desks and chairs were ordered from a props company specifically for the film.
  4. Cookie the robot from The Near Future. A Better Place. makes a cameo appearance in the background of one of the classrooms.
  5. To get the AI Agent to appear to float on the moon, the actress stood on a green painted Lazy Susan-like disk, and two technicians manually spun her around on it as she was being filmed. The green disk was removed in post-production and replaced with visual effects, and the actress was shrunk down to the appropriate size for the scene.
  6. The name, Dot, is a take on the first smart watch, Spot, from 2004.
  7. The garden scene was shot at an elementary school in Mill Valley where gardening is a part of the curriculum.
  8. The Light Field scene at the end required a very specific office layout. Several offices were scouted over several weeks and one was finally found in a high-rise in downtown San Francisco.
  9. That same Light Field scene took about 20 takes to get all four actors to choreograph their parts properly, on top of having no reference to the holodeck media they should be seeing.
  10. Prior to filming The Near Future. Ready for Anything., the film’s camera technician had just finished work on Jurassic World, and has worked on every film in that series since the first Jurassic Park in 1999. The amount of green screen work and visual effects in the film required his expertise.

Now, sit back, relax and see if you can spot all 10 in our video:

You can learn more about the integral role the cable industry is playing in the innovations of the #nearfuture by clicking below.

Learn More About The Near Future


  CableLabs Unveils its Vision of the Future of Education

Aug 7, 2018

According to a 2018 national Education Week survey, the majority of education leaders report that digital technologies are an important supplemental resource used to personalize the learning experience based on each student’s strengths, weaknesses and preferences.

How can children be prepared for a work environment that looks nothing like today? How can subjects be taught that don’t yet exist? And how can students be well equipped for future problems that are currently unknown? In order to be prepared for this vision of the future, education needs to teach a lifelong love of learning.

Today, CableLabs is here to invent a better future. We created the Near Future film series to serve as an inspiration for innovators. As the industry-leading provider for broadband, we want to guide those creating technologies and experiences supported by the broadband platform. Our vision uses network technologies to help create a compelling learning environment for students of all ages. The technologies make environments more creative, collaborative, and personal, always leaving the students wanting to come back for more and ready for anything.

Now, take a peek into our vision of the Near Future...

Learn More About The Near Future


Innovation Showcase 2018: Summer Conference

Scott Brown
VP of Technology Outreach & Managing Director of UpRamp

Aug 6, 2018

The UpRamp team is currently at Keystone Resort for CableLabs Summer Conference 2018, where Innovation Showcase is bringing together eight of the top young startups in connectivity to give live demos to decision-makers in the connectivity industry. At the end of the event, the audience will vote on the Best New Product.

Since Innovation Showcase began, over 300 startups have given live demos of their cutting-edge technology to high-level, curated, private audiences - with another eight presenting at this Summer Conference. The incredible technology that has come across the stage is a testament to the burgeoning relationship between the global connectivity industry and the startup ecosystem.

The technology being demoed at this Innovation Showcase went through a rigorous selection process to determine its potential future place within the connectivity industry. UpRamp’s programming was designed to provide a gateway at every stage of the entrepreneurial lifecycle, and we’re excited to continue collaborating with these startups as they establish a name for themselves among our members.

Read More on the UpRamp Blog


Introducing #Fiterator3: CX, Edge Compute, and Cybersecurity

Lisa Schwab
Program Director, UpRamp

Aug 6, 2018

In late 2017, we graduated three incredible startups from the second Fiterator cohort. While we continue to collaborate with them and help them gain traction within (and outside of) our industry, they’re busy making over 40 deals happen - so it’s time to look into the future and introduce the 2018 Fiterator cohort!

We’re really excited about the technologies our new cohort brings to the table this year, ranging from identity security to AI-enabled VR/chat support to a twist on cloud computing. The teams are also pretty badass, and what’s even more exciting is how they are going to impact member companies and their customers. We’ve been hard at work vetting the technology, teams, and business models of these startups - and we’re excited to introduce them.

We proudly present Fiterator 2018:

Read More on the UpRamp Blog


CableLabs Innovation Series: Transforming Ideas into Solutions

Ike Elliott
Chief Strategy Officer and Senior VP, Strategy and Innovation

Aug 2, 2018

Innovation is both an art and a science. It is equal parts inspiration and hard work. It requires creativity and systems, passion and persistence. And most of all, innovation requires people — teams of people that work together to create what none of them could do on their own.

CableLabs is arguably one of the most impactful industry innovation labs in the world, generating immense value for the dollars invested by our members. A prime example:

Technology developed and specified at CableLabs is used by over half a billion people in the world every day, and the number is growing rapidly.

What is the secret to that success?

  • Do we have better researchers?
  • Do we have better leadership?
  • Do we have better facilities?

While we do have great people, we have fewer than 200 of them, so surely other research groups vastly outnumber us. We do have good leaders, and excellent facilities, though we don’t believe we have a monopoly on these. So, none of these things by themselves explain the success we’ve had.

From the founding of CableLabs until today, we have recognized that our success derives from two things:

  1. Our position in an ecosystem, and our practical focus on building innovations that will really be adopted. The ecosystem is made up of companies, yes, but within these companies are individuals.
  2. And the real secret is that we multiply the impact of our almost 200 people by engaging with the ecosystem and bringing the power of thousands of additional people to bear on our industry’s needs.


Ideas are where innovation starts, so CableLabs casts a wide net for ideas by working with our own teams, and also engaging the ecosystem around us. We create programs and often organize teams to gather participants from our members, from vendors, from academic researchers, co-innovation partners, and startups, as shown on the Innovation Input section of the diagram below. A few examples:

  • Full Duplex DOCSIS: A technology that allows radio frequency spectrum to be simultaneously used for upstream and downstream communications on the cable plant, was inspired by an idea that we found through academic research work with Stanford a number of years ago.
  • Low Latency DOCSIS Mobile Backhaul: Our work came out of a collaboration with Cisco, a major vendor to the cable industry.
  • Proactive Network Maintenance: A CableLabs project that enables operators to find plant maintenance needs before they become customer impacting, resulted from a close collaboration with Comcast, one of our members.
  • UpRamp: Our team engages deeply with the startup community, evaluating over 1,000 new startups every year to find the handful that will be selected for our Fiterator program.
  • We also source ideas internally, collecting over 200 potentially impactful ideas every year from our teams at CableLabs, Kyrio, and UpRamp.
Cablelabs Ecosystem Innovation

Click the image for more information

We take this big pile of ideas and systematically sort them, filtering out the ideas that won’t create enough impact, or the ideas that are best pursued by other parts of the ecosystem. Once we have an idea that we think has promise, the ecosystem engagement continues. We often work on the idea together with vendors, startups, and members to build and validate the idea, asking and answering questions like:

  • Does the technology really work?
  • Does it really save as much money as we thought?
  • Does the customer really want it?

The ideas that make it through testing and still look good are ready to go to the next step.


Once we know that an idea has been validated and can have a major impact for our members, we turn our attention to commercialization. The end objective here is to really finish the race, which means that our work is not complete until members have deployed the technology and are generating revenue, cost savings, or improved user experiences with the idea. We get tired of hearing it, but our CEO Phil McKinney is right when he says that:

“Ideas without adoption are a hobby, and we aren’t in the hobby business.”

Here, we have a lot of tools in the toolkit, because it is important to use the right tool for the job with each individual idea. Broadly, as shown on the Commercialization Output section of the diagram above, our commercialization paths include:

  • Specifying technology for production by the vendor ecosystem
  • Licensing intellectual property, including contributions to open source communities
  • Direct adoption by members or by other companies outside of the cable industry
  • Commercializing services and digital products for member or non-member companies through our subsidiary, Kyrio
  • Through our UpRamp subsidiary, helping startups adapt their products to the industry’s needs and having the startup make direct sales to cable operators

Here are a few examples of how we use these different commercialization paths:

  • We created intellectual property when we developed our Proactive Network Maintenance (PNM) technologies, and now we license this intellectual property to the vendor ecosystem for use in products that serve our industry. It is free for use on member networks. For non-member networks, the vendors pay a fee.
  • We developed systems and technology to support the use of digital security certificates in cable modems, and we leverage that work through Kyrio, which sells digital security certificates to many industries, including the energy, medical, and communications equipment industries.
  • We work closely with vendors and members to help write the specifications for every DOCSIS release, and we test vendor DOCSIS gear against those specifications with Kyrio.
  • We developed open source software for our SDN NFV Application Platform and Stack (SNAPS), and for our Low-Power Wide Area Networking LoRa Server, and license that software through the open source community.

It Takes an Ecosystem

Any world-class innovation effort needs to leverage ideas and resources throughout the ecosystem of suppliers, researchers, startups, and adopting companies or customers in order to find the best ideas and get them commercialized. At CableLabs, Kyrio, and UpRamp, we are continuing to develop the relationships with key ecosystem partners, because we know that we can’t achieve our mission to deliver impactful innovation without the whole ecosystem working together. It is only through collaboration that we can continue as one of the world’s most impactful industry innovation labs.

This is an introduction to how CableLabs' ideas become solutions. Subscribe to our blog to automatically receive the next installment of our CableLabs innovation story. 



But it’s Just a Light Bulb, Does it Need All This Security?

Brian Scriber
Principal Architect, Security

Aug 2, 2018

A version of this blog was published by S&P Global Market Intelligence.

In IoT security, one of the common arguments is about “how much security” a given device needs (as if we could measure that in grams). The typical example is usually a light bulb. The objective in asking the question this way is usually to vacate some or all of the security requirements for that class of device; the real question we care about, however, is the security available to protect the network, not the just the device.

Lightbulb iot security

The light bulb question tricks us into thinking in the wrong frame, it focuses on the device and not the network.

  • Why would anyone attack this?
  • What would they do if they compromised it, turn my light on and off?
The real question is about the security available to protect the network, not the just the device.

If an attacker were able to compromise the light bulb, they may initially try to test the compromise with a change in command from on to off and back again, but then they would likely not do anything else that would signal the fact that they’ve gained control over that device. The likely target was never the light bulb, this is just a means to an end and part of a larger attack vector.

The light bulb is an interesting initial attack target for several reasons. One of the most pertinent aspects is the fact that the bulb has constant power. The light may be off, but the “smart” element of the bulb is awake and listening to network traffic. The bulb also has a network stack, this is how it communicates with the smart light switch, the rules engine, the family hub, or the owner's phone; this bulb isn’t just listening, it’s also transmitting on that network.

The likely target was never the light bulb, this is just a means to an end and part of a larger attack vector.

To do this work, the bulb also has a processor; since custom hardware is expensive, that processor can likely perform many functions (so that it can be included in other IoT devices) if not address them all generally. The light bulb also has storage for maintaining state, auditing, and communication, memory to run the operating system and the network stack. Additionally, the bulb also includes drivers for the filament, LEDs, coloration, and dimming aspects of the bulb. Most importantly, when we onboard the light bulb into a network that allows us to control the bulb, we provision that device with networking credentials.

The combination of the above aspects of the smart bulb, combined with either the extremely unlikely chance of discovery or the potentially less likely chance that the firmware or operating system will be updated by the user, make this an excellent first attack point for a network. Once compromised, the attacker can cautiously watch the network, potentially interact with other devices on the same network (including cameras and sensors), spoof other devices, and even perform some physical actions that could compromise the safety of the inhabitants of the home (e.g. by advising the front door to unlock or turning the oven on).

iot security lightbulb

It’s unlikely that anyone - other than a prankster or the neighbor whose house you insist on parking in front of - wants to turn your light off and on. That said, the likelihood of other malicious attacks, the ability to gain access to your network and to the other devices in your home make the light bulb a perfect first step in an attack. A well-known cybersecurity attack principle is lateral movement. An adversary compromises a less protected target on a network and then uses that device or system as a pivot point to perform reconnaissance, move laterally in the network, escalate privileges, and finally reach their objectives.

The ability to find devices such as a light bulb and attack them has never been easier; adversaries can use device identification tools (e.g. to find these light bulbs (both online and as a pin on a map) and then attack them. Some of these light bulbs provide discovery and introspection information that may make for easy interactions within the home but also allow attackers to look up specific attacks based on known vulnerabilities in that bulb’s device and firmware version. These attacks are carried out either locally from a radio within the attacker’s car, or from across the globe, if they’re internet-connected.

Once the light bulb is compromised, they can horizontally attack the rest of the network, attempt to escalate privilege, interact with the other devices, and even use other legitimate devices to spoof interactions with outside equipment, other internet connected services, or other bridged devices within the home. Underestimating the importance of the security for all devices leads to holes in network security and is a path to risk exposure (financial, privacy, safety, litigation, and well-being). It’s not just a light bulb, it’s the network, and that network needs to have strong security.

At CableLabs, we are partnering with manufacturers and working to protect consumers and their networks; to do this, we are contributing device security expertise to IoT standards bodies like OCF and to open-source initiatives like IoTivity. Please join us in these initiatives, either as part of the creation and engineering process or by leveraging this work in your devices.

Join Us


Introducing the DOCSIS Synchronization Techniques Specification

Jennifer Andreoli-Fang
Distinguished Technologist, Wireless Technologies

Jul 31, 2018

It’s been nearly a year since the Mobile Backhaul vendor and operator team that I lead started working on techniques to improve DOCSIS® technology to provide better backhaul for mobile. One of the team’s main and most pressing issues was to solve the problem of how to provide precision synchronization and timing.

Today, I am happy to announce that we have published the first draft release of the Synchronization Techniques for DOCSIS Technology Specification. This spec is the first under a new category of DOCSIS specs designed for Mobile Applications.

Synchronization service is fundamental to any mobile deployment

You can read all about the technical details in the SCTE white paper that I co-authored last year. Traditionally, macrocell sites use GPS for synchronization. But as small cells are being deployed on a large scale, GPS may not be an economic solution, and may not be feasible in deployment scenarios, such as instances when there isn’t a clear view of the sky outdoors or indoors. This is why the transport and the backhaul networks will need to provide timing services.

The Solution? DOCSIS Time Protocol

With the varying network architectures that our mobile operator members have, how do we approach the solution? Turns out the common denominator is DOCSIS Time Protocol (DTP). One of the most significant challenges DOCSIS technology faces in providing precision timing service is the differences in delay in forward and reverse paths due to network asymmetry. This means standard protocols such as Precision Time Protocol (PTP) cannot be carried over the DOCSIS network directly.

DTP was introduced back in 2012 as part of DOCSIS 3.1 specs, in order to solve the asymmetry issue. In this draft release of the mobile sync spec, the team specified the performance requirements on the DOCSIS equipment when running DTP, in order to meet an end-to-end timing performance budget that the mobile operators require for LTE and LTE-A deployments.

Future Plans

  • My team will be working on a second draft release that focuses on a different set of transport network requirements.
  • At the same time, we will be setting out to prove the performance capabilities of the DOCSIS equipment by establishing a Mobile Backhaul lab here at CableLabs, turning specs into a reality. We mentioned this in a previous blog in May, and we will be providing more updates later.

I hope the ability to provide reliable and precision timing services will make it easier for the mobile operators to choose DOCSIS backhaul as a high performing and economic solution.

The draft spec is available to CableLabs operator members and NDA vendors only at this time on InfoZone. As an NDA vendor with CableLabs, you get early and exclusive access to:

  • Spec information,
  • Technical papers and documentation,
  • Software code and more

You can find more information here. Don't have an InfoZone account? Register here.

A big round of applause goes to my colleagues that did a lot of the heavy lifting in the spec work: Yair Neugeboren (ARRIS), John Chapman (Cisco), Peter Meyer (Microsemi), and Alvaro Simon (Vodafone).

Visit InfoZone


Wi-Fi Proactive Network Maintenance: Making Wi-Fi Frictionless, Invisible, and Reliable

Josh Redmore
Lead Architect, Wireless Research & Development

Jul 25, 2018

The term Wi-Fi, coined by the Wi-Fi Alliance, is one of the most widely used and recognized technology terms in the world. That’s understandable when you consider facts like these:

  • KPCBs Mary Meeker, in her highly regarded annual global internet survey, found worldwide Wi-Fi networks grew from 90 million in 2012 to 450 million in 2017—an incredible 500% growth in 5 years.
  • Rakesh Taori, VP Systems and Standards at Phazr, says their research shows over 90% of travelers rate the availability of Wi-Fi as their #1 amenity when choosing a hotel.

Hotels, retailers, corporations, and others dependent on Wi-Fi networks understand its importance and value to their businesses. They are concerned with their Wi-Fi’s uptime availability and are eager to develop proactive network maintenance capabilities.

Proactive network maintenance (PNM) is a revolutionary philosophy. Unlike reactive or preventive maintenance, proactive maintenance depends on a constant and rigorous inspection of the network to look for the causes of a failure, before that failure occurs, and not treating network failures as routine or normal. PNM is about detecting impending failure conditions followed by remediation before problems become evident to users.

Multiple Systems Operators (MSOs) report that no standard exists currently to capture key performance data from residential Wi-Fi. Proprietary solutions exist, but the problem is they lock MSOs into deploying a specific agent onto the consumer premise equipment (CPE) and can be restrictive in terms of analytics availability. At CableLabs, we’re determined to change that.

Promising Wi-Fi PNM Field Trial

We created a proof of concept Wi-Fi PNM-enabled Access Point, which we then tested in a field trial involving 10 members in 7 countries and hundreds of millions of data points. The captured data demonstrated our ability to identify Wi-Fi issues remotely, such as poor coverage and time-based channel degradation. With this proven architecture, we successfully lobbied the Wi-Fi Alliance to create a task group around Wi-Fi PNM.

Wi-Fi Data Elements Vision

We’re working with the Wi-Fi Alliance and their members to create the global standard for KPI capture—called Wi-Fi Data Elements. These data elements form a standardized data model that encompass the key performance indicators (KPI's) of a Wi-Fi network. Our aim is the rapid collection of data necessary to respond to the dynamic nature of Wi-Fi in residential, small and midsize businesses, and operator-managed enterprise systems.

  • Data—both a lack of and an overabundance—is holding up efforts to enact Wi-Fi PNM: Traditionally, cable operators have taken an all-or-nothing approach when polling information from a residential gateway, which means all MIBs or other data objects are polled at once. This could mean polling over 400 objects. As a result, operators minimize the number of device contacts, perhaps as infrequently as once a day.
  • Wi-Fi is a very dynamic technology, requiring a rapid response: One way to deal with this infrequent polling is to focus the data collection on a few critical pieces of information. Sending this critical information through a framework that supports scheduled and asynchronous transmission of ONLY the critical information would support scalability.
  • The majority of Wi-Fi support issues can be addressed by a handful of KPIs: An efficient framework would be one where data can be analyzed at high resolution and then distributed to OSS systems at a lower resolution. In home networks, this transmission would only occur in an exceptional condition.
  • It’s important to collectively evaluate all data: Wi-Fi troubleshooting can’t be accomplished by looking at a single data point. WFA’s release plan addresses a solution for scalable and efficient Wi-Fi PNM data collection with options for event-driven data distribution.

CableLabs would like to facilitate better use of the DOCSIS 3.1 PNM capabilities to improve the effectiveness of the Data Elements architecture by creating a single repository for all PNM data, regardless of the source. The Wi-Fi Alliance Data Elements standard furthers that vision by allowing all CPE vendors to supply the same data.

Subscribe to our blog for further updates here or at the Wi-Fi Alliance website to see how Wi-Fi Data Elements is moving forward to improve Wi-Fi availability through proactive network maintenance, making highly available Wi-Fi networks accessible for the millions of users depending on them.



CableLabs Announces SNAPS-Kubernetes

Randy Levensalor
Lead Architect, Wired Technologies

Jul 23, 2018

Today, I’m pleased to announce the availability of SNAPS-Kubernetes. The latest in CableLabs’ portfolio of open source projects to accelerate the adoption of Network Functions Virtualization (NFV), SNAPS-Kubernetes provides easy-to-install infrastructure software for lab and development projects. SNAPS-Kubernetes was developed with Aricent and you can read more about this release on their blog here.

In my blog 6 months ago, I announced the release of SNAPS-OpenStack and SNAPS-Boot, and I highlighted Kubernetes as a future development area. As with the SNAPS-OpenStack release, we’re making this installer available while it's still early in the development cycle. We welcome contributions and feedback from anyone to help make this an easy-to-use installer for a pure open source and freely available environment. We’re also releasing the support for the Queens release of OpenStack—the latest OpenStack release.

Member Impact

The use of cloud-native technologies, including Kubernetes, should provide for even lower overhead and an even better-performing network virtualization layer than existing virtual machine (VM)-based solutions. It should also improve total cost of ownership (TCO) and quality of experience for end users. A few operators have started to evaluate Kubernetes, and we hope with SNAPS-Kubernetes that even more members will be able to begin this journey.

Our initial total cost of ownership (TCO) analysis with a virtual Converged Cable Access Platform (CCAP) core distributed access architecture (DAA) and Remote PHY technology has shown the following improvements:

  • Approximately 89% savings in OpEx costs (power and cooling)
  • 16% decrease in rack space footprint
  • 1015% increase in throughput

We anticipate that Kubernetes will only increase these numbers.

Three Waves of NFV

SNAPS-Kubernetes will help deliver Virtual Network Functions (VNFs) that use fewer resources, are more fault-tolerant and quickly scale to meet demand. This is a part of a movement coined “cloud native.” This the second of the waves of NFV maturity that we are observing.

With the adoption of NFV, we have identified three overarching trends:

  1. Lift & Shift
  2. Cloud Native
  3. Autonomous Networks

SNAPS Kubernetes three waves of nfv

Lift & Shift

Service providers and vendors typically support the Lift & Shift model today. These are large VMs running on an OpenStack-type Virtualized Infrastructure Manager (VIM). This is a mature technology, and many of the gaps in this area have closed.

VNF vendors often brag that their VNF solution runs the same version of software that runs on their appliances in this space. Although achieving feature parity with their existing product line is admirable, these solutions don’t take advantage of the flexibility and versatility that can be achieved by fully leveraging virtualization.

There can be a high degree of separation between the underlying hardware and operating system from the VM. This separation is great for portability, but it comes at a cost. Without some level of hardware awareness, it isn’t possible to take full advantage of acceleration capabilities. An extra layer of indirection is included, which can add latency.

Cloud Native

Containers and Kubernetes excel in this quickly evolving section of the market. These solutions aren’t yet as mature as OpenStack and other virtualization solutions, but they are lighter weight and integrate software and infrastructure management. This means that Kubernetes will scale and fail over applications, and the software updates are also managed.

Cloud native is well suited for edge and customer-premises solutions where compute resources are limited by space and power.

Autonomous Networks

Autonomous networks are the desired future in which every element of the network is automated. High-resolution data is being evaluated to continually optimize the network for current and projected conditions. The 3–6-year projection for this technology is probably a bit optimistic, but we need to start implementing monitoring and automation tools in preparation for this shift.


This release is based on Kubernetes 1.10. We will update Kubernetes as new releases stabilize and we have time to validate these releases. As with SNAPS-OpenStack, we believe it’s important to adopt the latest stable releases for lab and evaluation work. Doing so will prepare you for future features that help you get the most out of your infrastructure.

This initial release supports Docker containers. Docker is one of the most popular types of containers, and we want to take advantage of the rich ecosystem of build and management tools. If we later find other container technologies that are better suited to specific cable use cases, this support may change in future releases.

Because Kubernetes and containers are so lightweight, you can run SNAPS-Kubernetes on an existing virtual platform. Our Continuous Integration (CI) scripts use SNAPS-OO to completely automate the installation on almost any OpenStack platform. This should work with most OpenStack versions from Liberty to Queens.

SNAPS-Kubernetes supports the following six solutions for cluster-wide networking:

  • Weave
  • Flannel
  • Calico
  • Macvlan
  • Single Root I/O Virtualization (SRIOV)
  • Dynamic Host Configuration Protocol (DHCP)

Weave, Calico and Flannel provide cluster-wide networking and can be used as the default networking solution for the cluster. Macvlan and SRIOV, however, are specific to individual nodes and are installed only on specified nodes.

SNAPS-Kubernetes uses Container Network Interface (CNI) plug-ins to orchestrate these networking solutions.

Next Steps

As we highlighted before, serverless infrastructure and orchestration continue to be future areas of interest and research. In addition to extending the scope of our infrastructure, we are focusing on using and refining the tools.

Multiple CMTS vendors have announced and demonstrated virtual CCAP cores, so this will be an important workload for our members.

Try It Today

Like other SNAPS releases, SNAPS-Kubernetes is available on GitHub under the Apache Version 2 license. SNAPS-Kubernetes follows the same installation process as SNAPS-OpenStack. The servers are prepared with SNAPS-Boot, and then SNAPS-Kubernetes is installed.

Have Questions? We’d Love to Hear from You

Subscribe to our blog to learn more about SNAPS in the future.



  Meet UpRamp Executive Director and CableLabs VP of Ventures and Outreach Scott Brown

Jul 19, 2018

Scott Brown is the Executive Director of UpRamp, backed by CableLabs. He is the driving force behind UpRamp’s mission to connect radical entrepreneurs to the most powerful network in the world.

UpRamp was established in 2016 as a platform to connect cutting-edge, agile startups with the connectivity industry with programs designed for every stage in the entrepreneurial life cycle - from idea to IPO. CableLabs members around the world look to UpRamp as a way to engage with startups, drive innovation and promote entrepreneurship. UpRamp runs several programs, including its flagship program, the Fiterator. The Fiterator is a three-month program for later stage startups to help them secure product-market fit and guarantees deals, not demo days. UpRamp also runs the Innovation Showcase series, which presents up-and-coming tech startups to the industry at several events throughout the year, including CES, CableLabs Summer Conference, and CableLabs Inform[ED].

Scott is an eight-time startup founder with a strong history of building companies from inception to profitability. As an active angel investor and advisor, he has helped hundreds of startups perfect their pitch with a framework he created called (C)lean Messaging. In 2016, Scott was credited with inventing the world's first bacon-wrapped tot.

Now, meet the man bringing radical entrepreneurship to cable.

Visit UpRamp