Tech-invite  3GPPspace  IETFspace
96  95  94  93  92  91  90  89  88  87  86  85  84  83  82  81  80  79  78  77  76  75  74  73  72  71  70  69  68  67  66  65  64  63  62  61  60  59  58  57  56  55  54  53  52  51  50  49  48  47  46  45  44  43  42  41  40  39  38  37  36  35  34  33  32  31  30  29  28  27  26  25  24  23  22  21  20  19  18  17  16  15  14  13  12  11  10  09  08  07  06  05  04  03  02  01  00 
in Index   Prev   Next

RFC 9295

Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm Identifiers

Pages: ~5
IETF/sec/lamps/draft-ietf-lamps-8410-ku-clarifications-02
Proposed Standard
Updates:  8410 

 Top   ToC   RFCv3-9295
S. Turner
sn3rd
S. Josefsson
SJD AB
D. McCarney
Square Inc.
T. Ito
SECOM CO., LTD.
September 2022

Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm Identifiers

Abstract

This document updates RFC 8410 to clarify existing semantics, and specify missing semantics, for key usage bits when used in certificates that support the Ed25519, Ed448, X25519, and X448 Elliptic Curve Cryptography algorithms.

Status of This Memo

This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc9295.

Copyright Notice

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.
 Top   ToC   RFCv3-9295

Table of Contents

 Top   ToC   RFCv3-9295

1.  Introduction

[RFC 8410] specifies the syntax and semantics for the Subject Public Key Information field in certificates that support Ed25519, Ed448, X25519, and X448 Elliptic Curve Cryptography (ECC) algorithms. As part of these semantics, it defines what combinations are permissible for the values of the keyUsage extension [RFC 5280]. [RFC 8410] did not define what values are not permissible, nor did it refer to keyEncipherment or dataEncipherment. [Err5696] has also been submitted to clarify that keyCertSign is always set in certification authority certificates. To address these changes, this document replaces Section 5 of RFC 8410 with Section 3.
 Top   ToC   RFCv3-9295

2.  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 [RFC 2119] [RFC 8174] when, and only when, they appear in all capitals, as shown here.
 Top   ToC   RFCv3-9295

3.  New Section 5 for RFC 8410

The intended application for the key is indicated in the keyUsage certificate extension.
If the keyUsage extension is present in a certificate that indicates id-X25519 or id-X448 in SubjectPublicKeyInfo, then the following MUST be present: 
  keyAgreement
One of the following MAY also be present: 
  encipherOnly
  decipherOnly
and any of the following MUST NOT be present: 
  digitalSignature
  nonRepudiation
  keyEncipherment
  dataEncipherment
  keyCertSign
  cRLSign
If the keyUsage extension is present in an end-entity certificate that indicates id-Ed25519 or id-Ed448 in SubjectPublicKeyInfo, then the keyUsage extension MUST contain at least one of the following: 
  nonRepudiation
  digitalSignature
  cRLSign
and any of the following MUST NOT be present: 
  keyEncipherment
  dataEncipherment
  keyAgreement
  keyCertSign
  encipherOnly
  decipherOnly
If the keyUsage extension is present in a CRL issuer certificate that indicates id-Ed25519 or id-Ed448 in SubjectPublicKeyInfo, then the keyUsage extension MUST contain: 
  cRLSign
and zero or more of the following: 
  nonRepudiation
  digitalSignature
and any of the following MUST NOT be present: 
  keyEncipherment
  dataEncipherment
  keyAgreement
  encipherOnly
  decipherOnly
and if the CRL issuer is also a certification authority, then the keyUsage extension MUST also contain: 
  keyCertSign
If the keyUsage extension is present in a certification authority certificate that indicates id-Ed25519 or id-Ed448 in SubjectPublicKeyInfo, then the keyUsage extension MUST contain: 
  keyCertSign
and zero or more of the following: 
  nonRepudiation
  digitalSignature
  cRLSign
and any of the following MUST NOT be present: 
  keyEncipherment
  dataEncipherment
  keyAgreement
  encipherOnly
  decipherOnly
 Top   ToC   RFCv3-9295

4.  Security Considerations

This document introduces no new security considerations beyond those found in [RFC 8410].
 Top   ToC   RFCv3-9295

5.  IANA Considerations

This document has no IANA actions.
 Top   ToC   RFCv3-9295

6.  References

6.1.  Normative References

[RFC2119]
S. Bradner, "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>.
[RFC5280]
D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008,
<https://www.rfc-editor.org/info/rfc5280>.
[RFC8174]
B. Leiba, "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>.
[RFC8410]
S. Josefsson, and J. Schaad, "Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure", RFC 8410, DOI 10.17487/RFC8410, August 2018,
<https://www.rfc-editor.org/info/rfc8410>.

6.2.  Informative References

[Err5696]
RFC Errata, "Erratum ID 5696",
<https://www.rfc-editor.org/errata/eid5696>.
 Top   ToC   RFCv3-9295

Acknowledgments

We would like to thank Russ Housley, Mike Jenkins, and Corey Bonnell for their comments.
 Top   ToC   RFCv3-9295

Authors' Addresses

Sean Turner

sn3rd

Simon Josefsson

SJD AB

Daniel McCarney

Square Inc.

Tadahiko Ito

SECOM CO., LTD.
 Top   ToC