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

Franck Martin <fmartin@linkedin.com> Sun, 30 June 2013 19:14 UTC

Return-Path: <prvs=8862bb6e8=fmartin@linkedin.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 1496521F963F for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 12:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.264
X-Spam-Level:
X-Spam-Status: No, score=-6.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 uc22lkXa4gc5 for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 12:14:10 -0700 (PDT)
Received: from esv4-mav04.corp.linkedin.com (esv4-mav04.corp.linkedin.com [69.28.149.80]) by ietfa.amsl.com (Postfix) with ESMTP id 67F9921F949F for <dmarc@ietf.org>; Sun, 30 Jun 2013 12:14:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1372619650; x=1404155650; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=A7+266SPeuPEXh6c3VJiSQ529U7B1l9ZK0xUquC7wQs=; b=08byvvJB4C8zayKPpsjfJbgqO2lMVRCqbN3qpJlNmdjldEHCwH9iKvD8 zXUViFdgO6zO2p1M06kNhv/NTdx4XhC1d9JK/XngnJHNUchwN+RCNmqpI 30mdD144EOSpG04xsFvbb1xRwhMdAi4ojbcnhzXOelWCEsLghghAGdWNB Y=;
X-IronPort-AV: E=Sophos; i="4.87,969,1363158000"; d="scan'208,217"; a="52653801"
Received: from ESV4-MBX01.linkedin.biz ([fe80::d029:a1fa:62c4:2641]) by esv4-cas02.linkedin.biz ([172.18.46.142]) with mapi id 14.02.0328.011; Sun, 30 Jun 2013 12:13:48 -0700
From: Franck Martin <fmartin@linkedin.com>
To: Barry Leiba <barryleiba@computer.org>
Thread-Topic: [dmarc-ietf] DMARC BoF at IETF 87, Berlin
Thread-Index: AQHOdCfI9b5jenK0uUGXlrIwu64RYJlL68eAgAAqogCAAAVjgIACw5YAgAADJACAAC8KAIAAB2uA
Date: Sun, 30 Jun 2013 19:13:47 +0000
Message-ID: <77426B543150464AA3F30DF1A91365DE53383898@ESV4-MBX01.linkedin.biz>
References: <20130628211600.84812.qmail@joyce.lan> <51CE0195.8090504@gmail.com> <EAB182AB-76D4-4F88-8BBD-CC327C39BC8D@vigilsec.com> <1453736.2es1zahXvQ@scott-latitude-e6320> <CAC4RtVD1f0ahd_pQaFLcTNYVy3gV_zXH1j40w2FxHXwtqQe-9Q@mail.gmail.com>
In-Reply-To: <CAC4RtVD1f0ahd_pQaFLcTNYVy3gV_zXH1j40w2FxHXwtqQe-9Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.18.46.250]
Content-Type: multipart/alternative; boundary="_000_77426B543150464AA3F30DF1A91365DE53383898ESV4MBX01linked_"
MIME-Version: 1.0
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, Scott Kitterman <sklist@kitterman.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: Sun, 30 Jun 2013 19:14:14 -0000


On Jun 30, 2013, at 11:47 AM, Barry Leiba <barryleiba@computer.org<mailto:barryleiba@computer.org>> wrote:

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

First, the DMARC spec is sufficiently well baked and mature that it should provide a solid enough basis for discussion.  It's not likely that changes to it would be so drastic as to invalidate the BoF results.

Second, the *plan* right now is to have the base spec AD sponsored, but the BoF could provide input to that plan.  We expect to hear what the community thinks of the work and how it should proceed, as well as to get a sense of who will work on it, who will implement it, and that sort of thing.


You can find the spec here: http://tools.ietf.org/html/draft-kucherawy-dmarc-base-00 and it has not much changed (in terms of functionality) since the first release, one year ago: http://dmarc.org/draft-dmarc-base-00-01.txt

It has been 3 months since the spec has been released as an IETF document, where people had the opportunity to comment and as Barry said no drastic changes required have surfaced, and prior to that for more than a year the DMARC group has been taking input from the whole industry. so I'm not expecting any surprise, tho it may happen.