[IANA #1272257] application/vnd.ipfs.ipns-record registration request

[lidel]

In effort to standardize content type used in ipfs/specs#351 we will be submitting a request for registering application/vnd.ipfs.ipns-record at https://www.iana.org/assignments/media-types/media-types.xhtml

[lidel]

Submitted:

Media type name: application

Media subtype name: vnd.ipfs.ipns-record

Required parameters: N/A

Optional parameters: N/A

Encoding considerations: binary



Security considerations: The media type inherits the security considerations for application/octet-stream,
contains no executable code,

When used in IPFS/IPNS context, it is strongly recommended verifying record integrity based on expected signature digest <https://specs.ipfs.tech/ipns/ipns-record/#record-verification>.

Interoperability considerations: N/A

Published specification: <https://specs.ipfs.tech/ipns/ipns-record/#record-serialization-format>

Applications which use this media: IPFS <https://ipfs.tech> uses signed IPNS records as means of introducing cryptographically-verifiable mutable pointers to immutable data <https://specs.ipfs.tech/ipns/ipns-record/>.

IPNS allows addressing dynamic content in a decentralized network with changing location and version. Signed IPNS records in IPFS enable secure, tamper-proof content-addressable applications and services with high resilience against censorship and data loss.


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): N/A
   3. File extension(s): ipns-record
   4. Macintosh file type code: N/A
   5. Object Identifiers: N/A

General Comments:

Person to contact for further information:

   1. Name: Marcin Rataj
   2. Email: lidel@protocol.ai

Intended usage: COMMON

IPNS records can be exchanged using a variety of transport mechanisms, including P2P, HTTP, or even sneakernet.

Author/Change controller: Protocol Labs
<https://protocol.ai>
<standards@protocol.ai>

[lidel]

Reviewer asked for revised security considerations section with privacy/integrity notes.

Submitted:

Security considerations:

The media type inherits the security considerations from application/octet-stream,
contains no executable code, offers no data confidentiality,
but provides integrity protection through a signature digest:
<https://specs.ipfs.tech/ipns/ipns-record/#record-verification>

In the IPFS/IPNS contexts, it is mandatory to verify the integrity
based on the expected signature digest before acting
on any content-addressed data linked from the record.

[lidel]

Done:

https://www.iana.org/assignments/media-types/application/vnd.ipfs.ipns-record