This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

This draft is an update to and an extension of RFC 8776, and contains
over 100 pages of YANG module definitions.  This reviewer is not a traffic
engineering expert, and hence did not review the YANG contents in detail.

A few nits did turn up:

[a] Most, but not all, of the metrics include references.  A scan to supply
references for metrics wherever possible is suggested.

[b] Appendix B states that the te-gen-node-id data type has been added to
the 'ietf-te-types' module, but that te-gen-node-id data type is not
present in the YANG content.

[c] Some instances of RFC XXXX or rfcXXXX do not have adjacent notes to
the RFC Editor indicating what to do with the XXXX.  The missing notes
should be added unless an RFC Editor note elsewhere covers an instance.

[d] At the end of Appendix B, there is a list of 5 identities that
have been obsoleted in the 'ietf-te-types' module.  Each of these
identities has actually been superseded, as indicated in the YANG
content.  It would be helpful for Appendix B to provide the name
of the superseding identity (that should be used) for each of the 5.