Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin

Dave Crocker <dcrocker@gmail.com> Mon, 01 July 2013 23:12 UTC

Return-Path: <dcrocker@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 B91C511E82F1 for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 16:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 jwVdidRbrO8o for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 16:12:14 -0700 (PDT)
Received: from mail-gh0-x22b.google.com (mail-gh0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id B536F11E82D8 for <dmarc@ietf.org>; Mon, 1 Jul 2013 16:12:14 -0700 (PDT)
Received: by mail-gh0-f171.google.com with SMTP id f15so2246819ghb.30 for <dmarc@ietf.org>; Mon, 01 Jul 2013 16:12:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=V4QXY5avqve3vx29D1jL0KBt6syjO4KRbPpa+YMgdn4=; b=AgXTIJHXpFB1/Vi/yQ5f359kOlykd0tCzbBjx3oqlZbeV74k+Dc1IvNny7EARsbvyj hvF9F7PzHG4alHIubACW5ADnuUg976Ip8EElKK3ErkzwyNCTchOwOAbsz/NbpWZ5yTcy ogb6oH7u8Ynj2ih6JHaL6rhlTQKhI152lZxj7QAAUULgi7Rs40mIB/dlwptbN0/d8UK7 ySWJnQJYZWjXCAlf8o1DAwOpcdnhuP7frlX7p/sg/GLRsWJQtv6Ek8uX0Lo8vFvNiA4T SrErZKUZp3mPG/cnvqU8CRcEUFLZDaChafzu7mQxzxJC4mGLN4U32HP30gYEZE34Ef/L ZrJw==
X-Received: by 10.236.174.199 with SMTP id x47mr13403448yhl.257.1372720334251; Mon, 01 Jul 2013 16:12:14 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net. [76.218.9.215]) by mx.google.com with ESMTPSA id b48sm9711652yhc.8.2013.07.01.16.12.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 16:12:13 -0700 (PDT)
Message-ID: <51D20CC0.6020605@gmail.com>
Date: Mon, 01 Jul 2013 16:12:00 -0700
From: Dave Crocker <dcrocker@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
References: <20130630221443.71098.qmail@joyce.lan>
In-Reply-To: <20130630221443.71098.qmail@joyce.lan>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: dmarc@ietf.org
Subject: Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin
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: Mon, 01 Jul 2013 23:12:15 -0000

On 6/30/2013 3:14 PM, John Levine wrote:
>> And there have recently been some detail, independent reviews that
>> are prompted a document revision that will be issued within days.
>
> While I don't doubt that the next version will be better, I think that
> the dmarc.org group needs to make up its mind and either get a
> reasonably chartered IETF WG that says no gratuitous changes to the
> bits, contribute all of the drafts to the WG, and take its chances. or
> else contribute none of them and just send them in via the independent
> stream.


John,

Your premise is that something problematic and possibly wrong is being 
done.  It isn't.

The base specification is being submitted through the 'individual 
submission' path within the IETF stream.  We have a sponsoring AD and we 
are following his guidance for this.

An initial version of the draft was posted as an I-D.  The sponsoring AD 
has pressed for a number of reviews to be done.  An initial set were 
done and came back calling for some significant editorial changes, but 
no technical changes, essentially to make the document better to read.

Let me repeat:  better writing; no technical changes.

That seemed like an obviously good suggestion, so we are responding to 
it.  Rather than impose the original I-D on further reviewers, we 
decided to fold in their guidance now, with initial update, so that 
further reviewers can benefit from the improvements.

A working group is for technical work.  We've solicited suggestions for 
incremental technical work at least twice in two forums and there has 
been no constituency developed for any near-term work.  If you know of 
work to be done and can develop community support for it, please, 
please, please document it.

At that point, it will be worth considering working group chartering for 
technical effort on the base dmarc spec.  Absent that, it isn't.

As for the 'status' of the document, we are targeting a standards track 
RFC through the IETF stream.  The copyright choices for that are quite 
constrained.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net