On Mon, Jul 13, 2015 at 03:43:59PM +0100, Robert Wilton wrote: > Hi Juergen, > > If I understand your comment correctly, this would imply that you have a > separate interface representing the basecaps independently from the > interface itself. As far as I know this isn't widely done even if it > supported by ifStack.
Whatever basecaps are... > More naturally it feels that the interface layering is more useful to > represent LAG interfaces or VLAN sub-interfaces, which can be done, but > section 3.3 Interface Layering from YANG Interface Management indicates > that the layering attributes are read only, so you still need separate > configuration leaves to set up the parent<->child relationship. See Appendix C in RFC 7223 how this was envisioned to be done. /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
