IETF Logo Mail Archive

Re: [dmarc-ietf] Proposed charter spiff to accept EAI clarification within email authentication stack

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 05 November 2018 04:05 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89FEB1298C5 for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 20:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 y20-vmI1UFBp for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 20:05:40 -0800 (PST)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 53B4F128CF2 for <dmarc@ietf.org>; Sun, 4 Nov 2018 20:05:40 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id t22-v6so6698604lji.7 for <dmarc@ietf.org>; Sun, 04 Nov 2018 20:05:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wABzwUCbH6eQzqloT0EOEMv+wuxWKKSAObLS+LTDMds=; b=MIMGCY5qvLjBfl79IfOm2Uauuc3QKVVHuMuvzcZIicZMiyeInWZOAlSngT9HhkP4Yh 4uxtpda6fYuIa3m5lE9qvIKARBFmPvpvljUScjsHGWXLgIRRkTJZIV5fLi6G68HRTEN9 VRTwfceLAHJqXGMWGYgV9RZgkTuVvzPSwin6/jA9M5oiAAGnpIKIS9Jx1i8gC4wi/Hr4 MHakjSFTmqbLRGZAc6a5HoD2tkbdMt3rJfmnVq9dPRo8wmB2tPnuiBQv2IOByvDzTWi/ 5FpuvinRgYG6SsM0gqQg7TofWSy0OiDhCkqpfMGpKQfI12FCPhHpTE4xKDDJz51XcEss CXrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wABzwUCbH6eQzqloT0EOEMv+wuxWKKSAObLS+LTDMds=; b=Vld2D3VmMRqlzbc/WtkpV4tsYIb13IQ4CCXmE+KDLGlQ1kL8ofWyuuv/neTWqXyfpE iUl8b48cTYgVbR9JS+bpEK4GLZ1673URGyjtItHhsYNAWY4qdby61RVgaGhFfFIBDNHI cEE7sTEL/xQIqcUUz6t+i2UuCaBitc3CqglqAB/QyrLrwNG9gn98qSfihkQAdn8IkiiG jv6CkW0bbO+Qe6tWzIorKp6lTBViH9PfpONL2S5GtKvLuXnG2GFQZ9ILU1VTWbyHA7HP fgwNxhmlc48c3s+8rSDqKOCEnUX3Ys2881x72dIC5+Fn37MTTz9EVFiJu7BvVzn0ccuK T+IA==
X-Gm-Message-State: AGRZ1gL7gj/FItZKNClPiV8CNYNdBSXgzeC+XQJbsVWmqDnIJp+lc7cr NB/LP+DqUVQK42GgMGNO1d9YKOZYZAi7ztSVL8jpr0qGaX4=
X-Google-Smtp-Source: AJdET5dLN8BxiDBYMP5S3S3gGH035QzLEAuA6kseF9bFEtj8UmVDAQnxPGkjg8Xi5RzHESzzjQBd2XU/8qEgtAdSuW4=
X-Received: by 2002:a2e:9e53:: with SMTP id g19-v6mr14505780ljk.39.1541390738375; Sun, 04 Nov 2018 20:05:38 -0800 (PST)
MIME-Version: 1.0
References: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com> <CALaySJLRWjtX+JYpxVvXkx_2-gehTppTaer2BbocOP7gNni89g@mail.gmail.com>
In-Reply-To: <CALaySJLRWjtX+JYpxVvXkx_2-gehTppTaer2BbocOP7gNni89g@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Mon, 05 Nov 2018 13:05:25 +0900
Message-ID: <CAL0qLwbRvsZ+72+PrrL68JpxmbiuizTntDHJArczxRoLfWDSNQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: "<kboth@drkurt.com>" <kboth@drkurt.com>, Alexey Melnikov <alexey.melnikov@isode.com>, IETF DMARC WG <dmarc@ietf.org>, John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="0000000000006bcbcd0579e2ff60"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/cZPzT5wbOnXYIPprNcqOks22LaM>
Subject: Re: [dmarc-ietf] Proposed charter spiff to accept EAI clarification within email authentication stack
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2018 04:05:42 -0000

I proposed adding this right above "Work Items" (it accomplishes the same
thing):

4. Incidental related work

Any issues related to the email authentication space that are large enough
to mandate working group review but do not already fit under the charter of
an existing working group can be considered for adoption by DMARC.  A
prime example is draft-levine-appsarea-eaiauth, which provides EAI-related
updates to DMARC and the protocols upon which it depends.


On Mon, Nov 5, 2018 at 1:03 PM Barry Leiba <barryleiba@computer.org> wrote:

> I was about to propose something very similar, so I'm happy to go with
> Kurt's text.  Alexey, do you think this will work?
>
> DMARC working group, are you OK with that addition to the charter?
> Any objections?
>
> Barry
> On Mon, Nov 5, 2018 at 10:01 AM Kurt Andersen (b) <kboth@drkurt.com>
> wrote:
> >
> > I think that we could possibly already read this into the existing
> charter, but the following one sentence patch makes it explicit:
> >
> > diff --git a/dmarc-wg-charter b/dmarc-wg-charter
> > index a1d0fac..c8ac6bc 100644
> > --- a/dmarc-wg-charter
> > +++ b/dmarc-wg-charter
> > @@ -81,6 +81,9 @@ the working group can consider extending the base
> DMARC specification
> >  to accommodate such a standard, should it be developed during the
> >  life of this working group.
> >
> > +Clarifying the handling of internationalized email addresses (EAI)
> > +throughout the authentication stack of SPF, DKIM, and DMARC.
> > +
> >  Improvements in DMARC features (identifier alignment, reporting,
> >  policy preferences) will be considered, such as:
> >
> > --Kurt
>
>
>
> --
> Barry
> --
> Barry Leiba  (barryleiba@computer.org)
> http://internetmessagingtechnology.org/
>

v2.23.0 | Report a Bug | By Email