1 / 7

ASN.1 2002 Tutorial

ASN.1 2002 Tutorial. Jim Schaad. Why we care. Paul Hoffman and Jim Schaad have a contract to develop a freeware 2002 ASN.1 compiler Expect to be released by the end of the year We will be doing updates to “core” 1988 ASN.1 modules. Component Relation Constraint. ContentInfo ::= SEQUENCE {

agnes
Download Presentation

ASN.1 2002 Tutorial

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. ASN.1 2002 Tutorial Jim Schaad

  2. Why we care • Paul Hoffman and Jim Schaad have a contract to develop a freeware 2002 ASN.1 compiler • Expect to be released by the end of the year • We will be doing updates to “core” 1988 ASN.1 modules

  3. Component Relation Constraint ContentInfo ::= SEQUENCE { contentType CONTENT-TYPE.&id({ContentSet}), content [0] EXPLICIT CONTENT-TYPE.&Type ({ContentSet}{@contentType})} ContentSet CONTENT-TYPE ::= { -- Define the set of content types to be recognized. -- Import and add any from external modules at this point. -- ct-Data | ct-SignedData | ct-EncryptedData | ct-EnvelopedData | ct-AuthenticatedData | ct-DigestedData, … } }

  4. Algorithms Constraint DigestAlgorithmList ALGORITHM ::= { -- Include digest algorithm set here alg-sha-1 | alg-md5, … } DigestAlgorithmIdentifier ::= AlgorithmIdentifier {{DigestAlgorithmList}}

  5. Algorithm Associations ALGORITHM::= CLASS { &id OBJECT IDENTIFIER UNIQUE, &ExtnType } WITH SYNTAX {PARAMS &ExtnType IDENTIFIED BY &id } • Add other fields? • <ID, Params, Value> • Use different ones for Signature, Encrypted Data and Key

  6. Extensibility RecipientInfo ::= CHOICE { ktri KeyTransRecipientInfo, kari [1] KeyAgreeRecipientInfo, kekri [2] KEKRecipientInfo, pwri [3] PasswordRecipientInfo, ori [4] OtherRecipientInfo, … } Other structures as well.

  7. Questions • Other items we should use? • Should we do as much decoration as possible? • People who want specific compiler features – see me after the meeting.

More Related