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

"John Levine" <johnl@taugh.com> Fri, 28 June 2013 21:16 UTC

Return-Path: <johnl@iecc.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 3358921F9CF8 for <dmarc@ietfa.amsl.com>; Fri, 28 Jun 2013 14:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.333
X-Spam-Level:
X-Spam-Status: No, score=-108.333 tagged_above=-999 required=5 tests=[AWL=2.866, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 n68pRhiXHUoa for <dmarc@ietfa.amsl.com>; Fri, 28 Jun 2013 14:16:24 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CBEF621F85D1 for <dmarc@ietf.org>; Fri, 28 Jun 2013 14:16:23 -0700 (PDT)
Received: (qmail 2250 invoked from network); 28 Jun 2013 21:16:22 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 Jun 2013 21:16:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51cdfd26.xn--9vv.k1306; i=johnl@user.iecc.com; bh=ttUY3n49ZRFiCdeB6x1xOXDZZDV15aSktw/qJsAEVKE=; b=FHlZVnZVfVmahAPR76dqBOp8yw72V0d0ljngziqWfOsKjL6muyBnI4cU1O5MDV2NMNPkrHhFJpbxOkBm0a/r1qRm8iES2hoIh9T8DhaKepheZyzPXy4AX9ObZmL1ehYLARTyUI+vJ9meo2v3zs0tsyh1f+IDGeHikbkqcKaZznyg/CvbrwgoeWUieZB4WqTOImit9XXTT2Dpa2CdVlMjgTVHRh6Vb4uJ/t1jibJH0Zb+gqwlR/t1V5w6ZcYhknpR
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51cdfd26.xn--9vv.k1306; olt=johnl@user.iecc.com; bh=ttUY3n49ZRFiCdeB6x1xOXDZZDV15aSktw/qJsAEVKE=; b=HKGZeNBUnsEjl4AZIt/dCAUsMkx7mp3N6ryvki3SHFQ544+pWEQo4dSEfPhA20SvF//ZmaOKR98Cx4G7T+VAfFV0escYmOf7al0pAxwzdDWDNw5Yh3ImYR0fPZeayuxV3Qny1mskW0KwWETAp3IB+WbpSSO32EnZVQpWbXuJyy4ELMEJehanFohoSmyOjTSuWeif5VlOIjuOxPfdmTzCHKeOEZ/khoi0VqRuChFhq3GTpV7Pgd5KXS0NbLlJwhaM
Date: Fri, 28 Jun 2013 21:16:00 -0000
Message-ID: <20130628211600.84812.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
In-Reply-To: <377AA4D7-3202-42B9-B6D6-05510F08990D@vigilsec.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
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:16:28 -0000

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

We've also had people who want it to be the magic spam bullet, aka
FUSSP, and demand horrible hacks to fix what they perceive as holes in
the spec, e.g., the alleged mailing list problem.  Those sorts of
changes need to be totally off the table.

Other than that, no prob.

R's,
John