--- 1/draft-ietf-curdle-rc4-die-die-die-14.txt	2019-01-16 23:13:19.891595446 -0800
+++ 2/draft-ietf-curdle-rc4-die-die-die-15.txt	2019-01-16 23:13:19.903595737 -0800
@@ -1,19 +1,19 @@
 
 Internet Engineering Task Force                                L. Camara
 Internet-Draft
 Obsoletes: 4345 (if approved)                              L. Velvindron
 Intended status: Best Current Practice                     cyberstorm.mu
-Expires: June 28, 2019                                 December 25, 2018
+Expires: July 20, 2019                                  January 16, 2019
 
                  Deprecating RC4 in Secure Shell (SSH)
-                  draft-ietf-curdle-rc4-die-die-die-14
+                  draft-ietf-curdle-rc4-die-die-die-15
 
 Abstract
 
    This document deprecates RC4 in Secure Shell (SSH).  Therefore, this
    document formally obsoletes and moves to Historic RFC4345.
 
 Status of This Memo
 
    This Internet-Draft is submitted in full conformance with the
    provisions of BCP 78 and BCP 79.
@@ -21,25 +21,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 June 28, 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
@@ -56,22 +56,22 @@
    6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
      6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
      6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4
 
 1.  Introduction
 
    The usage of RC4 suites ( also designated as arcfour ) for SSH are
    specified in [RFC4253] and [RFC4345].  [RFC4253] specifies the
    allocation of the "arcfour" cipher for SSH.  [RFC4345] specifies and
-   allocates the the "arcfour-128" and "arcfour-256" ciphers for SSH.
-   RC4 encryption has known weaknesses [RFC7465]
+   allocates the "arcfour-128" and "arcfour-256" ciphers for SSH.  RC4
+   encryption has known weaknesses [RFC7465]
    [I-D.ietf-curdle-des-des-des-die-die-die], and the deprecation
    process should be begun for their use in Secure Shell (SSH)
    [RFC4253].  Accordingly, [RFC4253] is updated to note the deprecation
    of the RC4 ciphers and [RFC4345] is moved to Historic as all ciphers
    it specifies MUST NOT be used.
 
 1.1.  Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this