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

Dave Crocker <dcrocker@gmail.com> Fri, 28 June 2013 21:35 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 4E27D21F9A1C for <dmarc@ietfa.amsl.com>; Fri, 28 Jun 2013 14:35:32 -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 jdMJIDecCVUJ for <dmarc@ietfa.amsl.com>; Fri, 28 Jun 2013 14:35:31 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B365321F9A52 for <dmarc@ietf.org>; Fri, 28 Jun 2013 14:35:29 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so2898826pad.19 for <dmarc@ietf.org>; Fri, 28 Jun 2013 14:35:29 -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=TYtSMkZx4dEDxjLrPCYm3sXjb6xzcdfTz25es5BBh/0=; b=nsI9/jp5AydKr0CMLbJUW5d0PJWYIae3gHoAu0gwVx7Mpx1z0y/Z3M3vNnyOy0UjA4 hrX9CL+EF1BOW7LOxnGXa5gvhPJihLJma9KFxLbgWvcU8IriEz/zlpvUchVP9oYMYA6/ +BSi5lDDHIgJk++GlOHJG9ffhkdsFX/81XCmvUyL8QcExLI1ULrbTYHNzxSz5XVz6Kx7 uw9huOhEc6tSoKqNgPqP1sk69xfXhllHJwbQ6t/1sFhQTS9NcRxagrHXygA90dT+zD7k YivimrQcM5ohbon+X82Dzc372o2aq9I6fn+o3wOH6QG3ZnqY9JAEm0NILr6M3Eu9eyc8 IKew==
X-Received: by 10.68.114.36 with SMTP id jd4mr13423904pbb.12.1372455329382; Fri, 28 Jun 2013 14:35:29 -0700 (PDT)
Received: from [192.168.1.116] (cpe-76-93-128-131.san.res.rr.com. [76.93.128.131]) by mx.google.com with ESMTPSA id v20sm10685368paj.4.2013.06.28.14.35.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Jun 2013 14:35:28 -0700 (PDT)
Message-ID: <51CE0195.8090504@gmail.com>
Date: Fri, 28 Jun 2013 14:35:17 -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: dmarc@ietf.org
References: <20130628211600.84812.qmail@joyce.lan>
In-Reply-To: <20130628211600.84812.qmail@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: housley@vigilsec.com
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: Fri, 28 Jun 2013 21:35:32 -0000

On 6/28/2013 2:16 PM, John Levine wrote:
>> that we modify the proposed agenda as follows:
>> -- Summary of DMARC
>> -- Summary of open issues
>> -- Charter review
>> -- Hums
>>
>> Comments? Thoughts?


> This version presumes that people attending the BOF need to read the
> drafts first, which seems utterly reasonable.
>
> For the charter, I think it's important for people to understand that
> DMARC is basically done with multiple working implementations
> including several at giant mail systems. (I've written one of the
> smaller ones.)  So the WG can certainly clean up and clarify the text,
> and improve the discussion of where it's useful, but it's too late
> to make incompatible changes to the bits on the wire.

This presumes that the DMARC base specification is part of the working 
group effort.  There's been enough back and forth on this point that 
it's probably worth clarifying it for this list.

To counter the suggestion not to discuss the current "Using" draft: 
Normally a BOF will provide some commentary about documents intended as 
input to the proposed working group.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net