I have closed the subject ticket and incorporated relevant text changes in draft-ietf-dmarc-dmarcbis-02, which will be published on Datatracker as soon as the chairs have a chance to do so.
The relevant text changes here include clarification of the meaning of the pct tag as well as a much longer discussion of message sampling and the limitations inherent in the application of the pct tag. The text changes all fall under the umbrella of "proposed text", and I expect there will be further discussion of the topic. On Fri, Jun 4, 2021 at 4:00 PM Tim Wicinski <[email protected]> wrote: > +1 With Mr Levine's line of thinking. > > I also agree with keeping pct= tag. > > tim > > > On Thu, Jun 3, 2021 at 7:16 PM Dotzero <[email protected]> wrote: > >> >> >> On Thu, Jun 3, 2021 at 6:17 PM John Levine <[email protected]> wrote: >> >>> It appears that Alessandro Vesely <[email protected]> said: >>> >On Thu 03/Jun/2021 05:45:33 +0200 Murray S. Kucherawy wrote: >>> >> I don't understand what "demeaning a domain's policy" means. >>> > >>> >I meant to say that p=quarantine; pct=0 is to be considered a strict >>> policy to >>> >all effects. Saying so should prevent reasoning something like "Oh, >>> they said >>> >quarantine, but since pct=0 it is somewhat faked, so I'll skip X", >>> where X >>> >could be rewriting From:, displaying a BIMI image, record aggregate >>> data, or >>> >any other action that might depend on the policy. That is to say pct=0 >>> does >>> >not alter the value of p=, otherwise testing becomes a nightmare. >>> >>> If we agree that's what we mean, that's what we should say, e.g., add >>> something >>> like this: >>> >>> Senders may use pct=0 to signal an intention to apply a stricter >>> DMARC policy in the future, and to request receivers that do special >>> processing based on DMARC policy to do that processing. Examples of >>> special processing might include mailing list software rewriting >>> addresses in From headers. >>> >> >> As long as we get the wording right, I agree with your line of thinking >> John. Again, we don't have insight as to the extent that receivers will >> honor the request. >> >> Michael Hammer >> _______________________________________________ >> dmarc mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/dmarc >> > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc > -- *Todd Herr* | Technical Director, Standards and Ecosystem *e:* [email protected] *m:* 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 [email protected] https://www.ietf.org/mailman/listinfo/dmarc
