didcomm-messaging
didcomm-messaging copied to clipboard
Are file extensions supposed to be registered with IANA?
Noticed when reading through that we're specifying the file extensions, but not sure if these need to be registered anywhere. I couldn't find any where they needed to be, so thinking the answer is no.
The description/registration of a media type can include file extensions (see RFC6838), but they do not get tabulated anyplace - they are only visible when looking at the spec/registration.
For an example, from https://www.iana.org/assignments/media-types/audio/mpeg :
Additional information:
Magic number(s): none
File extension(s): .mp1, .mp2, .mp3
Macintosh File Type Code(s): MPEG
Object Identifier(s) or OID(s): none
Thanks, your insights into the standards space are always appreciated.
With that, it looks like we just need to add this IANA registrations section to register the media-types at the bottom of the spec and then include the file type code in that registration.
Related to #279
The answer for how this should be done has been addressed. Closing this and the work to get it done will be tracked in #279
Woops, just realized that ticket is slightly different then this one. Reopening this which will be used to track the actual registrations of the media-type and file-type extensions
Discussed WG 20220502. Needs IANA PR/Submission, but this is nice to have, not a strict requirement.
Needs IANA PR/Submission
If this is the case, then I believe this spec needs to define those submissions within the spec itself. I'm not quite as familiar with the file extensions registry process, but that's the same way I've seen this done for nearly every other IANA registry
I'm unlikely to get around to doing this so going to unassign myself, but leave it open.