Re: [Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Barry Leiba
As someone who has, as an AD, questioned the publication of such background documents, even in working groups I chartered, I can give a related opinion about this one: I do think the background is important to publish separately for this work, however easy the problem is to describe. I think it's

Re: [Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Murray S. Kucherawy
On Tue, Aug 1, 2023 at 8:29 AM Laura Atkins wrote: > We have a current version of the draft problem statement available on the > data tracker. Murray and a few others made a few comments that were added > in the -03 version. > > > https://mailarchive.ietf.org/arch/msg/ietf-dkim/Q5ybHiYkMlg5QFaFp2

Re: [Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Tim Wicinski
Problem Statements may be published but are more importantly considered working documents with consensus from the working group. We should get more "what didn't work" - people should send text ! tim On Tue, Aug 1, 2023 at 12:01 PM Dave Crocker wrote: > On 8/1/2023 8:56 AM, Barry Leiba wrote:

Re: [Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Dave Crocker
On 8/1/2023 8:56 AM, Barry Leiba wrote: The eventual product should point back to the problem statement for the background information. That is certainly a valid approach.  However I suggest it's less efficient for this topic and possibly will lose some casual readers of the spec, by virtue o

Re: [Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Barry Leiba
I would prefer to see the "what hasn't worked" stuff as part of the problem statement, as those things will inform the work we do so they need to be documented up front, and they will not be part of the product of what we do so it doesn't make sense to include them later. The eventual product shoul

Re: [Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Dave Crocker
On 8/1/2023 8:28 AM, Laura Atkins wrote: Based on discussions, there seems to be favor to documenting what has been tried and not worked. Question for the working group: Should the discussion of what hasn’t worked be in the problem statement as an Appendix? Or should it be in a separate do

[Ietf-dkim] Call for adoption results: draft-ietf-dkim-replay-problem Adopted

2023-08-01 Thread Laura Atkins
Hi, All, We have a current version of the draft problem statement available on the data tracker. Murray and a few others made a few comments that were added in the -03 version. https://mailarchive.ietf.org/arch/msg/ietf-dkim/Q5ybHiYkMlg5QFaFp28Y8uSme1Q/ Based on discussions, there seems to be