You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Date

Attendees

Goals

Continue review of spec changes, plus review of edits since last meeting:   https://www.ietf.org/rfcdiff?url1=draft-kunze-ark-18.txt&url2=draft-kunze-ark-21.txt

General Comments

  • Roxanne noted that SNAC might be considering moving away from ARKs; John will follow up
  • Adrien has indicated he likely will not be continuing to participate in TWG meetings; consensus was that team as constituted has critical mass, and can continue without looking just now for a replacement
  • All are agreed in finding the "diff" format convenient for tracking changes in draft specification; Discussion items below will refer to locations in that diff (at link above) for today's discussion

Discussion items

TimeItemWhoNotes

Section 2 Ark Anatomy


  • Terminology clarified: resolving service vs. Mapping authority (host), Base object name (most important part to be opaque),Optional /:  APPROVED

Section 2.3
  • instead of calling ark:/ “deprecated” call it “older”   APPROVED

  • longer NaaN allowed, stating as policy (separate from standard) that in practice we expect not change to sequences bigger than 5 characters  APPROVED


2.6  Character repertoire


  • For received ARKs implementations must handle a minimum 255 octets; no statement of maximum, but caution for ARK-generating implementations that if length greater than 255, ARK might not be handled by some receiving implementations  APPROVED

  • ~ instead of / in characters  APPROVED

  • Question arose as to whether we should use all caps wherever such key words as 'must' or 'should' or 'may' appear – Agreed this was not necessary
















Action items

  •  
  • No labels