[media-types] Re: [IANA #1418198] application/vnd.an gel.evidence-package registration request
"Murray S. Kucherawy" <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <CAL0qLwZxZGrko4xnr-JRRvUikxKc5RcBD3XjAjU8z1CJYipm4A@mail.gmail.com> |
On Wed, May 7, 2025 at 6:36 PM Amanda Baber via RT < [email protected]> wrote: > > > The requester adds, "I intend to publish a formal format specification > on > > > the same GitHub repository (lilopkins/evidenceangel) soon." > > > > > > > What's the timeline on such publication? I'm tempted to suggest holding > a > > final decision until we can see that. > > The timeline for format publication is likely within a week or so. I do > intend to publish this as an RFC once I have worked out a few of the finer > details, and am happy to wait for the media type allocation until this is > handled if that is preferred. > I see that this has been published, apparently with intent to seek publication as an RFC. If that's being done in the IETF stream, this becomes eligible for a place on the standards tree. Do we want to proceed with a vendor tree registration or just leave it to the publication of that document? > > > ===== > > > > > > Name: Lily Hopkins > > > > > > Email: [email protected] > > > > > > Media type name: application > > > > > > Media subtype name: vnd.angel.evidence-package > > > > > > Required parameters: N/A > > > > > > Optional parameters: N/A > > > > > > Encoding considerations: binary > > > > > > Security considerations: This type can store arbitrary files and data > > > within it. These files are never executed and must only be expanded > from > > > the format. Potentially, data might be handled in other manners when > > > exported to another format, this should be handled by the exporting > code. > > > > > > Interoperability considerations: The format is based upon the > > > application/zip format, with specific internal structure. Other > software > > > could implement specific ways to handle this format, or may just > handle it > > > as an application/zip file. Software that implements this format should > > > expect that it may have invalid internal data, and should handle this > > > reasonably. > > > > > > As such, this format can interoperate similarly to application/zip. > > > > > > > Are there any prior versions of this media type out in the wild? > > > > Are there any concerns with interoperation across platforms or particular > > transports? > > The current scope of this format is very limited to the best of my > knowledge, and data has not been shared beyond a small group of about 5 > testers. There has been a previous version, however the change introduced a > new field and this is backwards compatible. > OK. > There are no concerns for interoperation in the context of platforms or > transports. > Please say this as part of "Interoperability considerations". -MSK _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]