Re: [dmarc-ietf] Fwd: [Editorial Errata Reported] RFC7489 (7835)

2024-03-07 Thread Todd Herr
On Wed, Mar 6, 2024 at 7:02 PM Murray S. Kucherawy wrote: > On Wed, Mar 6, 2024 at 11:42 AM Todd Herr 40valimail@dmarc.ietf.org> wrote: > >> The text reported in the erratum doesn't really exist in DMARCbis; it's >> been replaced by the DNS Tree Walk ( >>

Re: [dmarc-ietf] Fwd: [Editorial Errata Reported] RFC7489 (7835)

2024-03-06 Thread Murray S. Kucherawy
On Wed, Mar 6, 2024 at 11:42 AM Todd Herr wrote: > The text reported in the erratum doesn't really exist in DMARCbis; it's > been replaced by the DNS Tree Walk ( > https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-30.html#name-dns-tree-walk > ) > > Are we to issue an actual update to RFC

Re: [dmarc-ietf] Fwd: [Editorial Errata Reported] RFC7489 (7835)

2024-03-06 Thread Todd Herr
On Wed, Mar 6, 2024 at 1:10 PM Murray S. Kucherawy wrote: > Since we're in WGLC here, this erratum is worth consideration. I've > recommended "Held For Document Update" as the disposition. > > My reply to the erratum was: > > === > > The algorithm as presented is correct, but I understand this

[dmarc-ietf] Fwd: [Editorial Errata Reported] RFC7489 (7835)

2024-03-06 Thread Murray S. Kucherawy
Since we're in WGLC here, this erratum is worth consideration. I've recommended "Held For Document Update" as the disposition. My reply to the erratum was: === The algorithm as presented is correct, but I understand this report. The steps are, paraphrased: (1) Go get a set of things. (2)