1 / 8

LTANS WG: ERS Status

LTANS WG: ERS Status. November 9, 2006 Tobias Gondrom. LTANS WG (ltans): ERS. Current draft is version 08 incorporated changes as discussed at last WG meeting Second WG last call initiated on ERS-08 started October 18 th concluded October 30th. LTANS WG (ltans): ERS.

nam
Download Presentation

LTANS WG: 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. LTANS WG: ERS Status November 9, 2006 Tobias Gondrom

  2. LTANS WG (ltans): ERS • Current draft is version 08 • incorporated changes as discussed at last WG meeting • Second WG last call initiated on ERS-08 • started October 18th • concluded October 30th

  3. LTANS WG (ltans): ERS WG Last Call Review results • minor formal corrections corrected references, adjusted reference naming convention, added small chapter to list the imported ASN.1 structures to improve readability • structure change for better extensibility to CryptoInfos and EncryptionInfos • minor structure change to EvidenceRecord (added three dots at the end of the structure) • improved text about default version value 1 in “Syntax” section • changed IMPORTS of • ContentInfo from: CryptographicMessageSyntax2004 To: PKCS-7 • AlgorithmIdentifier from: PKIX1Explicit88 To: AuthenticationFramework

  4. LTANS WG (ltans): ERS WG Last Call Review results • change IMPORTS: • ContentInfo: • old source: CryptographicMessageSyntax2004 • new source: PKCS-7 • AlgorithmIdentifier: • old source: PKIX1Explicit88 • new source: AuthenticationFramework • Reason: Peter explained the new imports are using more current ASN.1 syntax than the old ones. (and please note: Peter also provided a reference to a free and open source ASN.1 compiler that supports the most current version of ASN.1 syntax.: http://lionet.info/asn1c/ • The authors see no problems with the new import sources (also not with the old ones) and can accept the reason from Peter. No objections on the mailing-list. • (History note: at Montreal WG meeting Peter proposed to replace the IMPORTS for these two objects with explicit definitions for easier parsing, this was rejected in the WG meeting by the AD and others.)

  5. LTANS WG (ltans): ERS WG Last Call Review results change IMPORTS of ContentInfo: • old source: CryptographicMessageSyntax2004 ContentInfo FROM CryptographicMessageSyntax2004 -- FROM [RFC3852] { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) modules(0) cms-2004(24) } • new source: PKCS-7 ContentInfo FROM PKCS-7 {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-7(7) modules(0) pkcs-7(1)}

  6. LTANS WG (ltans): ERS WG Last Call Review results change IMPORTS of AlgorithmIdentifier: • old source: PKIX1Explicit88-- Imports from RFC 3280 [RFC3280], Appendix A.1 AlgorithmIdentifier FROM PKIX1Explicit88 { iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) mod(0) pkix1-explicit(18) } • new source: AuthenticationFrameworkAlgorithmIdentifier FROM AuthenticationFramework {joint-iso-itu-t ds(5) module(1) authenticationFramework(7) 4}

  7. LTANS WG (ltans): ERS • Implementations: • Fraunhofer finished product implementation • Open Text finished product implementation • further implementations have been announced and demonstrated by other vendors - but current number and status is not completely known. • In parallel to ERS: progressing with XML spec of ERS (Aleksej) • Once ERS is stable a new I-D will be published based on structure of ERS • Several large organization in Europe (as end users) need to use ERS: i.e. to be stable

  8. LTANS WG (ltans): ERS Next step: • Submit ERS-10 with the proposed and discussed changes to the AD and IESG for IETF Last Call

More Related