Internet-Draft IPSECKEY EdDSA December 2022
Moskowitz, et al. Expires 1 July 2023 [Page]
Workgroup:
IPSECME
Internet-Draft:
draft-moskowitz-ipsecme-ipseckey-eddsa-08
Published:
Intended Status:
Standards Track
Expires:
Authors:
R. Moskowitz
HTT Consulting
T. Kivinen
M. Richardson
Sandelman

EdDSA value for IPSECKEY

Abstract

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 1 July 2023.

Table of Contents

1. Introduction

IPSECKEY [RFC4025) is a resource record (RR) for the Domain Name System (DNS) that is used to store public keys for use in IP security (IPsec) systems. The IPSECKEY RR relies on the IPSECKEY Algorithm Type Field registry [IANA-IPSECKEY] to enumerate the permissible formats for the public keys.

This document adds support for Edwards-Curve Digital Security Algorithm (EdDSA) public keys in the format defined in [RFC8080] to the IPSECKEY RR.

2. IPSECKEY support for EdDSA

When using the EdDSA public key in the IPSECKEY RR, then the value TBD1 is used as an algorithm and the public key is formatted as specified in Section 3 of the "Edwards-Curve Digital Security Algorithm (EdDSA) for DNSSEC" ([RFC8080]) document.


Value  Description                Format description    Reference

TBD1   An EdDSA Public Key        [RFC8080], Sec. 3     [ThisRFC]

3. IANA Considerations

3.1. IANA IPSECKEY Registry Update

3.1.1. Reformat Algorithm Type Field Subregistry

This document requests IANA to add a new field "Format description" to the "Algorithm Type Field" subregistry of the "IPSECKEY Resource Record Parameters" [IANA-IPSECKEY]. Also, this document requests IANA to update the "Description" field in existing entries of that registry to explicitly state that is for "Public" keys:


Value  Description                Format description    Reference
0      No key is present                                [RFC4025]
1      A DSA Public Key           [RFC2536], Sec. 2     [RFC4025]
2      A RSA Public Key           [RFC3110], Sec. 2     [RFC4025]
3      An ECDSA Public Key        [RFC6605], Sec. 4     [RFC8005]

IANA is requested to update the reference of that registry by adding the RFC number to be assigned to this document.

3.1.2. Add to Algorithm Type Field Subregistry

Further, 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 2) in the "Algorithm Type Field" subregistry of the "IPSECKEY Resource Record Parameters" registry.

Value  Description                Format description    Reference

TBD1   An EdDSA Public Key        [RFC8080], Sec. 3     [ThisRFC]

4. Security Considerations

No new issues than [RFC4025] describes.

5. References

5.1. Normative References

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

5.2. Informative References

[RFC4025]
Richardson, M. and RFC Publisher, "A Method for Storing IPsec Keying Material in DNS", RFC 4025, DOI 10.17487/RFC4025, , <https://www.rfc-editor.org/info/rfc4025>.

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

Acknowledgments

Thanks to Security Area director, Paul Wouters, for initial review. And Security Area director, Roman Danyliw, for final reviews and draft shepherding.

Authors' Addresses

Robert Moskowitz
HTT Consulting
Oak Park, MI 48237
United States of America
Tero Kivinen
Michael C. Richardson
Sandelman Software Works