Object Identifier Registry for the Long-Term Archive and Notary Services (LTANS) Working Group
RFC 7036
Document | Type |
RFC - Informational
(October 2013; No errata)
Was draft-housley-ltans-oids (individual in sec area)
|
|
---|---|---|---|
Author | Russ Housley | ||
Last updated | 2015-10-14 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Carl Wallace | ||
Shepherd write-up | Show (last changed 2013-07-02) | ||
IESG | IESG state | RFC 7036 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Sean Turner | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) R. Housley Request for Comments: 7036 Vigil Security Category: Informational October 2013 ISSN: 2070-1721 Object Identifier Registry for the Long-Term Archive and Notary Services (LTANS) Working Group Abstract When the Long-Term Archive and Notary Services (LTANS) working group was chartered, an object identifier arc was set aside for use by that working group. This document describes the object identifiers that were assigned, and it establishes IANA allocation policies for any future assignments within that arc. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7036. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Housley Informational [Page 1] RFC 7036 LTANS OID Registry October 2013 Table of Contents 1. Introduction ....................................................2 2. Subordinate Object Identifier Arcs ..............................2 3. Module Identifiers ..............................................3 4. CMS Content Types ...............................................4 5. ERS Encryption Methods ..........................................4 6. Security Considerations .........................................4 7. IANA Considerations .............................................4 7.1. SMI Security for Mechanism Codes Registry ..................5 7.2. SMI Security for LTANS Registry ............................5 7.3. SMI Security for LTANS Module Identifier Registry ..........5 7.4. SMI Security for LTANS CMS Content Type Registry ...........6 7.5. SMI Security for LTANS ERS Encryption Method Registry ......6 8. References ......................................................6 8.1. Normative References .......................................6 8.2. Informative References .....................................7 9. Acknowledgements ................................................7 1. Introduction When the Long-Term Archive and Notary Services (LTANS) working group was chartered, an object identifier arc was set aside for use by that working group. These object identifiers are primarily used with Abstract Syntax Notation One (ASN.1) [ASN1-88] [ASN1-97]. The LTANS object identifier arc is: id-ltans OBJECT IDENTIFIER ::= { iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) ltans(11) } This document describes the object identifiers that were assigned, and it establishes IANA allocation policies for any future assignments within that arc. 2. Subordinate Object Identifier Arcs Three subordinate object identifier arcs were used. The first arc, id-mod, was used to assign ASN.1 module identifiers. The second arc, id-ct, was used to assign Cryptographic Message Syntax (CMS) content types. The third arc, id-em, was set aside for Evidence Record Syntax (ERS) encryption methods. id-mod OBJECT IDENTIFIER ::= { id-ltans 0 } id-ct OBJECT IDENTIFIER ::= { id-ltans 1 } id-em OBJECT IDENTIFIER ::= { id-ltans 2 } Housley Informational [Page 2] RFC 7036 LTANS OID Registry October 2013 3. Module Identifiers The Evidence Record Syntax (ERS) [RFC4998] includes two ASN.1 modules. Both modules define the same syntax, but one module uses the 1997 ASN.1 syntax, and the other module uses the 1988 ASN.1Show full document text