Re: [ekmi] Groups - Proposal for a message-structure for SKMS (PDF) (SKSML-1.0-Error-Message-Codes.pdf) uploaded

[Allen <netsecurity@sound-by-design.com>]

Hi Arshad,

I have two problems with the proposal:

1) The window to implement is too long. I think it should be 6 to 
12 months in order to encourage uptake. The way I would structure 
this is that they get 6 months upon application approval, with 
the option of a 6 months extension if they ask for it. Longer 
would require re-approval. I'd make this fairly automatic, but 
leave them with the idea that they'd better get cracking or they 
lose their place in line.

2) If it is restricted to OASIS only members, then you will not 
get uptake among the smaller companies as the cost of membership 
for a company is not trivial for a startup. This puts an 
impediment to widespread adoption by potential vendors that would 
interfere with adoption that we would not want. What other OASIS 
standard requires membership? All we are offering them is a 
dedicated block for error and message codes. (Personally I think 
1000 is overkill, I'd used 100 and hold 400 in reserve for each 
registered entity, but that almost doesn't matter as we can 
extend the numbering schema in a later release.)

Best,

Allen

Best,

Allen

arshad.noor@strongauth.com wrote:
> Folks,
> 
> Based on our recent discussion, I've put together a proposal for the
> message structure.  Please review and comment on this structure.
> 
> One question for the group: should we focus on only messages in the SKSML
> protocol (the messages sent between the client and server) or should we
> also focus on some standard messages on the SKCL and the SKS server?
> 
> Thanks and have a great weekend.
> 
> Arshad Noor
> StrongAuth, Inc.
> 
>  -- Arshad Noor*
> 
> The document named Proposal for a message-structure for SKMS (PDF)
> (SKSML-1.0-Error-Message-Codes.pdf) has been submitted by Arshad Noor* to
> the OASIS Enterprise Key Management Infrastructure (EKMI) Technical
> Committee document repository.
> 
> Document Description:
> A proposal, based on recent discussions on the TC, for standardized codes
> and messages within an SKMS.
> 
> View Document Details:
> http://www.oasis-open.org/committees/document.php?document_id=29560
> 
> Download Document:  
> http://www.oasis-open.org/committees/download.php/29560/SKSML-1.0-Error-Message-Codes.pdf
> 
> 
> PLEASE NOTE:  If the above links do not work for you, your email application
> may be breaking the link into two pieces.  You may be able to copy and paste
> the entire link address into the address field of your web browser.
> 
> -OASIS Open Administration