[Docs] [txt|pdf|xml|html] [Tracker] [WG] [Email] [Nits]

Versions: 00 01 02 03 RFC 8411

Curdle                                                         J. Schaad
Internet-Draft                                            August Cellars
Intended status: Informational                                R. Andrews
Expires: November 9, 2017                      Symantec Website Security
                                                             May 8, 2017


        Object Identifier Registry for the Curdle Working Group
                  draft-schaad-curdle-oid-registry-00

Abstract

   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.  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 http://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 November 9, 2017.








Schaad & Andrews        Expires November 9, 2017                [Page 1]


Internet-Draft                OID Registry                      May 2017


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
   (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.

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.  These 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.

   The Curdle object identifier range is:

     { iso (1) identified-organization (3) thawte (101) 100 }
     to
     { iso (1) identified-organization (3) thawte (101) 127 }

   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
   within that range.

2.  IANA Considerations

   IANA is asked to create one new registry table.

2.1.  "SMI Security for Curdle" Registry

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








Schaad & Andrews        Expires November 9, 2017                [Page 2]


Internet-Draft                OID Registry                      May 2017


   +---------+--------------------------------+------------------------+
   | Decimal | Description                    | References             |
   +---------+--------------------------------+------------------------+
   | 100     | Reserved for future sub-       |                        |
   |         | registry                       |                        |
   |         |                                |                        |
   | 110     | id-X25519                      | [I-D.ietf-curdle-pkix] |
   |         |                                |                        |
   | 111     | id-X448                        | [I-D.ietf-curdle-pkix] |
   |         |                                |                        |
   | 112     | id-EdDSA25519                  | [I-D.ietf-curdle-pkix] |
   |         |                                |                        |
   | 113     | id-EdDS448                     | [I-D.ietf-curdle-pkix] |
   |         |                                |                        |
   | 114     | id-EdDSA25519-ph               | [I-D.ietf-curdle-pkix] |
   |         |                                |                        |
   | 115     | id-EdDS448=ph                  | [I-D.ietf-curdle-pkix] |
   |         |                                |                        |
   | 120     | Safecurves-pkix-0              | [I-D.ietf-curdle-pkix] |
   +---------+--------------------------------+------------------------+

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

   Future updates to this table require both 'Specification Required'
   and 'Expert Review' as defiened in [RFC5226].

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

   [ASN.1]    "Information Technology - Abstract Syntax Notation One
              (ASN.1): Specification of basic notation.  ITU-T
              Recommendation X.680 (2008)", ITU-T X.680, ISO/
              IEC 8824-1:2008, November 2008.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              DOI 10.17487/RFC5226, May 2008,
              <http://www.rfc-editor.org/info/rfc5226>.





Schaad & Andrews        Expires November 9, 2017                [Page 3]


Internet-Draft                OID Registry                      May 2017


4.2.  Informational References

   [I-D.ietf-curdle-pkix]
              Josefsson, S. and J. Schaad, "Algorithm Identifiers for
              Ed25519, Ed448, X25519 and X448 for use in the Internet
              X.509 Public Key Infrastructure", draft-ietf-curdle-
              pkix-04 (work in progress), March 2017.

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

   Jim Schaad
   August Cellars

   Email: ietf@augustcellars.com


   Rick Andrews
   Symantec Website Security

   Email: Rick_Andrews@symantec.com






















Schaad & Andrews        Expires November 9, 2017                [Page 4]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/