On Wed, Dec 14, 2022 at 05:05:53PM +0000, tom petch wrote: > Yeeees but looking at s2.5 I see > "To uniquely > identify a TE tunnel, we use the combination of the destination IP > address (an address of the node which is the egress of the tunnel), a > Tunnel ID, and the tunnel ingress node's IP address, which is placed > in the Extended Tunnel ID field." > s.4.6.1.1 goes on to say normally set to all zeros. My take is that if the > field is needed for disambiguation of the tunnel, then it is an IPv4 or IPv6 > address; if it is not needed for disambiguation of the tunnel, then it is set > to all zeros. That to me says union, although in the absence of uint128 in > YANG, I am not sure what the union would be of.
That text talks about what goes into the Extended Tunnel ID field? If so, whatever the Extended Tunnel ID is, it is likely not an IP address. IP addresses where all bits are zero have a defined textual representation. If what you are modeling is not an IP address, well then its something else. ;-) /js -- Jürgen Schönwälder Constructor University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
