Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dmarcbis-07.txt
Scott Kitterman <sklist@kitterman.com> Tue, 19 April 2022 04:00 UTC
Return-Path: <sklist@kitterman.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 4F73B3A10DA for <dmarc@ietfa.amsl.com>; Mon, 18 Apr 2022 21:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=oZ2sXGj4; dkim=pass (2048-bit key) header.d=kitterman.com header.b=j1f80je+
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 XMjClXReFJQu for <dmarc@ietfa.amsl.com>; Mon, 18 Apr 2022 21:00:24 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C3683A10BE for <dmarc@ietf.org>; Mon, 18 Apr 2022 21:00:24 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id E917AF801DB for <dmarc@ietf.org>; Tue, 19 Apr 2022 00:00:19 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1650340819; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=HAib8/XK7ZzYdy9ID+JguJvCEAdK5S0swJyeQd7C2+Q=; b=oZ2sXGj49ok2l8P3+OgD1sUdiWeOiDYJegfU9VfRda6w+8EyXDizaaMHhUCJjcuZ9bi0W TFD+VS9JFycAk3cDQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1650340819; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=HAib8/XK7ZzYdy9ID+JguJvCEAdK5S0swJyeQd7C2+Q=; b=j1f80je+sN1p8V+KjH11rIBf4tfWs0CIaNR/wyXMhyIqE10Dh3htzynrDnt0jMl89Odwn KhY6XAmE/0BMcHsHu4fKyp+h1w/HXi59KU+BALRdiiLe35ueZUlWdf8meMWtEae84fGe9yH ApZ7MQiOuT7mw0cUh/6JTPAHKmLqFz/veqrnROIxWwH2vPHkmh4yYveoP5+BoHLKY2Jk8e8 cKP0XJ1IDN9it6YTJr9tq3EEClGg8HP1HSojoJGYf1jZ5ugDAjNpMyQq9ArQqshT8YW2DOP On7UUWEv7Q0peg2rCBiuLiZcLMtABr55MDR2yq/QHJWnlN9CERdO0fiXSrOA==
Received: from zini-1880.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id AD25AF802DD for <dmarc@ietf.org>; Tue, 19 Apr 2022 00:00:19 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Tue, 19 Apr 2022 00:00:19 -0400
Message-ID: <1763264.1lysBax9Yy@zini-1880>
In-Reply-To: <CAH48Zfwqnbr2qyBkorQMtH+SkJk8U5P=Ns6ygmk1BApdGdUHvg@mail.gmail.com>
References: <164925666278.4445.13789431014958416691@ietfa.amsl.com> <4266119.zEdeCrfD3z@zini-1880> <CAH48Zfwqnbr2qyBkorQMtH+SkJk8U5P=Ns6ygmk1BApdGdUHvg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/KZn-btsZGAA33xbKAjzHrpHI-R8>
Subject: Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dmarcbis-07.txt
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: Tue, 19 Apr 2022 04:00:31 -0000
On Monday, April 18, 2022 10:14:37 PM EDT Douglas Foster wrote: > Concern 1 > Of the several thousand private registry domains listed in the PSL, 45 have > DMARC policies at or above the registry point. 40 of these 45 specify > relaxed alignment for both DKIM and SPF. Upon activation of the tree walk, > these policies will be treated as organizational domains to any private > registry clients that have not published their own psd=y policy. Because > of relaxed alignment, these private registry clients will be able to > impersonate their siblings and parents and produce a DMARC result of PASS. Please provide your list of ones you think might be problematic. > Concern 2 > Since the longest current PSL entry has 5 segments, the longest > organizational domain is 6 segments. The "jump to 5" logic needs to be > changed to "jump to 6". What PSL entries that are 5 long are you worried about? When we looked at this before, 5 seemed sufficient. Changing the number, now, isn't a big deal. > Concern 3 > The "psd=u" language is inconsistent. Which is true? > "This token indicates that this policy is not an organizational domain,, > the organizational domain is above this point" > or > "This token indicates no usable information, proceed with the heuristic to > determine if this policy is the organizational domain" It should be the latter. If we're inconsistent, please propose corrected text. Scott K > Doug Foster > > On Sun, Apr 17, 2022 at 4:54 PM Scott Kitterman <sklist@kitterman.com> > > wrote: > > I've finished going through this and also updated authheaders [1] to > > match. It > > now has a script called dmarc-policy-find which you can used to determine > > the > > DMARC policy to be applied for a domain. You can use RFC 7489, RFC 7489 + > > RFC > > 9091, and DMARCbis-07. > > > > It does currently cheat and assume psd=y is in the records for domains on > > the > > PSD DMARC registry list, since no one has actually published that yet. > > > > Scott K > > > > [1] https://github.com/ValiMail/authentication-headers (also on pypi) > > > > On Wednesday, April 6, 2022 12:27:04 PM EDT Scott Kitterman wrote: > > > I believe it does. > > > > > > Thanks, > > > > > > Scott K > > > > > > On April 6, 2022 2:53:59 PM UTC, Todd Herr > > > > <todd.herr=40valimail.com@dmarc.ietf.org> wrote: > > > >I believe this rev has the proposed text that was submitted in various > > > >messages in the thread titled "*5.5.4. Publish a DMARC Policy for the > > > >Author Domain - dmarcbis-06"* > > > > > > > >On Wed, Apr 6, 2022 at 10:51 AM <internet-drafts@ietf.org> wrote: > > > >> A New Internet-Draft is available from the on-line Internet-Drafts > > > >> directories. > > > >> This draft is a work item of the Domain-based Message Authentication, > > > >> Reporting & Conformance WG of the IETF. > > > >> > > > >> Title : Domain-based Message Authentication, > > > > Reporting, > > > > > >> and Conformance (DMARC) > > > >> > > > >> Authors : Todd M. Herr > > > >> > > > >> John Levine > > > >> > > > >> Filename : draft-ietf-dmarc-dmarcbis-07.txt > > > >> Pages : 62 > > > >> Date : 2022-04-06 > > > >> > > > >> Abstract: > > > >> This document describes the Domain-based Message Authentication, > > > >> Reporting, and Conformance (DMARC) protocol. > > > >> > > > >> DMARC permits the owner of an email author's domain name to enable > > > >> verification of the domain's use, to indicate the Domain Owner's > > > >> or > > > >> Public Suffix Operator's message handling preference regarding > > > > failed > > > > > >> verification, and to request reports about use of the domain name. > > > >> Mail receiving organizations can use this information when > > > > evaluating > > > > > >> handling choices for incoming mail. > > > >> > > > >> This document obsoletes RFC 7489. > > > >> > > > >> The IETF datatracker status page for this draft is: > > > >> https://datatracker.ietf.org/doc/draft-ietf-dmarc-dmarcbis/ > > > >> > > > >> There is also an HTML version available at: > > > >> https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-07.html > > > >> > > > >> A diff from the previous version is available at: > > > >> https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-dmarcbis-07 > > > >> > > > >> Internet-Drafts are also available by rsync at rsync.ietf.org: > > > >> :internet-drafts > > > >> > > > >> _______________________________________________ > > > >> dmarc mailing list > > > >> dmarc@ietf.org > > > >> https://www.ietf.org/mailman/listinfo/dmarc > > > > > > _______________________________________________ > > > dmarc mailing list > > > dmarc@ietf.org > > > https://www.ietf.org/mailman/listinfo/dmarc > > > > _______________________________________________ > > dmarc mailing list > > dmarc@ietf.org > > https://www.ietf.org/mailman/listinfo/dmarc
- [dmarc-ietf] I-D Action: draft-ietf-dmarc-dmarcbi… internet-drafts
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Todd Herr
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Douglas Foster
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Robert
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Todd Herr
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… John Levine
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Douglas Foster
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Douglas Foster
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Douglas Foster
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… John Levine
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Barry Leiba
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Douglas Foster
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Robert
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Todd Herr
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Todd Herr
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Robert
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Scott Kitterman
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Todd Herr
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Les Barstow
- Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dma… Les Barstow
- Re: [dmarc-ietf] cleaning up the ABNF, was I-D Ac… John Levine