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

"John R Levine" <johnl@taugh.com> Mon, 01 July 2013 22:59 UTC

Return-Path: <johnl@taugh.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 3367E21F9FF6 for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 15:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 rGdnuqtVV0pd for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 15:59:20 -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 D2ECF21F90EF for <dmarc@ietf.org>; Mon, 1 Jul 2013 15:58:57 -0700 (PDT)
Received: (qmail 47090 invoked from network); 1 Jul 2013 22:58:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=b7f1.51d209ab.k1307; bh=j3WqiAcjwJWagm5rLSFWJhmEcdW1EIBMyFxEovA/2jo=; b=UBxCHL61Rr+UqbI9u2D7I1dLGeXl0tBxwBxEfWANMf3SKTUcwiuLlnEgTbBPJsSq6YRn2l7eRNvukKQR3Zxw6DZ71c0UoS1VQjdmdagUuBzMeaQBMZIUyT4Z00OiO72JPNXe3AMdyu5kilrk2Gni7WqXix3P7xRdCXJ3zDLYSobzU4MrdUfHvqRjdoGD2M0OAVapO2bH3CRgbmwId49QgYVxjlv0upuxLHDzZ6nK3pIC+AmgM/nqa0ZBCgIp/dJi
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=b7f1.51d209ab.k1307; bh=j3WqiAcjwJWagm5rLSFWJhmEcdW1EIBMyFxEovA/2jo=; b=DlCpyM9x5Seo4asCopiO5mnKg85fWHhZYyuBOscBQU4ymWE5cBCVY8tRnhNZb8gZx/Se+1C51rdP8eSWV8vopOKT2QDmQHTbmAkdYv0Yqv7GIIuZ/fUAzrkkhbAloBa8Inam56eZzLK483WaMr7xN94pnuOb26CByvakERo9mLgnm4IeUbLnDyIXrQpZg7bzFw8ScANLh2n8wHrofjDh24Ws7lS87xyW+d4uPKZ2EUDkWqTSOu9cTSeNJSO+g0rf
Received: (ofmipd 127.0.0.1); 1 Jul 2013 22:58:29 -0000
Date: Mon, 01 Jul 2013 18:58:51 -0400
Message-ID: <alpine.BSF.2.00.1307011829180.14225@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Franck Martin <fmartin@linkedin.com>, DMARC IETF list <dmarc@ietf.org>
In-Reply-To: <77426B543150464AA3F30DF1A91365DE53395A88@ESV4-MBX01.linkedin.biz>
References: <20130630221443.71098.qmail@joyce.lan> <77426B543150464AA3F30DF1A91365DE53395A88@ESV4-MBX01.linkedin.biz>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
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:59:21 -0000

>> 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 draft-kucherawy-dmarc-base-00 document has a license that, as I read 
it, is not compatible with a standards track document.  It wouldn't be 
hard to fix, but it needs fixing.

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

That's not the question I see.  It's whether this is an IETF effort or a 
dmarc.org effort.  Maybe the base document will be all done by the time 
the WG is spun up, maybe not, but that should be the WG's decision.  I 
think everyone agrees that the BCP is a long way from being publishable, 
so there's certainly work there.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.