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

"John R Levine" <johnl@taugh.com> Tue, 02 July 2013 03:30 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 5740111E83AC for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 20:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075, 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 WTWBh4MvV0Dz for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 20:30:55 -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 4610011E83A1 for <dmarc@ietf.org>; Mon, 1 Jul 2013 20:30:46 -0700 (PDT)
Received: (qmail 99975 invoked from network); 2 Jul 2013 03:30:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=18685.51d24963.k1307; bh=0W7ieboF+m30x7ZRxW82M5Fep5cNpgwJNkeIXLPmtPQ=; b=gfX5tZ6Ic5dIYm/Vdp5quVtafsUHwMiIVhoqPC/dGY2C4sQPbcw8XFnYPyksGiDFbBBdTkTqRYFrP+h9FiggFAKTj/1MJS7uK2sz7sI9lHql4D72bFx9+IdWdN0rgQTqwhuK7we4so0qnA4Gb9yyiihyRrdkvTMHAyuOuI3Z9eGPab7ZfItWQz/cU+O1QnYuKhCXGL1wBQMIOqw8HR5xuy+nDbTgTH3hMdnKIZoYLuSFaMr9vexmifA3NqVSbzmh
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=18685.51d24963.k1307; bh=0W7ieboF+m30x7ZRxW82M5Fep5cNpgwJNkeIXLPmtPQ=; b=g5vJjOc1svlL9jCPNSZGkpKZogcfGAC96xe08ckxT/8UmwFMn6i/auSuQADm7XBYJHG5/xb1QuTSXaPDB5tb4azsAFm0BxxtJLqVxymu4kBfa1IxELWyuASzHyOZDeDgYIZbtz9WlGYVptdHJwnIPys6TxlAuz2fimqjcz7Xo37sq8Ung5UC1BZbWKvIiapWAAesoXAyUd1fa0++Zm4V6kxLkE44s0hRE+yOT/QwS8FQWlSWOlseaEvNCqvuv0xv
Received: (ofmipd 127.0.0.1); 2 Jul 2013 03:30:21 -0000
Date: Mon, 01 Jul 2013 23:30:43 -0400
Message-ID: <alpine.BSF.2.00.1307012319400.15177@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Dave Crocker <dcrocker@gmail.com>
In-Reply-To: <51D23F9C.2040707@gmail.com>
References: <20130702013302.14968.qmail@joyce.lan> <51D23955.8030902@gmail.com> <alpine.BSF.2.00.1307012226360.15177@joyce.lan> <51D23F9C.2040707@gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: 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: Tue, 02 Jul 2013 03:30:56 -0000

We do seem to be suffering from a failure to communicate, don't we?

According to the subject lines of the messages we've been exchanging, 
we're talking about a BoF for DMARC.  I hope we agree that the reason to 
have a BoF is to see if a topic merits a working group.

According to what you've said, the DMARC technical draft is good enough 
that you'll send it in as an independent submission, no WG involved. 
Franck says that if people have comments on it, they can send them to the 
dmarc.org list and that group will listen, which matches my experience.

The only other document I'm aware of is the BCP draft.  That draft is a 
mess, but the dmarc.org group who wrote the technical draft seems entirely 
able to fix it into something reasonable and send it in as another 
independent submission, leaving nothing for a WG to do.

Perhaps my reference to volunteer time was confusing.  I realize that an 
independent submission takes some time from the AD*, IESG*, and whoever 
looks at it in last call, but a WG is a lot more with chairs, members, 
document editors, and whoever.  It's the latter group who don't need to 
spend time on DMARC.

Unless I'm missing something important here, it seems so obvious that 
DMARC doesn't need a WG that perhaps we should can the BoF and give the 
slot back, since I gather there's a lot of other groups who could use it.

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

* - who are stuck either way