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

Dave Crocker <dcrocker@gmail.com> Tue, 02 July 2013 02:22 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 CC8D211E8381 for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 19:22:27 -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 Go7nKeBGNqOz for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 19:22:27 -0700 (PDT)
Received: from mail-ye0-x233.google.com (mail-ye0-x233.google.com [IPv6:2607:f8b0:4002:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC4011E837F for <dmarc@ietf.org>; Mon, 1 Jul 2013 19:22:26 -0700 (PDT)
Received: by mail-ye0-f179.google.com with SMTP id r3so1409740yen.24 for <dmarc@ietf.org>; Mon, 01 Jul 2013 19:22:26 -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=ozRv6Yhs682x1b318DHgTFG7AmmbsD4MEHsgHWM29XU=; b=S/UTWyqgeD1x92OM0863kys9V93zhiCElGSjt89g+wv3SpFFTUrjKsLHKdFt9T04Ta tiWTXgrJ4Egwmt95c8xGRUI+dsM0Jp+cUTO0Usi6ts4FHjP0WSKvkqLUFX7OW2nltkG2 iN9aR4fhpe6LXXQg2EG3pEOZ70PiRzM+sWOvDZOV/MlOxZaCOEGB7HN+X+OMboVib7tC LCjW0Fv+MjGBCzIECIVpQDSjiXRQX18LB20kHyVJCSDYXnxjxZ/afhfuuXSCsQphIW1m 34bRPVhx52VOsEsgDILo3fhpJ5Ej/A9Or8kyqEuLaDsWVNMLkS9GJnY+5DnrNEQNN1z+ lbUQ==
X-Received: by 10.236.88.170 with SMTP id a30mr13473673yhf.85.1372731746537; Mon, 01 Jul 2013 19:22:26 -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 d68sm37405824yhk.7.2013.07.01.19.22.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 19:22:25 -0700 (PDT)
Message-ID: <51D23955.8030902@gmail.com>
Date: Mon, 01 Jul 2013 19:22:13 -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: John Levine <johnl@taugh.com>
References: <20130702013302.14968.qmail@joyce.lan>
In-Reply-To: <20130702013302.14968.qmail@joyce.lan>
Content-Type: text/plain; charset="UTF-8"; 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 02:22:28 -0000

On 7/1/2013 6:33 PM, John Levine wrote:
>> A working group is for technical work.  We've solicited suggestions for
>> incremental technical work at least twice in two forums and there has
>> been no constituency developed for any near-term work.  If you know of
>> work to be done and can develop community support for it, please,
>> please, please document it.
>
> If reviewing the spec is off the table,

That's not what I said.


 > I don't see any work other
 > than cleaning up the BCP.

If you mean the "Using" draft, it needs considerably more than cleaning up.


> Since the dmarc.org group seems to have a working process to write
> drafts adequate to publish using member employees and consultants, I
> see no reason for the IETF to invest volunteer cycles on it.

Sorry you are not a fan of the individual submission path for the IETF 
stream.

Oh, wait:

    RFC 6713
    RFC 6143
    RFC 5518

These appear to be RFCs you authored that were through the IETF's 
individual submission path and RFC 5518 (VBR) appears to be Proposed 
Standard.

So now I'm confused about what your objection is.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net