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

Scott Kitterman <sklist@kitterman.com> Sun, 30 June 2013 15:59 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 C5E3521F9A1F for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 08:59:10 -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 vQ4gzGt96-lO for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 08:59:06 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 547F921F9A1A for <dmarc@ietf.org>; Sun, 30 Jun 2013 08:59:06 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 731A120E40D7; Sun, 30 Jun 2013 11:59:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1372607945; bh=2goa0SNqYkCfcL+C3KcAP7LHH3KuCQInFRMAEBRZLjw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IapK/YbIgyt0MnLBKYvBZulAAR6PeDF/XwZi1p+gsvbvJ77SS1leKf7dfncv+SSX6 Rr+jsQsyeFNiN3b2KL4VOu7SOeOZ7PUx54BPD7MzzlR21BkxpxCBUdlH7TmylmgZev PVzTOgA2NBdkZx/rBZZ8GZ1PaSmFdP//3sp/8wTA=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 53D3120E4081; Sun, 30 Jun 2013 11:59:04 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sun, 30 Jun 2013 11:59:04 -0400
Message-ID: <1453736.2es1zahXvQ@scott-latitude-e6320>
User-Agent: KMail/4.10.4 (Linux/3.8.0-25-generic; KDE/4.10.4; i686; ; )
In-Reply-To: <EAB182AB-76D4-4F88-8BBD-CC327C39BC8D@vigilsec.com>
References: <20130628211600.84812.qmail@joyce.lan> <51CE0195.8090504@gmail.com> <EAB182AB-76D4-4F88-8BBD-CC327C39BC8D@vigilsec.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
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: Sun, 30 Jun 2013 15:59:10 -0000

Then why have a BoF at all?  It seems rather premature to discuss work beyond 
the base specification before we know what will be in the base specification.

Scott K

On Sunday, June 30, 2013 11:47:50 AM Russ Housley wrote:
> Barry tells me that the base DMARC specification will be AD sponsored. 
> Therefore, the BOF will talk about work beyond the base DMARC
> specification.
> 
> Russ
> 
> On Jun 28, 2013, at 5:35 PM, Dave Crocker wrote:
> > 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/
> 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc