RE: Things to do - Requirement Document. Security.

[Michael Zolotarev <michael.zolotarev@baltimore.com>]

Krishna,

> thinking about
> it, in your mind what other sections need to be there ?
> 

I'm really unclear on this one. Mostly because I'm yet not sure what is the
audience of the solution we are trying to produce. It is a set of standard
tokens structures and common use cases, I realise, but where and how would
they be used? The point is, that without having a good, and common,
understanding of how the solution is going to be used by the industry, it is
impossible to put moreless specific requirements in place. It'd just waste
of time, IMHO.

I have previously expressed my opinion about having an election back-bone,
with various election system providers being able to interop at the
back-bone level. Some people agree, some not. 

Whatever the "common" vision may become, I'm soliciting that it for must
come from the election system vendors, not from security expers and other
"auxiliary" facilities :). This is why I was first trying to see a number of
use cases put together *by the vendors*. So that they become clear on were
we go, and whether there is a need in any standartization at all. 

<< Once I've touched that slippery subject: I'm not afraid to say that one
of the possible outputs of that TC may be a resolution that we don't need
any standard, at all or in the foreseen future. It MAY happen, and we should
keep our minds open.>>

Regards
Michael


-----------------------------------------------------------------------------------------------------------------
"How can I make sure the right people get access to the right resources 
and business applications, with a user base that's constantly growing and
changing?" 
The answer... 
Baltimore SelectAccess 
Next Generation Authorisation Management 
http://www.baltimore.com/selectaccess/index.html
-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

In addition, certain Marketing collateral may be added from time to time to 
promote Baltimore Technologies products, services, Global e-Security or 
appearance at trade shows and conferences.
 
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.