Prohibiting RC4 in all IETF Protocols
draft-luis140219-curdle-rc4-die-die-die-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-06-16
Replaced by draft-ietf-curdle-rc4-die-die-die
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force (IETF)                         L. Camara
Internet-Draft                                             June 16, 2017
Obsoletes: 3078, 4345, 4757, 6229
Updates: 2118, 3961, 4120, 4253, 6150, 6649, 7457, 7905, xxxx
Intended Status: Best Current Practice
Expires: December 18, 2017

                 Prohibiting RC4 in all IETF Protocols
               draft-luis140219-curdle-rc4-die-die-die-00

[[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, nnn with
  its BCP number, MMMMMMMM with the month of its publishing as RFC, and
  YYYY with the year of its publishing as RFC.]]

[[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. Documents that
   provide technology that can only use RC4 are obsoleted by this
   document, so this document obsoletes and moves to Historic RFC 3078
   "Microsoft Point-to-Point Encryption (MPPE) Protocol" (only supports
   RC4), RFC 4345 "Improved Arcfour Modes for the Secure Shell (SSH)
   Transport Layer Protocol" (note Arcfour and RC4 are synonymous),
   RFC 4757 "The RC4-HMAC Kerberos Encryption Types Used by Microsoft
   Windows" (only supports RC4) and RFC 6229 "Test Vectors for the
   Stream Cipher RC4" (provides test vectors for historic cryptography).
   RFC 2118, RFC 3961, RFC 4120, RFC 4253, RFC 6150, RFC 6649, RFC 7457,
   RFC 7905 and RFC xxxx are updated to note the deprecation of RC4 in
   all IETF protocols. (Please do not confuse RFC 4757 with RFC 7457.)

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 December 18, 2017.

Camara                 Expires December 18, 2017                [Page 1]
Internet-Draft      Prohibiting RC4 in all Protocols           June 2017

Copyright Notice

   Copyright (c) 2017 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
   (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 3078, RFC 4345, RFC 4757 and RFC 6229  . . . .  3
   3. Updates to RFC 2118 . . . . . . . . . . . . . . . . . . . . . .  3
   4. Updates to RFC 3961 . . . . . . . . . . . . . . . . . . . . . .  3
   5. Updates to RFC 4120 . . . . . . . . . . . . . . . . . . . . . .  3
   6. Updates to RFC 4253 . . . . . . . . . . . . . . . . . . . . . .  3
   7. Updates to RFC 6150 . . . . . . . . . . . . . . . . . . . . . .  4
   8. Updates to RFC 6649 . . . . . . . . . . . . . . . . . . . . . .  4
   9. Updates to RFC 7457 . . . . . . . . . . . . . . . . . . . . . .  5
   10. Updates to RFC 7465  . . . . . . . . . . . . . . . . . . . . .  5
   11. Updates to RFC xxxx  . . . . . . . . . . . . . . . . . . . . .  5
   12. Action to be taken . . . . . . . . . . . . . . . . . . . . . .  6
   13. IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  6
   14. Security Considerations  . . . . . . . . . . . . . . . . . . .  6
   16. References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   16.1. Normative References . . . . . . . . . . . . . . . . . . . .  7
   16.2. Informative References . . . . . . . . . . . . . . . . . . .  7
   17. Author's Address . . . . . . . . . . . . . . . . . . . . . . .  8
   Appendix A. Status of Updated Documents as of 2017-06-16 . . . . .  8
   Appendix B. Changelog  . . . . . . . . . . . . . . . . . . . . . . 10
Show full document text