EdDSA value for IPSECKEY

Internet-Draft	IPSECKEY EdDSA	August 2022
Moskowitz & Kivinen	Expires 11 February 2023	[Page]

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 11 February 2023.¶

Copyright Notice

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

1. Introduction

The IPSECKEY IANA Registry specifically enumerates the various Algorithm Types used. This document adds support for the EdDSA algorithm's Public Keys in IPSECKEY.¶

The IPSECKEY RR [RFC4025] defines the 'Algorithm Type' for specifying the PK Algorithm. Herein we are adding the EdDSA algorithm.¶

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

   TBD1 (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 clarify the text in the "Algorithm Type Field" subregistry of the "IPSECKEY Resource Record Parameters" [IANA-IPSECKEY] registry to explicitly state this is for "Public" keys:¶


Value  Description                                                      Reference

1    A DSA Public Key is present, in the format defined in [RFC2536]    [RFC4025]
2    A RSA Public Key is present, in the format defined in [RFC3110]    [RFC4025]
3    An ECDSA Public Key is present, in the format defined in [RFC6605] [RFC8005]

Futher, this document requests IANA to make the following addition to the "IPSECKEY Resource Record Parameters" [IANA-IPSECKEY] registry:¶

IPSECKEY:: This document defines the new IPSECKEY value TBD1 (suggested: 4) (Section 3) in the "Algorithm Type Field" subregistry of the "IPSECKEY Resource Record Parameters" registry.¶


   Value  Description         Reference

   TBD1 (suggested value 4)   [This]
          An EdDSA Public Key is present, in the format defined
          in [RFC8080]

6. References

6.1. Normative References

[RFC2119]: Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC4025]: Richardson, M., "A Method for Storing IPsec Keying Material in DNS", RFC 4025, DOI 10.17487/RFC4025, March 2005, <https://www.rfc-editor.org/info/rfc4025>.
[RFC8174]: Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.

6.2. Informative References

[IANA-IPSECKEY]: IANA, "IPSECKEY Resource Record Parameters", <https://www.iana.org/assignments/ipseckey-rr-parameters/ipseckey-rr-parameters.xhtml>.
[RFC8080]: Sury, O. and R. Edmonds, "Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSEC", RFC 8080, DOI 10.17487/RFC8080, February 2017, <https://www.rfc-editor.org/info/rfc8080>.

Appendix A. IPSECKEY EdDSA example

The following is an example of an IPSECKEY RR with an EdDSA public key base64 encode with no gateway:¶


   foo.example.com IN IPSECKEY
   (10 0 4 . 3WTXgUvpn1RlCXnm80gGY2LZ/ErUUEZtZ33IDi8yfhM= )

The associated EdDSA private key (in hex):¶


   c7be71a45cbf87785f639dc4fd1c82637c21b5e02488939976ece32b9268d0b7