Re: Starting in on a document

Hadmut Danisch <[email protected]> wrote:
> >   My opinion is that we should describe the smallest design and
> > implementation which will address as much of the problem as possible.
> 
> No. For two reasons: First, we don't have a precise description of the 
> problem yet. 

  Hmm... I had thought that the scope statements narrowed down the
problem to something fairly straightforward: publishing and verifying
consent on the use of domain names in EHLO/HELO and MAIL FROM.

> Second: Keep the 80/20 rule in mind. You usually can solve 80% of the
> problem with 20% of the work/cost. Following your proposol, we'd have
> to describe a solution which is cheap (20%), but does solve only 80%
> of the problem. This won't sell.

  I understand.  Do you have examples as to why a small design is
unsufficient?

  Alan DeKok.