[media-types] [IANA #1458688] application/vnd.nnu.profile+json registration request

[David Dong via RT <[e-mail]>]

Hi Darrel,

Following up for this request from August 25th.

Thank you.

Best regards,

David Dong
IANA Services Sr. Specialist

On Tue Aug 25 20:11:13 2026, amanda.baber wrote:
> Hi Darrel,
> 
> Could you review this new one by September 8th?
> 
> thanks,
> Amanda
> 
> =====
> 
> Name: Binbin Shen
> 
> Email: [e-mail]
> 
> Media type name: application
> 
> Media subtype name: vnd.nnu.profile+json
> 
> Required parameters: N/A
> 
> Optional parameters: N/A
> 
> Encoding considerations: binary
> 
> Security considerations: The representation is declarative JSON and
> contains no active or executable content. RFC 8259 Section 12 applies.
> Implementations must treat text and URLs as untrusted, escape rendered
> text, bound resource consumption, and apply SSRF, redirect, content-
> size, and remote-context protections before dereferencing URLs. The
> format itself provides no confidentiality, integrity, authentication,
> authorization, freshness, non-repudiation, or legal-identity proof.
> HTTPS protects origin authentication and transit integrity; durable or
> offline assertions require an additional signature or credential
> mechanism. A public manifest must not contain secrets or private
> identifiers and must not be the sole basis for high-risk
> authorization. See Section 8 of https://nnu.us/specifications/nnu-
> profile-manifest-1.0.txt
> 
> Interoperability considerations: JSON object member order is
> insignificant. The representation is UTF-8 JSON without a BOM.
> Revisions are base-10 integer strings, timestamps are RFC 3339 values
> with offsets, and URLs are canonical public authority-form HTTPS URLs.
> Consumers must inspect schema_version and must not interpret
> unsupported versions as version 1. See Sections 2, 7, and 9 of the
> published specification.
> 
> Published specification: https://nnu.us/specifications/nnu-profile-
> manifest-1.0.txt
> JSON Schema: https://nnu.us/specifications/nnu-profile-manifest-
> 1.0.schema.json
> 
> Applications which use this media: nnu.us servers, AI agent clients,
> identity discovery clients, browser extensions, and SDKs that consume
> public nnu.us Profile manifests.
> 
> Fragment identifier considerations: No subtype-specific fragment
> identifier syntax is defined. The fragment identifier considerations
> for the +json structured syntax suffix apply.
> 
> 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): N/A
> 3. File extension(s): N/A
> 4. Macintosh file type code: N/A
> 5. Object Identifiers: N/A
> 
> General Comments: The fixed representation is available at
> https://nnu.us/@{handle}.profile.json and the canonical Profile URL
> supports HTTP content negotiation with Accept:
> application/vnd.nnu.profile+json. This registration is requested in
> the vendor tree and is not represented as complete until IANA
> publishes it.
> 
> Person to contact for further information:
> 
> 1. Name: Binbin Shen, Grid Heap, Inc.
> 2. Email: [e-mail]
> 
> Intended usage: COMMON
> 
> Author/Change controller: Grid Heap, Inc. <[e-mail]>