Re: [core-parameters] Content-Format for application/sdf+json

[Esko Dijk <[e-mail]>]

Hi Carsten,

Maybe the draft could hint how this format is going to be used over CoAP? E.g. a future IoT device can host its own sdfThing description; or an action resource could have an associated sdfAction description hosted.
The registration looks good - allocation should be handled in the upcoming IANA review of the draft I think.

Regards
Esko

-----Original Message-----
From: core-parameters <[e-mail]> On Behalf Of Carsten Bormann
Sent: Monday, March 11, 2024 08:26
To: [e-mail]
Subject: [core-parameters] Content-Format for application/sdf+json

Hi,

Please review the Content Format registration for application/sdf+json, as in Section 7.2 [2] of draft-ietf-asdf-sdf [1].

For your convenience, I have reproduced the section below.

Grüße, Carsten

[1]: https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/
[2]: https://www.ietf.org/archive/id/draft-ietf-asdf-sdf-18.html#name-content-format

7.2.  Content-Format

   This document adds the following Content-Format to the "CoAP Content-
   Formats", within the "Constrained RESTful Environments (CoRE)
   Parameters" registry, where TBD1 comes from the "IETF Review" 256-999
   range.

   +======================+================+======+===========+
   | Content Type         | Content Coding | ID   | Reference |
   +======================+================+======+===========+
   | application/sdf+json | -              | TBD1 | RFC XXXX  |
   +----------------------+----------------+------+-----------+

            Table 12: SDF Content-format Registration

   // RFC Ed.: please replace TBD1 with the assigned ID, remove the
   requested range, and remove this note.
   // RFC Ed.: please replace RFC XXXX with this RFC number and remove
   this note.

_______________________________________________
core-parameters mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/core-parameters