Should this method have an easy solution to "Right to be forgotten"?

[brianorwhatever]

Currently the deactivate method still returns a DID and the log still exists. Should we make this more robust and delete the log or something along those lines?

[Reccetech]

In the conversation @swcurran mentioned that a 3rd party operator handling a "right to be forgotten" request could just delete the relevant DID log and then anyone trying to resolve the DID would get a 404. I think this is a satisfactory solution. Maybe a description of this flow can be added to the spec under "Security and Privacy Considerations"