When it comes to making collaboration technology such as high-definition video open and broadly available, it’s clear that the web browser plays an important role. The question is, how do you enable real-time video natively on the Web? It’s a question that folks are anxious to have answered.
WebRTC--a set of enhancements to HTML5--will address the issue head on. But, there is an important hurdle that must first be cleared, and that’s standardizing on a common video codec for real-time communications on the web – something the Internet Engineering Task Force (IETF) will decide next week.
The industry has been divided on the choice of a common video codec for some time, namely because the industry standard--H.264--requires royalty payments to MPEG LA. Today, I am pleased to announce Cisco is making a bold move to take concerns about these payments off the table.
We plan to open-source our H.264 codec, and to provide it as a binary module that can be downloaded for free from the Internet. Cisco will not pass on our MPEG LA licensing costs for this module, and based on the current licensing environment, this will effectively make H.264 free for use in WebRTC.
I’m also pleased that Mozilla has announced it will enable Firefox to utilize this module, bringing real-time H.264 support to their browser.
“It hasn’t been easy, but Mozilla has helped to lead the industry toward interoperable video on the Web,” said Brendan Eich, Mozilla Chief Technology Officer. “Cisco’s announcement helps us support H.264 in Firefox on most operating systems, and in downstream and other open source distributions using the Cisco H.264 binary module. We are excited to work with Cisco on advancing the state of interoperable Web video.”
Why is Cisco Doing This? Read More »
Tags: Cisco, collaboration, H.264, html5, Mozilla, open source, video, WebRTC
The first time I met Jim Barton (DVR pioneer and TiVo co-founder) I was a young man looking at the hottest company in Silicon Valley in the day: SGI, the place where Michael Jackson and Steven Spielberg just arrived to visit, the same building in Mountain View as it were, that same week in late Spring, 1995.
The second question that Jim asked me that day was if I knew H.263 – a fledgling, new specification promising to make video ubiquitous, affordable over any public or private network – oh, those 90’s seem so far away…
For a hard core database, kernel and compiler hacker, that was a bit too much telco chit-chat for me, though remembering this was supposed to be an interview, and that the person who asks the questions is in control, not knowing the answer, I managed to mumble a question instead of an answer. Jim liked the conversation and obliged me with an explanation equally encrypted, that one day, we will have these really cool, ubiquitous players on all sorts of video devices, not just “geometry engines” running workstations in “Jurassic Park” post-production studios (actually, come to think of it, the scene itself), but over all sorts of networked devices and maybe that should be a great opportunity to dive into and change the world.
Open standards and open source live in an entangled relationship, or so I wrote about it years ago, the Yang of Open Standards, the Ying of Open Source. Never has it been more intertwined and somewhat challenging than with the case of H.264, MPEG4 and the years old saga of so-called “standard” video codecs.
Almost a generation later, even if H.263 and its eventual successors H.264 and MPEG4 came a long way, we still don’t have a truly standard and open source implementation of such a video codec, though we are hoping to change that now!
My colleagues announced today that we are open sourcing our H.264 codec. We still have a bit of work left to do as we start this new open source project and I am counting on both communities to receive it with “open” arms. It is meant to remove all barriers, to be truly free and open, as open source was meant to be.
Please join us this morning in a twitter chat covering this event. We are convinced no matter how one looks at this, it is a positive move for the industry.
Tags: codec, collabchat, collaboration, dvr, entangled, H.263, H.264, MPEG, MPEG4, Open at Cisco, open source, video, VP8, WebRTC, Ying and Yang
In the previous installment of the onePK series, you received a crash course on Cisco’s onePK. In this article, you’ll take the next step with a fun little exposé on onePK’s C API. You will learn how to write a simple program to reach out and connect to a network element. This is staple onePK functionality and is the foundation upon which most onePK applications are built.
The following short program “ophw” (onePK Hello World), is a fully functional onePK application that will connect to a network element, query its system description, and then disconnect. It doesn’t do anything beyond that, but it does highlight some lynchpin onePK code: network element connection and session handle instantiation. This is the foundational stuff every onePK application needs before useful work can get done. Read More »
Tags: Cisco, cisco ios, Cisco Security, cisco sio, IOS, ncsam-2013, network security, One Platform Kit, onePK, open source, secure software, security
Cisco celebrated OpenStack’s 3rd birthday recently by releasing the Cisco OpenStack Installer for Grizzly. This blog post has more details.
The OpenStack foundation organizes a four-day OpenStack Summit every six months for contributors, enterprise users, service providers, application developers and ecosystem members. It facilitates the community to gather, discuss and present on several different streams ranging from keynote presentations and general sessions to workshops and developer sessions for planning the next OpenStack release. The next OpenStack Summit will be held in Hong Kong from November 5th to the 8th 2013 at the Asia World-Expo. The number of attendees for the Summit is expected to be around 5000 people. More information on the Summit and how you can register to attend is available here.
Speaking proposals are submitted by the community from anyone with an idea or topic they would like to present. The proposals are voted on by the community to secure a slot in session track. Submissions for the OpenStack summit general sessions closed on July 31st 2013 and are now available for vote.
As compared to the Portland summit that had 250 proposal submissions [you can view session videos from OpenStack Portland Summit here, the Hong Kong summit has more than 600 submissions. There are a lot of great proposals but only the best and most popular will make it to the Summit. The approved sessions typically get recorded and are available for viewing online as well.
Cisco’s OpenStack team submitted several proposals that highlight our involvement and contributions to OpenStack. The table below lists the proposals along with a link to the abstract and speaker details.
Community voting is open now and if you are interested in any (or all) of the above proposals, please vote for them here. The voting is open until Sunday, August 25th 2013. Please note that you do need to be an OpenStack Community member in order to vote; If you are not currently a member, you can easily register for membership via the OpenStack website.
Stay tuned for more updates, as we get closer to the OpenStack summit.
Tags: Cisco, cloud, data center, Hong Kong, icehouse, networking, Neutron, open source, opendaylight, OpenStack, openstack installer, Puppet, SDN
One feature of the usNIC ultra-low latency Ethernet solution for the UCS Cisco VIC that we think is interesting is the fact that it is based on SR-IOV.
What is SR-IOV, and why is it relevant in the HPC world?
SR-IOV (Single Root I/O Virtualization) is commonly used in the server virtualization world. The most commonly described purpose of SR-IOV in the hypervisor world is to allow a device partition, called VF (Virtual Function), to be mapped in the guest operating system address space. This allows the guest operating system to enjoy higher I/O performance and lower CPU utilization as compared to the alternative: software-emulated devices that are traditionally implemented in hypervisors.
Compared to the old world before hypervisors came along, that use of SR-IOV seems to allow to regain back some performance lost due to the hypervisor software intervention in the I/O data path. But why should I care about SR-IOV in the world of my network-latency-bound HPC applications running on common operating systems on bare metal servers?
Read More »
Tags: HPC, mpi, open source, SR-IOV, USNIC, VIC