Deprecating RC4 in all IETF Protocols
draft-ietf-curdle-rc4-die-die-die-02

Document Type Active Internet-Draft (curdle WG)
Last updated 2017-08-16 (latest revision 2017-08-08)
Replaces draft-luis140219-curdle-rc4-die-die-die
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force (IETF)                         L. Camara
Internet-Draft                                            August 8, 2017
Obsoletes: 4345
Updates: 3501, 4253, 6649, 6733
Intended Status: Best Current Practice
Expires: February 9, 2018

                 Deprecating RC4 in all IETF Protocols
                  draft-ietf-curdle-rc4-die-die-die-02

[[RFC-Editor: Please replace all instances of xxxx in this document with
  the RFC number of draft-ietf-curdle-des-des-des-die-die-die.]]

[[RFC-Editor: please replace the second character of my surname by
U+00E2 when publishing as RFC in the header and in all pages.
Non-ASCII characters are allowed in RFCs as per RFC 7997.]]

Abstract

   RC4 is extremely weak as shown by RFC 6649 and RFC 7457, is
   prohibited in TLS by RFC 7465, is prohibited in Kerberos by RFC xxxx
   and it needs to be prohibited in all IETF protocols. This document
   obsoletes RFC 4345 "Improved Arcfour Modes for the Secure Shell (SSH)
   Transport Layer Protocol" (note Arcfour and RC4 are synonymous).
   RFC 3501, RFC 4253, RFC 6649 and RFC 6733 are updated to note the
   deprecation of RC4 in all IETF protocols.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 http://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 January 4, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Camara                  Expires February 9, 2018                [Page 1]
Internet-Draft      Deprecating RC4 in all Protocols         August 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
   described in the Simplified BSD License.

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. Why obsolete RFC 4345 . . . . . . . . . . . . . . . . . . . . .  2
   3. Updates to RFC 3501 . . . . . . . . . . . . . . . . . . . . . .  3
   4. Updates to RFC 4253 . . . . . . . . . . . . . . . . . . . . . .  3
   5. Updates to RFC 6649 . . . . . . . . . . . . . . . . . . . . . .  4
   6. Updates to RFC 6733 . . . . . . . . . . . . . . . . . . . . . .  4
   7. Action to be taken  . . . . . . . . . . . . . . . . . . . . . .  5
   8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  5
   9. Security Considerations . . . . . . . . . . . . . . . . . . . .  5
   10. Acknowlegdements . . . . . . . . . . . . . . . . . . . . . . .  5
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   11.1. Normative References . . . . . . . . . . . . . . . . . . . .  6
   11.2. Informative References . . . . . . . . . . . . . . . . . . .  6
   12. Author's Address . . . . . . . . . . . . . . . . . . . . . . .  7
   Appendix A. Changelog  . . . . . . . . . . . . . . . . . . . . . .  8

1. Introduction

   RC4 is extremely weak [RFC6649] [RFC7457] [RFCxxxx] and this document
   deprecates its use in all IETF protocols, including Kerberos and
   Secure Shell (SSH). The reasons for obsoleting RFC 4345 are discussed
   in Section 2. The updates to RFC 3501, RFC 4253, RFC 6649 and RFC
   RFC 6733 and the reasons for doing them are specified in sections 3,
   4, 5 and 6, respectively.

   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
   BCP 14 [RFC2119, RFC8174].

2. Why obsolete RFC 4345

   RFC 4345 defines the "arcfour-128" and "arcfour-256" modes for Secure
   Shell (SSH), and is moved to Historic as RC4 is extremely
   weak [RFC6649, RFC7457, RFCxxxx] and there is research that is at
Show full document text