Re: [ietf-dkim] scenarios

2006-07-30 Thread Mark Delany
On Sun, Jul 30, 2006 at 03:15:57PM -0400, Hector Santos allegedly wrote: > I think not understanding something does not give those who do, those who > has put in the time to help engineer this all out, from a real production > standpoint, the benefit of the doubt. Thanks, you demonstrate the poin

Re: [ietf-dkim] scenarios

2006-07-30 Thread Hector Santos
- Original Message - From: "Mark Delany" <[EMAIL PROTECTED]> To: Sent: Sunday, July 30, 2006 12:27 PM Subject: Re: [ietf-dkim] scenarios > > It is easy to state a functional "requirement" but it is often difficult to > > explain why it is n

Re: [ietf-dkim] scenarios

2006-07-30 Thread Mark Delany
> It is easy to state a functional "requirement" but it is often difficult to > explain why it is needed or to convince people that it is essential to support > that requirement. > > The easiest way to handle this is to ensure that every functional requirement > is > explained in terms of a detai

[ietf-dkim] scenarios

2006-07-30 Thread Dave Crocker
John L wrote: > I still don't understand the scenario. It occurs to me that discussion of usage scenarios should be required for every requirement. It is easy to state a functional "requirement" but it is often difficult to explain why it is needed or to convince people that it is essential t