--- 1/draft-ietf-curdle-ssh-ed25519-ed448-07.txt	2019-01-16 23:13:11.067382421 -0800
+++ 2/draft-ietf-curdle-ssh-ed25519-ed448-08.txt	2019-01-16 23:13:11.083382807 -0800
@@ -1,20 +1,20 @@
 
 Internet Engineering Task Force                                B. Harris
 Internet-Draft
 Intended status: Standards Track                           L. Velvindron
-Expires: April 18, 2019                                    cyberstorm.mu
-                                                        October 15, 2018
+Expires: July 20, 2019                                     cyberstorm.mu
+                                                        January 16, 2019
 
    Ed25519 and Ed448 public key algorithms for the Secure Shell (SSH)
                                 protocol
-                 draft-ietf-curdle-ssh-ed25519-ed448-07
+                 draft-ietf-curdle-ssh-ed25519-ed448-08
 
 Abstract
 
    This document describes the use of the Ed25519 and Ed448 digital
    signature algorithm in the Secure Shell (SSH) protocol.
 
 Status of This Memo
 
    This Internet-Draft is submitted in full conformance with the
    provisions of BCP 78 and BCP 79.
@@ -22,25 +22,25 @@
    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 April 18, 2019.
+   This Internet-Draft will expire on July 20, 2019.
 
 Copyright Notice
 
-   Copyright (c) 2018 IETF Trust and the persons identified as the
+   Copyright (c) 2019 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 Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
@@ -62,33 +62,41 @@
 
    [TO BE REMOVED: Please send comments on this draft to
    curdle@ietf.org.]
 
 2.  Conventions Used in This Document
 
    The descriptions of key and signature formats use the notation
    introduced in [RFC4251], Section 3 [RFC4251] and the string data type
    from [RFC4251], Section 5 [RFC4251].
 
+2.1.  Requirements Language
+
+   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 RFC 2119 [RFC2119].
+
 3.  Public Key Algorithm
 
    This document describes a public key algorithm for use with SSH in
    accordance with [RFC4253], Section 6.6 [RFC4253].  The name of the
    algorithm is "ssh-ed25519".  This algorithm only supports signing and
    not encryption.
 
    Additionally, this document describes another public key algorithm.
    The name of the algorithm is "ssh-ed448".  This algorithm only
    supports signing and not encryption.
 
-4.  Public Key Format
+   Standard implementations of SSH SHOULD implement these signature
+   algorithms.
 
+4.  Public Key Format
    The "ssh-ed25519" key format has the following encoding:
 
    string    "ssh-ed25519"
    string    key
 
    Here 'key' is the 32-octet public key described by [RFC8032],
    Section 5.1.5 [RFC8032].
 
    The "ssh-ed448" key format has the following encoding:
 
@@ -195,20 +203,25 @@
 11.  Acknowledgements
 
    The OpenSSH implementation of Ed25519 in SSH was written by Markus
    Friedl.  We are also grateful to Mark Baushke and Daniel Migault for
    their comments.
 
 12.  References
 
 12.1.  Normative References
 
+   [RFC2119]  Bradner, S., "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>.
+
    [RFC4250]  Lehtinen, S. and C. Lonvick, Ed., "The Secure Shell (SSH)
               Protocol Assigned Numbers", RFC 4250,
               DOI 10.17487/RFC4250, January 2006,
               <https://www.rfc-editor.org/info/rfc4250>.
 
    [RFC4251]  Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
               Protocol Architecture", RFC 4251, DOI 10.17487/RFC4251,
               January 2006, <https://www.rfc-editor.org/info/rfc4251>.
 
    [RFC4253]  Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)