[media-types] Re: [Vcon] Re: Media type registration r eview request for vCon
Daniel Petrie <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Hi Murray:Thank you for the pointer and identifying the issue with encoding and pointing out the missing policy for the JSON registry. Both very helpful inputs!
What I am still not clear on is if I need to register two or three subtypes. Clearly, I need to register "vcon+gzip". However, if vcon is in the JSON format, do I need to register the subtype "vcon+json" and/or just "vcon"?
Cheers,Dan
On Wednesday, July 23, 2025 at 04:52:47 AM EDT, Murray S. Kucherawy <[email protected]> wrote:
On Tue, Jul 22, 2025 at 12:02 PM Daniel Petrie <[email protected]> wrote:
Hi Media Type Experts:Could someone please review what we are proposing to register with IANA for vCon. There is a brief below. I expect this should be a pretty quick read for a Media Type expert.
Here is an updated link as this has been split off into a separate draft:https://www.ietf.org/archive/id/draft-ietf-vcon-vcon-core-00.html#name-json-format-vcon-mediatype
I would really appreciate your help on this so that we can move our I-D forward.
Daniel,
A couple of quick things I notice:
* There are several fields in the template that are blank and shouldn't be. Even if you just say something trivial for them.
" "[JSON]" and "[GZIP]" are not valid values for Encoding Considerations (see RFC 6838 Section 4.8).
While I'm at it, your IANA Considerations section creates a number of registries but I couldn't see where any of them specify what registration policy they are to use (see RFC 8126, Section 4).
-MSK--
Vcon mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]