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

Dave Crocker <dcrocker@gmail.com> Wed, 16 January 2019 15:05 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 D01E3130E74 for <dmarc@ietfa.amsl.com>; Wed, 16 Jan 2019 07:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 1bzCsIv3t-gA for <dmarc@ietfa.amsl.com>; Wed, 16 Jan 2019 07:05:14 -0800 (PST)
Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (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 CEEBB130E5B for <dmarc@ietf.org>; Wed, 16 Jan 2019 07:05:14 -0800 (PST)
Received: by mail-ot1-x329.google.com with SMTP id v23so7692072otk.9 for <dmarc@ietf.org>; Wed, 16 Jan 2019 07:05:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=VrOtcSf85d3LF1geQFJPDHjZBA3ZekeUpzXyEl3yVfk=; b=tzFiwXK3TGhmN9QqKx0LTLzQsDMBlIfuCDVWbStIi9opCjoC7vn6GrTRH/FYqD6N3u c7tF2GkO2ueyU7rjaHXeWwhIv0hPqXwupbh+GSQ9iF5TIMc8FNd8Z7IYSAH9VbVcA741 F9Q8MBzUg7NXlIzIGGYD1YSkKUucwSa7qXrTTTwbPMweBZT60Isdci7TCAvXK63fW1eI FafzVmb6NqOiX/DbbXM0TXz5b1ElspOjM87FfLoRJIUKTmMyNe3J2/9QLUaJHubiI48Y +QTsDZmmnxnl6N8pwEz2oTTLwve0pdAJly7kSVHWnvY9Ke7VZgKtVGLOHS1IJiz3SEx0 goUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=VrOtcSf85d3LF1geQFJPDHjZBA3ZekeUpzXyEl3yVfk=; b=Qt4HoJTKbXOO47OdPNshNzh3IfDoeeAh+zewse0mZz3MnmKRgRFLvkMZkYSZD/wxw0 1PyWj81W+2VUZ1J06cGW4NzCugNMB4qpR925yAd4YdWecYYG4AflzUa+LaMnLwahhNom +a2pmX9d6yIQCAIS+COcRGviZ51YJ98iPWNxAR+44qCDyF1ZqVOb8TszYzcFjYyq6/Cc 9ElcZL5+AwI4RUL57YIGhXOAAVJDHHib6zkA89XAHkfEeky4yE/Z5iTj6tV1a2Ml6JLn 0EHfUgfqp5CvoHNgvoBw7pbVflHq2PEBLTL3gDk6zWy40sWPN1XjJdPVAPyL17FYnia3 wB5A==
X-Gm-Message-State: AJcUukdTYzmVkw6bCKQ+Un8HU5KUjXgmbqkpEtV7nj6ME48cRMtBTBjL T7ZqnL+NtIMXYn9JOKiyd1qnwg4d
X-Google-Smtp-Source: ALg8bN7rVJS1x+ICbkwM5eiKU8DfMoOr1sNwzx+xlBZqt0rG7EKnkFJuwbbID2m9W5ITeEfGh/+clg==
X-Received: by 2002:a9d:f05:: with SMTP id 5mr5952981ott.123.1547651113657; Wed, 16 Jan 2019 07:05:13 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net. [76.218.8.128]) by smtp.gmail.com with ESMTPSA id 31sm6099519otw.55.2019.01.16.07.05.12 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 16 Jan 2019 07:05:12 -0800 (PST)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20190116005804.A0A80200CACDA9@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <b6d9024b-8a88-66fb-cfe7-800ee463c01c@gmail.com>
Date: Wed, 16 Jan 2019 07:05:10 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <20190116005804.A0A80200CACDA9@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/U8rv-iwG8w2h_Y5a4vRltcUNP8k>
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: Wed, 16 Jan 2019 15:05:17 -0000

On 1/15/2019 4:58 PM, John Levine wrote:
> I am staring at RFC 7489, and at a bunch of purported DMARC records
> (see previous message.)
> 
> The RFC says that all records must start with "v=DMARC1".  Is it OK
> if they start with "v=dmarc1"?  It says that record is a DKIM tag-value
> list, and the DKIM ABBF defines all the characters with hex escapes
> rather than letters which tells me that it's specifically saying
> that case matters.
> 
> How about if there's a space before the v=DMARC1?  The tag-value syntax
> allows FWS before the first tag, but 7489 says in several places


The formal specification is quite clear on both of your questions:

    Section 6.4:

    dmarc-version   = "v" *WSP "=" *WSP %x44 %x4d %x41 %x52 %x43 %x31


which means that the white space is required to be allowed and the value 
in this tag-value is case sensitive.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net