idnits 2.17.1 draft-housley-ltans-oids-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (29 July 2013) is 3924 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT R. Housley 3 Intended Status: Informational Vigil Security 4 Expires: 29 January 2014 29 July 2013 6 Object Identifier Registry for the 7 Long-Term Archive and Notary Services (LTANS) Working Group 8 10 Abstract 12 When the Long-Term Archive and Notary Services (LTANS) Working Group 13 was chartered, an object identifier arc was set aside for use by that 14 working group. This document describes the object identifiers that 15 were assigned, and it establishes IANA allocation policies for any 16 future assignments within that arc. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as 26 Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/1id-abstracts.html 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html 39 Copyright and License Notice 41 Copyright (c) 2013 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Subordinate Object Identifier Arcs . . . . . . . . . . . . . . 2 58 3. Module Identifiers . . . . . . . . . . . . . . . . . . . . . . 3 59 4. CMS Content Types . . . . . . . . . . . . . . . . . . . . . . 4 60 5. ERS Encryption Methods . . . . . . . . . . . . . . . . . . . . 4 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 63 7.1. Update to SMI Security for Mechanism Codes Registry . . . 4 64 7.2. Add SMI Security for LTANS Registry . . . . . . . . . . . 4 65 7.3. Add SMI Security for LTANS Module Identifier Registry . . 5 66 7.4. Add SMI Security for LTANS CMS Content Type Registry . . . 5 67 7.5. Add SMI Security for LTANS CMS Content Type Registry . . . 6 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 70 8.2. Informative References . . . . . . . . . . . . . . . . . . 6 71 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 73 1. Introduction 75 When the Long-Term Archive and Notary Services (LTANS) Working Group 76 was chartered, an object identifier arc was set aside for use by that 77 working group. These object identifiers are primarily used with 78 Abstract Syntax Notation One (ASN.1) [ASN1-88] [ASN1-97]. 80 The LTANS object identifier arc is: 82 id-ltans OBJECT IDENTIFIER ::= { iso(1) identified-organization(3) 83 dod(6) internet(1) security(5) 84 mechanisms(5) ltans(11) } 86 This document describes the object identifiers that were assigned, 87 and it establishes IANA allocation policies for any future 88 assignments within that arc. 90 2. Subordinate Object Identifier Arcs 92 Three subordinate object identifier arcs were used. The first arc, 93 id-mod, was used to assign ASN.1 module identifiers. The second arc, 94 id-ct, was used to assign Cryptographic Message Syntax (CMS) content 95 types. The third arc, id-em, was set aside for Evidence Record 96 Syntax (ERS) encryption methods. 98 id-mod OBJECT IDENTIFIER ::= { id-ltans 0 } 99 id-ct OBJECT IDENTIFIER ::= { id-ltans 1 } 100 id-em OBJECT IDENTIFIER ::= { id-ltans 2 } 102 3. Module Identifiers 104 The Evidence Record Syntax (ERS) [RFC4998] includes two ASN.1 105 modules. Both modules define the same syntax, but one module uses 106 the 1997 ASN.1 syntax, and the other module uses the 1988 ASN.1 107 syntax. These module identifiers are: 109 id-mod-ers OBJECT IDENTIFIER ::= { id-mod 1 } 110 id-mod-ers-v1 OBJECT IDENTIFIER ::= { id-mod 1 1 } 111 id-mod-ers88 OBJECT IDENTIFIER ::= { id-mod 2 } 112 id-mod-ers88-v1 OBJECT IDENTIFIER ::= { id-mod 2 1 } 114 The Long-term Archive Protocol (LTAP) [LTAP] includes two ASN.1 115 modules. While this protocol was never published as an RFC, the 116 module identifiers were assigned to facilitate implementation. Both 117 modules define the same syntax, but one module uses the 1997 ASN.1 118 syntax, and the other module uses the 1988 ASN.1 syntax. These 119 module identifiers are: 121 id-mod-ltap88 OBJECT IDENTIFIER ::= { id-mod 3 } 122 id-mod-ltap88-v0 OBJECT IDENTIFIER ::= { id-mod 3 0 } 123 id-mod-ltap88-v1 OBJECT IDENTIFIER ::= { id-mod 3 1 } 124 id-mod-ltap OBJECT IDENTIFIER ::= { id-mod 4 } 125 id-mod-ltap-v0 OBJECT IDENTIFIER ::= { id-mod 4 0 } 126 id-mod-ltap-v1 OBJECT IDENTIFIER ::= { id-mod 4 1 } 128 The document that describes the conventions for using Simple 129 Certificate Validation Protocol (SCVP) to convey Long-term Evidence 130 Records [RFC5276] includes one ASN.1 module. The module identifier 131 is: 133 id-mod-ers-scvp OBJECT IDENTIFIER ::= { id-mod 5 } 134 id-mod-ers-scvp-v1 OBJECT IDENTIFIER ::= { id-mod 5 1 } 136 The Data Structure for the Security Suitability of Cryptographic 137 Algorithms (DSSC) [RFC5698] includes two ASN.1 modules. Both modules 138 define the same syntax, but one module uses the 1997 ASN.1 syntax, 139 and the other module uses the 1988 ASN.1 syntax. These module 140 identifiers are: 142 id-mod-dssc88 OBJECT IDENTIFIER ::= { id-mod 6 } 143 id-mod-dssc88-v1 OBJECT IDENTIFIER ::= { id-mod 6 1 } 144 id-mod-dssc OBJECT IDENTIFIER ::= { id-mod 7 } 145 id-mod-dssc-v1 OBJECT IDENTIFIER ::= { id-mod 7 1 } 147 4. CMS Content Types 149 A CMS content type for an Evidence Record was reserved, but no 150 specification points to this value. It remains reserved. 152 id-ct-evidence-record OBJECT IDENTIFIER ::= { id-ct 1 } 154 The Data Structure for the Security Suitability of Cryptographic 155 Algorithms (DSSC) [RFC5698] specifies three CMS content types. These 156 CMS content types are: 158 id-ct-dssc-asn1 OBJECT IDENTIFIER ::= { id-ct 2 } 159 id-ct-dssc-xml OBJECT IDENTIFIER ::= { id-ct 3 } 160 id-ct-dssc-tbsPolicy OBJECT IDENTIFIER ::= { id-ct 6 } 162 The Long-term Archive Protocol (LTAP) [LTAP] defines two CMS content 163 types. While this protocol was never published as an RFC, the CMS 164 content types were assigned to facilitate implementation. These CMS 165 content types are: 167 id-ct-LTAPRequest OBJECT IDENTIFIER ::= { id-ct 4 } 168 id-ct-LTAPResponse OBJECT IDENTIFIER ::= { id-ct 5 } 170 5. ERS Encryption Methods 172 An arc was set up for Evidence Record Syntax (ERS) encryption 173 methods, and one object identifier was assigned. However, that 174 object identifier is obsolete, and it should not be used. 176 id-em-enveloped-data OBJECT IDENTIFIER ::= { id-em 1 } -- obsolete 178 6. Security Considerations 180 This document populates an IANA registry, and it raises no new 181 security considerations. The protocols that specify these values 182 include the security considerations associated with their usage. 184 7. IANA Considerations 186 IANA is asked to update one registry table and create four additional 187 tables. 189 Updates to the four new tables require Expert Review as defined in 190 [RFC5226]. The expert is expected to ensure that any new values are 191 strongly related to the work that was done by the LTANS WG. Object 192 identifiers for other purposes should not be assigned in this arc. 194 7.1. Update to SMI Security for Mechanism Codes Registry 196 Please update the reference in the Long-Term Archive and Notary 197 Services entry (decimal value 11) so that it points to this document. 199 7.2. Add SMI Security for LTANS Registry 201 Within the SMI-numbers registry, add a "SMI Security for LTANS 202 (1.3.6.1.5.5.11)" table with three columns: 204 Decimal Description References 205 ------- ---------------------- ---------- 206 0 module-identifiers {This RFC} 207 1 cms-content-types {This RFC} 208 2 ers-encryption-methods {This RFC} 210 Future updates to this table require Expert Review as defined in 211 [RFC5226]. 213 7.3. Add SMI Security for LTANS Module Identifier Registry 215 Within the SMI-numbers registry, add a "SMI Security for LTANS Module 216 Identifier (1.3.6.1.5.5.11.0)" table with three columns: 218 OID Value Description References 219 -------------------- ------------------- ---------- 220 1.3.6.1.5.5.11.0.1 id-mod-ers [RFC4998] 221 1.3.6.1.5.5.11.0.1.1 id-mod-ers-v1 [RFC4998] 222 1.3.6.1.5.5.11.0.2 id-mod-ers88 [RFC4998] 223 1.3.6.1.5.5.11.0.2.1 id-mod-ers88-v1 [RFC4998] 224 1.3.6.1.5.5.11.0.3 id-mod-ltap88 Reserved 225 1.3.6.1.5.5.11.0.3.0 id-mod-ltap88-v0 Reserved 226 1.3.6.1.5.5.11.0.3.1 id-mod-ltap88-v1 Reserved 227 1.3.6.1.5.5.11.0.4 id-mod-ltap Reserved 228 1.3.6.1.5.5.11.0.4.0 id-mod-ltap-v0 Reserved 229 1.3.6.1.5.5.11.0.4.1 id-mod-ltap-v1 Reserved 230 1.3.6.1.5.5.11.0.5 id-mod-ers-scvp [RFC5276] 231 1.3.6.1.5.5.11.0.5.1 id-mod-ers-scvp-v1 [RFC5276] 232 1.3.6.1.5.5.11.0.6 id-mod-dssc88 [RFC5698] 233 1.3.6.1.5.5.11.0.6.1 id-mod-dssc88-v1 [RFC5698] 234 1.3.6.1.5.5.11.0.7 id-mod-dssc [RFC5698] 235 1.3.6.1.5.5.11.0.7.1 id-mod-dssc-v1 [RFC5698] 237 Future updates to this table require Expert Review as defined in 238 [RFC5226]. 240 7.4. Add SMI Security for LTANS CMS Content Type Registry 242 Within the SMI-numbers registry, add a "SMI Security for LTANS CMS 243 Content Type (1.3.6.1.5.5.11.1)" table with three columns: 245 Decimal Description References 246 ------- --------------------- ---------- 247 1 id-ct-evidence-record Reserved 248 2 id-ct-dssc-asn1 [RFC5698] 249 3 id-ct-dssc-xml [RFC5698] 250 4 id-ct-LTAPRequest Reserved 251 5 id-ct-LTAPResponse Reserved 252 6 id-ct-dssc-tbsPolicy [RFC5698] 254 Future updates to this table require Expert Review as defined in 255 [RFC5226]. 257 7.5. Add SMI Security for LTANS CMS Content Type Registry 259 Within the SMI-numbers registry, add a "SMI Security for LTANS ERS 260 Encryption Method (1.3.6.1.5.5.11.2)" table with three columns: 262 Decimal Description References 263 ------- --------------------- --------------------- 264 1 id-em-enveloped-data Reserved and Obsolete 266 Future updates to this table require Expert Review as defined in 267 [RFC5226]. 269 8. References 271 8.1. Normative References 273 [ASN1-88] International Telephone and Telegraph Consultative 274 Committee, "Specification of Abstract Syntax Notation One 275 (ASN.1)", CCITT Recommendation X.208, 1988. 277 [ASN1-97] International Telecommunications Union, "Abstract Syntax 278 Notation One (ASN.1): Specification of basic notation", 279 ITU-T Recommendation X.680, 1997. 281 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 282 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 283 May 2008. 285 8.2. Informative References 287 [LTAP] Jerman Blazic, A., Sylvester, P., and C. Wallace, "Long- 288 term Archive Protocol (LTAP)", work-in-progress, July 289 2009. 291 [RFC4998] Gondrom, T., Brandner, R., and U. Pordesch, "Evidence 292 Record Syntax (ERS)", RFC 4998, August 2007. 294 [RFC5276] Wallace, C., "Using the Server-Based Certificate 295 Validation Protocol (SCVP) to Convey Long-Term Evidence 296 Records", RFC 5276, August 2008. 298 [RFC5698] Kunz, T., Okunick, S., and U. Pordesch, "Data Structure 299 for the Security Suitability of Cryptographic Algorithms 300 (DSSC)", RFC 5698, November 2009. 302 9. Acknowledgements 304 Thanks to Carl Wallace, Sean Turner, Paul Hoffman, and Carsten 305 Bormann for their review and comments. 307 Author's Addresses 309 Russ Housley 310 918 Spring Knoll Drive 311 Herndon, VA 20170 312 USA 313 EMail: housley@vigilsec.com