Re: [Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)

2023-02-02 Thread Wei Chuang
On Tue, Jan 31, 2023 at 7:23 PM Murray S. Kucherawy wrote: > On Tue, Jan 31, 2023 at 2:12 PM Michael Thomas wrote: > >> Also: the date on the problem statement seems awfully aggressive. My >> thinking is that the problem statement should at least discuss (as is >> mentioned in the charter) how

Re: [Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)

2023-01-31 Thread Murray S. Kucherawy
On Tue, Jan 31, 2023 at 2:12 PM Michael Thomas wrote: > Also: the date on the problem statement seems awfully aggressive. My > thinking is that the problem statement should at least discuss (as is > mentioned in the charter) how "replays" are completely legitimate uses > of DKIM, and thus limit

Re: [Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)

2023-01-31 Thread Michael Thomas
Also: the date on the problem statement seems awfully aggressive. My thinking is that the problem statement should at least discuss (as is mentioned in the charter) how "replays" are completely legitimate uses of DKIM, and thus limit the solution space to not break those uses. Also: I hope

[Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)

2023-01-31 Thread Lars Eggert via Datatracker
Lars Eggert has entered the following ballot position for charter-ietf-dkim-04-05: Block When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with