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

"John Levine" <johnl@taugh.com> Fri, 19 October 2018 09:30 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682EB130E54 for <extra@ietfa.amsl.com>; Fri, 19 Oct 2018 02:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=HTokln7q; dkim=pass (1536-bit key) header.d=taugh.com header.b=Xkxwqeed
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 6ntwDAGpiCbU for <extra@ietfa.amsl.com>; Fri, 19 Oct 2018 02:30:08 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 E6CE5130E4B for <extra@ietf.org>; Fri, 19 Oct 2018 02:30:07 -0700 (PDT)
Received: (qmail 52176 invoked from network); 19 Oct 2018 09:30:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=cbcb.5bc9a41c.k1810; bh=NxAaLTa4QCoRGOFQQ95IkQm4NTSHY1juUf37Dv0Rv3c=; b=HTokln7qhGYSZIDi+tPF2f8JkSByMCo67D6Oy46Uzqzparo+bBgi0f4TrX8OY3FzX9WBeB2uDAuiKwUbe4QOmADbCpwG4oYKpTGg8drJMtG2z5Ivi/hMcPyXXg+atp8gdP14Pg5yJJsLCqHLKbltmru2UHA0ydW+d/8YJXfhmOHvVCqtn4tuD4nxQQ8Hr5RYA2SIrmSIZtP3TZsEBnxh2tIEGQqtS5G+MNJG6YECS2ms9Rg5TGapjYXPO/HlFVxz
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=cbcb.5bc9a41c.k1810; bh=NxAaLTa4QCoRGOFQQ95IkQm4NTSHY1juUf37Dv0Rv3c=; b=XkxwqeedKQwjY2l591MCFxuhToqK5B/Fqr1I0q6bx5CsGjZ9fWXCUYPTElY9juGojA3Tz0fSqCX0wgLPnaI2aKseKwjZL/scOf8aiOE5DgC7xpMkG5zmBuChyCVLiwgj2sJMTcY9QHb3/NfQavzSMogoQDba+dIXT+WePSLyoeJQFQmod1+6CQXrJN6hgcvd5L8eOoRZGDSypwe8v2+2bHTFSLfPwn+JBwPpjESpWGREnYaN+ZNJodkaAXhuiKgE
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 19 Oct 2018 09:30:04 -0000
Received: by ary.local (Postfix, from userid 501) id 8768E20070B80F; Fri, 19 Oct 2018 11:30:02 +0200 (CEST)
Date: 19 Oct 2018 11:30:02 +0200
Message-Id: <20181019093003.8768E20070B80F@ary.local>
From: "John Levine" <johnl@taugh.com>
To: extra@ietf.org
Cc: alexey.melnikov@isode.com
In-Reply-To: <f0f09879-cf78-edbf-17e7-edc79034c9e1@isode.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/-U_eIBSFRhFnvJ174HsUN5dOESY>
Subject: Re: [Extra] Fwd: [Ietf-message-headers] Registration update: Content-MD5
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2018 09:30:09 -0000

In article <f0f09879-cf78-edbf-17e7-edc79034c9e1@isode.com> you write:
>Hi,
>(Sorry for cross posting)
>
>Is there any interest in deprecating use of Content-MD5 for email?

I know it's defined in RFC 1864 but I've never seen in in a mail message.

That RFC suggests it's useful for message/external-body MIME parts,
but I haven't seen any of those in mail lately either.  I gather they
may be used in SIP.