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: Re: [kmip] RE: KMIP to P1619.3 Mapping


As the P1619.3 liaison into KMIP, I'll take a look at the copyright rules of both OASIS and IEEE, and provide links to each of their policies.  However, like anything legal, It will likely be up to your lawyers to provide accurate interpretations of these policies.

Cheers,
-Matt

Larry.Hofer@Emulex.Com wrote:
CB376E1C24DB4A43A1D596B2BC1BD828771EF52981@EXMAIL.ad.emulex.com" type="cite">
As far as the proposal for P1619.3 to conform to KMIP, I have also seen statements for P1619.3 to adopt "part of " KMIP for the binary. I don't yet understand what "part of" would mean to the P1619.3 group. Seems like it should adopt/support "all of" KMIP that is relevant.
 
I would not like to see P1619.3 move ahead of KMIP in functionality to avoid possible complications in adopting it in a future KMIP version. I have heard that IEEE copyrights might become an issue later if IEEE specified functionality were to be added to a future KMIP version.  Maybe someone can research copyright complications as far possible difficulties in sharing between the two groups. Maybe the group liasions could figure that out.
 
Larry H

From: Robert Lockhart [mailto:Robert.Lockhart@thalesesec.com]
Sent: Saturday, May 16, 2009 11:17 AM
To: kmip@lists.oasis-open.org
Subject: [kmip] KMIP to P1619.3 Mapping

Since we have not had time during the weekly phone calls I would like to mention several things about the mapping process.
 
I would like to open it up to P1619.3 to get their feedback.  The document is public and can be accessed by them currently and it was brought up in the most recent meeting. 
 
Within P1619.3 there has been a proposal although deferred to move P1619.3 to conform (there is that word again) with KMIP and use it as the binary messaging format.  Once we have a formal liaison in place (status?) can we discuss this?
 
I would like to get this and the conformance discussion on the agenda for this next weeks meeting and would like to plan for 15 minutes for each topic with any additional conversation occuring via email reflector due to time constraints we currently have in the meeting.
 
Thanks,
 
Bob L.
 

Robert A. (Bob) Lockhart

Senior Solutions Architect

THALES Information Systems Security

 

-------------------------------------------------------

T:      +1 408 457 7711 (Direct)

M:     +1 510 410 0585

F:      +1 408 457 7681

E:      rlockhart@ncipher.com

W:     www.nCipher.com

 

         nCipher product line. See www.nCipher.com

 


The information contained in this e-mail is confidential. It may also be privileged. It is only intended for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee or the intended addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error please delete it (and all copies) from your system, please also inform us immediately on +1 (781) 994 4000 or email ussales@ncipher.com. Commercial matters detailed or referred to in this e-mail are subject to a written contract signed for and on behalf of nCipher Inc.
begin:vcard
fn:Matt Ball
n:Ball;Matthew
org:Sun Microsystems, Inc.;Key Management
adr:;;500 El Dorado Blvd, Bldg 5;Broomfield;CO;80021;U.S.A.
email;internet:matthew.ball@sun.com
title:Staff Engineer
tel;work:303-272-7580
tel;fax:303-272-3023
tel;cell:303-717-2717
x-mozilla-html:TRUE
url:http://www.sun.com
version:2.1
end:vcard



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