BCP 218, RFC 8429 on Deprecate Triple-DES (3DES) and RC4 in Kerberos
rfc-editor@rfc-editor.org Wed, 31 October 2018 21:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C83129C6A; Wed, 31 Oct 2018 14:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wGtl5v-gfeKR; Wed, 31 Oct 2018 14:14:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05B05130DD4; Wed, 31 Oct 2018 14:14:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 313ABB80581; Wed, 31 Oct 2018 14:14:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 218, RFC 8429 on Deprecate Triple-DES (3DES) and RC4 in Kerberos
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181031211442.313ABB80581@rfc-editor.org>
Date: Wed, 31 Oct 2018 14:14:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/9VfIhmiAb4lhJuDaKRVXHJ2BlJc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2018 21:14:53 -0000
A new Request for Comments is now available in online RFC libraries. BCP 218 RFC 8429 Title: Deprecate Triple-DES (3DES) and RC4 in Kerberos Author: B. Kaduk, M. Short Status: Best Current Practice Stream: IETF Date: October 2018 Mailbox: kaduk@mit.edu, michikos@microsoft.com Pages: 10 Characters: 22340 Updates: RFC 3961, RFC 4120 See Also: BCP 218 I-D Tag: draft-ietf-curdle-des-des-des-die-die-die-05.txt URL: https://www.rfc-editor.org/info/rfc8429 DOI: 10.17487/RFC8429 The triple-DES (3DES) and RC4 encryption types are steadily weakening in cryptographic strength, and the deprecation process should begin for their use in Kerberos. Accordingly, RFC 4757 has been moved to Historic status, as none of the encryption types it specifies should be used, and RFC 3961 has been updated to note the deprecation of the triple-DES encryption types. RFC 4120 is likewise updated to remove the recommendation to implement triple-DES encryption and checksum types. This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF. BCP: This document specifies an Internet Best Current Practice for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC