Re: [dmarc-ietf] Nitpicky questions about DMARC record syntax

"John Levine" <johnl@taugh.com> Thu, 17 January 2019 16:53 UTC

Return-Path: <johnl@iecc.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 D1442130EAB for <dmarc@ietfa.amsl.com>; Thu, 17 Jan 2019 08:53:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=DPjAo8/o; dkim=pass (1536-bit key) header.d=taugh.com header.b=aABF58UO
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 1ZHm1YSUdV1F for <dmarc@ietfa.amsl.com>; Thu, 17 Jan 2019 08:53:19 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96312130EA0 for <dmarc@ietf.org>; Thu, 17 Jan 2019 08:53:19 -0800 (PST)
Received: (qmail 54548 invoked from network); 17 Jan 2019 16:53:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=d512.5c40b2fe.k1901; bh=VFos/77HqdthkwKEjr9Qtf6cm+KEsA2+z9Rqv+pDGYw=; b=DPjAo8/o3mU30FnFUFwk70GpJouY+EK/WiQzbDfKJxLYKXsGhnd21LP0Jya9hCGni83eeWdVgOJhdeZ56sYF9AKm7EOj80qawSqOeUgf0df7PYxgvuV1YUSnlhnM86fJGvu5jwlEV7RZLAQ13di6yfSz7Jr13bU5P4/rABy65+q/1C1YfIw2/+bzVbDEKrbFQ5KI3MlTh5YISxzz74EOouOgm09KdnO49GD9j5PBvE3qXiubCpJ8RmffPgfnKp3k
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=d512.5c40b2fe.k1901; bh=VFos/77HqdthkwKEjr9Qtf6cm+KEsA2+z9Rqv+pDGYw=; b=aABF58UODIySn/D9F68rtXwiVQFK16L67s7W3CU1sYHKxJOjE4R7NZFHvJF/khqqWiGoyV2bg0nTFLfQafN4nbk6m5Owpv9O/WRhF3pL1lTLZ0fht9B1h0DHROEkfE/F3T1z8+/q0B/XuuzeQcbGkacYtgUeBOgbB972IZwdDA5bhsYnWIPRMVWJfC5d00E4rBbNSdu2XPpe7MEzF32U3w7qxnslwI8GvFQWTn7+85MCwaUUVig4aLF5x6X5DI1+
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 17 Jan 2019 16:53:18 -0000
Received: by ary.qy (Postfix, from userid 501) id E79D7200CD8A31; Thu, 17 Jan 2019 11:53:17 -0500 (EST)
Date: 17 Jan 2019 11:53:17 -0500
Message-Id: <20190117165317.E79D7200CD8A31@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: gtaylor@tnetconsulting.net
In-Reply-To: <43ae9a84-75e3-1292-d3f4-68f3a74458a3@spamtrap.tnetconsulting.net>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/I3HO1oPYFxDPgWwfjC70wHoNQ7o>
Subject: Re: [dmarc-ietf] Nitpicky questions about DMARC record syntax
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 17 Jan 2019 16:53:22 -0000

In article <43ae9a84-75e3-1292-d3f4-68f3a74458a3@spamtrap.tnetconsulting.net> you write:
>However I still feel like /requiring/ exact case is contrary to the idea 
>of "Be liberal in what you accept and conservative in what you send.".

Yup.  See

https://datatracker.ietf.org/doc/html/draft-iab-protocol-maintenance

a/k/a "Postel was wrong".

>I don't see any security implications in accepting the following:
>
>dmarc-version = ("v" / "V") *WSP "=" *WSP ("D" / "d") ("M" / "m") ("A" / 
>"a") ("R" / "r") ("C" / "c") "1"

Please see the previous several dozen messages, particularly the one
about the brown M&M's.  If you know that someone didn't read the spec,
you can only guess what else they got wrong, and you're not doing
anyone a favor by doing that.

>I agree that this is contrary to the letter of the specification. 
>However I think it is completely within the spirit.  Especially when 
>dealing with DNS data which is inherently / invariable human entered.

Once again, please try not to assume that everyone's experience is the
same as yours.  On my DNS server, the DMARC records are generated
automatically when I add a new mail domain and their syntax is
correct.  (Or every DMARC record is wrong, but I would notice that
pretty soon.)  On the large systems which these days host most mail
it's hard to see how they could do it manually.

R's,
John