<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2409 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2409.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC3174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3174.xml">
<!ENTITY RFC3526 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3526.xml">
<!ENTITY RFC4253 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4253.xml">
<!ENTITY RFC6194 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6194.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="no"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="std"
     docName="draft-baushke-ssh-dh-group-sha2-00"
     updates="4253"
     ipr="trust200902">
 <front>
   <!-- The abbreviated title is used in the page header - it is only necessary if the
        full title is longer than 39 characters -->

   <title abbrev="More MODP DH groups for SSH">More Modular Exponential (MODP)
   Diffie-Hellman Groups for SSH</title>
    <author initials="M. D." surname="Baushke" fullname="Mark D.
    Baushke">
      <organization>Juniper Networks, Inc.</organization>
      <address>
        <postal>
          <street>1133 Innovation Way</street>
          <city>Sunnyvale</city>
          <region>CA</region>
          <code>94089-1228</code>
          <country>US</country>
        </postal>
        <phone>+1 408 745 2952</phone>
        <email>mdb@juniper.net</email>
        <uri>http://www.juniper.net/</uri>
      </address>
    </author>
   <date year="2015" />

   <workgroup>Internet Engineering Task Force</workgroup>
   <abstract>
     <t>This document defines two added Modular Exponential (MODP)
     Groups for the Secure Shell (SSH) protocol. It also updates <xref
     target="RFC4253"/> by specifying new RECOMMENDED and new OPTIONAL
     Diffie-Hellman key exchange algorithms using SHA-2 hashes.</t>
   </abstract>
 </front>

 <middle>
   <section title="Overview and Rationale">
     <t>Secure Shell (SSH) is a common protocol for secure
     communication on the Internet. In <xref target="RFC4253"/>, SSH
     originally defined the Key Exchange Method Name
     diffie-hellman-group1-sha1 which used <xref target="RFC2409"/>
     Oakley Group 1 (a MODP group with 768 bits) and SHA1 <xref
     target="RFC3174"/>. Due to recent security concerns with SHA-1
     <xref target="RFC6194"/> and with MODP groups with less than 2048
     bits <xref target="NIST-SP-800-131Ar1"/> implementors and users
     request support for larger MODP group sizes with data integrity
     verification using the SHA-2 family of secure hash algorithms as
     well as MODP groups providing more security.</t>
     <t>Please send comments on this draft to ietf-ssh@NetBSD.org.</t>
   </section>

   <section title="Requirements Language">
     <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
     document are to be interpreted as described in <xref
     target="RFC2119"/>.</t>
   </section>

   <section title="Key Exchange Algorithms">
     <t>This memo adopts the style and conventions of
     <xref target="RFC4253"/> in specifying how the use of new
     data key exchange is indicated in SSH.
     </t>
     <figure anchor="figure.algs">
       <preamble>The following new key exchange algorithms are
       defined:</preamble>
       <artwork>
Key Exchange Method Name          Note
diffie-hellman-group1-sha1        NOT RECOMMENDED
diffie-hellman-group14-sha256     RECOMMENDED
diffie-hellman-group15-sha256     RECOMMENDED
diffie-hellman-group16-sha256     OPTIONAL
       </artwork>
     </figure>
     <t>The SHA-2 family of secure hash algorithms are defined in
     <xref target="FIPS-180-4"/>.
     </t>
     <t>The method of key exchange used for the name
     "diffie-hellman-group14-sha256" is the same as that for
     "diffie-hellman-group14-sha1" escept that the SHA2-256 hash
     algorith is used.</t>
     <t>The group15 and group16 names are the same as those specified
     in <xref target="RFC3526"/> as 3072-bit MODP Group 14 and
     4096-bit MODP Group 15.</t>
   </section>

   <section title="IANA Considerations">
     <t>This document augments the Key Exchange Method Names in
     <xref target="RFC4253"/>.</t>
     <figure anchor="figure.iana">
       <preamble>IANA is requested to update the SSH
       algorithm registry with the following entries:</preamble>
       <artwork>
Key Exchange Method Name       Reference   Note
diffie-hellman-group1-sha1     RFC4253     NOT RECOMMENDED
diffie-hellman-group14-sha256  This draft  RECOMMENDED
diffie-hellman-group15-sha256  This draft  RECOMMENDED
diffie-hellman-group16-sha256  This draft  OPTIONAL
       </artwork>
     </figure>
   </section>

   <section title="Security Considerations">
     <t>The security considerations of
     <xref target="RFC4253"/> apply to this
     document.
     </t>
     <t>The security considerations of
     <xref target="RFC3526"/> suggest that these
     MODP groups have security strengths given in this table.
     </t>
     <figure anchor="figure.strength">
       <preamble>Group modulus security strength estimates</preamble>
       <artwork>
+--------+----------+---------------------+---------------------+
| Group  | Modulus  | Strength Estimate 1 | Strength Estimate 2 |
|        |          +----------+----------+----------+----------+
|        |          |          | exponent |          | exponent |
|        |          | in bits  | size     | in bits  | size     |
+--------+----------+----------+----------+----------+----------+
|  14    | 2048-bit |      110 |     220- |      160 |     320- |
|  15    | 3072-bit |      130 |     260- |      210 |     420- |
|  16    | 4096-bit |      150 |     300- |      240 |     480- |
+--------+----------+---------------------+---------------------+
       </artwork>
     </figure>
     <t>Many users seem to be interested in the perceived safety of
     using the SHA2-based algorithms for hashing.</t>
   </section>

 </middle>

 <back>

   <references title="Normative References">
     &RFC2119;

     &RFC3526;

     &RFC4253;

     <reference
         anchor="FIPS-180-4"
         target="http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">
       <front>
         <title>Secure Hash Standard (SHS)</title>
         <author>
           <organization>National Institute of Standards and Technology
           </organization>
         </author>
         <date month="August" year="2015"/>
       </front>
       <seriesInfo name="FIPS PUB" value="180-4"/>
     </reference>

   </references>

   <references title="Informative References">
     <!-- Here we use entities that we defined at the beginning. -->

     &RFC2409;

     &RFC3174;

     &RFC6194;

     <reference
         anchor="NIST-SP-800-131Ar1"
         target="http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar1.pdf">
       <front>
         <title>Transitions: Recommendation for the Transitioning of
         the Use of Cryptographic Algorithms and Key Lengths</title>
         <author surname="Barker" fullname="Elaine Barker"/>
         <author surname="Roginsky" fullname="Allen Roginsky"/>
         <date month="November" year="2015"/>
       </front>
       <seriesInfo
           name="NIST Special Publication" value="800-131A Revision 1"/>
     </reference>

   </references>

   <!-- Change Log

v00 2012-10-15  MDB   Initial version

   -->
 </back>
</rfc>
