search

ietf-ivy-wg / network-inventory-topology

Other
0 stars 1 forks source link

discuss whether/where to put this text #7

Open boucadair opened 1 week ago

boucadair commented 1 week ago

, i.e., the path name of a corresponding interface data node on the containing node is reminiscent of data type interface-ref defined in RFC 8343. It should be noted that data type interface-ref of RFC 8343 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

(used to be in the yang, but the reasoning is better discuss (if needed) in the narrative text.

lana-wu commented 1 week ago

That text is to explain why “interface-name” should be used, not “interface-reference” of RFC 8343 device model. The text is borrowed from "interface-name" of L2 topology (RFC 8944) and L3 topology (RFC8346). https://datatracker.ietf.org/doc/html/rfc8944#name-layer-2-topology-yang-module https://datatracker.ietf.org/doc/html/rfc8346#autoid-6

There is also a relevant CCAMP draft: https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-if-ref-topo-yang-01 defines tp-to-interface-ref. I was wondering if our document could cover this defined in draft-ietf-ccamp-if-ref-topo-yang.