Hi, Balazs Lengyel <[email protected]> wrote: > Hello, > IMHO the case, when 2 deviation statements point at the same target should be > clarified and declared as an error or implementation dependent feature. I see > no > good way of deciding which deviation statement has precedence.
This was discussed back in 2009: https://mailarchive.ietf.org/arch/msg/netmod/IYW1t0PX34cf2GEGAlM98XFOfKw This thread ends w/o clear resolution, but I think that the proposal in the last email in this thread (please read the thread) would be a useful addition: After applying all deviations, in any order, the resulting data model MUST still be valid. For example, it is an error to add a default value that doesn't match the type in a deviation. /martin > Balazs > > -------- Forwarded Message -------- > Subject: [netmod] Multiple deviations with same target > Date: Thu, 10 Dec 2015 11:12:02 +0100 > From: Balazs Lengyel <[email protected]> > To: [email protected] <[email protected]> > > Hello, > What happens if I have multiple deviation statements with the same > target node, possibly in separate deviation files. > E.g it is possible to have two deviation statements setting the range > for an integer type leaf to 1..5 in one statement while setting it to > 2..6 in another. > What is the end result? Error? > regards Balazs > > -- > Balazs Lengyel Ericsson Hungary Ltd. > Senior Specialist > ECN: 831 7320 > Mobile: +36-70-330-7909 email: [email protected] > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod > > -- > Balazs Lengyel Ericsson Hungary Ltd. > Senior Specialist > ECN: 831 7320 > Mobile: +36-70-330-7909 email: [email protected] _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
