[Curdle] RFC 8411 on IANA Registration for the Cryptographic Algorithm Object Identifier Range
rfc-editor@rfc-editor.org Tue, 07 August 2018 05:38 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F9F130F19; Mon, 6 Aug 2018 22:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Te5EUTYr8GAA; Mon, 6 Aug 2018 22:38:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 904FB130E09; Mon, 6 Aug 2018 22:38:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6B391B817C1; Mon, 6 Aug 2018 22:38:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180807053842.6B391B817C1@rfc-editor.org>
Date: Mon, 06 Aug 2018 22:38:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/uje8jWdNWsJIs3zplmn24l9dzr4>
Subject: [Curdle] RFC 8411 on IANA Registration for the Cryptographic Algorithm Object Identifier Range
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Aug 2018 05:38:54 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8411
Title: IANA Registration for the Cryptographic
Algorithm Object Identifier Range
Author: J. Schaad,
R. Andrews
Status: Informational
Stream: IETF
Date: August 2018
Mailbox: ietf@augustcellars.com,
rick.andrews@digicert.com
Pages: 5
Characters: 8985
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-schaad-curdle-oid-registry-03.txt
URL: https://www.rfc-editor.org/info/rfc8411
DOI: 10.17487/RFC8411
When the Curdle Security Working Group was chartered, a range of
object identifiers was donated by DigiCert, Inc. 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 donated range and the identifiers that were
assigned from that range, transfers control of that range to IANA,
and establishes IANA allocation policies for any future assignments
within that range.
This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC