A---------> B
\ .
\ .
\ .
V V
C . . . . > D
I had lunch with Rob today and explained the situation.
There are two answers!
If D is a new YANG module (/RFC) that wants to
augment B
and augment C
then it just works, and it's okay to say:
augment "B" {}
augment "C" {}
I was worried that this would *not* allowed.
i.e. D might not even add anything, although maybe it refines existing
things.
There is, however, another way to build a "D" that does not add anything,
which is using
https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-packages/
In the context of ANIMA, A=>rfc8366, B=>brski-prm, C=>constrained-voucher.
D=>a mythical constrianed-brski-prm. Whether or not D needs an RFC because
it creates new semantics is a different question. {It might need an RFC for
trade agreement reasons though}
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
