Tom, On 8/26/2015 9:34 AM, Nadeau Thomas wrote: > ... > This is exactly what I want to get on the table.
So taking a step back, perhaps there is a YANG language question at the heart of this discussion. I think we're seeing cases where the same data model is useful in multiple cases/places. The example I like to use (although I know others disagree with the example) is the case of PE/CE config information, where some of the exact same information may end up on the CE and PE devices as well as the L3 service model. In this case we'd like a core model to be "included" (or "linked") into two larger models. Importantly, I'm referring to doing this as part of model definition - not at server/device run time. This is important for the pre-provisioning case. It is my understanding that there is no way to really do this in a general and extensible way (including allowing for augmentations) today. If there was such support, I do think we'd be saying that we'd like the existing models to support this mechanism rather than our current proposal of being relocated . Lou (BTW this is my opinion, not speaking for the DT.) _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
