OASIS Key Management Interoperability Protocol (KMIP) TC

I've asked Rene if his team would be willing to also implement at least some portion in python for OpenStack. Begin forwarded message: From: Pawlitzek René < rene.pawlitzek@ntb.ch > Date: May 17, 2013 9:56:17 AM EDT To: kwburgi@tycho.ncsc.mil < kwburgi@tycho.ncsc.mil > Subject: KMIP support in OpenStack Good day Kelley:   I am one of the original KMIP contributors and work as an Assistant Professor at a State University in Switzerland. We have two smart bachelor students working on an Open Source implementation of a KMIP client and a KMIP server using Java and plan to release the codebase under a BSD license in Mid-August. It would be a pleasure to see this code working in OpenStack.   Best regards Rene   PS: Feel free to post this mail on oasis-open.org   -----   René Pawlitzek Dozent für Informatik Interstaatliche Hochschule für Technik Buchs NTB Werdenbergstrasse 4 CH-9471 Buchs Tel: ++41 81 755-3183 Fax: ++41 81 756-5434 rene.pawlitzek@ntb.ch http://www.ntb.ch     Subject :   KMIP support in OpenStack From :   Kelley Burgin < kwburgi@tycho.ncsc.mil > To :   kmip@lists.oasis-open.org Date : Thu, 2 May 2013 09:29:12 -0400 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        

And another example of reach beyond the walls - nice interaction here between KMIP and OpenStack and academia...  ---------- Forwarded message ---------- From: Kelley Burgin < kwburgi@tycho.ncsc.mil > Date: Fri, May 17, 2013 at 1:44 PM Subject: [kmip] Fwd: KMIP support in OpenStack To: kmip@lists.oasis-open.org I've asked Rene if his team would be willing to also implement at least some portion in python for OpenStack. Begin forwarded message: From: Pawlitzek René < rene.pawlitzek@ntb.ch > Date: May 17, 2013 9:56:17 AM EDT To: " kwburgi@tycho.ncsc.mil " < kwburgi@tycho.ncsc.mil > Subject: KMIP support in OpenStack Good day Kelley:   I am one of the original KMIP contributors and work as an Assistant Professor at a State University in Switzerland. We have two smart bachelor students working on an Open Source implementation of a KMIP client and a KMIP server using Java and plan to release the codebase under a BSD license in Mid-August. It would be a pleasure to see this code working in OpenStack.   Best regards Rene   PS: Feel free to post this mail on oasis-open.org   -----   René Pawlitzek Dozent für Informatik Interstaatliche Hochschule für Technik Buchs NTB Werdenbergstrasse 4 CH-9471 Buchs Tel: ++41 81 755-3183 Fax: ++41 81 756-5434 rene.pawlitzek@ntb.ch http://www.ntb.ch     Subject :   KMIP support in OpenStack From :   Kelley Burgin < kwburgi@tycho.ncsc.mil > To :   kmip@lists.oasis-open.org Date : Thu, 2 May 2013 09:29:12 -0400 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         -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open