Reviewer: Andy Bierman Review result: Ready Comments: 1) Measuring Interoperability for groupings and identities [same comment for SSH and TLS drafts] These modules are intentionally abstract. There are no protocol-accessible objects defined at all. Interoperability is usually measured in the context of a specific protocol (e.g., NETCONF). There is an assumption that interoperability will be achieved by some other RFCs that will have "uses" statements to create protocol-accessible or otherwise implementable objects. There is also an assumption that the groupings will be used the same everywhere, and the only difference will be the path from root to the objects in these groupings. In fact, the "refine" statement allows each usage to be different. Perhaps the drafts should mention these interoperability issues. 2) same feature names in 2 modules - feature userauth-hostbased - feature userauth-none - feature userauth-password - feature userauth-publickey The ietf-ssh-client and ietf-ssh-server modules both use these feature names. IMO users will not expect this, and this will cause confusion. Why can't these features be defined once in ietf-ssh-common.yang? Seems like client and server will advertise the feature for implementing their relevant values. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
