IANA Registration for Donated Symantec Website Security Object Identifier Range
draft-schaad-curdle-oid-registry-02

Abstract

When the Curdle Security Working Group was chartered, a range of object identifiers was donated by Symantec Website Security for the purpose of registering the Edwards Elliptic Curve key agreement and signature algorithms. This donated set of OIDs allowed for shorter values than would be possible using the existing S​/​MIME or PKIX arcs. This document describes the range of identifiers that were assigned in that donated range, transfers control of that range to IANA, and establishes IANA allocation policies for any future assignments within that range.

Contributing to this document

The source for this draft is being maintained in GitHub. Suggested changes should be submitted as pull requests at <https://github.com/lamps-wg/smime>. Instructions are on that page as well. Editorial changes can be managed in GitHub, but any substantial issues need to be discussed on the LAMPS mailing list.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on March 16, 2018.

Copyright Notice

Copyright (c) 2017 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 (https://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.

1. Introduction

When the Curdle Security Working Group was chartered, a range of object identifiers was donated by Symantec Website Security for use by that working group. The use of these object identifiers allowed for the Edwards Ellitptic Curve key agreement [RFC7748] and signature [RFC8032] algorithms to be defined with encodings that are smaller than similar ones would be if assigned from the existing S​/​MIME or PKIX arcs. These initial registrations from this arc were done while developing [I-D.ietf-curdle-pkix]. After those registrations were done, there were still some unused values that can be used for other security groups, there were still some unused values.

Object identifiers are primarily used with Abstract Syntax Notation (ASN.1) [ASN.1]. The ASN.1 specifications continue to evolve, but object identifiers can be used with any and all versions of ASN.1.

This document describes the object identifiers that were assigned in that donated range, transfers control of the range to IANA, and establishes IANA allocation policies for any future assignments.

first: { iso (1) identified-organization (3) thawte (101) 100 }
last: { iso (1) identified-organization (3) thawte (101) 127 }
          

The donated range from Symantec Website Security is:

2. IANA Considerations

IANA is asked to create one new registry table.

2.1. "SMI Security for Cryptographic Algorithms" Registry

Within the SMI-numbers registry, add an "SMI Security for Cryptographic Algorithms" table with the three columns:

The column 'Decimal' is required to be a number between 100 and 127 inclusive.

The value of 100 has been reserved so that a new arc below that point can be established in the future. (I.e. starting at 1.3.101.100.1) If the new child registry is established, a name for this value is to be assigned at that point. The experts can, at their discretion, assign an algorithm OID instead.

The registry is to be created using the "Specification Required" policy as defined in [RFC8126].

3. Security Considerations

This document populates an IANA registry, and it raises no new security considerations. The protocols that specify these values include the security considerations associated with their usage.

4. References

4.1. Normative References

4.2. Informational References

Acknowledgments

Our thanks go out to Symantec for donating the range of OIDs covered in this document.

This document stole text heavily from a previous document doing similar thing by Russ Housely. Copying always makes things easier and less error prone.

Authors' Addresses

Table of Contents

• 1. Introduction
• 2. IANA Considerations
• 2.1. "SMI Security for Cryptographic Algorithms" Registry
• 3. Security Considerations
• 4. References
• 4.1. Normative References
• 4.2. Informational References
• Acknowledgments
• Authors' Addresses