OASIS Key Management Interoperability Protocol (KMIP) TC

OpenStack has a need for key management where I think KMIP makes perfect sense (see the first diagram at  https://wiki.openstack.org/wiki/VolumeEncryption for a few more details of one place KMIP could be used). Intel is planning to post a (very TPM-centric) blueprint  and dedicate resources to building the Key Manager for the next (Havana) release. If no one challenges the write up it will most likely be the default implementation for Openstack and difficult to get changes (such as KMIP support) made. See  https://wiki.openstack.org/ wiki/KeyManager Now is the time for KMIP to make ourselves known (if we want to be a part of the OpenStack cloud offering). OpenStack is very code oriented (those who submit code get the most influence) but also requires socialization (wiki, blueprints, chat, and summit attendance) to get the job done.  So, if anyone is interested in participating, here's what is needed: 1. someone (not necessarily one person) willing to commit resources to interact with OpenStack in order to get KMIP into the right place in the OpenStack design 2.  a reference (open source) client implementation, with a mock-up server for testing. I'm willing to help socialize KMIP in OpenStack, but some vendor support would be great. Kelley

I think this is a fabulous idea – I believe I should reach out to the TC and let them know that I can help, not sure how, any ideas? dee   From: kmip@lists.oasis-open.org [mailto:kmip@lists.oasis-open.org] On Behalf Of Kelley Burgin Sent: Thursday, May 02, 2013 9:29 AM To: kmip@lists.oasis-open.org Subject: [kmip] KMIP support in OpenStack   OpenStack has a need for key management where I think KMIP makes perfect sense (see the first diagram at  https://wiki.openstack.org/wiki/VolumeEncryption for a few more details of one place KMIP could be used).   Intel is planning to post a (very TPM-centric) blueprint and dedicate resources to building the Key Manager for the next (Havana) release. If no one challenges the write up it will most likely be the default implementation for Openstack and difficult to get changes (such as KMIP support) made. See  https://wiki.openstack.org / wiki/KeyManager   Now is the time for KMIP to make ourselves known (if we want to be a part of the OpenStack cloud offering). OpenStack is very code oriented (those who submit code get the most influence) but also requires socialization (wiki, blueprints, chat, and summit attendance) to get the job done.    So, if anyone is interested in participating, here's what is needed:   1. someone (not necessarily one person) willing to commit resources to interact with OpenStack in order to get KMIP into the right place in the OpenStack design 2.  a reference (open source) client implementation, with a mock-up server for testing.   I'm willing to help socialize KMIP in OpenStack, but some vendor support would be great.   Kelley      

Maybe first reach out to Kelley privately and ask if he/she has any advice for how OASIS can help support this. In the meantime, let's watch the TC list and see what kind of responses appear. On Thu, May 2, 2013 at 9:30 AM, Dee Schur < dee.schur@oasis-open.org > wrote: I think this is a fabulous idea – I believe I should reach out to the TC and let them know that I can help, not sure how, any ideas? dee   From: kmip@lists.oasis-open.org [mailto: kmip@lists.oasis-open.org ] On Behalf Of Kelley Burgin Sent: Thursday, May 02, 2013 9:29 AM To: kmip@lists.oasis-open.org Subject: [kmip] KMIP support in OpenStack   OpenStack has a need for key management where I think KMIP makes perfect sense (see the first diagram at  https://wiki.openstack.org/wiki/VolumeEncryption for a few more details of one place KMIP could be used).   Intel is planning to post a (very TPM-centric) blueprint and dedicate resources to building the Key Manager for the next (Havana) release. If no one challenges the write up it will most likely be the default implementation for Openstack and difficult to get changes (such as KMIP support) made. See  https://wiki.openstack.org / wiki/KeyManager   Now is the time for KMIP to make ourselves known (if we want to be a part of the OpenStack cloud offering). OpenStack is very code oriented (those who submit code get the most influence) but also requires socialization (wiki, blueprints, chat, and summit attendance) to get the job done.    So, if anyone is interested in participating, here's what is needed:   1. someone (not necessarily one person) willing to commit resources to interact with OpenStack in order to get KMIP into the right place in the OpenStack design 2.  a reference (open source) client implementation, with a mock-up server for testing.   I'm willing to help socialize KMIP in OpenStack, but some vendor support would be great.   Kelley       -- Carol Geyer Senior Director of Communications and Development OASIS Advancing open standards for the information society  +1.781.425.5073 x209 (Office) +1.941.284.0403 (Cell) http://www.oasis-open.org Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open YouTube:     http://www.youtube.com/oasisopen

I asked Sanjay directly - he's on several OpenStack groups as an advocate for standards. On 5/2/2013 11:35 AM, Carol Geyer wrote: Maybe first reach out to Kelley privately and ask if he/she has any advice for how OASIS can help support this. In the meantime, let's watch the TC list and see what kind of responses appear. On Thu, May 2, 2013 at 9:30 AM, Dee Schur < dee.schur@oasis-open.org > wrote: I think this is a fabulous idea – I believe I should reach out to the TC and let them know that I can help, not sure how, any ideas? dee   From: kmip@lists.oasis-open.org [mailto: kmip@lists.oasis-open.org ] On Behalf Of Kelley Burgin Sent: Thursday, May 02, 2013 9:29 AM To: kmip@lists.oasis-open.org Subject: [kmip] KMIP support in OpenStack   OpenStack has a need for key management where I think KMIP makes perfect sense (see the first diagram at  https://wiki.openstack.org/wiki/VolumeEncryption for a few more details of one place KMIP could be used).   Intel is planning to post a (very TPM-centric) blueprint and dedicate resources to building the Key Manager for the next (Havana) release. If no one challenges the write up it will most likely be the default implementation for Openstack and difficult to get changes (such as KMIP support) made. See  https://wiki.openstack.org / wiki/KeyManager   Now is the time for KMIP to make ourselves known (if we want to be a part of the OpenStack cloud offering). OpenStack is very code oriented (those who submit code get the most influence) but also requires socialization (wiki, blueprints, chat, and summit attendance) to get the job done.    So, if anyone is interested in participating, here's what is needed:   1. someone (not necessarily one person) willing to commit resources to interact with OpenStack in order to get KMIP into the right place in the OpenStack design 2.  a reference (open source) client implementation, with a mock-up server for testing.   I'm willing to help socialize KMIP in OpenStack, but some vendor support would be great.   Kelley       -- Carol Geyer Senior Director of Communications and Development OASIS Advancing open standards for the information society  +1.781.425.5073 x209 (Office) +1.941.284.0403 (Cell) http://www.oasis-open.org Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open YouTube:     http://www.youtube.com/oasisopen -- Laurent Liscia, CEO OASIS: Advancing open standards for the information society (510) 669-1261 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open Take a tour of OASIS at: http://www.oasis-open.org/home/tour.php

Great catch. Thanks. Sanjay does sound like one good focal point Ultimately what they are asking for, though. are internal expert evangelists from within KMIP TC towards OpenStack. So as Carol says, we need to see if anyone bites, and then maybe go stir up the fish, if they don't. tJBC On Thu, May 2, 2013 at 6:30 AM, Dee Schur <dee.schur@oasis-open.org> wrote: > I think this is a fabulous idea – I believe I should reach out to the TC and > let them know that I can help, not sure how, any ideas? > > dee

Thanks Jamie. dee
Original Message----- From: Jamie Clark [ mailto:jamie.clark@oasis-open.org ] Sent: Thursday, May 02, 2013 12:34 PM To: Dee Schur Cc: BizDev Group Subject: Re: [staff-bizdev] FW: [kmip] KMIP support in OpenStack Great catch. Thanks. Sanjay does sound like one good focal point Ultimately what they are asking for, though. are internal expert evangelists from within KMIP TC towards OpenStack. So as Carol says, we need to see if anyone bites, and then maybe go stir up the fish, if they don't. tJBC On Thu, May 2, 2013 at 6:30 AM, Dee Schur <dee.schur@oasis-open.org> wrote: > I think this is a fabulous idea - I believe I should reach out to the > TC and let them know that I can help, not sure how, any ideas? > > dee

On 2/05/2013 11:29 PM, Kelley Burgin wrote: OpenStack has a need for key management where I think KMIP makes perfect sense (see the first diagram at  https://wiki.openstack.org/wiki/VolumeEncryption for a few more details of one place KMIP could be used). Intel is planning to post a (very TPM-centric) blueprint  and dedicate resources to building the Key Manager for the next (Havana) release. If no one challenges the write up it will most likely be the default implementation for Openstack and difficult to get changes (such as KMIP support) made. See  https://wiki.openstack.org/ wiki/KeyManager The link that Subhash was talking about on the call with comments based on review of the usage guide. https://etherpad.openstack.org/havana-key-manager Tim.