Hi, Andy Bierman <[email protected]> wrote: > Hi, > > I asked about this text on page 156: > > > In statements that have any data definition statements as > substatements, those data definition substatements MUST NOT be > reordered. > > I asked why this new rule was added.
It is not a new rule, it is there in RFC 6020 as well. In rpc/action input/output the nodes are encoded in XML in the order they are defined. So this rule is there to protect clients that might depend on that order. > I do not see why it is needed, or how it can be enforced. > > If I add a new object to grouping A, then every place there > is a "uses A", a new data node will be inserted inline. Newly inserted nodes does not change the order between the old nodes. We could relax the rule and say that it only applies to input/output and groupings (since they might be in input/output. Or we revisit the original rule that nodes in input/output are encoded in the order they are defined - however, that rule has huge implications on performance in some rpc (specifically edit-config). /martin _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
