IETF Logo Mail Archive

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

Dave Crocker <dcrocker@gmail.com> Wed, 16 January 2019 15:38 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 30013130E57 for <dmarc@ietfa.amsl.com>; Wed, 16 Jan 2019 07:38:37 -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 99yg8sPYg_0t for <dmarc@ietfa.amsl.com>; Wed, 16 Jan 2019 07:38:34 -0800 (PST)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (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 4A9AB1200D7 for <dmarc@ietf.org>; Wed, 16 Jan 2019 07:38:34 -0800 (PST)
Received: by mail-ot1-x32f.google.com with SMTP id 81so7957450otj.2 for <dmarc@ietf.org>; Wed, 16 Jan 2019 07:38:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=hDlwI/2CjZMa4+S0lrxVEv3OG53zdU6HtMYArFBlD+0=; b=J1l7W68mc+lb7EYGPiZkpuXcJbBZx+S4F7XIPYuxZuH+dGkA9JTO0XTAXZJ6Kx9dqS GrG3Rd17DrGzbzgJcMAgErp4YJw4FlGCNUfaLYRXt8ZtqQMZICVNigcB2RmEr1Wq0gc4 0vh/F9zx6/t5BeaKA0ArlEbCHVw4lPPFhAc7AbRN43WvD17dOA2rWIw3xSucSK3yjmuY 2ZSoaeXouZdK5K6huGhW1XtoVtJvl2t69NyO8AvLXHYiIii5GO2pTcNrYWGTvX8F6uaw gw6aZ1ACzdwky1SPqLLb+46L298OLqJlAOaWVd/NDQLdUEwI1EAM8bsQRIAWou24qRM1 EX6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hDlwI/2CjZMa4+S0lrxVEv3OG53zdU6HtMYArFBlD+0=; b=DQ44BwCDo0KYZZikyQFLvXXOgjDqOKMZJ/mXoU1UKSBl02ulWDLpm3b3wh9FdAjOsa BplnaFziRSozQScSFo0uGjlDgbc1bKYOpRb2ZxQaGUpiLY04oVV1s3mEXzQ1aQHPFS6u fYn4I33HHsP4wgWEiVy1Ot1vQF+mdPtihaYEQYmz6Xyma7SvnhA0Kl1W83v8H8KhjSdn En4IxqsCelZlMOhXGN6PCoVSXlMaDyuYNIga6P2dlHoIaZhJpXq4WjXp7d2MoZeOpG90 u9sueXlV+FWtipKTfCKzrEaVTf2WqIrFVMcrPAB/rlTe3VdNj6sgtNGQczhxc4Axa6Cj RHzw==
X-Gm-Message-State: AJcUukeUVSHvv83JpnxCZX5LrAtr8DVprBhB+6eR3p9ABC3jCn/ivtsq 8+4F8lJYFvr8ePOwcQ0Jt3SleO8w
X-Google-Smtp-Source: ALg8bN4Vb+bFqZjJxEGG8P2cJULX3Ayc/76K0PgXsf1AdnvMXiRm5kkigEBre8Rv4gtOhghQK9L9Yw==
X-Received: by 2002:a9d:1d43:: with SMTP id m61mr6204313otm.170.1547653113242; Wed, 16 Jan 2019 07:38:33 -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 102sm2860605otj.65.2019.01.16.07.38.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 16 Jan 2019 07:38:32 -0800 (PST)
To: John R Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20190116005804.A0A80200CACDA9@ary.qy> <b6d9024b-8a88-66fb-cfe7-800ee463c01c@gmail.com> <alpine.OSX.2.21.1901161029520.36401@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <babe5ec6-9ceb-c7e1-1758-8dc20d116b55@gmail.com>
Date: Wed, 16 Jan 2019 07:38:29 -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: <alpine.OSX.2.21.1901161029520.36401@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tUL2VAxDb_iOo-p7KIgWBVaxOWk>
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:38:37 -0000

On 1/16/2019 7:30 AM, John R Levine wrote:
>> 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.
> 
> Thanks, but the white space in question is before the "v".


The ABNF rule I included, and the one that cites it (dmarc-record) do 
not show any white space permitted before the 'v', so no it's not legal.

So the formalities are quite clear on both your questions.

Whether there is benefit or detriment in making the parser more robust 
than the formal rules define goes to the heart of the last point in your 
original note.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email