Reclassification of Suite B Documents to Historic Status
RFC 8423
| Document | Type |
RFC - Informational
(July 2018; Errata)
Was draft-housley-suite-b-to-historic (individual)
|
|
|---|---|---|---|
| Last updated | 2019-04-09 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Sean Turner | ||
| Shepherd write-up | Show (last changed 2018-02-15) | ||
| IESG | IESG state | RFC 8423 (Informational) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Eric Rescorla | ||
| IESG note |
Here is what I propose for an IESG note to clarify IESG review comments "Suite B algorithms are defined to support two minimum levels of security: 128 and 192 bits. It is believed that the Suite B algorithms continue to meet these security goals. The algorithm identifiers for all of the Suite B algorithms remain available for anyone that wants to use them." |
||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - No Actions Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) R. Housley
Request for Comments: 8423 Vigil Security
Category: Informational L. Zieglar
ISSN: 2070-1721 National Security Agency
July 2018
Reclassification of Suite B Documents to Historic Status
Abstract
This document reclassifies the RFCs related to the United States
National Security Agency (NSA) Suite B cryptographic algorithms as
Historic, and it discusses the reasons for doing so. This document
moves seven Informational RFCs to Historic status: RFCs 5759, 6239,
6318, 6379, 6380, 6403, and 6460. In addition, it moves three
obsolete Informational RFCs to Historic status: RFCs 4869, 5008, and
5430.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8423.
Housley & Zieglar Informational [Page 1]
RFC 8423 Suite B to Historic July 2018
Copyright Notice
Copyright (c) 2018 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
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The RFCs Related to Suite B . . . . . . . . . . . . . . . . . 3
4. Documents That Reference the Suite-B-Related RFCs . . . . . . 3
4.1. Documents That Reference RFC 4869 . . . . . . . . . . . . 4
4.2. Documents That Reference RFC 5759 . . . . . . . . . . . . 4
4.3. Documents That Reference RFC 6379 . . . . . . . . . . . . 4
4.4. Documents That Reference RFC 6403 . . . . . . . . . . . . 4
4.5. Documents That Reference RFC 6460 . . . . . . . . . . . . 5
5. Impact of Reclassifying the Suite-B-Related RFCs to Historic 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Several RFCs profile security protocols for use with the National
Security Agency (NSA) Suite B Cryptography. Suite B is no longer
supported by NSA, and the web pages that specify the cryptographic
algorithms are no longer available.
In July 2015, NSA published the Committee for National Security
Systems Advisory Memorandum 02-15 as the first step in replacing
Suite B with NSA's Commercial National Security Algorithm (CNSA)
Suite. Information about the CNSA Suite can be found in [CNSA].
Housley & Zieglar Informational [Page 2]
RFC 8423 Suite B to Historic July 2018
2. Rationale
As indicated in [CNSA], NSA is transitioning from Suite B to the CNSA
Suite. As a result, the profiles of the security protocols for the
Suite B algorithms are now only of historic interest.
3. The RFCs Related to Suite B
Between 2007 and 2012, several Suite-B-related RFCs were published to
profile security protocols for use with the Suite B algorithms. They
are:
o [RFC4869], "Suite B Cryptographic Suites for IPsec" (Obsoleted by
RFC 6379)
o [RFC5008], "Suite B in Secure/Multipurpose Internet Mail
Extensions (S/MIME)" (Obsoleted by RFC 6318)
o [RFC5430], "Suite B Profile for Transport Layer Security (TLS)"
(Obsoleted by RFC 6460)
Show full document text