This call gets a slice name bound to the requesting user. The name is determined by the Naming Authority and is guaranteed to be globally unique. Of course a name is only issued to a user with proper credentials and a fault issued if they are unacceptable. If the allocation is successful, the new slicename is returned.

Bind an additional user to this slice. The user credentials and slice name are passed and if either is unacceptable the operation fails with a standard fault message. Otherwise the new name is bound.

Remove the given user from the slice. If either the user or slice is unacceptable, a standard fault message is issued. Otherwise the user is removed. A slice without any users bound to it is garbage collected. If we allow this operation, there's a question about who the resource allocations owe their validity to. If it's the user, should the allocations end if the user leaves the slice?

Return the user credentials associated with the slice. Right now the same credentails are returned that are used to authenticate the various calls, but this is obviously unacceptable. That will be fixed.

Remove the slice from the global name space. This asks a lot of questions. Should the slice be confirmed to be empty before it is removed? If so how might one do that? Forcably shutting down the slice is similarly problematic - only the user(s?) knows for sure what resources are allocated to the slice.