LA PRESENTE EDICIÓN, TRADUCCIÓN Y COMENTARIO

• So if I understand the problem with the infrastructure you are trying to solve with an orchestrator, the control software, how would the Open Daylight do it ?



Answer:

• They’ve written a nice orchestrator that works for the data center model and it probably can be extended to do some video things.

• It’s probably part of a solution for some class of problems, but is optimized around host and multi tenancy and hosting situations.

• There are elements that will work for the broadcast space.

 Question:

• Can you view a HD-SDI source, it’s sync and it’s network routing as an Open Daylight “gadget”.

 Answer:

• Potentially.

 Corresponding Question:

• How much of the code can you borrow or do you have to start code development from scratch ?

 Answer:

• It’s between those two extremes right now.

• There’s a couple different interrelated challenges.

• If all we are going to do is say we still going to still have SDI devices but were going to put this IP switching in the middle then it’s not really worth doing, the economics don’t work.

• If you don’t start having devices that actually natively speak IP, you are just translating at either end and move the cost out of the switches but put it in translators on either side.

• The economics start to actually shift when you have devices that natively speak IP.

• If you take apart a NEXIO server or for that matter, an Omneon server and you look at it, it’s a commercial off the shelf computer inside.

• A nice one, but still a commercial off the shelf computer.

 Answer continued:

• The custom item in it is the HD-SDI IO card and the reference input and a couple of other things to tie it to the legacy broadcast industry standards.

• As soon as we can move away from that and use SMPTE ST 2059 PTP timing instead of color black and SMPTE ST 2022-6 instead of HD-SDI, the economics change for everybody involved.

• They change for you as a customer because you are working on 10 gigabit Ethernet instead of SDI.

• It’s a harder cable to fabricate, but is an easier cable to buy.

• There is higher signal density instead of having one signal per cable, you’ve got twelve signals per cable.

• Fundamentally, one of the things the orchestrator has to do is turn up and down these software apps the way you want them and then the other things is has to do is set up connections.

• The turning up and down and redundancy management are borrowed straight from open sources and open collaboration projects out there.

• It’s when you get into the specifics of how and why the signals are routed that the broadcast industry has a very different use model than what the IT industry uses right now.



Question:

• When do you see this rolling out and becoming a viable way to start designing facilities and taking advantage of this ?



Answer:

• There are working prototypes now in our labs now but I wouldn’t start putting live signals through it today.

• We’re engaging lead customers now as are Evertz and Belden and others and will become standard shipping items in the next years.

 Question:

• Do you see camera manufacturers getting involved with this.

• Facilities that are file based can leverage this, will the camera will have an IP an ethernet connection off the side as opposed to a video connection of the side ?

 Answer:

• Sony says this will happen.

• They turned on a dime at NAB .

• If you asked Sony a year ago about IP, they said no; but now they are quite open about putting gig E on the camera.

• They are in the camp of compressing the signal before they put it on IP and that makes sense in some domains.

• The camera manufacturers are looking to move to IT based technology because again they can leverage the cost point and price using chips that do IP a lot

cheaper that making their own silicon for everything.

 Question:

• Since media companies value their media assets, how do you dispel their concerns over open source code ?

 Answer:

• As an example, they already run Linux.

• However, you still have a challenge with network security as you do already with file based workflows.

• The network is separated by proper firewalls, but as an industry, there will be developments to design for techniques to ensure that we have asset protection and security.

• The challenge of open source code is that you didn’t control its development and nor did your vendor necessarily control its development.

• The benefit is that the code is open and you can fix it or add the feature you want, but the curse is that you might actually have to do that.

• Somebody could bury a Trojan horse inside the Open Daylight code using a password and someone could hack in and delete all your files or do something more interesting with them.

• It’s always a possibility in small open source code projects.

• Open Daylight created a follow on to all these separate little open source projects.

• It now has enough participation from the A list vendors and data centers that there are eyes on it to make sure that this doesn’t happen.

• The open source projects you need to worry about only are the ones that really have a small number of developers.

• If a open source project has a community of five hundred developers or a thousand developers, there’s a little more people watching each other.



Question:

• Is there latency issues ?



Answer:

• There’s always latency issues ?



Corresponding question: