< draft-ietf-pkix-asn1-translation-02.txt   draft-ietf-pkix-asn1-translation-03.txt >
Network Working Group C. Wallace Network Working Group C. Wallace
Internet-Draft Cygnacom Solutions Internet-Draft Cygnacom Solutions
Intended status: Informational C. Gardiner Intended status: Informational C. Gardiner
Expires: November 11, 2010 BBN Technologies Expires: February 27, 2011 BBN Technologies
May 10, 2010 August 26, 2010
ASN.1 Translation ASN.1 Translation
draft-ietf-pkix-asn1-translation-02 draft-ietf-pkix-asn1-translation-03
Abstract Abstract
Abstract Syntax Notation One (ASN.1) is widely used throughout the Abstract Syntax Notation One (ASN.1) is widely used throughout the
IETF security area and has been for many years. Some specifications IETF security area and has been for many years. Some specifications
were written using a now deprecated version of ASN.1 and some were were written using a now deprecated version of ASN.1 and some were
written using the current version of ASN.1. Not all ASN.1 compilers written using the current version of ASN.1. Not all ASN.1 compilers
support both older and current syntax. This document is intended to support both older and current syntax. This document is intended to
provide guidance to specification authors and to implementers provide guidance to specification authors and to implementers
converting ASN.1 modules written using one version of ASN.1 to converting ASN.1 modules written using one version of ASN.1 to
another version without causing changes to the "bits on the wire". another version without causing changes to the "bits on the wire".
This document does not provide a comprehensive tutorial of any This document does not provide a comprehensive tutorial of any
version of ASN.1. Instead, it addresses ASN.1 features that are used version of ASN.1. Instead, it addresses ASN.1 features that are used
in IETF security area specifications with focus on items that vary in IETF security area specifications with focus on items that vary
with the ASN.1 version. with the ASN.1 version.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on February 27, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 11, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. ASN.1 design elements . . . . . . . . . . . . . . . . . . . . 4 2. ASN.1 design elements . . . . . . . . . . . . . . . . . . . . 4
2.1. Open types . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Open types . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1. ANY DEFINED BY . . . . . . . . . . . . . . . . . . . . 4 2.1.1. ANY DEFINED BY . . . . . . . . . . . . . . . . . . . . 4
2.1.2. OCTET STRINGs and BIT STRINGs . . . . . . . . . . . . 5 2.1.2. OCTET STRINGs and BIT STRINGs . . . . . . . . . . . . 5
2.1.3. Information Object Classes . . . . . . . . . . . . . . 6 2.1.3. Information Object Classes . . . . . . . . . . . . . . 6
skipping to change at page 3, line 36 skipping to change at page 4, line 5
1.1. Terminology 1.1. Terminology
This document addresses two different versions of ASN.1. The old This document addresses two different versions of ASN.1. The old
(1988) version was defined in a single document (X.208) and the newer (1988) version was defined in a single document (X.208) and the newer
(1998, 2002) version is defined in a series of documents (X.680, (1998, 2002) version is defined in a series of documents (X.680,
X.681, X.682 and X.683). For convenience, the series of documents is X.681, X.682 and X.683). For convenience, the series of documents is
henceforth referred to as X.68x. Specific documents from the series henceforth referred to as X.68x. Specific documents from the series
are referenced by name where appropriate. are referenced by name where appropriate.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. ASN.1 design elements 2. ASN.1 design elements
When translating an ASN.1 module from X.208 syntax to X.68x syntax, When translating an ASN.1 module from X.208 syntax to X.68x syntax,
or vice versa, many definitions do not require or benefit from or vice versa, many definitions do not require or benefit from
change. Review of the original ASN.1 modules updated by change. Review of the original ASN.1 modules updated by
[I-D.ietf-pkix-new-asn1] and [I-D.ietf-smime-new-asn1] and the [I-D.ietf-pkix-new-asn1] and [I-D.ietf-smime-new-asn1] and the
revised modules included in those documents indicates that most revised modules included in those documents indicates that most
changes can be sorted into one of a few categories. This section changes can be sorted into one of a few categories. This section
describes these categories. describes these categories.
skipping to change at page 22, line 39 skipping to change at page 22, line 39
Consultative Committee, "Abstract Syntax Notation One Consultative Committee, "Abstract Syntax Notation One
(ASN.1): Constraint specification", CCITT Recommendation (ASN.1): Constraint specification", CCITT Recommendation
X.682, July 2002. X.682, July 2002.
[CCITT.X683.2002] [CCITT.X683.2002]
International International Telephone and Telegraph International International Telephone and Telegraph
Consultative Committee, "Abstract Syntax Notation One Consultative Committee, "Abstract Syntax Notation One
(ASN.1): Parameterization of ASN.1 specifications", (ASN.1): Parameterization of ASN.1 specifications",
CCITT Recommendation X.683, July 2002. CCITT Recommendation X.683, July 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
7.2. Informative References 7.2. Informative References
[CCITT.X209.1988] [CCITT.X209.1988]
International Telephone and Telegraph Consultative International Telephone and Telegraph Consultative
Committee, "Specification of Basic Encoding Rules for Committee, "Specification of Basic Encoding Rules for
Abstract Syntax Notation One (ASN.1)", Abstract Syntax Notation One (ASN.1)",
CCITT Recommendation X.209, 1988. CCITT Recommendation X.209, 1988.
[CCITT.X690.2002] [CCITT.X690.2002]
International International Telephone and Telegraph International International Telephone and Telegraph
skipping to change at page 24, line 9 skipping to change at page 24, line 9
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, May 2008. (CRL) Profile", RFC 5280, May 2008.
Authors' Addresses Authors' Addresses
Carl Wallace Carl Wallace
Cygnacom Solutions Cygnacom Solutions
Suite 5200 Suite 5400
7925 Jones Branch Drive 7925 Jones Branch Drive
McLean, VA 22102 McLean, VA 22102
Email: cwallace@cygnacom.com Email: cwallace@cygnacom.com
Charles Gardiner Charles Gardiner
BBN Technologies BBN Technologies
10 Moulton Street 10 Moulton Street
Cambridge, MA 02138 Cambridge, MA 02138
 End of changes. 9 change blocks. 
23 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/