NETMOD WG, The chairs received and discussed the following message recently:
> On Sep 11, 2022, at 3:00 AM, IETF Secretariat > <[email protected]> wrote: > > The following draft will expire soon: > > Name: draft-ietf-netmod-rfc6991-bis > Title: Common YANG Data Types > State: I-D Exists > Expires: 2022-09-23 (in 1 week, 4 days) 1) With regard to the ip-address-no-zone discussion, it is the chair's understanding that there is NO CONSENSUS either way. That is, the two sides have equal support. However, the WG must make progress and the chairs feel that the safest course of action is to make no change, effectively kicking the proverbial can down the road (a future rfc6991-bis-bis can pick it up). 2) With regards to the [date/time]-[with/no]-zone, in https://mailarchive.ietf.org/arch/msg/netmod/PGFFlBm-oT8OVSKvzHuXmtHPBfM/, it seems that Randy and I agreed that having it be a conscious/explicit selection by module designers is goodness. Should there be an update to the draft to rename "date" to "date-with-zone" *and* rename "time" to "time-with-zone"? Sorry, but going back to (1), IDK if it was discussed, but would it make sense to move towards the kind of ip-address be explicit also? That is: 1) add "ip-address-with-zone" and 2) deprecate "ip-address"? This way no break in backwards compatibility and yet paves the way for a future NBC change? Followed later with, e.g., an alias for "ip-address-no-zone" to be "ip-address" (similar to OpenConfig)? 3) There was also a discussion regarding a "language" tag that ended here: https://mailarchive.ietf.org/arch/msg/netmod/aYthsN4MhsjclIqzfvxz9ak1Gpw/. I don't see a conclusion to this discussion. Did another WG meanwhile publish a definition and so the time-utility window for NETMOD to act has since passed? Kent // Shepherd
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
