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] KMIP to P1619.3 Mapping

KMIP and P1619.3 focus on different areas of Key
Management Service architecture (see Bob Lockhart's
slide deck for further details).  Where there is overlap, there
appears to be close alignment.  A number of vendors are
pursuing both complementary standards.

We believe that it is extremely important that implementations
have the opportunity to be both KMIP and P1619.3 compliant.
We welcome Bob Lockhart's proposal to receive P1619.3
feedback on the public document.

chongo (Landon Curt Noll) /\oo/\


On 2009-May-16, at 23:55, Benjamin Tomhave wrote:

> I'm not sure that I agree that this should be a priority. It seems  
> to be
> more a distraction than anything else. Is there a reason KMIP should  
> be
> pegged against P1619.3? Just curious why this is seen as important,  
> but
> mapping to other standards committees is not.
> Robert Lockhart wrote:
>> 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 <http://www.ncipher.com/>
>>         nCipher product line. See www.nCipher.com <http://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.
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

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