W3C home > Mailing lists > Public > public-credentials@w3.org > March 2018

Question: Can DID Documents define permanent email addresses?

From: Steven Rowat <steven_rowat@sunshine.net>
Date: Sun, 11 Mar 2018 17:25:43 -0700
To: public-credentials@w3.org
Message-ID: <bed4ba0c-8c11-fae1-05e9-b29191fbb930@sunshine.net>

Could some combination of DID Document, Method, and Services allow the 
entity that has the email (and aliases) to define those in a central 
place, ie the DID Document, and then merely point to the current 
server for them? So if the server changes, the email address doesn't 
have to? And so all the correspondents of Entity X will never have to 
know, and can still communicate with Entity X by the same email 
address, forever (or until Entity X wishes to change it)?

This seems like it would potentially be a big advance on the current 
system, which is either:

  A. ISP based, so the email address must change if Entity X moves to 
a different ISP;

  B. Cloud-based, so the Entity X is tied to [Google, Microsoft, etc.] 
who handles their email, and must change their email address if they 
wish a different provider;

  C. Own domain (EntityX@EntityX.com) which is possible but somewhat 
of a pain to set up, especially for the 99% of the Internet who don't 
know what a server is (see: 
https://konklone.com/post/take-control-of-your-email-address for how 
that can be done).

I haven't seen any mention of this on the list or DID discussions, but 
it seems like it would be a good thing to have if it's possible; 
potentially a simpler method, or at least one that the entity has 
control over.


Received on Monday, 12 March 2018 00:26:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:25 UTC