Re: [Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)
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 the solution space to not break those uses. > Milestones are negotiable, and the one(s) I used for this are largely dart throws. We can change them to be something more practical once chairs have been secured. -MSK ___ Ietf-dkim mailing list Ietf-dkim@ietf.org https://www.ietf.org/mailman/listinfo/ietf-dkim
Re: [Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)
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 the folks on the IESG have read at least a couple of the proposed drafts which link content and envelope. The prospect of that seems extremely frightening and I think there should be discussion at a meta level about whether that is even a valid approach. Frankly, I don't really see this as a DKIM specific issue and seems like it would have wider consequences if it were allowed. Mike On 1/31/23 1:18 AM, Lars Eggert via Datatracker wrote: 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 other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-dkim/ -- BLOCK: -- # GEN AD review of charter-ietf-dkim-04-05 CC @larseggert ## Discuss ### "A", paragraph 2 ``` The DKIM working group will first develop a clear problem statement, which it may choose to publish. ``` This seems super-unusual. Assuming this problem statement informs the following group work, it should be published? ### Chairs Who are the chairs? -- COMMENT: -- ## Comments ### "A", paragraph 8 ``` Apr 2023 - Post a consensus problem statement draft to the datatracker (may not go to the IESG) ``` See DISCUSS. ## Notes This review is in the ["IETF Comments" Markdown format][ICMF], You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT]. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments [IRT]: https://github.com/larseggert/ietf-reviewtool ___ Ietf-dkim mailing list Ietf-dkim@ietf.org https://www.ietf.org/mailman/listinfo/ietf-dkim ___ Ietf-dkim mailing list Ietf-dkim@ietf.org https://www.ietf.org/mailman/listinfo/ietf-dkim
[Ietf-dkim] Lars Eggert's Block on charter-ietf-dkim-04-05: (with BLOCK and COMMENT)
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 other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-dkim/ -- BLOCK: -- # GEN AD review of charter-ietf-dkim-04-05 CC @larseggert ## Discuss ### "A", paragraph 2 ``` The DKIM working group will first develop a clear problem statement, which it may choose to publish. ``` This seems super-unusual. Assuming this problem statement informs the following group work, it should be published? ### Chairs Who are the chairs? -- COMMENT: -- ## Comments ### "A", paragraph 8 ``` Apr 2023 - Post a consensus problem statement draft to the datatracker (may not go to the IESG) ``` See DISCUSS. ## Notes This review is in the ["IETF Comments" Markdown format][ICMF], You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT]. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments [IRT]: https://github.com/larseggert/ietf-reviewtool ___ Ietf-dkim mailing list Ietf-dkim@ietf.org https://www.ietf.org/mailman/listinfo/ietf-dkim
