RefID creates IDs for REFs and maps between the two. An ID is simply a laundered REF, which can be passed across an RPC connection. When a REF is "sealed" into an ID, this package holds onto the REF so that it is not garbage collected. IDs must be explicitly released to indicate that interest in the REF no longer exists.

See the interface for further documentation, which is just a set of laundering functions for calls to the standard Cedar CardTab package, which is a clone of the RefTab package using CARDs instead of REFs for keys.