1.1
It does not mention:
- multiple import-stmt for the same module now allowed
- description-stmt and reference-stmt now allowed in
import-stmt and include-stmt
(There are no examples of any of the above changes)
5.1:
o A module MUST include all its submodules.
This is not 100% correct.
A module MUST include one revision of all its submodules.
This includes a submodule with all obsolete definitions I guess.
7.1.6
It does not say what happens if a nested submodule includes-by-revision
a different revision that the parent module.
Multiple revisions of the same submodule MUST NOT be included.
It is not clear that this applies to all include-stmt for the same module
module A {
include A1 {
revision-date 2016-01-01;
}
include A2;
include A3;
}
submodule A1 { ... }
submodule A2 {
include A1; // which revision is included if no date? conflict w/
module?
}
submodule A3 {
include A1 {
revision-date 2015-01-01; // this is an error, right?
}
}
9.12
It doesn't say what happens when a union containing a leafref
or instance-identifier becomes invalid or changes member types.
Is this just a server implementation detail? Is should at least be clear
a valid union leaf/leaf-list applies to a valid datastore
(e.g. running, not candidate).
Andy
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
