So from an OpenFlow standardization perspective, it's very, very important to have hardware that can interoperate with a variety of software controllers. From our side, since we're building our own hardware, that was less important. But we definitely had to improvise, and certainly the OpenFlow standard has evolved and we've had to be nimble with that internally.

Did you have any setbacks of note?

I think Urs Hölzle [senior vice president of technical infrastructure and Google Fellow] said it best when he said it actually has gone more smoothly than he expected with less down time. The main issues we ran into from an OpenFlow perspective is the first version doesn't fully allow you to take advantage of all of the hardware capabilities in modern switch silicon in an easy way. That's not to say it's not possible, it's just not easy. So we have to do some work to get around some of those mismatches and, if you will, interface them. But this is now substantially improved from the OpenFlow standard perspective.

How far away is OpenFlow from being fully baked?

I think it's going to be a multi-year process, but the message we want to send is it's at a point now where it's incredibly useful and can deliver substantial benefits in a variety of settings.