Re: [Ietf-dkim] What has been tried and doesn't work should be documented in the problem statement

> On Mar 26, 2023, at 1:11 PM, Michael Thomas wrote: > My contention is that documenting what has failed in the problem statement > saves time eventually in the solution space as you can reference it when > somebody brings it up as to why it doesn't work. It would be just a cut and > paste

Re: [Ietf-dkim] What has been tried and doesn't work should be documented in the problem statement

> On Mar 26, 2023, at 6:13 AM, Murray S. Kucherawy wrote: > > On Sat, Mar 25, 2023 at 10:29 AM Michael Thomas > wrote: >> On 3/24/23 6:19 PM, Barry Leiba wrote: >> > I don't agree with the premise. I think what was tried and didn't >> > work should be documented in the

Re: [Ietf-dkim] What has been tried and doesn't work should be documented in the problem statement

On 3/26/23 3:13 AM, Murray S. Kucherawy wrote: On Sat, Mar 25, 2023 at 10:29 AM Michael Thomas wrote: On 3/24/23 6:19 PM, Barry Leiba wrote: > I don't agree with the premise.  I think what was tried and didn't > work should be documented in the result that the working group comes

Re: [Ietf-dkim] What has been tried and doesn't work should be documented in the problem statement

On Sat, Mar 25, 2023 at 10:29 AM Michael Thomas wrote: > On 3/24/23 6:19 PM, Barry Leiba wrote: > > I don't agree with the premise. I think what was tried and didn't > > work should be documented in the result that the working group comes > > out with, but not in the problem statement. > >