From 54f4a04e295654a8c29e000ce7fd4fde0713d418 Mon Sep 17 00:00:00 2001 From: Darren Loher Date: Thu, 5 Mar 2026 13:22:33 -0800 Subject: [PATCH] Update JSON_ETF encoding rules in gnmi specification Added emphasis that JSON_IETF must use namespace qualified names where required as we observe a variety of implementations do not strictly adhere to section 4 of RFC7951. --- rpc/gnmi/gnmi-specification.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/rpc/gnmi/gnmi-specification.md b/rpc/gnmi/gnmi-specification.md index 181a61b..ec476c7 100644 --- a/rpc/gnmi/gnmi-specification.md +++ b/rpc/gnmi/gnmi-specification.md @@ -479,7 +479,9 @@ used. This results in quoted string values, and unquoted number values. described in [RFC7951](https://tools.ietf.org/html/rfc7951). Data specified with a type of JSON MUST be valid JSON, but no additional constraints are placed upon it. An implementation MUST NOT serialise data with mixed `JSON` and `JSON_IETF` -encodings. +encodings. Also note, data must be encoded using namespace +qualified names where required per +[RFC7951 Section 4]([https://tools.ietf.org/html/rfc7951](https://datatracker.ietf.org/doc/html/rfc7951#section-6.8)). Both the client and target MUST support the `JSON` encoding as a minimum.