Re: [dmarc-ietf] Proposed charter spiff to accept EAI clarification within email authentication stack
Barry Leiba <barryleiba@computer.org> Mon, 05 November 2018 04:03 UTC
Return-Path: <barryleiba@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 1678412D4E9 for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 20:03:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level:
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 Fd-Z_2ATr9Da for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 20:03:33 -0800 (PST)
Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) (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 5EE9A128CF2 for <dmarc@ietf.org>; Sun, 4 Nov 2018 20:03:33 -0800 (PST)
Received: by mail-io1-f43.google.com with SMTP id c6-v6so5493195iob.11 for <dmarc@ietf.org>; Sun, 04 Nov 2018 20:03:33 -0800 (PST)
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=F4nFOjnfYxFBygLsekA45tq6V3+l0wkz+hylcKDl5uc=; b=Ylg+Y6MC+1viAqpFBYEMwH/r7Z/dMkAym4AHCBLQdxeIo33PxGD4GLks1FxYLj+3cU wky1P8hrQHIwxgLBt6OHaOD0qfbLmAngN3//163XaHMODMtFZM12LUxwE89sH2sQARjc Ngt+GMFzEaWFLGxrwcPUYCRNC2q+anaMXx9h70l4VrZjwq8Y0kAYTYwHRr7Uz8degkXg SONWxC5S/V4z+zbappSmMDqat78MzFn1bfzyJjsRSJkiyxB9JVjTFxfBQGrEObBbhNCP N02oOOv0n1tM+EsClVGQ5augxHSOnOYqTS5Gahjow0kfM+u2bBA/BM8SbKySVSeN/eab upRg==
X-Gm-Message-State: AGRZ1gKd7npB9HdkdHEQJsiaQv0f6H5DnoXbFA676i/PIKH4/wWAT8FM FAbQwdDHlIhykQ8WBcQRJWG70lJJzpj4jvR7IzI=
X-Google-Smtp-Source: AJdET5dme6kvIEcEchFtxAMJSsQyAqc8VI+2A2+BSinvhsbOZqQZ4+8PZhSgDd2ti0KHdDfIsf4nU1esTZZ0mFHLmtA=
X-Received: by 2002:a6b:620d:: with SMTP id f13-v6mr7769511iog.11.1541390612082; Sun, 04 Nov 2018 20:03:32 -0800 (PST)
MIME-Version: 1.0
References: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com>
In-Reply-To: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 05 Nov 2018 11:03:46 +0700
Message-ID: <CALaySJLRWjtX+JYpxVvXkx_2-gehTppTaer2BbocOP7gNni89g@mail.gmail.com>
To: "Kurt Andersen (b)" <kboth@drkurt.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Murray Kucherawy <superuser@gmail.com>, dmarc@ietf.org, John Levine <johnl@taugh.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/iq1HvM-ueoHI04U_-CLVWaZsGec>
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:03:35 -0000
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/
- [dmarc-ietf] Proposed charter spiff to accept EAI… Kurt Andersen (b)
- Re: [dmarc-ietf] Proposed charter spiff to accept… Scott Kitterman
- Re: [dmarc-ietf] Proposed charter spiff to accept… Kurt Andersen (b)
- Re: [dmarc-ietf] Proposed charter spiff to accept… Barry Leiba
- Re: [dmarc-ietf] Proposed charter spiff to accept… Murray S. Kucherawy
- Re: [dmarc-ietf] Proposed charter spiff to accept… Scott Kitterman
- Re: [dmarc-ietf] Proposed charter spiff to accept… Seth Blank
- [dmarc-ietf] Fwd: Proposed charter spiff to accep… Seth Blank
- Re: [dmarc-ietf] Fwd: Proposed charter spiff to a… Murray S. Kucherawy
- [dmarc-ietf] Does EAI doc need to flag SPF macro … Kurt Andersen (b)
- Re: [dmarc-ietf] Does EAI doc need to flag SPF ma… Scott Kitterman
- Re: [dmarc-ietf] Fwd: Proposed charter spiff to a… Scott Kitterman
- Re: [dmarc-ietf] Does EAI doc need to flag SPF ma… Seth Blank