Comment 1 for bug 1077282

Each KVS driver is in a different situation:

- kvs policy driver is new (for v3) and can be removed immediately without seeing a release
- kvs identity driver is probably the easiest existing kvs driver to remove, and the most complex to maintain
- kvs catalog driver is the basis for the templated driver, although that inheritance could change to the sql driver
- kvs token driver has been documented, and should at least be maintained for a deprecation period

ayoung: if you don't mind, I'd like to see this issue target the kvs identity driver in particular.