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

Franck Martin <fmartin@linkedin.com> Mon, 01 July 2013 22:11 UTC

Return-Path: <prvs=887ab8cb2=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 A0D0911E82A4 for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 15:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level:
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 PU5UW12WcOBJ for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 15:11:38 -0700 (PDT)
Received: from esv4-mav05.corp.linkedin.com (esv4-mav05.corp.linkedin.com [69.28.149.81]) by ietfa.amsl.com (Postfix) with ESMTP id D5E5711E829B for <dmarc@ietf.org>; Mon, 1 Jul 2013 15:11:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1372716698; x=1404252698; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=jZ9QOyTRzWljtsPInUrYSrPk62onzjdP1Jcsr54AUig=; b=BKsthO5hucnfADb1q3m12E7eP/AzI68OA/YiCowk/4WLsYrdeHXeR1zI 8u0M/58CawGsEukCpT24aOMNxxXsom5YEhR5v8hWVOuE5uH/lfPn8KBy6 bst1mJ/3mlkg7AHkZy8MbfIXGtNpKvaTsgC/STMr6raW4N8OE9ghQ8Xox Q=;
X-IronPort-AV: E=Sophos;i="4.87,976,1363158000"; d="scan'208";a="54396573"
Received: from ESV4-HT02.linkedin.biz (172.18.46.236) by esv4-cas01.linkedin.biz (172.18.46.140) with Microsoft SMTP Server (TLS) id 14.2.328.11; Mon, 1 Jul 2013 15:11:19 -0700
Received: from ESV4-MBX01.linkedin.biz ([fe80::d029:a1fa:62c4:2641]) by ESV4-HT02.linkedin.biz ([::1]) with mapi id 14.02.0328.009; Mon, 1 Jul 2013 15:11:19 -0700
From: Franck Martin <fmartin@linkedin.com>
To: John Levine <johnl@taugh.com>
Thread-Topic: [dmarc-ietf] DMARC BoF at IETF 87, Berlin
Thread-Index: AQHOdCfI9b5jenK0uUGXlrIwu64RYJlL68eAgAAqogCAAAVjgIACw5YAgAADJACAAC8KAIAAB2uAgAAH+YCAAAYRAIAAAQsAgAAjaoCAAZFxAA==
Date: Mon, 01 Jul 2013 22:11:19 +0000
Message-ID: <77426B543150464AA3F30DF1A91365DE53395A88@ESV4-MBX01.linkedin.biz>
References: <20130630221443.71098.qmail@joyce.lan>
In-Reply-To: <20130630221443.71098.qmail@joyce.lan>
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: text/plain; charset="us-ascii"
Content-ID: <2DED75D38A128A4AACDF504410540FE4@linkedin.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dcrocker@gmail.com>" <dcrocker@gmail.com>, "<dmarc@ietf.org>" <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 22:11:42 -0000

On Jun 30, 2013, at 3:14 PM, John Levine <johnl@taugh.com> 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.
> 
> I understand why you might want to tell the IETF that it can only
> change the minor documents, not the major one, but I don't see why the
> IETF would be interested.
> 

This is my take on the process so far.

The spec has been handed over to IETF already. IETF can do what it likes with it. So I don't think the DMARC.org group worries (much) about what can be changed or not.

The question is: is there sufficiently enough work to be done in the current spec (besides editorial) that warrants an IETF WG to work on the spec?

So far the answer to that question is no. The reason: even has a non IETF WG, the DMARC.org group has been listening to all comments and the deployment experience has shown the mechanism is robust across multiple segments.

So the logic conclusion: the spec needs to be AD sponsored to be on the standard track.

But I realize this will not stop conspiracy theories.

If I'm mistaken, please review the spec and answer the question with specifics.