Model-Driven Networking on Software Gone Wild

The Model-driven Networking seems to be another buzzword riding on top of the SDN wave. What exactly is it, how is it supposed to work, will it be really vendor-independent, and has anyone implemented it? I tried to get some answers to these questions from Jeff Tantsura, chair of IETF Routing Area Working Group, in Episode 55 of Software Gone Wild.

I also did a bit of research after the podcast to figure out whether individual vendors support IETF or OpenConfig YANG models. Here's what I found:

Have I missed anything? Please write a comment!


  1. Arista has support for the OC BGP model I believe in their 4.1 software. I'm not sure about other YANG models they support. They have a few blog posts on it out there if you search around.

    Junos' entire configuration has been modeled in proprietary YANG for a few releases now. The engine they are working on for 16.1 will allow people to write/install their own YANG modules that translate into native Junos ones, from the best of my recollection. They certainly have working prototypes of support for the OC BGP model.

    I am a member of the OC consortium and I think we'll continue to see more vendor adoption as providers push/require their support.

  2. Junos has been data driven from day one. The Junos YANG models are shipped as part of the Junos release posting. This whitepaper elaborates how Junos supports OpenConfig and other standard YANG models:
    1. Pallavi, nobody ever doubted the data-driven approach the designers of Junos took, and I often emphasize it in my webinars, workshops and other materials.

      As for Junos support of OpenConfig etc, could you please point me to Junos documentation explaining how to configure it?

      Thank you!
Add comment