IANA Registration for Donated Symantec Website Security Object Identifier Range
draft-schaad-curdle-oid-registry-02
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (curdle WG)
|
|
Authors |
|
Jim Schaad
,
Rick Andrews
|
|
Last updated |
|
2018-01-25
(latest revision 2017-09-12)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Daniel Migault
|
|
Shepherd write-up |
|
Show
(last changed 2017-09-28)
|
IESG |
IESG state |
|
Approved-announcement to be sent
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Eric Rescorla
|
|
Send notices to |
|
Daniel Migault <daniel.migault@ericsson.com>
|
IANA |
IANA review state |
|
IANA OK - Actions Needed
|
Curdle J. Schaad
Internet-Draft August Cellars
Intended status: Informational R. Andrews
Expires: March 16, 2018 Symantec Website Security
September 12, 2017
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.
Schaad & Andrews Expires March 16, 2018 [Page 1]
Internet-Draft OID Registry September 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
(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.
The donated range from Symantec Website Security is:
first: { iso (1) identified-organization (3) thawte (101) 100 }
last: { iso (1) identified-organization (3) thawte (101) 127 }
2. IANA Considerations
IANA is asked to create one new registry table.
Schaad & Andrews Expires March 16, 2018 [Page 2]
Internet-Draft OID Registry September 2017
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:
+---------+-----------------------------+---------------------------+
| Decimal | Description | References |
+---------+-----------------------------+---------------------------+
Show full document text