Standardization. Review the ARK specification so that the authors, who are WG members, can finalize it and submit it to the IETF for publication as an Internet RFC.
NAAN procedures. Adapt current CDL procedures for updating NAANs and registering new NAANs so that these maintenance activities can be shared by the community, eg, on github. (The NAAN registry that CDL currently maintains is a text file of globally unique 5-digit Name Assigning Authority Numbers (NAANs) reserved for organizations that wish to assign ARKs.)
Counting ARKs. Work with the Outreach WG to Working Group to implement mechanisms to measure ARK usage world-wide.

Kickoff: clarify objectives and assign roles for (a) standardization and (b) NAAN procedures designers; spec authors articulate areas they think are problematic
Months 1-5: several rounds of review, feedback, and revision for (a) and (b), including public review via the arks-forum list; expect also interaction with the Outreach WG when they send requirements for (c) the “counting ARKs” project, for which design and prototyping then begins
Month 6: ARK spec submitted to IETF; NAAN procedures are piloted; counting ARKs prototype is tested
Months 7-12: further refinements to procedures; ask Outreach WG Working Group to identify more orgs with ARKs to be counted; deal with inevitable spec feedback from the IETF
Month 11: production-ready procedures in place; production-ready ARK counting is in place
Month 12: updated WG objectives and deliverables for the coming year, with an accordingly updated overall AITO roadmap

Resources

...

Page tree