Issue 129 is already open to discuss all existing RFC 7489 Errata in DMARCbis
On Mon, Mar 11, 2024 at 12:40 PM Eliot Lear <l...@lear.ch> wrote: > FYI > > -------- Forwarded Message -------- > Subject: [Errata Held for Document Update] RFC7489 (7835) > Date: Mon, 11 Mar 2024 09:34:11 -0700 (PDT) > From: RFC Errata System <rfc-edi...@rfc-editor.org> > <rfc-edi...@rfc-editor.org> > To: giuse...@ohpe.it, superu...@gmail.com, zwi...@yahoo-inc.com > CC: rfc-...@rfc-editor.org, rfc-...@rfc-editor.org, > rfc-edi...@rfc-editor.org > > The following errata report has been held for document update for RFC7489, > "Domain-based Message Authentication, Reporting, and Conformance (DMARC)". > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7835 > > -------------------------------------- > Status: Held for Document Update > Type: Technical > > Reported by: Giuseppe Trotta <giuse...@ohpe.it> <giuse...@ohpe.it> > Date Reported: 2024-03-04 > Held by: Eliot Lear (ISE & Editorial Board) > > Section: 6.6.3 > > Original Text > ------------- > 2. Records that do not start with a "v=" tag that identifies the > current version of DMARC are discarded. > > 3. If the set is now empty, the Mail Receiver MUST query the DNS for > a DMARC TXT record at the DNS domain matching the Organizational > Domain in place of the RFC5322.From domain in the message (if > different). This record can contain policy to be asserted for > subdomains of the Organizational Domain. A possibly empty set of > records is returned. > > 4. Records that do not start with a "v=" tag that identifies the > current version of DMARC are discarded. > > Corrected Text > -------------- > 2. Records that do not start with a "v=" tag that identifies the > current version of DMARC are discarded. > > 3. If the set is now empty, the Mail Receiver MUST query the DNS for > a DMARC TXT record at the DNS domain matching the Organizational > Domain in place of the RFC5322.From domain in the message (if > different). This record can contain policy to be asserted for > subdomains of the Organizational Domain. A possibly empty set of > records is returned. > > Notes > ----- > The intent of the original text is that indeed step 2 should be repeated > as follows: > (1) Go get a set of things. > (2) Filter them. > (3) If the set is now empty, go get a set of things from a different > location. > (4) Filter them. > > At the time of this writing, draft-ietf-dmarc-dmarcbis is being developed, > and so that text may clarify this point. As such we will hold this erratum > for update. > > -------------------------------------- > RFC7489 (draft-kucherawy-dmarc-base-12) > -------------------------------------- > Title : Domain-based Message Authentication, Reporting, and Conformance > (DMARC) > Publication Date : March 2015 > Author(s) : M. Kucherawy, Ed., E. Zwicky, Ed. > Category : INFORMATIONAL > Source : INDEPENDENT > Area : N/A > Stream : INDEPENDENT > Verifying Party : ISE & Editorial Board > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc > -- Todd Herr | Technical Director, Standards & Ecosystem Email: todd.h...@valimail.com Phone: 703-220-4153 This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
