New IETF version for ARK - Recommendations

[Erez Kalman]

I would love to join the technical discussion but can't seem to find how to join.

Any way, I recommend the following:

1. All new NAANs will register a TXT record on their domain root with the subdomain for accessing the ARK resource, e.g.:

a.b.c.example.com will have a txt record and their declared scope

_ark.example.com with NAAN 99999 BY [ISSUER DOMAIN] IN a.b.c.example.com

This will allow enhanced software solutions as any software can check the local record.

The record can be enhanced by adding an optional signature by the issuing authority of the NAAN, simply signing NAAN 99999 BY [ISSUER DOMAIN] IN a.b.c.example.com this stored as

_arksig.example.com with [signed signature]

2. Any NAAN may self add a shoulder by creating a TXT record, as follows:

_arksub.example.com with x1,x5,a3

which may be utilized on a different domain, e.g.:

_arksub.example.com with x1,x5,a3:a.blah.org

This becoming the issuing authority for 99999/a3 (can provide it signatures, and so forth)

3. Any top level issuer must maintain a synchronized list of all other top level issuers.

4. A policy file may be stored, under the TXT record:

_arkpol.example.com with URIs, unique shoulders (e.g. physical):

URI0:Privacy Policy:https://bbb.example.com/arkprivacypolicy.pdf

URI1:Records Policy:https://a.b.c.example.com/aaa.txt

.....

URI9.....

t1:Temporary Conference ARKs0584005000expire 2023-09-01

t2:Asset inventory:physical:expire 48H

b22:Guests:person:expire manual