RE: user-visible goals

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Bruce Lilly
> Sent: Monday, February 23, 2004 10:18 PM
> To: [email protected]
> Subject: Re: user-visible goals

> We should keep in mind the excellent suggestions 
> in RFC 1958. As this relates to user-visible
> goals:

> - users want a solution today, even if it is incomplete.

Conventional email with way too many "patches" to accommodate for
shifting user requirements is the solution today, and it is incomplete.
What we need to do is think new, leave "traditional" email as it is, and
develop something that users will want to merge to because it is The
Next Big Thing(TM). We should IMNSHO not let ourselves be held back by
the way email works today, because this will lead to further "patches",
and not the revolutionary new system this list is preparing goals and
requirements for.

One of the requirements I see emerging from the partly conflicting goals
is flexibility. The protocol should be extensible, and new extensions
should be formally expressed and approved. In the protocol there should
be defined a minimum of testable requirements which the client must
support to be allowed to say that it supports e.g. signing of messages.

Just my two centimes.

Yours sincerely,
-- 
Victor Engmark
Quid quid latine dictum sit, altum viditar - What is said in latin,
sounds profound