On Tue, Sep 06, 2016 at 11:38:03AM +0200, Martin Bjorklund wrote: > > I think there are two things that I am trying to understand: > > (i) Identification > > In order to be able to pre configure a component, the operator > needs a deterministic way to idenfity the component. How > exactly is this done? > > One way is to rely on the name of the to-be-present component. > Another way is to identify its parent by name, and provide a > parent-rel-pos integer. (The latter assumes that the parent's > name is known...)
For interfaces, some implementations carry the information where an interface is physically located in the interface name. Others generate (almost) dynamic interface names with no specific meaning (in the worst case these names change on every reboot). I assume that the first option works better in many cases. Of course, there are conceivable situations where you like to bind pre-configuration to an interface using other properties (e.g., here is an interface pre-configuration that should be applied to whatever interface has a certain MAC address) but to support such things one would need a way more expressive binding mechanism (or a way to rename interfaces on the fly, i.e., another layer of indirection). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
