Re: Options for temporary operational solution to DMARC problem

Dave Crocker <dcrocker@gmail.com> Sun, 06 November 2016 22:23 UTC

Return-Path: <dcrocker@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D73129565 for <ietf@ietfa.amsl.com>; Sun, 6 Nov 2016 14:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Dk8dPF9mr2n for <ietf@ietfa.amsl.com>; Sun, 6 Nov 2016 14:23:09 -0800 (PST)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E7E812949A for <ietf@ietf.org>; Sun, 6 Nov 2016 14:23:09 -0800 (PST)
Received: by mail-pf0-x235.google.com with SMTP id n85so80615217pfi.1 for <ietf@ietf.org>; Sun, 06 Nov 2016 14:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:references:reply-to:to:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ml4OgA9AuGAlOH3ozcscpKer8yJc8aYpC38Q7XBFR8s=; b=HJMibgzMMJ8NRSIuKI+6L7q/SUhKkyA3a7I3MwVVkFJf8O1zdLS8fuvF4Roi1U6ksF Dwno9MamoKnpw3VjVLnOMHGAyBdDNH8aG5cF8mJ7vzpUxT92SQRvikZ8CsoHGmNtCY7R eX5MOp9dGkq82vnjZrea5vDXg9nuovMYCi8ZQAqCQxn+vSKUlXg42LWQD3vcrrsv3YSY VHj4vaU9sNWguX1K3e/kpYnUU0jnIMUC5PFnZEZm+p4MYKhszWrXCt+ZmHZLiyiSxnr+ tlyc/cb1Y0XvYAOmuEQgOv3qcCc/QomOXg5JIsW87o+k4eAZHOeOw+88Xy+TTdGKGF6Q rE6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:references:reply-to:to:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Ml4OgA9AuGAlOH3ozcscpKer8yJc8aYpC38Q7XBFR8s=; b=Uks3QiTgyQBgojravKVx+X8662ThfGBaP+4o0vG5dt6tjUJEblx0OCYkERxuNARvaA Xlea7P6pDqpIA2tAjc0m1/+q7niW62TE6yELi8/cBRnD8RyAaUs64o5HXFYeTLK2Njwf TDi6sdrAkGuwRkNSTkgeTOE8cWjGnvyjZNTsBtED80BDF34oykjGEWtrRlNumHr/Vope xrPXqX4fMRHcA8vnx05Oj6Y442AbrqWQH8qKNPXfEwW3tfQqVnIaHakjNxgUu01+beuQ gcuMP2eKOywEoyUpwlGNWectiIpSYFpOWJ1rMX4nPkpcdrP3c8NbtltHlSmLwV+zp0qR y+hg==
X-Gm-Message-State: ABUngvc6FTZw3XZOO98NUMzgMuavwxd6ASV34VbU4EvRAH/K7QqjvegFdokImgj73XkrTg==
X-Received: by 10.99.136.194 with SMTP id l185mr6213290pgd.106.1478470560603; Sun, 06 Nov 2016 14:16:00 -0800 (PST)
Received: from ?IPv6:2602:304:cda0:8800:d0c4:5336:57f3:1e21? ([2602:304:cda0:8800:d0c4:5336:57f3:1e21]) by smtp.gmail.com with ESMTPSA id t20sm34966385pfk.48.2016.11.06.14.15.59 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Nov 2016 14:15:59 -0800 (PST)
From: Dave Crocker <dcrocker@gmail.com>
X-Google-Original-From: Dave Crocker <dhc@dcrocker.net>
Subject: Re: Options for temporary operational solution to DMARC problem
References: <20161104024822.74577.qmail@ary.lan> <10589.1478470261@obiwan.sandelman.ca>
To: ietf@ietf.org
Organization: Brandenburg InternetWorking
Message-ID: <fa7eccd1-7c04-b54e-c9b6-cec73375637f@dcrocker.net>
Date: Sun, 06 Nov 2016 14:15:53 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <10589.1478470261@obiwan.sandelman.ca>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qf5__LEWXNgws1A-f5jTl7a5wCM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Nov 2016 22:23:12 -0000

On 11/6/2016 2:11 PM, Michael Richardson wrote:
> We've had serious problems for 2 + years, and we've been told "wait a few
> months" multiple times now.


It has been oddly amusing to watch experienced IETF folk make 
recommendations based on that sort of timeframe, for work that was, at 
the time, only just starting (outside of the IETF) and even now is only 
just underway.

Given the realities of IETF processes and, worse, the realities of 
production implementation at scale, anyone thinking in terms of small 
numbers of months is fooling themselves.


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net