RFC 7036

Object Identifier Registry for the Long-Term Archive and Notary Services (LTANS) Working Group

📅 published October 2013, from ietf

Object Identifier Registry for the Long-Term Archive and Notary Services (LTANS) Working Group 🎀

Okay so this is RFC 7036 💖, and it's an Informational doc, not a standards-track one. The author is R. Housley from Vigil Security, and it's dated October 2013. It has ISSN 2070-1721. The title block doesn't list anything it obsoletes or updates, so it just kind of stands on its own 🦋.

Abstract

Bestie, the LTANS working group got an object identifier arc set aside for them when they were chartered 🌸. This doc lists the OIDs that got assigned, and it sets up the IANA allocation rules for any future stuff in that arc 💅.

Status of This Memo

This one is NOT an Internet Standards Track spec. It's just published for info 🧚.

It's a product of the IETF, it represents the consensus of the IETF community, it got public review, and the IESG approved it for publication ✨. Not every IESG-approved doc is a candidate for any level of Internet Standard, so check out Section 2 of RFC 5741 if you want the deets 🙈.

For the current status, errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc7036 🔥.

Copyright Notice

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they were in effect on the date of publication. Please read these carefully, bestie, because they're all about your rights and restrictions with this doc 🫶. Code Components pulled out of this doc must include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come without warranty, as the Simplified BSD License describes 🌈.

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 ✨

Okay so when LTANS got chartered, they got an OID arc set aside just for them 👑. These OIDs are mostly used with Abstract Syntax Notation One (ASN.1) [ASN1-88] [ASN1-97] 🤓.

The LTANS OID arc is:

   id-ltans OBJECT IDENTIFIER ::= { iso(1) identified-organization(3)
                                    dod(6) internet(1) security(5)
                                    mechanisms(5) ltans(11) }

This doc describes the OIDs that were assigned, and it sets the IANA allocation policies for any future assignments in that arc 💖.

2. Subordinate Object Identifier Arcs 🦋

There are three subordinate arcs under there. The first one, id-mod, is for assigning ASN.1 module identifiers 📦. The second one, id-ct, is for Cryptographic Message Syntax (CMS) content types 💌. The third one, id-em, got 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 }

3. Module Identifiers 🧚

Okay the Evidence Record Syntax (ERS) [RFC4998] has two ASN.1 modules, and they define the exact same syntax 🎀. The difference is one uses the 1997 ASN.1 syntax and the other uses the 1988 one 🙈. Here are the module IDs:

   id-mod-ers           OBJECT IDENTIFIER ::= { id-mod 1 }
   id-mod-ers-v1        OBJECT IDENTIFIER ::= { id-mod 1 1 }
   id-mod-ers88         OBJECT IDENTIFIER ::= { id-mod 2 }
   id-mod-ers88-v1      OBJECT IDENTIFIER ::= { id-mod 2 1 }

Next up, the Long-term Archive Protocol (LTAP) [LTAP] has two ASN.1 modules too 🌸. Ngl, this protocol never got published as an RFC, but its module IDs still got assigned to help with implementation 🫶. Same deal here: both modules define the same syntax, one with 1997 ASN.1 and one with 1988 ASN.1 💅.

   id-mod-ltap88        OBJECT IDENTIFIER ::= { id-mod 3 }
   id-mod-ltap88-v0     OBJECT IDENTIFIER ::= { id-mod 3 0 }
   id-mod-ltap88-v1     OBJECT IDENTIFIER ::= { id-mod 3 1 }
   id-mod-ltap          OBJECT IDENTIFIER ::= { id-mod 4 }
   id-mod-ltap-v0       OBJECT IDENTIFIER ::= { id-mod 4 0 }
   id-mod-ltap-v1       OBJECT IDENTIFIER ::= { id-mod 4 1 }

The doc about using the Server-Based Certificate Validation Protocol (SCVP) to carry Long-Term Evidence Records [RFC5276] has one ASN.1 module 🌈. Its module ID is:

   id-mod-ers-scvp      OBJECT IDENTIFIER ::= { id-mod 5 }
   id-mod-ers-scvp-v1   OBJECT IDENTIFIER ::= { id-mod 5 1 }

Then there's the Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC) [RFC5698], which has two ASN.1 modules 🔥. Both define the same syntax, with one using 1997 ASN.1 and the other using 1988 ASN.1 ✨. The module IDs are:

   id-mod-dssc88        OBJECT IDENTIFIER ::= { id-mod 6 }
   id-mod-dssc88-v1     OBJECT IDENTIFIER ::= { id-mod 6 1 }
   id-mod-dssc          OBJECT IDENTIFIER ::= { id-mod 7 }
   id-mod-dssc-v1       OBJECT IDENTIFIER ::= { id-mod 7 1 }

4. CMS Content Types 💜

A CMS content type for an Evidence Record got reserved, but no spec points to that value, so it's still reserved 🙃. Here it is:

   id-ct-evidence-record  OBJECT IDENTIFIER ::= { id-ct 1 }

DSSC [RFC5698] specifies three CMS content types 🧁. They are:

   id-ct-dssc-asn1        OBJECT IDENTIFIER ::= { id-ct 2 }
   id-ct-dssc-xml         OBJECT IDENTIFIER ::= { id-ct 3 }
   id-ct-dssc-tbsPolicy   OBJECT IDENTIFIER ::= { id-ct 6 }

LTAP [LTAP] defines two CMS content types 🍓. Same tea as before: the protocol never got published as an RFC, but the content types were assigned to help implementers 🫶. They are:

   id-ct-LTAPRequest      OBJECT IDENTIFIER ::= { id-ct 4 }
   id-ct-LTAPResponse     OBJECT IDENTIFIER ::= { id-ct 5 }

8.1. Normative References ✨

Okay so the normative references are the ones you literally must read to get the spec, and bestie, these two ASN.1 ones are giving classic. 💖

[ASN1-88]  International Telephone and Telegraph Consultative
           Committee, "Specification of Abstract Syntax Notation One
           (ASN.1)", CCITT Recommendation X.208, 1988.

[ASN1-97]  International Telecommunications Union, "Abstract Syntax
           Notation One (ASN.1): Specification of basic notation",
           ITU-T Recommendation X.680, 1997.

[RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
           IANA Considerations Section in RFCs", BCP 26, RFC 5226,
           May 2008.

RFC5226 is the one that tells you how to write an IANA Considerations section, which is so relevant to everything we just went through in Section 7 🧚

8.2. Informative References 🦋

These ones are the extra reading. Not required to build the thing, but iykyk, they're the reason the vibes make sense. 🌸

[LTAP]     Jerman Blazic, A., Sylvester, P., and C. Wallace, "Long-
           term Archive Protocol (LTAP)", Work in Progress, July
           2009.

[RFC4998]  Gondrom, T., Brandner, R., and U. Pordesch, "Evidence
           Record Syntax (ERS)", RFC 4998, August 2007.

[RFC5276]  Wallace, C., "Using the Server-Based Certificate
           Validation Protocol (SCVP) to Convey Long-Term Evidence
           Records", RFC 5276, August 2008.

[RFC5698]  Kunz, T., Okunick, S., and U. Pordesch, "Data Structure
           for the Security Suitability of Cryptographic Algorithms
           (DSSC)", RFC 5698, November 2009.

[RFC4998] is the big one here, the Evidence Record Syntax itself 😭 It's literally the foundation for the ERS stuff we covered earlier. Obsessed. 💅

9. Acknowledgements 🫶

Thanks to Carl Wallace, Sean Turner, Paul Hoffman, and Carsten Bormann for their review and comments. Main character energy for the reviewers, no cap. 👑

Author's Address

Russ Housley
Vigil Security, LLC
918 Spring Knoll Drive
Herndon, VA 20170
USA

EMail: housley@vigilsec.com

Russ Housley from Vigil Security is the author who made all of this happen, so big thank-you to him 🎀✨

📦 where this page comes from

ietf: rfc7036 2013-10
💖 girlified by claude-haiku-5-5 on 2026-10-17: a language model's rewrite of the original, under its terms