Darren Loher

@kbchandradeep or @nkitchen would you like to send a PR to change this? At a minimum it should change the type for `offset`, as @nkitchen pointed out, offset needs to...

Options to resolve include: - only use uint64 as a unique identifier for items in the list - Change the hex-string type to something that can be differentiated from uint64,...

I move that we change the format of a hex-string to be a string delimited with `:` in between each byte, in the same style as the IETF https://datatracker.ietf.org/doc/rfc6991/ hex...

@m26singhvi Can you explain the motivation for #737 ? Creating a union of uint64 and hex-string raises this issue of ambiguity between the types. It is also undesirable to use...

> @dplore - As captured in #733, this was done to primarily support Macsec model. Changing it back to uint64 would mean that Macsec model will need it's own keychain...

It appears hex-string type [is used in 5 places](https://github.com/search?q=repo%3Aopenconfig%2Fpublic%20hex-string&type=code). * 2 in macsec * 1 in keychain * 1 optional-capabilities in ospf * 1 evpn esi type I'd appreciate any...

Here are links regarding gNMI deprecating the Decimal64 message from gNMI at https://github.com/openconfig/gnmi/commit/d5360e33fc3b22effeaaaf55f345c1f950765bed. The motivation is documented at: https://github.com/openconfig/reference/blob/master/rpc/gnmi/decimal64-deprecation.md

> > * there has been a discussion the other way -- which @gcsl initiated, whereby there was a discussion around moving completely away from `decimal64`. specifically -- this looked...

Do I understand the target scenario for this use case is a network device (or simulated device via confd) running a kubernetes cluster? Or is the network device a host...

Moved to 1st comment/main description for the PR