Re: [ietf-smtp] Fwd: I-D Action: draft-melnikov-smtp-metadata-00.txt

"John Levine" <johnl@taugh.com> Mon, 23 March 2015 21:43 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E96EB1B29BB for <ietf-smtp@ietfa.amsl.com>; Mon, 23 Mar 2015 14:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.862
X-Spam-Level:
X-Spam-Status: No, score=0.862 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 27chQ6MRsw3u for <ietf-smtp@ietfa.amsl.com>; Mon, 23 Mar 2015 14:43:51 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C499F1A1A2F for <ietf-smtp@ietf.org>; Mon, 23 Mar 2015 14:43:50 -0700 (PDT)
Received: (qmail 1972 invoked from network); 23 Mar 2015 21:43:49 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 23 Mar 2015 21:43:49 -0000
Date: Mon, 23 Mar 2015 21:43:27 -0000
Message-ID: <20150323214327.39177.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
In-Reply-To: <CABa8R6sQ1MCpYLW7NzwJTiVdWFgFOBEEx7GxJxJL71p+FBfsgg@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-smtp/gvcWYm9o-gIvRYYU0ueGUPmtZa8>
Cc: blong@google.com
Subject: Re: [ietf-smtp] Fwd: I-D Action: draft-melnikov-smtp-metadata-00.txt
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 21:43:52 -0000

In article <CABa8R6sQ1MCpYLW7NzwJTiVdWFgFOBEEx7GxJxJL71p+FBfsgg@mail.gmail.com> you write:
>The problem with BINARYMIME is that unless everyone supports it, someone
>may have to transform the message... and that will break DKIM signatures
>and make life annoying.  Hence my colleagues question about a mime aware
>dkim canonicalization format as a pre-req for binarymime.

We considered it when we were doing the strict/loose c14n but decided
against it as a swamp.  If a relay is going to change MIME structures,
it can recode parts and reorder them while keeping the "same" contents
which will make it quite a challenge to describe what one has to do to
put them into canonical form.

There is a c14n registry to which new values can be added, so if you
want to propose a MIME c14n, the first step is to write it up in a draft.

R's,
John