I don’t support adoption as I think this solution to the problem of receiving unknown bits is excessive and the fact that it is Non-Backward Compatible (NBC) change to remove the unknown bits once they are defined. Rather, just add an optional read-only unknown-foo-bits leaf of type yang:hex-string and return the hex representation if they’re any unknown bits in the field.
Thanks, Acee > On Aug 3, 2023, at 14:02, Kent Watsen <kent+i...@watsen.net> wrote: > > NETMOD WG, > > This email begins a 2-week adoption poll for: > https://datatracker.ietf.org/doc/draft-haas-netmod-unknown-bits/02 > > There is no known IPR on this draft (IPR call > <https://mailarchive.ietf.org/arch/msg/netmod/zJPEgqyi9yXzRqPO6NPJklQsBcU/>). > > Please voice your support or technical objections to adoption on the list by > the end of the day (any time zone) Aug 17. > > PS: I was hoping that Jeff would update the draft to reflect comments > received on-list (e.g., here > <https://mailarchive.ietf.org/arch/msg/netmod/8vk2TU2yaT8kLc1N7sbxiVs27UY/>) > before starting this poll, but he is going on PTO shortly and wouldn’t be > able to get to it for awhile, though he’s happy to do so upon returning. > > Thank you, > Kent (as Co-chair) > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod