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

Scott Kitterman <sklist@kitterman.com> Mon, 05 November 2018 03:11 UTC

Return-Path: <sklist@kitterman.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 A41F7129619 for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 19:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=3OxIiFxg; dkim=pass (2048-bit key) header.d=kitterman.com header.b=hj3YHTNb
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 RlBYvTWOFyVc for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 19:11:26 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AED2B128BCC for <dmarc@ietf.org>; Sun, 4 Nov 2018 19:11:26 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1541387484; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=dQJ2oYSNAEIYTp5IMSphhb2ZK+514DoERtoibxIl8u0=; b=3OxIiFxgbuaDqEJTZYy/GkMwMVu/yzIE9qN20mOct2cAgOxw2gYGMxit r8MLliUiDGHHMrFBiyJRF51BUEG1CA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1541387484; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=dQJ2oYSNAEIYTp5IMSphhb2ZK+514DoERtoibxIl8u0=; b=hj3YHTNbK0Er7+HUF9fCX1rNGoek80i7SWCMCdxJm+mkMHLwCCuOEH7z sFEAcFOKdHH+05YBHu7AM7xqJrPrIEx3tr4lkdSRQZv5nKvESTw/DsTvE8 HjtldgHY1AQSrCUgHj6Bw/wuwGHhUoVVwPVWJPhiU5QWaT2af4mqI5ISW9 08AZ53AWexPG9wlrU7oc1cmtTHFfWbZ8HRqFczXx08D5jpx5uVQlEUdUjO qcB+ggjb+geeOjj3+NgCmgJOqsJySSx/sB94jXhy2Vd22wcrjCZxX5ZH8V UeZqhUDwu6kwNFeMuaUJtzJVsT672TSPqkn8Shf8XXlksMgCULrr3g==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 45C91C400ED for <dmarc@ietf.org>; Sun, 4 Nov 2018 21:11:24 -0600 (CST)
From: Scott Kitterman <sklist@kitterman.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Date: Sun, 04 Nov 2018 22:11:23 -0500
Message-ID: <2393746.3XrAvFVKfY@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-158-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com>
References: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YkHEQFWDbYvWVkxYSDaUGoqvGMY>
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 03:11:29 -0000

On Monday, November 05, 2018 10:01:03 AM Kurt Andersen 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

I don't see anything about changes to SPF or DKIM being within the current 
charter, so if we are going to do this, then I think it definitely needs a 
charter change.

What needs changing in SPF/DKIM that we need to take this on?

Scott K