Comment 5 for bug 1182920

I think a security note is most appropriate.

There might be ways to mitigate in the future, such as running memcached on multiple machines to ensure redundancy should the Keystone server fail. In a clustered environment, it will only be an issue if all of the memcached machines shutdown.

Memcachedb might also be a potential way to mitigate.

http://memcachedb.org/

It might also be possible to record the revocation list upon update, and to read that value in on start up. It depend on how common revocation events are whether that will have a negative impact, but I suspect it would be negligible.