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

Scott Kitterman <sklist@kitterman.com> Sun, 30 June 2013 20:30 UTC

Return-Path: <sklist@kitterman.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 0D81B21F9C0E for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 13:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 5ClZ4Aq2Agwi for <dmarc@ietfa.amsl.com>; Sun, 30 Jun 2013 13:30:53 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 994CC21F9B15 for <dmarc@ietf.org>; Sun, 30 Jun 2013 13:30:53 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 82B6F20E40D7; Sun, 30 Jun 2013 16:30:52 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1372624252; bh=3xdJBTvNGkEnxjQO33duwwFu9im6CiX/8kfw1yN9n/c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IA8LXPK4OZSeda59QTxChD3Qat++OLHLpp5V41VeLeIlDvldK5qr3TGT/ZQHwraj+ MBsTbyYcGxoI38cBPKZmVtEP9Qbct26usd12Himd4WSOJ+S+g6MzpZQA/4YpsF4Yra NPFXjPUh9favg4ODyhHwsn5aDj6bpSRRO1AYZTJs=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 6211420E4081; Sun, 30 Jun 2013 16:30:52 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sun, 30 Jun 2013 16:30:51 -0400
Message-ID: <1464579.xSTkz0YGGa@scott-latitude-e6320>
User-Agent: KMail/4.10.4 (Linux/3.8.0-25-generic; KDE/4.10.4; i686; ; )
In-Reply-To: <51D0901E.4000003@gmail.com>
References: <20130630200414.70742.qmail@joyce.lan> <51D0901E.4000003@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
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 20:30:59 -0000

On Sunday, June 30, 2013 01:07:58 PM Dave Crocker wrote:
> On 6/30/2013 1:04 PM, John Levine wrote:
> > I'm with Scott.  While I agree that it would be bad to make
> > incompatible changes to the many bits on the wire, the document itself
> > could be improved.
> 
> Indeed, purely editorial, non-technical work rarely (if ever) warrants a
> working group.
> 
> And there have recently been some detail, independent reviews that are
> prompted a document revision that will be issued within days.

So then we're discussing about a BoF that may or may not include discussion of 
a document that we haven't actually seen yet because it's being developed in 
private.  

1.  Definitely premature to be discussing it.

2.  I don't think the IETF should be in the rubber stamp business.

Scott K