Long-term Archive and Notary Services (LTANS) Working Group

1
Long-term Archive and Notary Services (LTANS)
Working Group
2
Administrivia

• Chairs
• Tobias Gondrom and Carl Wallace
• Security Area Directors
• Tim Polk (Security Area Advisor) and Pasi Eronen
• Mailing List
• Discussion ietf-ltans_at_imc.org
• To Subscribe ietf-ltans-request_at_imc.org
• In Body subscribe
• Archive http//www.imc.org/ietf-ltans
• Web site
• http//ltans.edelweb.fr/
• Hosted by Peter Sylvester
• Contains charter, related documents, milestones,
  etc.
• Audio feed (Salon 2)
• http//videolab.uoregon.edu/events/ietf/ietf717.m3
  u
• Jabber
• ltans_at_jabber.ietf.org

3
Note Well

• Any submission to the IETF intended by the
  Contributor for publication as all or part of an
  IETF Internet-Draft or RFC and any statement made
  within the context of an IETF activity is
  considered an "IETF Contribution". Such
  statements include oral statements in IETF
  sessions, as well as written and electronic
  communications made at any time or place, which
  are addressed to
• -the IETF plenary session,
• -any IETF working group or portion thereof,
• -the IESG or any member thereof on behalf of the
  IESG,
• -the IAB or any member thereof on behalf of the
  IAB,
• -any IETF mailing list, including the IETF list
  itself,
• any working group or design team list, or any
  other list
• functioning under IETF auspices,
• -the RFC Editor or the Internet-Drafts function
• All IETF Contributions are subject to the rules
  of RFC 3978 (updated by RFC 4748) and RFC
  3979(updated by RFC 4879).
• Statements made outside of an IETF session,
  mailing list or other function, that are clearly
  not intended to be input to an IETF activity,
  group or function, are not IETF Contributions in
  the context of this notice.
• Please consult RFC 3978 (and RFC 4748) for
  details.
• A participant in any IETF activity is deemed to
  accept all IETF rules of process, as documented
  in Best Current Practices RFCs and IESG
  Statements.
• A participant in any IETF activity acknowledges
  that written, audio and video records of meetings
  may be made and may be available to the public.

4
Since Vancouver

• ERS/SCVP completed WG last call and is currently
  awaiting AD review
• Version -06 of LTAP
• Recently released, needs broader review from WG
• Released as Experimental (per decision in
  Vancouver) but will move back to Standards track
• Version -02 of Data Structure for Security
  Suitabilities of Cryptographic Algorithms (DSSC)
• Plan to begin working group last call soon
• Validate and XMLERS
• Unchanged

5
Post-Philadelphia

• Shepherd ERS/SCVP as Standards track
• Finish LTAP
• New version back on Standards track
• Aim for last call in May or June
• Circulate new artifacts for interoperability
  testing
• For ERS, ERS/SCVP and LTAP
• DSSC has an XML sample in Appendix A
• Solicit participation in interoperability trials
  from various implementers
• Last call for DSSC and XMLERS drafts
• New version of Validate draft
• Working group last call as Informational
• Final act before re-charter or close

6
Todays Agenda

• Introduction/Preliminary stuff - 5 minutes
• Milestone Review - 5 minutes
• ERS XMLERS review - 5 minutes
• LTAP update - 5 minutes
• Future/Milestone recap/Wrap-up - 5 minutes