Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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 Informational Internet RFC.
  2. 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.)

  3. Global ARK resolver. Guide the development and hosting of the N2T.net resolver.
  4. Counting ARKs. Work with the Outreach 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-9: several rounds of review, feedback, and revision for (a) and (b), including public review via the arks-forum list; NAAN procedures are piloted

  • Months 13-15: recruit NAAN registry workers

  • Recruit NAAN registry curators
  • Design and review Months 16-20: feedback and review of '?info' inflection for returning human- and machine-readable metadata; ARK spec submitted to IETF
  • Establish Months 18-19: establish NAAN request -to-entry online tool at N2T; further refinements to procedures
  • Months 20-24: deal with spec feedback from the IETF
  • Months 24-26: “counting ARKs” project design and prototyping then begins

  • Months 26-27: counting ARKs prototype is tested
  • Month 28: updated WG objectives and deliverables for the coming year, with an accordingly updated overall ARKA roadmap

  • form to generate NAAN entries at N2T
  • Submit ARK spec to IETF RFC process and respond to feedback with revisions
  • Prototype counting ARKs project

Resources

...

...