Comments on Meeting Agenda
Paul Rarey (Paul.Rarey@Clorox.com)
Tue, 6 Feb 1996 14:17:43 -0700
This is a re-posting to this list for discussion...
On Jan 26, 11:48, Dave Crocker wrote:
> Subject: FULL ANNOUNCEMENT: IMC Resolving Email Security Complexity Works
[ Stuff Deleted ]
After some more cogitation, I've another comment. Item two of the morning
agenda might lead one to believe the concers may not be couched in context of
the problem space each solution is trying to solve. I have found it is
frequently a mis-alignment of understanding the problem space that leads to
incongruent solutions arising. Thus, I could see the discussions in item two
getting bogged down in why certian function and technical issues are of
concern - there is no prior (rough) consensus on the ranking of issues that
need to be solved (thus are not of, or of high concern).
>Morning
>
>* Very briefly describe the MOSS, PGP, and S/MIME
> solutions
>* Review the functional and technical concerns
>* Review the extent to which each alternative satisfies
> the concerns
>* Seek consensus for concerns that qualify as
> requirements
Thus I would propose....:
* Very briefly describe the MOSS, PGP, and S/MIME
solutions
1 The brief overview should include a medium depth definition of
the problem space the solution is targeted to resolve. E.g:
a existing environment
b environment evolution envisioned <-- The big one
c issues of transition / co-existence
* Form rough concensus of the problem space <-- = (b-a)~c
* Review the functional and technical concerns
* Seek consensus on importance (ranking?) of concerns
* Review the extent to which each alternative satisfies
the concerns
>Afternoon
>
>* Haggle about the strengths and weaknesses of the
> technical alternatives
>* Explore the choices and/or negotiate a preferred
> solution
--
Cheers!
[ psr ]