This feature requires an Enterprise account.
In this article:
- What is Vimeo Enterprise eCDN?
- What is the difference between standard CDN and Enterprise eCDN?
- What devices & browsers are compatible?
- What happens on incompatible devices/browsers?
- What ports and domains should be whitelisted?
- How do you handle VPN?
- What is Subnet Matching?
- How do I know if it’s working?
What is Vimeo Enterprise eCDN?
Vimeo Enterprise eCDN (Content Delivery Network) is a peer-to-peer delivery system that will allow you to stream your event across your company network of users with minimal local bandwidth consumption. It’s browser-based and requires no plugins, workstation software, or hardware to install.
The eCDN enables the ability to deliver a high-quality live stream and video on demand within a corporate network without overusing or bottlenecking bandwidth. Streaming via eCDN ensures high-quality video delivery without impacting the corporate network or risking network health. It works with single sign-on (SSO) and is ideal for a corporate setting, such as internal town halls or training. This also means lower bandwidth usage—which leads to cost savings.
Enterprise eCDN is only available for Vimeo Enterprise-level accounts—if you are not currently affiliated with an Enterprise account, but would like to know more, feel free to contact our Enterprise team for more information. We provide integrations with the following eCDN:
- Kollective
- Hive Streaming
What is the difference between standard CDN and Enterprise eCDN?
Vimeo uses several different CDNs to deliver video content all over the world. Each CDN has their own network of distributed servers, called “edge servers” or “PoPs” (Points of Presence). For example, if you click on a standard video, your specific computer is requesting from a CDN.
An eCDN is a mesh sharing across a network that has capabilities to allow sharing across a local network (mesh). It requires less resources and better security since all requests are coming through the same access point.
What devices & browsers are compatible?
- Operating systems: Windows, MacOS, Linux
- Mobile devices: All the latest versions of mobile web browsers. The Vimeo app is not supported.
-
Browsers: All the latest versions of modern browsers except Internet Explorer.
- Browser-Based Peering and Agent- Chrome 79+, Firefox 72+, OSX Safari 12+, Edge (Chromium).
- BBP additionally supports iPadOS Safari 13.2+, iOS Safari, Chrome Android 79+, Firefox Android 68+, Teams App (Win/Mac), and Teams App (IOS/Andriod).
What happens on incompatible devices/browsers?
Both Kollective and Hive Streaming are fully hybrid solutions: for workstations on platforms that are not supported, delivery automatically falls back to full server-based delivery (no peer-to-peer is done) without any interruptions to playback or the video experience.
What ports and domains should be whitelisted?
- Kollective ECDN Network Requirements
- Kollective leverages HTTPS (TCP 443) under the *.kollective.app domain. Browser-based peering leverages the WebRTC data channel on the LAN using
- DTLS protocol (UDP 49152 - 65535).
IP Address Anonymization
To observe optimal peering performance, it is critical organizations deploy a browser policy to user devices to disable the IP anonymization features of modern browsers. Without this browser policy, peering efficiency is limited for event attendees.
In addition, your network should whitelist the following domain:
- *.kollective.app for Kollective
What ports and domains should be whitelisted for Hive Streaming?
Contact your success manager at Hive Streaming for network requirements.
How do you handle VPN?
In most situations, it’s desirable to not have VPN users peering at content through the VPN concentrator. In this case, the recommendation is to enable subnet matching and create a site that covers the VPN subnets. Within this site, peering can be disabled. Other options may include allowing split-tunneling for video traffic or handling it operationally by requiring users to disconnect from VPN to consume the video.
What is Subnet Matching?
Subnet matching is a feature of Kollective and Hive Streaming that gives network operations teams more control over the behavior of how the peer mesh forms. It helps network operators better handle the traffic inside their network.
By defining public and private pairings of IPs and subnets, users are able to define sites within their network, and thus limit peer exchanges to within the desired subnet ranges. This helps optimize the mesh formation and limits network traffic flowing over WAN links between customer sites.
If you are interested in subnet matching, reach out to your Account Manager.
How do I know if it’s working?
The technology is entirely based on standard web browser technology, and as such, it’s probably already working in your environment.
You can use Kollective's test link: https://kollective.com/vimeo to see if it is functioning appropriately. Additionally, both Hive Streaming and Kollective have analytics that you can reference during events to see the performance of the eCDN.