This is a fresh idea, I'd suggest you reformat as Web RFC.
The one part where I felt something felt not ideal was the
optional fields of the public personal profile reveal and
awful lot of information no sane human should share to all
7 billion other humans (including, sadly, many fraudsters):
do not disclose your date of birth to an unrestricted audience, for instance. Also, some people may break their
employment contract by disclosing the detailed department
in which they work, whereas it would be okay to disclose that
selectively after a link has been established.
What is the next step? Perhaps a prototypical implementation, as is custom before standardizing something.
Regarding the claim of security and decentralization compared to legacy email, the use of the Web infrastructure means that DNS and security certificates remain ITSEC/centralization bottlenecks.
Using the Web to get adoption makes sense from a practical point of view. Scientifically, I'd be interested to see a version of this ported on top of a P2P protocol.
The one part where I felt something felt not ideal was the optional fields of the public personal profile reveal and awful lot of information no sane human should share to all 7 billion other humans (including, sadly, many fraudsters): do not disclose your date of birth to an unrestricted audience, for instance. Also, some people may break their employment contract by disclosing the detailed department in which they work, whereas it would be okay to disclose that selectively after a link has been established.
What is the next step? Perhaps a prototypical implementation, as is custom before standardizing something.
Regarding the claim of security and decentralization compared to legacy email, the use of the Web infrastructure means that DNS and security certificates remain ITSEC/centralization bottlenecks.
Using the Web to get adoption makes sense from a practical point of view. Scientifically, I'd be interested to see a version of this ported on top of a P2P protocol.