[media-types] Re: [IANA #1445698] application/vnd.vn d.majikah.bundle registration request
Alexey Melnikov <[email protected]> Wed, 8 Apr 2026 10:22:04 +0100
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Hi Amanda, There is one typo in the registration (see below), but otherwise this is fine to register. On 16/03/2026 13:38, Amanda Baber via RT wrote: > Hi Alexey, > > Resending this one from March 7th. > > thanks, > Amanda > > On Sat Mar 07 03:34:14 2026, sabrina.tanamal wrote: >> Hi Alexey, >> >> Could you review this one for us by March 20th? >> >> Thank you, >> Sabrina >> >> ==== >> >> Name: Josef Elijah Delos Santos Fabian >> >> Email: [email protected] >> >> Media type name: application >> >> Media subtype name: vnd.vnd.majikah.bundle The published specification is using vnd.majikah.bundle, so I think the vnd.vnd. is an error in the form. >> Required parameters: N/A >> >> Optional parameters: N/A >> >> Encoding considerations: binary >> >> MJKB files are binary containers containing encrypted and compressed >> data. >> >> Security considerations: MJKB files may contain encrypted binary >> payloads including user-generated content. >> Applications processing MJKB files should validate file structure >> before parsing >> to avoid memory corruption vulnerabilities. >> >> MJKB containers may contain arbitrary data and should be treated as >> untrusted input. >> >> If the format includes encrypted payloads, implementations must ensure >> that >> cryptographic keys are handled securely and not exposed through >> metadata or logs. >> >> MJKB files may be large and should be processed using streaming where >> possible >> to avoid denial-of-service conditions due to memory exhaustion. >> >> Interoperability considerations: MJKB is designed as a self-contained >> binary container format for secure file >> transport and storage. Interoperability depends on correct >> implementation >> of the container specification including header parsing, compression, >> and cryptographic envelope handling. >> >> Implementations should follow the official MJKB specification to >> ensure >> compatibility across platforms. >> >> Published specification: https://github.com/Majikah/majik- >> file/blob/main/MJKB_SPEC.md >> >> Applications which use this media: Majik Message Desktop >> Majik Message Web >> Majikah Ecosystem >> >> Fragment identifier considerations: N/A >> >> Restrictions on usage: N/A >> >> Provisional registration? (standards tree only): No >> >> Additional information: >> >> 1. Deprecated alias names for this type: N/A >> 2. Magic number(s): 4D 4A 4B 42 >> 3. File extension(s): .mjkb >> 4. Macintosh file type code: N/A >> 5. Object Identifiers: N/A >> >> General Comments: >> >> Person to contact for further information: >> >> 1. Name: Josef Elijah Fabian >> 2. Email: [email protected] >> >> Intended usage: COMMON >> >> >> >> Author/Change controller: Majikah Information Technology Solutions Best Regards, Alexey _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]