IETF Logo Mail Archive

Re: [dmarc-ietf] Guidance around constructing an AAR when multiple AR headers are present?

"John R Levine" <johnl@taugh.com> Thu, 25 May 2017 00:27 UTC

Return-Path: <johnl@taugh.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 22341129353 for <dmarc@ietfa.amsl.com>; Wed, 24 May 2017 17:27:13 -0700 (PDT)
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, SPF_PASS=-0.001, URIBL_BLOCKED=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=f/LwLG+y; dkim=pass (1536-bit key) header.d=taugh.com header.b=wgqx4iY3
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 DWVEd9OXUG85 for <dmarc@ietfa.amsl.com>; Wed, 24 May 2017 17:27:11 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93E2D120724 for <dmarc@ietf.org>; Wed, 24 May 2017 17:27:11 -0700 (PDT)
Received: (qmail 28136 invoked from network); 25 May 2017 00:27:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=6de6.592624de.k1705; bh=KRlkyQ5ptzcVLht+ozUxZ31nKN91bBO1MEneg+Eqf7o=; b=f/LwLG+yDBjtkxckpssOPgxnaXilm35XLvE8v5L7b/QI0AnBjlDpcm0eotvzogLQws/j1t004zrdP35TZgC/BHp9ZeOFDndnKr5a4/xtLZ7KbOwmhETz/XPfVj4t39hVmteeed8cfFYNbhQgKHiZ2Y/dpye109OkzXzKcETMaREJgPN4qB9dRc64p6YqDCFLjVIax4nY32B3UCrP9VBx0sroE8S/kME7j4N/LzdhZ4G2oJ+Cd9Kxk4lfWgTslfvs
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=6de6.592624de.k1705; bh=KRlkyQ5ptzcVLht+ozUxZ31nKN91bBO1MEneg+Eqf7o=; b=wgqx4iY3h6lvsnru6N6V1WilfBGiyuJ/No8kueX6qKFglMLU3D6mWzWBGI8urnPsjSYRz+yjF/JQJdNl35sofsrdDjrfoBarUftOwA9rSuo5SMOut/wPvO9mNr1T114RYjNleHBy1QrrvS8ZZBBcKbWrw1vC16fzePt7Pd/EWP0Y4UuS99sInLQUlnmSLNO1PSX0aq1wrvlSG4XeVvQVgC+BBeRlebYLEnxLcWZbU45gITbb6K8JIx9PM8LoAgmx
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 25 May 2017 00:27:10 -0000
Date: Wed, 24 May 2017 20:27:09 -0400
Message-ID: <alpine.OSX.2.21.1705242026410.29429@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Brandon Long <blong@google.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
In-Reply-To: <CABa8R6s22u8E6zn5sBOc1C4B6kyLk8L7YaYnsz3VVHukm7CWFA@mail.gmail.com>
References: <CAOZAAfOsRrQF2M3NzcB3h2Tc03mtFfG8mOJ0pqU+_cx=whcBLQ@mail.gmail.com> <20170524192617.36732.qmail@ary.lan> <CABa8R6v4oGpFYeO8qGaKpbocr6f8V_+Hf7XavZ0h12d1RgWLBQ@mail.gmail.com> <CAOZAAfOrHku8x9UmxtkFNpRPdfgAzn2B2Kq6=Wngwk7bY1YpWw@mail.gmail.com> <alpine.OSX.2.21.1705241941430.29429@ary.qy> <CABa8R6s22u8E6zn5sBOc1C4B6kyLk8L7YaYnsz3VVHukm7CWFA@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1GzUssWcRMfzTyZbRqXZ9H6EdNw>
Subject: Re: [dmarc-ietf] Guidance around constructing an AAR when multiple AR headers are present?
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.22
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, 25 May 2017 00:27:13 -0000

>> Seems reasonable, give or take a word or two to make it clear we're just
>> talking about the ones for the current hop.
>
> There should only be the ones from the current hop if the admd is stripping
> previously existing ones prior to adding any new ones per the authres rfc.

I meant not to use a-r with different admds.  Should be obvious, but you 
never know.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email