Re: [Ietf-message-headers] Registration update: Content-MD5

Graham Klyne <gk@ninebynine.org> Tue, 16 October 2018 07:39 UTC

Return-Path: <gk@ninebynine.org>
X-Original-To: ietf-message-headers@ietfa.amsl.com
Delivered-To: ietf-message-headers@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04BBE12D4EB for <ietf-message-headers@ietfa.amsl.com>; Tue, 16 Oct 2018 00:39:10 -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] 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 MfkiRIaPS-sg for <ietf-message-headers@ietfa.amsl.com>; Tue, 16 Oct 2018 00:39:07 -0700 (PDT)
Received: from relay16.mail.ox.ac.uk (relay16.mail.ox.ac.uk [163.1.2.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5CB412D4EA for <ietf-message-headers@ietf.org>; Tue, 16 Oct 2018 00:39:07 -0700 (PDT)
Received: from smtp6.mail.ox.ac.uk ([163.1.2.206]) by relay16.mail.ox.ac.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <gk@ninebynine.org>) id 1gCJwW-0001zE-sH; Tue, 16 Oct 2018 08:39:05 +0100
Received: from gklyne38.plus.com ([81.174.129.24] helo=sasharissa.local) by smtp6.mail.ox.ac.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <gk@ninebynine.org>) id 1gCJwW-0007Ki-Ks; Tue, 16 Oct 2018 08:39:04 +0100
Message-ID: <5BC59599.3000501@ninebynine.org>
Date: Tue, 16 Oct 2018 08:39:05 +0100
From: Graham Klyne <gk@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>, ietf-message-headers@ietf.org
References: <B502C5C6-22AC-43B8-80A1-C69173DFBD0A@mnot.net>
In-Reply-To: <B502C5C6-22AC-43B8-80A1-C69173DFBD0A@mnot.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Oxmail-Spam-Status: score=0.0 tests=none
X-Oxmail-Spam-Level: /
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/NU7Z0dLhVsJk8oF0pJxtKAxyV74>
Subject: Re: [Ietf-message-headers] Registration update: Content-MD5
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-message-headers/>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Oct 2018 07:39:10 -0000

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?

#g
--

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)
>
> Cheers,
>
> 1.  https://www.w3.org/mid/C94E5914-F5F0-46D0-BABB-D42EE45DF10D@mnot.net
>
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> _______________________________________________
> Ietf-message-headers mailing list
> Ietf-message-headers@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-message-headers
>