draft-ietf-ipsecme-eddsa-03.txt   draft-ietf-ipsecme-eddsa-04.txt 
IPSecME Working Group Y. Nir IPSecME Working Group Y. Nir
Internet-Draft Check Point Internet-Draft Dell EMC
Intended status: Standards Track April 15, 2017 Intended status: Standards Track October 26, 2017
Expires: October 17, 2017 Expires: April 29, 2018
Using Edwards-curve Digital Signature Algorithm (EdDSA) in the Internet Using Edwards-curve Digital Signature Algorithm (EdDSA) in the Internet
Key Exchange (IKEv2) Key Exchange (IKEv2)
draft-ietf-ipsecme-eddsa-03 draft-ietf-ipsecme-eddsa-04
Abstract Abstract
This document describes the use of the Edwards-curve digital This document describes the use of the Edwards-curve digital
signature algorithm in the IKEv2 protocol. signature algorithm in the IKEv2 protocol.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 17, 2017. This Internet-Draft will expire on April 29, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 2, line 46 skipping to change at page 2, line 46
be-signed message is available at once. See section 8.5 or RFC 8032 be-signed message is available at once. See section 8.5 or RFC 8032
for that recommendation. for that recommendation.
EdDSA defines the binary format of the signatures that should be used EdDSA defines the binary format of the signatures that should be used
in the "Signature Value" field of the Authentication Data Format in in the "Signature Value" field of the Authentication Data Format in
section 3. The CURDLE PKIX document ([I.D-curdle-pkix]) defines the section 3. The CURDLE PKIX document ([I.D-curdle-pkix]) defines the
object identifiers (OIDs) for these signature methods. For object identifiers (OIDs) for these signature methods. For
convenience, these OIDs are repeated in Appendix A. convenience, these OIDs are repeated in Appendix A.
In order to signal within IKE that no hashing needs to be done, we In order to signal within IKE that no hashing needs to be done, we
define a new value has in the SIGNATURE_HASH_ALGORITHMS notification, define a new value in the SIGNATURE_HASH_ALGORITHMS notification, one
one that indicates that no hashing is performed. that indicates that no hashing is performed.
1.1. Conventions Used in This Document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. The "Identity" Hash Identifier 2. The "Identity" Hash Identifier
This document defines a new value called "Identity" (value is 5) in This document defines a new value called "Identity" (value is 5) in
the hash algorithm registry for use in the SIGNATURE_HASH_ALGORITHMS the hash algorithm registry for use in the SIGNATURE_HASH_ALGORITHMS
notification. Inserting this new value into the notification notification. Inserting this new value into the notification
indicates that the receiver supports at least one signature algorithm indicates that the receiver supports at least one signature algorithm
that accepts arbitrary-sized messages such as Ed25519 and Ed448. that accepts arbitrary-sized messages such as Ed25519 and Ed448.
Ed25519 and Ed448 are only defined with the Identity hash, and MUST Ed25519 and Ed448 are only defined with the Identity hash, and MUST
NOT be sent to a receiver that has not indicated support for the NOT be sent to a receiver that has not indicated support for the
"Identity" hash. "Identity" hash.
The pre-hashed versions of Ed25519 and Ed448 (Ed25519ph and Ed448ph The pre-hashed versions of Ed25519 and Ed448 (Ed25519ph and Ed448ph
respectively) SHOULD NOT be used in IKE. respectively) MUST NOT be used in IKE.
3. Security Considerations 3. Security Considerations
The new "Identity" value is needed only for signature algorithms that The new "Identity" value is needed only for signature algorithms that
accept an arbitrary-sized input. It MUST NOT be used if none of the accept an arbitrary-sized input. It MUST NOT be used if none of the
supported and configured algorithms have this property. On the other supported and configured algorithms have this property. On the other
hand there is no good reason to pre-hash the inputs where the hand there is no good reason to pre-hash the inputs where the
signature algorithm has that property. For this reason signature algorithm has that property. For this reason
implementations MUST have the "Identity" value in the implementations MUST have the "Identity" value in the
SIGNATURE_HASH_ALGORITHMS notification when EdDSA is supported and SIGNATURE_HASH_ALGORITHMS notification when EdDSA is supported and
skipping to change at page 4, line 8 skipping to change at page 4, line 8
reference. reference.
Upon publication of this document IANA is requested to update the Upon publication of this document IANA is requested to update the
entry with this document as reference. entry with this document as reference.
5. Normative References 5. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. [RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T.
Kivinen, "Internet Key Exchange Protocol Version 2 Kivinen, "Internet Key Exchange Protocol Version 2
(IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October (IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October
2014, <http://www.rfc-editor.org/info/rfc7296>. 2014, <https://www.rfc-editor.org/info/rfc7296>.
[RFC7427] Kivinen, T. and J. Snyder, "Signature Authentication in [RFC7427] Kivinen, T. and J. Snyder, "Signature Authentication in
the Internet Key Exchange Version 2 (IKEv2)", RFC 7427, the Internet Key Exchange Version 2 (IKEv2)", RFC 7427,
DOI 10.17487/RFC7427, January 2015, DOI 10.17487/RFC7427, January 2015,
<http://www.rfc-editor.org/info/rfc7427>. <https://www.rfc-editor.org/info/rfc7427>.
[RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital [RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital
Signature Algorithm (EdDSA)", RFC 8032, Signature Algorithm (EdDSA)", RFC 8032,
DOI 10.17487/RFC8032, January 2017, DOI 10.17487/RFC8032, January 2017,
<http://www.rfc-editor.org/info/rfc8032>. <https://www.rfc-editor.org/info/rfc8032>.
[I.D-curdle-pkix] [I.D-curdle-pkix]
Josefsson, S. and J. Schaad, "Algorithm Identifiers for Josefsson, S. and J. Schaad, "Algorithm Identifiers for
Ed25519, Ed25519ph, Ed448, Ed448ph, X25519 and X448 for Ed25519, Ed25519ph, Ed448, Ed448ph, X25519 and X448 for
use in the Internet X.509 Public Key Infrastructure", use in the Internet X.509 Public Key Infrastructure",
March 2017, <https://tools.ietf.org/html/draft-ietf- September 2017,
curdle-pkix-04>. <https://tools.ietf.org/html/draft-ietf-curdle-pkix-06>.
Appendix A. ASN.1 Objects Appendix A. ASN.1 Objects
The normative reference for the ASN.1 objects for Ed25519 and Ed448 The normative reference for the ASN.1 objects for Ed25519 and Ed448
is in [I.D-curdle-pkix]. They are repeated below for convenience. is in [I.D-curdle-pkix]. They are repeated below for convenience.
A.1. ASN.1 Object for Ed25519 A.1. ASN.1 Object for Ed25519
id-Ed25519 OBJECT IDENTIFIER ::= { 1.3.101.112 } id-Ed25519 OBJECT IDENTIFIER ::= { 1.3.101.112 }
skipping to change at page 5, line 29 skipping to change at page 5, line 29
id-Ed448 OBJECT IDENTIFIER ::= { 1.3.101.113 } id-Ed448 OBJECT IDENTIFIER ::= { 1.3.101.113 }
Parameters are absent. Length is 7 bytes. Parameters are absent. Length is 7 bytes.
Binary encoding: 3005 0603 2B65 71 Binary encoding: 3005 0603 2B65 71
Author's Address Author's Address
Yoav Nir Yoav Nir
Check Point Software Technologies Ltd. Dell EMC
5 Hasolelim st. 9 Andrei Sakharov St
Tel Aviv 6789735 Haifa 3190500
Israel Israel
EMail: ynir.ietf@gmail.com EMail: ynir.ietf@gmail.com
 End of changes. 13 change blocks. 
19 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/