IETF Logo Mail Archive

Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 11 May 2018 18:13 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BFC12D7E5 for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 11:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6VtnP4ub98Yj for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 11:13:43 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F35512D778 for <ietf@ietf.org>; Fri, 11 May 2018 11:13:43 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id g16-v6so1841145ywk.0 for <ietf@ietf.org>; Fri, 11 May 2018 11:13:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=66ObUhvbRI46rLsRQOgwHPpeB/6SZc4q7KhZtwxu5rw=; b=jTuCHy4dmQTUCgH8TDXTySdbKGoUl+ccDKZStAmCHBqeaH8ioHm6gbwyXk+vLmthrI 8usG3GniVxKTw+3G9noUE5HFSXPp1C/HBvkuYh0GgP1tjuOhj+KZ9DGO4QWm8md0/UTM HoYNMYTbkXzMo0JdzVW3bnqWWh4KjILHhoX/VSsPg/O1nIyTmXIUweC+/FdCHJPbKICF SbyLGr4mdWoDQNn050twCLK5EBMKQB0suvjPvyuvbGoq4MwIBIHx+o9edcLghM4y1SyO GGJ2cXe8CuwxPTyblzNPW0EBWNkQOdBHvdRwgDnS1CmWfCAmPhIom58Aion4EBSUWFqf gBKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=66ObUhvbRI46rLsRQOgwHPpeB/6SZc4q7KhZtwxu5rw=; b=X4yc1i78ASJksfM2t4ROlCsjGHXjNwy7Cc4GS/BquO2D5Q56JKOnVstFBxdV1uVrdu 78JBidtVzpjP1NLHahWJ+ob2eUIRDM9SqcweMmneQx8ltM1CVdkxi6rpF4VHEuaJFl5A coPK4Na0bEcGXX2GzeetUtEQNZmDgcbpFQ5w4DxLGAHeWKJUEQrxoOKlgo9KMWd2XKH2 E7Z/bTF1aBMi9XnHx3dKrbgq87ayZgOebzINdk9RN1HXw04lpgaipbVHYvpckPqnCrwN RD5vIXMNWLg8pyBGcQ3AQW9dtL6Pito30ZQNUppIeCB6HP4aZfn5aZFmtosGbdRi+f4z cKXw==
X-Gm-Message-State: ALKqPwdVYI6yqOPA2phGqxmWQBDgFmY+oTWwLw7nLikMBx0mUvjgdR5z K1I51fkL3wR47GoG7pPtwYF7OedZNwrLlmvcTvI=
X-Google-Smtp-Source: AB8JxZos1itJ+bVVLd62V3yDUYLOUtKbaokCZw3x3Z4fUOc1ow+mi/t+5iVi8bP7VpvGPjr5/Udhrk1cPi6GhnpYI4c=
X-Received: by 2002:a81:29d1:: with SMTP id p200-v6mr49290ywp.424.1526062422093; Fri, 11 May 2018 11:13:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Fri, 11 May 2018 11:13:41 -0700 (PDT)
In-Reply-To: <739143A6-90EB-4F26-8F54-B281DA2FB0E4@fastmail.fm>
References: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm> <61B1EDB45FC4FF33154B13B0@PSB> <739143A6-90EB-4F26-8F54-B281DA2FB0E4@fastmail.fm>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 11 May 2018 13:13:41 -0500
Message-ID: <CAKKJt-cvxgW2=Od_hkF8+keDHfT_1RJtSLwXSiiR7_dhmqPJYQ@mail.gmail.com>
Subject: Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000092f5c9056bf21825"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HEEoyw2UJWlmjSaaTxCpTvX7AOY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 18:13:45 -0000

Hi, Alexey,

On Fri, May 11, 2018 at 12:17 PM, Alexey Melnikov <aamelnikov@fastmail.fm>
wrote:

> Hi John,
>
> > On 11 May 2018, at 18:02, John C Klensin <john-ietf@jck.com> wrote:
> >
> > That said, I'm uncomfortable with using "=40" as a convention in
> > the middle of an address.  First, there is nothing that supports
> > the idea of encoded octets in the middle of local parts and, as
> > you know, there is ample precedent for interpreting an equal
> > sign in a local part as an indication of a name-value setup.
>
> As far as the DMARC workaround for IETF mailing lists is concerned, the
> encoding is an implementation detail and might change in the future. Use of
> = is in fact configurable.
> The only requirement on encoding is that it should somehow be reversible.


Perhaps I've spent too much time talking to  QUIC WG participants about
header invariants, but can you actually change the encoding, or did you
mean just adding a new encoding, so that if someone tries to respond to an
earlier e-mail from someone with a re-written =40 address, that would still
work?

Spencer

v2.23.0 | Report a Bug | By Email