[Top] [All Lists]

Re: [ietf-smtp] [Extra] Fwd: [Ietf-message-headers] Registration update: Content-MD5

2018-10-20 16:19:20
(Sorry for cross posting)

Is there any interest in deprecating use of Content-MD5 for email?

Seems like a lot of effort for no real again.

The few implementations I've seen do interoperate, so AFAIK that's
not a reason for deprecating it.

Of course MD5 isn't cryptographically strong, but it's fine for a checksum,
which is  what RFC 1864 says it is for. (At the time the RFC was written I
argued for extending its use to crypographic applications and in the process
moving the algorithm from the name to the value to provide for algorithm
flexibility, but there wasn't sufficient interest.)


Thank you,

-------- Forwarded Message --------
Subject: Re: [Ietf-message-headers] Registration update: Content-MD5
Date: Tue, 16 Oct 2018 08:39:05 +0100
From: Graham Klyne <gk(_at_)ninebynine(_dot_)org>
To: Mark Nottingham <mnot(_at_)mnot(_dot_)net>, 

Just to be clear, this is just use with HTTP that's being obsoleted?

It's also registered as a MIME header.  The reason for obsoleting per
RFC7231 appears to be inconsistent HTTP implementations, so I guess that
doesn't apply to MIME/email?


On 15/10/2018 05:30, Mark Nottingham wrote:
As discussed on the HTTP Working Group mailing list [1], we'd like to 
update the registry entry for Content-MD5 in HTTP.

Proposed template:

Header name: Content-MD5
Protocol: http
Status: obsoleted
Reference: RFC2616 (obsoleted by RFC7231, Appendix B)



Mark Nottingham

Ietf-message-headers mailing list

Ietf-message-headers mailing list

Extra mailing list

ietf-smtp mailing list

<Prev in Thread] Current Thread [Next in Thread>