On Wed, Sep 02, 2015 at 08:59:14AM -0700, Paul Borman wrote: > It depends on if you want to be able to just use YANG for schemas, or if > you want to force people to use another mechanism on top of YANG to make it > flexible enough for complete schemas. > > For example, an interfaces schema may end up with paths like (I am not > using full prefixed YANG paths, so please don't be confused by that): > > /interfaces/eth0/... > > But, if you want to report everything about a device, you would probably > want: > > /device/interfaces/eth0/.. > /device/protocols/tcp/... > > Now step back, you actually want to contain everything about all your > devices: > > /router1.me.com/interfaces/eth0/... > /router2.me.com/interfaces/eth1/...
Instance identification does not really work by putting 'names' into paths. Neither in NETCONF nor in RESTCONF. If your starting point is based on wrong assumptions, then the conclusions may be wrong as well. /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 netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
