Tags: tsaad-dev/te
Tags
Addressing 2n WG LC comments (#294) * Resolved idnits * Folded YANG trees * Added back change note on typedef te-node-id * Fixing .gitignore issue * Ignoring generated diff files * Ignoring folded trees * Addressing comments from Med * Updated IANA considerations * Removed change notes together with appendix B and C * Indented all derived identities in YANG models
Refreshing draft-ietf-teas-te-topology-profiles-03
Addressing RFC8776-bis WG LC comments (#291) Addressing additional WG LC comments: - Addressing minor comments from Med not implemented in PR #280 : fix #290 - Added an appendix with YANG tree to RFC8776-bis: fix #290 - Reordered the acronyms and abbreviations in RFC8776-bis: fix #290 - Updated bandwidth profile definitions: fix #285 - Removed te-gen-node-id and moved union within the te-generic-node-id: fix #288 - Fixed normative references: fix #287 - Clarify why path-computation-error-reason has not been defined in an IANA-maintained model: fix #281 - Added formats for the MPLS-TE path bandwidth: fix #284
Refresh draft-ietf-teas-yang-te-mpls-topology-01
TE Types: some WG LC comments resolution (#280) Comments resolution for the WG LC: - Updated range-bitmap description: fix #100 - Added description for minfill and maxfill: fix #267 - Updated description of te-node-id: fix #278 - Addressed some minor WG LC comments from Med: fix #290 - Created new PM groupings using gauge instead of uint: fix #289
TEAS WG adoption of draft-busi-teas-te-topology-profiles as draft-iet… …f-teas-te-topology-profiles
WG adoption of draft-ietf-teas-yang-te-mpls-topology-00
Preparation for v10 of RFC8776-bis (#270) - Added description of the YANG model changes in [draft-ietf-teas-rfc8776-update-09](https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc8776-update-09) - Replaced references to RFC3272 with references to RFC9522: fix #261 - Updated tiebreaker definition: fix #263 - Updated optimization metrics: fix #264 - Clean-up link and path metrics for generic and packet TE types: fix #103 - Added description of the changes from RFC8776: fix #220
PreviousNext