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

Dave Crocker <dcrocker@gmail.com> Tue, 02 July 2013 14:31 UTC

Return-Path: <dcrocker@gmail.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 885BF21F9EB5 for <dmarc@ietfa.amsl.com>; Tue, 2 Jul 2013 07:31:18 -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 7PPHaKcztCjy for <dmarc@ietfa.amsl.com>; Tue, 2 Jul 2013 07:31:17 -0700 (PDT)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4FAAB21F9EC1 for <dmarc@ietf.org>; Tue, 2 Jul 2013 07:31:10 -0700 (PDT)
Received: by mail-vc0-f182.google.com with SMTP id id13so2772075vcb.41 for <dmarc@ietf.org>; Tue, 02 Jul 2013 07:31:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=iphNzsB4mTCd8ixe7Msk3i1CE8ecgKIWHdIR6OrQ4UU=; b=NyT4Dgj8jw1uHFDj1sG9oUiME4Ssw3Muh6ZIS54/2eWj3zJjvLFTTVxGBYJsGzWZUt lgXb95LAdx/nQzujeTF4k39AEmJnAuUeM/9i77OY64h0OwRuSBf2icoCA9N1vREKQxgd tI4T+OFbRZ2UotU8mgLxd2kw0ef1j5wZkqpeZY/Sv51ljcxgSkJAg7Wb0RHtwzp1z5Un Egw6/7tPMyHBh0JNQdHOzV/JANOVLfnScQXAgwSpE4wgFpqfWYZat1gDC3pMS+kAJbLa mkZy6qvvMZtazz4Csv/iAilS+uASQ1GwJlBeTVRfAk66Y7fnV8p+d2I2JXTHbHSW9Goe 8fZw==
X-Received: by 10.220.251.3 with SMTP id mq3mr11623067vcb.20.1372775469653; Tue, 02 Jul 2013 07:31:09 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net. [76.218.9.215]) by mx.google.com with ESMTPSA id t5sm6506197vde.8.2013.07.02.07.31.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Jul 2013 07:31:08 -0700 (PDT)
Message-ID: <51D2E41E.5000609@gmail.com>
Date: Tue, 02 Jul 2013 07:30:54 -0700
From: Dave Crocker <dcrocker@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Scott Kitterman <sklist@kitterman.com>
References: <20130630221443.71098.qmail@joyce.lan> <16743503.BShYmKGdG4@scott-latitude-e6320> <CAL0qLwYA0B-j2J36C+7Efjkj=mzZuDGWeTqV24sjKEe7c4ACmA@mail.gmail.com> <3702901.qqViAzZfBM@scott-latitude-e6320>
In-Reply-To: <3702901.qqViAzZfBM@scott-latitude-e6320>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 14:31:18 -0000

On 7/1/2013 10:24 PM, Scott Kitterman wrote:
> I think it's very difficult to have a conversation about what work needs to be
> done at this point because we don't know what the base spec looks like.

Yes you do.

The changes being done are non-technical.  The technical details have 
been visible and stable for a long time.

You've also participated in other IETF group discussions during document 
development.  So the idea that a document is undergoing changes and yet 
is still being talked about is something you are familiar with.


> I
> think the last published version has some design issues that need to be
> addressed and it not nearly clear enough to support development of
> independent, interoperable implementations (including particularly the data
> exchange).

The clarity issue might well be a matter of writing quality, and that's 
what the current round of revisions is attempting to address.  "Design 
issues" sounds more technically substantive.  As has been said, no 
design changes are being made to the document in the current round.

Once again:  If you have technical concerns -- including design concerns 
-- please raise them here; pursue them here; resolve them here through 
group consensus.


> I'm not arguing for conspiracies, just that for those of us on the outside of
> the group, we don't know what we don't know.

You don't know what editorial changes are in the midst of being made. 
That's typically true for working group documents, too, since most leave 
such things to the editor.

However you /do/ know all the technical details, because they have been 
public and stable for quite awhile.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net