|Internet-Draft||IPSECKEY EdDSA||August 2022|
|Moskowitz & Kivinen||Expires 3 February 2023||[Page]|
- Intended Status:
- Standards Track
EdDSA value for IPSECKEY
This document assigns a value for EdDSA Public Keys to the IPSECKEY IANA registry.¶
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 3 February 2023.¶
Copyright (c) 2022 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The IPSECKEY IANA Registry specifically enumerates the various Algorithm Types used. This document adds support for the EdDSA algorithm's Public Keys in IPSECKEY.¶
2. Terms and Definitions
2.1. Requirements Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
3. IPSECKEY support for EdDSA
The new EdDSA value uses [RFC8080] for the IPSECKEY encoding:¶
Value Description TBD2 (suggested value 4) An EdDSA Public key is present, in the format defined in [RFC8080]¶
4. IANA Considerations
4.1. IANA IPSECKEY Registry Update
This document requests IANA to make the following change to the "IPSECKEY Resource Record Parameters" [IANA-IPSECKEY] registry:¶
- This document defines the new IPSECKEY value TBD2 (suggested: 4) (Section 3) in the "Algorithm Type Field" subregistry of the "IPSECKEY Resource Record Parameters" registry.¶
Value Description Reference TBD2 (suggested value 4) [This] An EdDSA Public key is present, in the format defined in [RFC8080]¶
6.1. Normative References
- Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", DOI 10.17487/RFC2119, BCP 14, RFC 2119, , <https://www.rfc-editor.org/info/rfc2119>.
- Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", DOI 10.17487/RFC8174, RFC 8174, BCP 14, , <https://www.rfc-editor.org/info/rfc8174>.
6.2. Informative References
- IANA, "IPSECKEY Resource Record Parameters", <https://www.iana.org/assignments/ipseckey-rr-parameters/ipseckey-rr-parameters.xhtml>.
- Sury, O. and R. Edmonds, "Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSEC", RFC 8080, DOI 10.17487/RFC8080, , <https://www.rfc-editor.org/info/rfc8080>.
Thanks to Security Area director, Paul Wouters, for initial review.¶