Skip to main content

MD4 to Historic Status
RFC 6150

Yes

(Jari Arkko)
(Peter Saint-Andre)
(Robert Sparks)
(Russ Housley)

No Objection

(Gonzalo Camarillo)
(Ralph Droms)
(Ron Bonica)
(Stewart Bryant)
(Tim Polk)

Recuse

(Sean Turner)

Note: This ballot was opened for revision 11 and is now closed.

Alexey Melnikov Former IESG member
Yes
Yes (2010-12-19) Unknown
The document header has:

   Updates: 1320 (once approved)

Why not "Obsoletes: 1320" ?
Jari Arkko Former IESG member
Yes
Yes () Unknown

                            
Peter Saint-Andre Former IESG member
Yes
Yes () Unknown

                            
Robert Sparks Former IESG member
Yes
Yes () Unknown

                            
Russ Housley Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
No Objection
No Objection (2011-01-05) Unknown
As with the MD2 document, I think it is worth listing the standards 
track documents shown in Section 3 as Updated in the document header.

It looks to me that you might also want to update some of the 
informational documents listed here.

The prime benefit is that those documents will be marked in the RFC
repository as having been updated by this document.

---

Abstract, etc.

Once published, this document should be more assertive. Thus:
OLD
This document recommends RFC 1320 be moved to Historic status.
NEW
This document moves RFC 1320 to Historic status.
END

etc.

---

4. Impact on Moving MD4 to Historic

s/on/of/

---

Section 4


   o MD4 was used in the Inter-Domain Routing Protocol (IDRP); each IDRP
     message carries a 16-octet hash that is computed by applying the
     MD-4 algorithm (RFC 1320) to the context of the message itself.
     Over time IDRP was replaced by BGP-4.

Need to add a refernce to 4271, and an indication that BGP-4 requires at
least MD-5. You could reference 2385, but that might be de trop.

---

Section 4

   o The three Microsoft RFCs, [RFC2433], [RFC2759], and [RFC4757], are

Do we need to describe these as "Microsoft RFCs"? 
How about: "The three RFCs describing Microsoft protocols"?
Gonzalo Camarillo Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection () Unknown

                            
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Stewart Bryant Former IESG member
No Objection
No Objection () Unknown

                            
Tim Polk Former IESG member
No Objection
No Objection () Unknown

                            
Sean Turner Former IESG member
Recuse
Recuse () Unknown