Re: [dmarc-ietf] Charter improvements

Barry Leiba <barryleiba@computer.org> Thu, 18 July 2013 18:25 UTC

Return-Path: <barryleiba.mailing.lists@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 029CA11E81BA for <dmarc@ietfa.amsl.com>; Thu, 18 Jul 2013 11:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level:
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojlr29ZsEugR for <dmarc@ietfa.amsl.com>; Thu, 18 Jul 2013 11:25:02 -0700 (PDT)
Received: from mail-vb0-x233.google.com (mail-vb0-x233.google.com [IPv6:2607:f8b0:400c:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4CC11E819E for <dmarc@ietf.org>; Thu, 18 Jul 2013 11:25:01 -0700 (PDT)
Received: by mail-vb0-f51.google.com with SMTP id x17so2581423vbf.24 for <dmarc@ietf.org>; Thu, 18 Jul 2013 11:25:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0W8aptvFQS1KaakvvF7VOu3URBrXQb5fZ19n3KE8LPU=; b=BRJSFRLhCYOx84FCKkzY2hSrg9nvkt4LINk5JZ+ZPPjF0SCfTguR7Rs0xLL2d8CJ1U JlAocGwmLUv0Wewd1o5DJQwLH2GzeIHnanxmOfy8PmMoRXqEy3FEQsPhPreK70qaT9Dx lcUA5OrG1smZlV2i7RZYMYf/FEcHszl65r7rkIcbfeP+lxKoB9cRaYRHe+Jui+99TadT Y84TWSMW+FYUh9OgecpgRcoq0iWkkHXbp+EwHo52xmFvqTPG5FzMQEbV4T4aEfAk4+EM zv3HjjLRDrwzkSaxXMTWZAhmuygMcf3UTiU5s1plnGVJgDrOtAxKUkcKaV3cyARfBVlj nWWg==
MIME-Version: 1.0
X-Received: by 10.52.164.227 with SMTP id yt3mr3759338vdb.107.1374171901555; Thu, 18 Jul 2013 11:25:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Thu, 18 Jul 2013 11:25:01 -0700 (PDT)
In-Reply-To: <51E5A667.50503@gmail.com>
References: <20130702052746.15876.qmail@joyce.lan> <51D3464D.2060502@sonnection.nl> <0A91244B-1CAE-491A-865B-E2BA64AFB366@tnpi.net> <51E56928.4020207@gmail.com> <b5b7a2e5-b650-494c-913e-a43d2d73f5d7@email.android.com> <51E5A667.50503@gmail.com>
Date: Thu, 18 Jul 2013 14:25:01 -0400
X-Google-Sender-Auth: sXJKxwRj1n6jyUSz_IeeJs0qx1c
Message-ID: <CAC4RtVBWpHkJ_K447-2YnPrupfBkdHKeNFkP4=pA91+zZPJDUw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, Scott Kitterman <sklist@kitterman.com>
Subject: Re: [dmarc-ietf] Charter improvements
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 18 Jul 2013 18:25:03 -0000

>> If the base spec is out of scope, I think the entire effort should be
>> deferred until after it's done. I don't think it makes sense to spin
>> up a working group to work on extensions until they can leverage a
>> stable foundation.

...

>   1.  There is no community support for any proposals to change the
> bits-over-the-wire.
>
>   2.  The current bits-over-the-wire protocol is widely
> deployed and is used for a very large fraction of the Internet's email
> traffic.
>
> Then if that does not constitute the ultimate form of "stable foundation",
> then I can't guess what you mean.

Indeed.  Let's be clear:

I have agreed to AD-sponsor the DMARC base spec *if* I see significant
community review and support for publishing it as Proposed Standard.
I do need to see more reviews and more comments about whether it
should be a Standards Track RFC, but that's a separate point.

We have gotten some reviews of it so far, and those reviews have
suggested some changes.

None of those suggested changes -- including the ones Scott and John
have made in their reviews -- are, in my view, of a nature that would
invalidate the work that the BoF is meant for.  I believe that, as
Dave says, the DMARC spec is sufficiently stable to be a foundation
for the BoF, and for the discussion we'll have there.

Let's please focus on two things:

1. For the BoF, let's work on using the time productively, starting
with the assumption that something fairly close to the currently
published DMARC spec is where we jump off from.

2. For the DMARC spec, let's please have more of the IETF community
review the document, specifically responding to the questions of (a)
what technical changes are needed in it, and (b) whether it should be
published as a Standards Track specification.

Barry, Applications AD