[urn] Registration request for urn:eris: namespace

[Endo Renberg <[e-mail]>]

Namespace Identifier:  ERIS
Version:  1
Date:  2023-09-16
Registrant:  Endo Renberg <[e-mail]>


Purpose:  ERIS URNs identify and verify immutable data.

ERIS URNs are application, location, and protocol independent and may be
created by anyone for any purpose which requires immutable data.

These URNs may be conveyed in URLs using the "URN to Resource" method
described in RFC2169 (https://datatracker.ietf.org/doc/html/rfc2169)

Software may resolve ERIS URNs to content by use of dedicated ERIS services
or by embedding an ERIS software library, both of which are freely
available.


Syntax:

BASE32    =   A-Z / 2-7
ERIS-URN  =  "urn:eris:" 106(BASE32)

The semantics of the base32 digits is described in
https://eris.codeberg.page/spec/#section-2.6.

The use of r/q/f components in URNs is application specific and is neither
defined or prohibited.


Assignment:  ERIS operates independently of any authority. Data is
assigned an ERIS URN by chunking it by one of two block-sizes and using
a convergent (deterministic) or unique block encoding. This results in two
possible convergent URNs for any given data or an unlimited number of unique
URNs.


Security and Privacy:  ERIS URNs identify data independently of location so
knowledge of a URN must be assumed to be sufficient authorization to access
the data that it refers to. This behavior also permits the so-called
"Confirmation of A File" attack which may be partially mitigated by
creating URNs using unique encodings.


Interoperability:  An ERIS namespace is not know to be in use elsewhere and
the ERIS URN is designed to be highly interoperable. The interpretation of
base32 data within the URN is constrained and non-extensible.


Resolution:  An ERIS URN may be resolved to content by standalone services
or embedded software libraries. No organization is responsible for hosting
and resolving ERIS encoded data.


Documentation:  http://purl.org/eris