1 / 5

ERS Status

ERS Status. Current Status. Version -03 released in October Minor changes vs. version -02 No syntax changes. Usage of X9.95 timestamps. Should ERS reference X9.95? X9.95 defines five methods RFC3161 is one All are CMS-based. ERS includes timestamp as a ContentInfo

rmichaud
Download Presentation

ERS Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ERS Status

  2. Current Status • Version -03 released in October • Minor changes vs. version -02 • No syntax changes 64th IETF - Vancouver

  3. Usage of X9.95 timestamps • Should ERS reference X9.95? • X9.95 defines five methods • RFC3161 is one • All are CMS-based. ERS includes timestamp as a ContentInfo • ERS text states that alternatives can be used • No change to current definitions required 64th IETF - Vancouver

  4. Relationship to X9.95 • X9.95 defines an extension for use in timestamp request messages to enable clients to renew a timestamp • This is an alternative to ERS structure • Results in nesting of timestamps via extensions field of TSTInfo structures instead of SEQUENCE OF ArchiveTimestampChain • X9.95 does not accommodate grouping documents prior to timestamping • Uses hash trees to link with earlier timestamps 64th IETF - Vancouver

  5. ERS/X9.95 Summary • ERS addresses different concerns than X9.95 (i.e., pre-timestamp generation data organization vs. timestamp protection) • The two can be used in tandem (though this could result in very complex validations) • Neither addresses inclusion of and preservation of validation information in the renewal chain 64th IETF - Vancouver

More Related