Re: [Rats] EAT I-D language for old interoperability

["Smith, Ned" <[e-mail]>]

I was reading it like a reference doc vs. novel. The explanatory text at the top of section 7.2.1 could be moved to the data type definitions being described. Something more like:
7.2.1.  Common Data Types
   time-int = #6.1(int)
   time-int is identical to the epoch-based time, but disallows floating-point representation.

   binary-data = JC< base64-url-text, bstr>

   base64-url-text = tstr .regexp "[A-Za-z0-9_-]+"

   general-oid = JC< json-oid, ~oid >
   For CBOR-encoded tokens, OIDs are specified using the CDDL type name "oid" from [RFC9090].  They are encoded without the tag number.  

   json-oid = tstr .regexp "([0-2])((\\.0)|(\\.[1-9][0-9]*))*"
   For JSON-encoded tokens, OIDs are a text string in the common form of  "nn.nn.nn..." from [RFC2252].

   general-uri = JC< text, ~uri >
   Unless explicitly indicated, URIs are not the URI tag defined in[RFC8949].  They are just text strings that contain a URI conforming to the format defined in [RFC3986].

   coap-content-format = uint .le 65535

On 3/8/24, 10:18 AM, "RATS on behalf of Thomas Fossati" <[e-mail] <mailto:[e-mail]> on behalf of [e-mail] <mailto:[e-mail]>> wrote:


On Fri, Mar 8, 2024 at 7:08 PM Smith, Ned <[e-mail] <mailto:[e-mail]>> wrote:
>
> Using `oid` in the JSON section is confusing because the json cdd doesn't ever use `oid` only `json-oid`.
>
> The cbor use of `oid` doesn't reference RFC9090. Whereas the equivalent JSON text references [RFC2252].


hmm, I look at §7.2.1 and see:


For CBOR-encoded tokens, OIDs are specified using the CDDL type name
"oid" from [RFC9090].


which looks good to me.


Then un §7.2.2 it says:


[...] the
following CDDL types are encoded in JSON as follows:
[...]
* oid -- MUST be encoded as a string using the well established
dotted-decimal notation (e.g., the text "1.2.250.1") [RFC2252].


So "oid" is still intended as the CDDL type defined in §6 of RFC9090
which, when serialized to JSON uses dotted-decimal notation. Again, a
pretty decent explanation :-)


You are right that there's a lack of linkage with json-oid though.


_______________________________________________
RATS mailing list
[e-mail] <mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/rats <https://www.ietf.org/mailman/listinfo/rats>