RFC 6149: MD2 to Historic Status
In plain English — editorial summary, not part of the RFC
This document retires MD2 and discusses the reasons for doing so. This document moves RFC 1319 to Historic status. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6149
- Published
- March 2011
- Authors
- S. Turner; L. Chen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoletes:
- RFC 1319
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6150MD4 to Historic StatusCurrent
March 2011
- RFC 1320The MD4 Message-Digest AlgorithmObsoleted
April 1992
- RFC 6151Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 AlgorithmsCurrent
March 2011
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 5091Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 CryptosystemsUpdated
December 2007
- RFC 7350Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)Current
August 2014
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?