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: Distributed Key Management Systems Usage Guide test


Hello All,

I would propose the following text for the usage guide following my talk at the face to face. Any comments most welcome.

4.7 Distributed Key Management Systems

Key management systems may be distributed across multiple servers which are not continuously connected. This means that updates can be made to one server that are inconsistent with updates to a second server. The inconsistency may not be detected until the servers communicate with each other which might be some time after the conflicting updates were made, so they cannot simply be rejected from the clients.

One example is that a given key may end up in inconsistent states on different servers, such as both Active and Compromized. Another is that two keys in different servers may end up with the same Name. And forward and backward links may be inconsistent.

Distributed KMIP systems need to be carefully designed to address such issues. For example, if inconsistent states are encountered, then a strategy is needed to produce a sensible resolution. Likewise having multiple keys from different sources with the same name should be resolved in a consistent manner, and operations such as Re-Key need to behave sensibly in such a situation.


--
Anthony Berglas Ph.D.
Principal Engineer
Anthony.Berglas@Cryptsoft.com



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