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

"Kurt Andersen (b)" <kboth@drkurt.com> Mon, 05 November 2018 03:21 UTC

Return-Path: <kurta@drkurt.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 549B1128CF2 for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 19:21:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=drkurt.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 2mSx041Z7YHg for <dmarc@ietfa.amsl.com>; Sun, 4 Nov 2018 19:21:48 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 C6946128BCC for <dmarc@ietf.org>; Sun, 4 Nov 2018 19:21:47 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id n26-v6so5081016lfl.1 for <dmarc@ietf.org>; Sun, 04 Nov 2018 19:21:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=m/p0Uqr64XKpo78tLaZ0YbcFt/PJDMfGEF9euBgRdtw=; b=OCp7Ul3CFWfWV5SFY+kcXE8+oBgFB8KBlCS3XzOPDC8A/LJKVG3ps3owF9Z8elFfU7 ojqdBV0rjgwKjs2cwuKxacZKyOxWLGx52hdKdIBtI71572H4CmeI/n1gNPUjffu0/ohf 6W+C7sNNYNhFyO92KP6JGiS5WQTETC0uVTLWE=
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=m/p0Uqr64XKpo78tLaZ0YbcFt/PJDMfGEF9euBgRdtw=; b=o49k5PMqzCI/GrfK8Wg1OQqyNsmpjTuPivaoadfoawtn0bi8aDQVQnnFOipIIvxCFn 7CpXl+y7Ujl60bauFxiaM8WbqClYpq+32RQBy/AtoZ6N7anEWKrgzOkmevmB/qbt4rDZ s1B+O8CcH9vct7gz/G4rHKTgMgr2YjTOx0M6JLYnknq6XTzkAZ/ix80Ca1TEzzDJYFs1 y4/DoV+40rZDAgadEk+QW+Wf0ViLSgFoT42EbhlpgQK4Ggq7SYRCnnGE47gAyWoz4meu UKwgnN5zxTqBU1QhHmLwRtzcizb3hiLfFgIHHvAGV69WIh+MJoGWzzUy7HzTzBXHaPZ8 df9g==
X-Gm-Message-State: AGRZ1gIX5IjN9wvrxAtEyrMQhOYrHW8xEybtoX4Fyg0tnh4H9G/qLdT8 BaiVDCVYHW7XRuhORlJi56UJ9L7DMihVD+fROO1PGhFzJ68Itw==
X-Google-Smtp-Source: AJdET5d11vt2XIrBpPdHl3hfquYgRTgJXCsW6xNTjNrDh/qyOR1hBPMMT2krfTtck3VRjgLuY43mTBbcDSu7+aWfJEc=
X-Received: by 2002:a19:e01e:: with SMTP id x30mr11014299lfg.89.1541388105794; Sun, 04 Nov 2018 19:21:45 -0800 (PST)
MIME-Version: 1.0
References: <CABuGu1qC=Hwu=2zzmApHKQ68H-X0UmLBZnvzABeXAfD_A4F6TQ@mail.gmail.com> <2393746.3XrAvFVKfY@kitterma-e6430>
In-Reply-To: <2393746.3XrAvFVKfY@kitterma-e6430>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Mon, 5 Nov 2018 10:21:15 +0700
Message-ID: <CABuGu1oQLCmmuKhfFZdgq9tmN-GOpCLikmu4OpN3MyAv3whw4g@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081e29e0579e26299"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xyMhTSVbQZAL5dIX3uj-k99_tZg>
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:21:51 -0000

On Mon, Nov 5, 2018 at 10:11 AM Scott Kitterman <sklist@kitterman.com>
wrote:

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

This came out of this morning's DISPATCH meeting at IETF103 (
https://tools.ietf.org/wg/dispatch/agenda) to be able to accept
http://tools.ietf.org/html?draft=draft-levine-appsarea-eaiauth into the WG
for advancing it to an RFC (probably informational).

--Kurt