Carl Lebsack

Section 2.3.3 was clarified in https://github.com/openconfig/reference/pull/151 and is explicit about the PROTOBUF encoding requiring the use of the TypedValue message on a per leaf basis. https://github.com/openconfig/gnmi/blob/master/proto/gnmi/gnmi.proto#L108 There is no reference...

That is correct. The gNMI specification prescribes the formatting for PROTO explicitly. An OOB agreed schema would be unspecified and not standardized, in clear contention with the goal to standardize...

We had done similar benchmarking early on with gNMI and precursors and I fully agree that there are more efficient ways to encode the data. The primary issue is one...

gNMI would support proprietary encodings for a different origin (not "openconfig") that would be akin to having a proprietary schema. I think there would be value in having a more...

I am going to close this old comment as the predates the inclusion of TypedValue for PROTO encoding of values which does allow for precise encoding of double and signed...