draft-ietf-curdle-ssh-modp-dh-sha2-00.txt   draft-ietf-curdle-ssh-modp-dh-sha2-01.txt 
Internet Engineering Task Force M. Baushke Internet Engineering Task Force M. Baushke
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Updates: 4253, 4432, 4462 (if approved) September 11, 2016 Updates: 4253, 4432, 4462 (if approved) September 13, 2016
Intended status: Standards Track Intended status: Standards Track
Expires: March 15, 2017 Expires: March 17, 2017
More Modular Exponential (MODP) Diffie-Hellman (DH) Key Exchange (KEX) More Modular Exponential (MODP) Diffie-Hellman (DH) Key Exchange (KEX)
Groups for Secure Shell (SSH) Groups for Secure Shell (SSH)
draft-ietf-curdle-ssh-modp-dh-sha2-00 draft-ietf-curdle-ssh-modp-dh-sha2-01
Abstract Abstract
This document defines added Modular Exponential (MODP) Groups for the This document defines added Modular Exponential (MODP) Groups for the
Secure Shell (SSH) protocol using SHA-2 hashes. Secure Shell (SSH) protocol using SHA-2 hashes.
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.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 http://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 March 15, 2017. This Internet-Draft will expire on March 17, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 (http://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
skipping to change at page 4, line 5 skipping to change at page 3, line 43
[RFC3526] 3071-bit MODP Group 15, 4096-bit MODP Group 16, 6144-bit [RFC3526] 3071-bit MODP Group 15, 4096-bit MODP Group 16, 6144-bit
MODP Group 17, and 8192-bit MODP Group 18. MODP Group 17, and 8192-bit MODP Group 18.
The SHA2-512 algorithm is to be used when "sha512" is specified as a The SHA2-512 algorithm is to be used when "sha512" is specified as a
part of the key exchange method name. part of the key exchange method name.
4. IANA Considerations 4. IANA Considerations
This document augments the Key Exchange Method Names in [RFC4253]. This document augments the Key Exchange Method Names in [RFC4253].
IANA is requested to update the SSH algorithm registry with the IANA is requested to add to the Key Exchange Method Names algorithm
following entries: registry with the following entries:
Key Exchange Method Name Reference Note
diffie-hellman-group14-sha256 This Draft MAY
diffie-hellman-group15-sha512 This Draft MAY
diffie-hellman-group16-sha512 This Draft MAY
diffie-hellman-group17-sha512 This Draft MAY
diffie-hellman-group18-sha512 This Draft MAY
gss-group14-sha256-* This Draft MAY
gss-group15-sha512-* This Draft MAY
gss-group16-sha512-* This Draft MAY
gss-group17-sha512-* This Draft MAY
gss-group18-sha512-* This Draft MAY
Figure 2 Key Exchange Method Name Reference
----------------------------- ----------
diffie-hellman-group14-sha256 This Draft
diffie-hellman-group15-sha512 This Draft
diffie-hellman-group16-sha512 This Draft
diffie-hellman-group17-sha512 This Draft
diffie-hellman-group18-sha512 This Draft
gss-group14-sha256-* This Draft
gss-group15-sha512-* This Draft
gss-group16-sha512-* This Draft
gss-group17-sha512-* This Draft
gss-group18-sha512-* This Draft
The Note in the above table is not an implementation suggestion/ [TO BE REMOVED: This registration should take place at the following
recommendation for the listed key exchange method. It is up to the location: <http://www.iana.org/assignments/ssh-parameters/ssh-
end-user as to what algorithms they choose to be able to negotiate. parameters.xhtml#ssh-parameters-16>]
This RFC is intended to provide IANA defined names for these groups
for interoperability.
5. Security Considerations 5. Security Considerations
The security considerations of [RFC4253] apply to this document. The security considerations of [RFC4253] apply to this document.
The security considerations of [RFC3526] suggest that these MODP The security considerations of [RFC3526] suggest that these MODP
groups have security strengths given in this table. They are based groups have security strengths given in this table. They are based
on [RFC3766] Determining Strengths For Public Keys Used For on [RFC3766] Determining Strengths For Public Keys Used For
Exchanging Symmetric Keys. Exchanging Symmetric Keys.
skipping to change at page 4, line 52 skipping to change at page 4, line 46
| | | | exponent | | exponent | | | | | exponent | | exponent |
| | | in bits | size | in bits | size | | | | in bits | size | in bits | size |
+--------+----------+----------+----------+----------+----------+ +--------+----------+----------+----------+----------+----------+
| 14 | 2048-bit | 110 | 220- | 160 | 320- | | 14 | 2048-bit | 110 | 220- | 160 | 320- |
| 15 | 3072-bit | 130 | 260- | 210 | 420- | | 15 | 3072-bit | 130 | 260- | 210 | 420- |
| 16 | 4096-bit | 150 | 300- | 240 | 480- | | 16 | 4096-bit | 150 | 300- | 240 | 480- |
| 17 | 6144-bit | 170 | 340- | 270 | 540- | | 17 | 6144-bit | 170 | 340- | 270 | 540- |
| 18 | 8192-bit | 190 | 380- | 310 | 620- | | 18 | 8192-bit | 190 | 380- | 310 | 620- |
+--------+----------+---------------------+---------------------+ +--------+----------+---------------------+---------------------+
Figure 3 Figure 2
Many users seem to be interested in the perceived safety of using Many users seem to be interested in the perceived safety of using
larger MODP groups and hashing with SHA2-based algorithms. larger MODP groups and hashing with SHA2-based algorithms.
6. References 6. References
6.1. Normative References 6.1. Normative References
[FIPS-180-4] [FIPS-180-4]
National Institute of Standards and Technology, "Secure National Institute of Standards and Technology, "Secure
 End of changes. 8 change blocks. 
25 lines changed or deleted 22 lines changed or added

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