At IETF96 in Berlin, the chairs of the NETMOD working group, and Operations Area Director (Benoit Claise) published a statement to say “Models need not, and SHOULD NOT, be structured to include nodes/leaves to indicate applied configuration”. Now, this might seem a pretty innocuous statement, but it actually has a number of implications for the data models for network configuration and state that are being produced in the industry.
imported Presentations · OpenConfig · YANG
Mark Townsley and Jean-Louis Rougier again invited me to come and lecture at �cole Polytechnique this year. Their course there focuses on analysing the success of network protocols - using the (fantastic) framework laid out in RFC5218. Given that I’d spoken about SR for the last couple of years in my lecture there, and was giving a (slightly) updated version of the SR lecture at Telecom ParisTech for JLR’s ‘Future Internet’ course earlier in the week, I decided to shift the focus of my lecture at X this year to the management plane.
imported Code · Tech · Work · ISP · IETF · python · OpenConfig · YANG
I’ve talked a little on this site before about what we’re trying to achieve with OpenConfig. However, one of the observations that it’s easy to make is that YANG models alone don’t really achieve anything in terms of making the network more programmable. To make the network more programmable, we need to have tooling that helps us create instances of those modules, manipulate them, and then serialise the into a format that can be used to transmit data that conforms to the model to a device.