Alissa Cooper has entered the following ballot position for
draft-ietf-i2rs-yang-l3-topology-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-yang-l3-topology/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

= Section 2 =

HTTP and ReST are defined, but they aren't used anywhere else in the
document in a way that requires definition.

= Section 5 =

"case interface-name {
             leaf interface-name {
               type string;
               description
                 "A name of the interface.  The name can (but does not
                  have to) correspond to an interface reference of a
                  containing node's interface, i.e. the path name of a
                  corresponding interface data node on the containing
                  node reminiscent of data type if-ref defined in
                  RFC 7223. It should be noted that data type if-ref of
                  RFC 7223 cannot be used directly, as this data type
                  is used to reference an interface in a datastore of
                  a single node in the network, not to uniquely
                  reference interfaces across a network.";
             }
           }"

In RFC 7223 the data type appears to be called interface-ref, not if-ref.
Would an example of this in this document be, say, a MAC address? 

= Section 6.1.1 and 6.2.1 =

While notational explanations are given for "?," "*," etc., none is given
for "!".

= Section 9 =

This section is missing a discussion of the potential sensitivity of the
data this module exposes even in a read-only use case. Filling in the
template at https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
and adding the text to this section should get that covered.


_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to