[dmarc-ietf] [Technical Errata Reported] RFC8601 (6026)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 22 March 2020 01:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8194F3A08C2 for <dmarc@ietfa.amsl.com>; Sat, 21 Mar 2020 18:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id CXzmZU-w4his for <dmarc@ietfa.amsl.com>; Sat, 21 Mar 2020 18:17:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C6983A08C1 for <dmarc@ietf.org>; Sat, 21 Mar 2020 18:17:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 67235F4071C; Sat, 21 Mar 2020 18:17:21 -0700 (PDT)
To: superuser@gmail.com, barryleiba@computer.org, aamelnikov@fastmail.fm, adam@nostrum.com, superuser@gmail.com, seth@sethblank.com, tjw.ietf@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ietf@johnlevine.com, dmarc@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20200322011721.67235F4071C@rfc-editor.org>
Date: Sat, 21 Mar 2020 18:17:21 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/q9j8ALn53etI2oyyPSztD5FEQj8>
X-Mailman-Approved-At: Sat, 21 Mar 2020 18:32:42 -0700
Subject: [dmarc-ietf] [Technical Errata Reported] RFC8601 (6026)
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: Sun, 22 Mar 2020 01:17:30 -0000

The following errata report has been submitted for RFC8601,
"Message Header Field for Indicating Message Authentication Status".

You may review the report below and at:

Type: Technical
Reported by: John Levine <ietf@johnlevine.com>

Section: 2.2

Original Text
     resinfo = [CFWS] ";" methodspec [ CFWS reasonspec ]
               [ CFWS 1*propspec ]

Corrected Text
     resinfo = [CFWS] ";" methodspec [ CFWS reasonspec ]
               *( CFWS propspec )

When there is more than one propspec, they are separated by spaces. Every implementation I know puts in the spaces. This was correct in RFC 7601, but see unconfirmed erratum 5435 which introduced the mistake.

While we're at it, take out the [CFWS] at the end of the definition of pvalue which is redundant and confusing.

This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

RFC8601 (draft-ietf-dmarc-rfc7601bis-06)
Title               : Message Header Field for Indicating Message Authentication Status
Publication Date    : May 2019
Author(s)           : M. Kucherawy
Category            : PROPOSED STANDARD
Source              : Domain-based Message Authentication, Reporting & Conformance
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG