LTANS WG meeting 11/9/2006 - 67th IETF - San Diego
Approximately 13 people attended the meeting in person
1 person not physically attending participated via Jabber

Introduction/Preliminary stuff (slides: ltans-0.ppt)
The current document suite was reviewed.  There are currently active working group documents.  The long-term archive requirements document is in IESG review.  A new version will be posted that addresses issues resulting from that review.  These modfications are generally for clarity.  ERS has completed working group last call.

Milestone Review (slides: ltans-1.ppt)
Most milestones are a little late, but close to the targets established in Montreal.  Reqs draft will be concluded as soon as possible.  Intend to submit ERS to IESG by end of year.  LTAP should reach working group last call by Prague.  Plan for working group shutdown by August.

ERS update (slides: ltans-2.ppt)
ERS completed working group last call.  A new version will be posted that addresses some offlist comments that were submitted during last call.  That version will be cross-posted to the S/MIME working group to elicit wider review prior to submission to IESG, which will ideally occur before the end of the year.  One comment related to the source for the ContentInfo and AlgorithmIdentifier IMPORT statements in the ASN.1 module.  Russ indicated that free compiler support was still lacking and recommended that we maintain the CMS and PKIX IMPORTS.  There was no objection, so this change will not be made in version -09.

ERS/SCVP update (slides: ltans-3.ppt)
No changes have been made to this specification.  The intent is to progress this draft once ERS has been submitted to the IESG.

PKI Retention update (slides: ltans-4.ppt)
No changes have been made to this specification.  The CRL extension in the appendix is somewhat controversial.  Dave Cooper prefers the similar X.509 extension to be used.  Client support for using CRLs generated after the time of interest to determine if there is a problem of the sort addressed by the new extension.  It is likely that the next version of this specification will drop this appendix.  The group was asked whether the ERS-SCVP and retention drafts were necessary in light of the prevalent approach of storing all verifcation data in each archived data object.  Plan is to proceed with both options.

LTAP update (slides: ltans-7.ppt)
LTAP -03 was posted recently.  The changes were relatively minor but some work remains to be done, including metadata format.  Version -04 is currently underway.   This draft will be the primary focus of the working group as work on ERS concludes.

Architecture document review (slides: ltans-5.ppt)
An overview of this new informational draft was provided.  Essentially, the document aims to provide a roadmap to using LTANS specifications.  It provides 3 architectures as examples.

Validation document review (slides: ltans-6.ppt)
An overview of this new informational draft was provided.  The motivation of the document was the specification of processing rules for RFC3161 timestamps.  Since ERS is timestamp neutral and the details are somewhat tricky, a document to establish the processing rules is necessary.  This draft may be better served as standards track.  A new co-author has been identified.  A vote was taken in the room to determine is the two new documents should be accepted as working group documents.  A straw poll on the list will be conducted to determine if these documents should proceed.