Yes absolutely, I'd love to talk about From rewriting and when to do it. I also want to talk about NULL body recipes and authentication handling, because I think they're tied together pretty closely with an underlying question of "how can we make it not misleading without forcing a re-writer to throw away the existing DKIM2 history".
Bron. On Mon, Nov 9, 2026, at 17:10, Wei Chuang wrote: > While this might be folded into Richard's spec presentation, can we > explicitly discuss the From header rewriting? My gut feeling is that it was > coming to a resolution, but I would like to test that at the meeting. > -Wei > > On Mon, Nov 9, 2026 at 2:02 PM Murray S. Kucherawy <[email protected]> > wrote: >> On Fri, Oct 16, 2026 at 1:41 PM Murray S. Kucherawy <[email protected]> >> wrote: >> > Similarly, since IETF 127 is about a month away, we will also need an >> > agenda for that meeting. We can use "TBD" for the agenda until the >> > interim, but the call is now open for topics we should ensure we >> > discuss in person (if the interim doesn't resolve them). >> >> What agenda items do people have for 127, other than the following? >> >> * Administrivia (chairs) >> * draft-ietf-dkim-dkim2-spec (Richard) >> * draft-ietf-dkim-dkim2-dns (Wei) >> * AOB (TBD) >> >> Also, how much time do the presenters need? We have a two hour block >> on Tuesday. >> >> FYI, the chairs think we should aim to start WGLC on the "spec" >> document after we meet in San Francisco, though if there are still >> significant open issues we can of course defer that. >> >> -MSK >> _______________________________________________ >> Ietf-dkim mailing list -- [email protected] >> To unsubscribe send an email to [email protected] > _______________________________________________ > Ietf-dkim mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC [email protected]
_______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
