OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

kmip message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Fwd: [GRAYMAIL] [kmip] Groups - KMIP Security Attributes uploaded


Let's try this again- had some listserv  hiccups.

Thanks!

Chuck



Howdy Mark!

 

Excellent Question – please see the attached spreadsheet. Hopefully this is a little clearer than mud.

 

In practice the security attribute in this model becomes a set of “handling instructions” for attributes and keys that are associated with the security attribute.

 

Workflow becomes interesting as the security attribute needs to be requested by the ID of the objects and attributes associated with it. Attributes will be a fun discussion topic I suspect.  Then you can use that information to request the material with the associated set of instructions.  The challenge here is that how does one go about determining the flow of information without dictating client and vendor implementation –  in practice this is part of the conversation we need to have as a TC, what is an agreeable process for negotiation of release and distribution of key material that further aligns with current and future NIST guidelines and doesn’t go about bloating the KMIP specification in the process.

 

Hope this helps!

 

Chuck

 

 

 

From: Mark Joseph [mailto:mark@p6r.com]
Sent: Tuesday, April 14, 2015 4:46 PM
To: Chuck White; kmip@lists.oasis-open.org
Subject: Re: [GRAYMAIL] [kmip] Groups - KMIP Security Attributes uploaded

 

Hey Charles,

 

    Could you add an example of what several security attributes would look like using Option 2.   It is hard to see what you are proposing from the table on slide 10.

 

Thanks,

Mark



Charles White <cwhite@fornetix.net> , 4/14/2015 10:31 AM:

Submitter's message
Good morning, afternoon, evening KMIP TC!

Please find a presentation on Security Attributes that is intended to derive feedback and options for an approach going forward.

Thanks!

Chuck
-- Mr. Charles White

Document Name: KMIP Security Attributes


Description
Presentation on additional approaches to Security Attributes to elicit
options on a path forward to support compliance with NIST SP800-130 and
SP800-152
Download Latest Revision
Public Download Link


Submitter: Mr. Charles White
Group: OASIS Key Management Interoperability Protocol (KMIP) TC
Folder: Drafts
Date submitted: 2015-04-14 10:25:57

 

Attachment: Example Security Attribute.xlsx
Description: Example Security Attribute.xlsx



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]