[media-types] [IANA #1452734] image/prs.aimg registrat ion request

Hi Darrel,

Resending this revision (with file extension comments) from June 8th. #3 of 3.

thanks,
Amanda

On Mon Jun 08 19:04:11 2026, amanda.baber wrote:
> Hi Darrel,
> 
> This is #3 of 3, revised per their June 1st update. The only changes
> are to the spec, contact name and change controller name fields
> (changing from a person's name to a company or role name). We'll
> remove the initial "Name" and "Email" fields before publishing.
> 
> They wanted to change all of three requests to the standards tree on
> these grounds:
> 
> ==
> 
> Registering as image/prs.aimg would create a direct mismatch between
> the registered MIME type and the actual file naming convention used in
> production. This would cause:
> 
> - Interoperability issues across browsers, CDNs, and media servers
> that rely on MIME type detection
> 
> - Confusion for developers implementing the format
> 
> - A need to rename all existing files or break backward compatibility
> in the future
> 
> The implementation is complete, the specification is published, and
> the format is ready for deployment. Registering as standard types from
> the beginning ensures that the MIME type matches the file extension
> exactly, avoiding unnecessary complexity and technical debt.
> 
> ==
> 
> When I let them know that this would require RFC publication,
> submission on behalf of an SDO, or indication that this could be
> grandfathered, they wrote, "Am a first timer in mime registration, So
> normally, I have never came across a mime extension with
> file_name.prs.extension type, Thats why I sent the update request. If
> am suppose to start with .prs.aimg after adoption and growth switch to
> .aimg, If thats the rule, We cant change the rule so its ok I can
> start with .prs."
> 
> thanks,
> Amanda
> 
> =====
> 
> Name: Elvis Ouma
> 
> Email: [email protected]
> 
> Media type name: image
> 
> Media subtype name: prs.aimg
> 
> Required parameters: N/A
> 
> Optional parameters: encoding: specifies the underlying transport
> encoding (e.g., "png")
> version: specifies AIMG format version (e.g., "1")
> 
> Encoding considerations: binary
> 
> Security considerations: This media type does not contain executable
> or active content.
> 
> The format is a container for binary media data (e.g., PNG) and
> associated AI provenance metadata. Implementations must treat all
> embedded data as untrusted input and avoid executing any content.
> 
> Integrity is a core feature of the format. AIMG includes a
> cryptographic hash of the payload and metadata, allowing detection of
> tampering. Future versions may include digital signatures for origin
> verification.
> 
> Privacy considerations apply as metadata may include information such
> as model name, generation timestamp, or prompt-derived hashes.
> Applications should avoid embedding sensitive data or should encrypt
> metadata externally when necessary.
> 
> If the container embeds existing formats such as PNG, the security
> considerations of those formats also apply.
> 
> Transport-level security (e.g., TLS) is recommended when transmitting
> AIMG files.
> 
> Interoperability considerations: AIMG is designed to be backward
> compatible with existing image systems by embedding its metadata
> within standard formats such as PNG during early deployment.
> 
> Systems that do not recognize AIMG metadata will continue to render
> the underlying image normally.
> 
> Interoperability depends on correct parsing of embedded metadata
> chunks and adherence to the AIMG specification.
> 
> Published specification: https://github.com/aimediaformat/media-
> engine/blob/main/spec/ai-media-format.md
> 
> Applications which use this media: AI content generation platforms,
> media verification tools, digital forensics systems, and content
> authenticity pipelines.
> 
> The format is intended for use in identifying, verifying, and auditing
> AI-generated media.
> 
> Fragment identifier considerations: N/A
> 
> Restrictions on usage: None
> 
> Provisional registration? (standards tree only): No
> 
> Additional information:
> 
> 1. Deprecated alias names for this type: AIMG
> 2. Magic number(s): 41 49 4D 47 ("AIMG")
> 3. File extension(s): .aimg
> 4. Macintosh file type code: N/A
> 5. Object Identifiers: N/A
> 
> General Comments:
> 
> Person to contact for further information:
> 
> 1. Name: Ai Media Format
> 2. Email: [email protected]
> 
> Intended usage: COMMON
> 
> AIMG is part of a broader AI media format family including AAUD
> (audio) and AVID (video), which follow similar design principles.
> 
> Author/Change controller: Ai Media Format
> Open-source community (future evolution)

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]