+ netmod WG, and YANG Drs. Widening scope to gather more opinions. So far, we have some opinions that are proto adding such IANA managed modules. However, thers have raised concerns at transferring full ownership/control to IANA -- especially when mapping from IANA Identifiers to string based YANG identityref is required. We are also aware of a proposal in netmod in draft-boucadair-netmod-iana-registries – we are wondering if we have further input that will help YANG document authors moving forward.
Regards, Tarek From: Tarek Saad <[email protected]> Date: Friday, May 13, 2022 at 1:59 PM To: [email protected] <[email protected]> Cc: Adrian Farrel <[email protected]> Subject: IANA managed modules for TE object types Hi WG, During the review of draft-ietf-teas-yang-te, Adrian raised an important point about IANA managing some YANG module that models specific TE types. For example, ID draft-ietf-teas-yang-te was modelling ‘no-path’ some error reasons as listed in https://www.iana.org/assignments/pcep/pcep.xhtml#no-path-vector-tlv or association types as defined in https://www.iana.org/assignments/pcep/pcep.xhtml#association-type-field. There are obvious advantages to having such YANG types in separate modules and letting IANA manage them. For example, 1. Other TE modules can freely import such types modules (without needing to import feature modules such as one defined in draft-ietf-teas-yang-te). 2. Allowing IANA to manage these modules may facilitate extensions in the future (IANA can automatically ensure that IANA types and YANG module are in sync). The authors discussed this suggestion and would like to proceed with it, but want to make sure this is the recommended approach for other types that are managed by IANA and may be modelled in YANG in the future. Regards, Tarek (for the co-authors of draft-ietf-teas-yang-te)
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
