Re: [dmarc-ietf] WGLC on draft-ietf-dmarc-arc-protocol-16

Steven M Jones <smj@crash.com> Sat, 04 August 2018 05:04 UTC

Return-Path: <smj@crash.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 38237130E21 for <dmarc@ietfa.amsl.com>; Fri, 3 Aug 2018 22:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=crash.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 24aqCngRvNVG for <dmarc@ietfa.amsl.com>; Fri, 3 Aug 2018 22:04:20 -0700 (PDT)
Received: from segv.crash.com (segv.crash.com [IPv6:2001:470:1:1e9::4415]) (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 A24C0130E07 for <dmarc@ietf.org>; Fri, 3 Aug 2018 22:04:20 -0700 (PDT)
Received: from [172.23.119.8] ([216.52.21.1]) (authenticated bits=0) by segv.crash.com (8.15.2/8.15.2/cci-colo-1.7) with ESMTPSA id w7454B4c004515 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dmarc@ietf.org>; Sat, 4 Aug 2018 05:04:20 GMT (envelope-from smj@crash.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 segv.crash.com w7454B4c004515
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=crash.com; s=201506-2k; t=1533359060; bh=2Ey707q4mPuNDN1nU9fj8RV7zsrq+8jB/pYJsthwK40=; h=From:Subject:To:References:Date:In-Reply-To; b=BE35r9GeCXa6L/c++yETVvyqZu7xjn8GISt/Bx3yGe7LTtaChN6HiQQmxGU7hlkyi iz2zYThgs21c/AKp+jI0+qSjDkPf6vWY1dmDHzQ8zyzrS9gegYh1jzjA2zsZFjMVVY nAyXkSSe3ahQxFR+rgUx+GJ6mXuD/r2lAvwSef6fw0aC7lkjdFCaDTXJerxauaU63I GZ4Z43KeviRh1F4+7zaWKtemVOXocLRgLT2wIeS+aHMXJHi2Urq7yHgeLpJfHxuAmb SqrIqW501E9FMaVMzXIJ7JEL4CKwyU7cDki768yc/6XagWy7MbapnDqLHijusmvLX1 rbuzKBu34ZOlQ==
X-Authentication-Warning: segv.crash.com: Host [216.52.21.1] claimed to be [172.23.119.8]
From: Steven M Jones <smj@crash.com>
To: dmarc@ietf.org
References: <CALaySJ+=OuyvCoivypLoKX_dznxi2xgqEJ1FKNniWDOT_3P+Rg@mail.gmail.com>
Message-ID: <3af55e32-b05f-76fb-4ab6-005ad0619530@crash.com>
Date: Fri, 03 Aug 2018 22:04:11 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+=OuyvCoivypLoKX_dznxi2xgqEJ1FKNniWDOT_3P+Rg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (segv.crash.com [72.52.75.15]); Sat, 04 Aug 2018 05:04:20 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ISs6dmG4YQxWVoWZiLyt6_-Ux-0>
Subject: Re: [dmarc-ietf] WGLC on draft-ietf-dmarc-arc-protocol-16
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 04 Aug 2018 05:04:22 -0000

It's been quite a while since my last full read-through of the spec, so 
apologies if I blunder into anything long-settled. And apologies if I'm 
repeating something from earlier commentary, I'm trying to get in under 
a very liberal interpretation of the deadline as is... ;)



Love the way Section 2 introduces and describes the basics.


Section 3.1 - I would suggest "the three header fields /from a 
particular Internet Mail Handler/ compose a single ARC Set." (Addition 
in /slashes/.) Best to be explicit that ARC sets are organized by 
(outdated term) ARC Intermediary. Or "Sealer," but that would be a 
forward reference...  But without this, the reader might be left 
scratching their head until Section 5.1 makes it clear that an ARC Set 
is created by a single entity.


Section 4.2 - I would suggest "An `ARC Set` is a single collection of 
three ARC Headers (AAR, AMS, and AS) /from a single ARC Sealer/." Same 
reasoning as previous.


Section 4.3 - Typo, "AS header fields allow messages handlers" - 
"messages" should lose the trailing "s" (or I suppose it could be 
modified to "allow a message's handlers" if that's what was intended...)


Section 5.2 Step 1 -- Because of the preceding reference to maximum 
number of ARC Sets, rephrase for clarity at the end, "In the following 
algorithm, the /highest instance value ("i=") present in the ARC being 
processed is referred to as `N.`/"



That's it. Great work -- what a long way this has come since oar-dev 
started up in 2014!
--Steve.