long term persistence of identifier association is a tricky issue. I don't have any answers, but can point you in the direction of some thinking we did in the PILIN project a while ago.
Firstly, have a look at "Persistence of Identifiers Guidelines" document http://resolver.net.au/hdl/102.100.272/V89DC0DQH
It discusses both the options you mention: changing access controls within an identifier management system and aliasing (redirecting) from one identifier to another.
Aliasing / redirecting is the approach recommended by the W3C Web Architecture (see http://www.w3.org/TR/webarch/#URI-persistence
), along with designing "cool" identifiers that can cope with change (see http://www.w3.org/Provider/Style/URI.html
). While redirects are technically elegant, they rely on maintaining the persistence of two identifier systems: one for the original identifier and one for the new identifier. The owners of the new identifier probably don't have access to the old identifier system, which means they have to trust that the original identifier system will persist for as long as they want to manage their new identifier. This is probably ok in the case of ANDS PIDs, which presumably have some sort of persistence guarantee.
The access control option requires a system that distinguishes between access control and ownership, and can delegate access control to entities other than the original identifier creator. While the Handle System can support this, you are correct that the ANDS PID service doesn't support these concepts at the moment.
Another option is to consider running your own identifier management system and guarantee persistence over your identifiers. While this is a big commitment, the W3C documents argue that you should be doing that for any URIs you publish anyway. For a longer discussion on the pros and cons of using HTTP URIs as persistent identifiers see "Using URIs as Persistent Identifiers" http://resolver.net.au/hdl/102.100.272/DMGVQKNQH
It'd be great to hear about what solution you finally decide on: it is something that many of us ANDS partners also have to consider.