On Mon, Jan 2, 2023 at 3:04 PM Evan Burke <[email protected]> wrote:
> > > On Sat, Dec 31, 2022 at 10:44 PM Wei Chuang <weihaw= > [email protected]> wrote: > > I'm worried about duplicating work unnecessarily as the M3AAWG has an > email authentication BCP. If the WG to-be indeed does want to generate the > BCP, perhaps the M3AAWG document can be the basis for an IETF document > assuming M3AAWG is okay with that, or the WG can partner with M3AAWG to > produce a common document. I think both are possible as there's a fair > amount of people overlapping between the IETF and M3AAWG, and I know that > M3AAWG organizationally wants to help here. > > I believe there's a revision underway for the general M3AAWG auth BCP doc, > which will include a handful of sender-focused recommendations for reducing > the viability of replay attacks. There is also a DKIM replay specific M3 > BCP doc in progress with more in-depth recommendations. > > Evan is correct on this point; there is a revision underway for the general M3AAWG auth BCP doc, for some values of "underway", anyway. I'm the person who's taken on the responsibility for authoring said revisions, but I've been waiting for the M3AAWG DKIM Replay work to produce something tangible to ensure that what I write doesn't conflict with that work. -- *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.
_______________________________________________ Ietf-dkim mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-dkim
