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: thoughts on [kmip] OASIS Security Standards Interop Demo at RSAExpo 2010

If we go with either scenario, I suggest there be separate clients for each server.  Having 1 client per server, even  if both clients are the same device type, would be preferred over 1 client sharing 2 servers.  

One client connected simultaneously to 2 servers can be perceived (to someone with no KMIP background) as demonstrating some server-server behavior, which is a perception we should probably avoid at this stage.  Plus, 2 server connections for a single purpose isn't expected.  Ideally the clients would represent existing product classes, not an abstraction.

Stan Feather

-----Original Message-----
From: robert.griffin@rsa.com [mailto:robert.griffin@rsa.com] 
Sent: Thursday, December 17, 2009 10:30 AM
To: kmip@lists.oasis-open.org
Subject: [kmip] thoughts on [kmip] OASIS Security Standards Interop Demo at RSA Expo 2010

Hi -

At our last KMIP TC call, I promised to send around some thoughts on
what we might do for this interop demo.

The goal of demo is to demonstrate the effectiveness of KMIP protocol
supporting the use cases such as symmetric key store and foundry across
multi-vendor implemenations of clients and servers. We could do this at
one of several levels:

Simplest: Demonstrate KMIP interoperability by sending the same
requests/responses from a single KMIP client to multiple servers. This
would entail at least one client system and two server systems. On the
client, a simple UI would display the following:

-	establish secure connection to server 1
-	create request message
-	send request (for example, create symmetric key) to server 1
-	receive response from server 1
-	establish secure connection to server 2
-	send request (for example, create symmetric key) to server 2
-	receive response from server 2

On the servers, UI would show:

-	establish secure connection from client
-	receive request
-	send response

2) A slightly more complex demo could add additional operations as part
of the script (for example, register). Alternatively, it could add other
key types for the same operation (create asymmetric keys, for example).

We would probably also want to have a brief rolling slide show on KMIP
on the client and server systems that could be interrupted when the demo
was run.

Is this worth doing? Do we have KMIP TC members who feel confident in
being able to dedicate resources (developing the demo, staffing the demo
at the show, and contributing to cost of the booth) to this demo? (Feel
free to respond either to the reflector or to Subash and myself.



-----Original Message-----
From: Jane Harnad [mailto:jane.harnad@oasis-open.org] 
Sent: Thursday, December 17, 2009 9:24 AM
To: xspa@lists.oasis-open.org; 'xacml'; imi@lists.oasis-open.org;
kmip@lists.oasis-open.org; security-services@lists.oasis-open.org;
xri@lists.oasis-open.org; wsfed@lists.oasis-open.org
Subject: [kmip] OASIS Security Standards Interop Demo at RSA Expo 2010

OASIS Security Standards Interop Demo


1-5 March 2010

Moscone Center
San Francisco, CA USA




An OASIS booth at the RSA Expo will showcase products that support open
standards for security including XSPA, KMIP and IMI.  Members will have
the opportunity to demonstrate how their products fit and interoperate
in real-world scenarios to the projected 12,000 RSA Expo attendees.
OASIS will provide contact information for all booth visitors to
participating members.


OASIS members interested in participating should complete the
Participant Reservation Form before 22 December.    


Participant Reservation Form:



Participant Fee

A cost of 4,500 USD per participating company will be allocated to cover
the costs associated with the show floor demonstration. 


OASIS Foundational- and Sponsor-level members receive a 25% discount off
the fee (3,375 USD).  Foundational-level members are also welcome to use
a Premium.  Please contact Carol Geyer (carol.geyer@oasis-open.org) for
more details.



Participant Benefits

Each company participating in the Interop will receive: 


*	One workstation within the showcase area including: three-foot
section of a table, one chair, internet connectivity, and electricity
(workstation selection priority to Foundational- and Sponsor-level
*	Up-to two complimentary booth staff registrations (four for
Foundational-level members) 
*	Company name in the Interop description for the expo on-site
*	Company logo on signage
*	Linked company logo and profile on OASIS website (with
Foundational and Sponsor-level members predominantly featured)  
*	Company logo on Interop handout  
*	Visibility and executive quote in OASIS press release (quotes
offered to Foundational- and Sponsor-level OASIS members only)
*	Booth visitor contact list, distributed after the event
*	Discounted rate to participate in a post Interop webinar
(complimentary option for Foundational-level OASIS members, a 250 USD



Booth Details

OASIS will reserve a 10'x20'- 20'x30' booth space on the Expo floor. The
size will be determined by the number of members participating.  Final
booth space selection will take place on 22 December, so all
participants should register
tact.php>  before then to ensure their space.


See the show floor diagram at:

About the Expo Attendees 
RSA Expo attendees come from around the world... 

*         31% are C-Level, senior executives or VP/director

*         24% are team leaders/managers 

*         19% are front-line IT/IS staff

In addition, 32% were CISSP Certified and 51% had 10+ years of

Attendees represent major industry verticals such as Banking, Finance,
Government, Healthcare, Pharmaceuticals, Computer Software Development
and Manufacturing.




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:

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