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

Ned Freed <ned.freed@mrochek.com> Tue, 24 March 2015 13:50 UTC

Return-Path: <ned.freed@mrochek.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 E89C51A86EF for <ietf-smtp@ietfa.amsl.com>; Tue, 24 Mar 2015 06:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level:
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YwYddX5p5SGT for <ietf-smtp@ietfa.amsl.com>; Tue, 24 Mar 2015 06:50:37 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id D46671A86EE for <ietf-smtp@ietf.org>; Tue, 24 Mar 2015 06:50:37 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PJZ5MJNOKW00FIHL@mauve.mrochek.com> for ietf-smtp@ietf.org; Tue, 24 Mar 2015 06:45:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mrochek.com; s=mauve; t=1427204735; bh=HVAErNdxPYHL6m74rmou6z7TOJB5S05/nl3sW990CkU=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=eqJaqM1jiCHyOFYiOgdjBW3j/H4W0+3EXboxuIumsH5AyGKplfRelAdAXsjxTOmys enjcOKKkk2zRhB7607B3nkppmL0nSBsgzgTP1BI1nrpVvhjtV4OQUTKO7GhvYJOoNk ZWJUN3kZeWSHzdSCHBdHA7N7H8DbJS1N33RwJOVw=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PJOO472LOW0000AQ@mauve.mrochek.com>; Tue, 24 Mar 2015 06:45:32 -0700 (PDT)
Message-id: <01PJZ5MHFIS40000AQ@mauve.mrochek.com>
Date: Tue, 24 Mar 2015 06:42:18 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 23 Mar 2015 13:17:59 -0700" <CABa8R6sQ1MCpYLW7NzwJTiVdWFgFOBEEx7GxJxJL71p+FBfsgg@mail.gmail.com>
References: <20150307202540.13358.58739.idtracker@ietfa.amsl.com> <550EE444.4040507@isode.com> <4175cf7b-c14e-455d-bd6b-0903d9de6194@gulbrandsen.priv.no> <550F2851.2010409@isode.com> <259d7567-2b13-46df-bb03-54f74fc9e1b4@gulbrandsen.priv.no> <01PJX8XAIWS0000090@mauve.mrochek.com> <CABa8R6sQ1MCpYLW7NzwJTiVdWFgFOBEEx7GxJxJL71p+FBfsgg@mail.gmail.com>
To: Brandon Long <blong@google.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-smtp/-arcg1AjSI5yFTnZWwZqYOys5RU>
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, Ned Freed <ned.freed@mrochek.com>, ietf-smtp <ietf-smtp@ietf.org>
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: Tue, 24 Mar 2015 13:50:39 -0000

> 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.

Which is why I said the target use with SUBMIT, not SMTP relay.

Of course another way to look at it is that this is Yet Another Way that
DKIM/DMARC is incompatiable with our existing standards and infrastructure.
Calling for Yet Another Fix.

				Ned