On Tue, 6 Aug 2019 at 00:00, Aaron <[email protected]> wrote: > The XML requirement doesn't sound odd since this is netconf/yang we are > talking about.
The rational architecture has master format X, and then it has outputters and inputters for each supported format. So anyX to anyY works by inputting anyX to master and outputting anyY from master. Example, Junos, you can offer it config in any format it supports or get the format out in any format it supports. Even in IOS-XE, you obviously can get any config out in nativeIOS or XML, you can also put any config in in nativeIOS (it understands startup-config) or XML. So all the pieces actually are there, it's just poor design it won't accept native over netconf/candidate. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
