Spec for consent wallet portability #8
Description
Support for portability across the consent wallets provided by different consent managers (like CM_1 and CM_2 are the providers of consent wallets).
option 1 - user has a new CM id and consent lifecycle data is moved from old to this new CM id.
In this who will inform the DPs and DCs that user has migrated from user CM_1 to CM_2 ? user itself or should it be part of the spec itself ?
option 2 - user just changes its CM provider. The users cm id will not change. Similar to how mobile portability works. The lifecycle data will still have to be moved.
Thought - for consent lifecycle data movement user could add the old CM as the DP to the new CM.