This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:s_cli:05_contents:02_prt:identity:03_theory:05_issues [2021/06/27 23:09] nick |
dido:public:s_cli:05_contents:02_prt:identity:03_theory:05_issues [2022/02/03 20:35] (current) 52.45.51.99 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The following issues are associated with the theoretical DIDO Identity workflow: | The following issues are associated with the theoretical DIDO Identity workflow: | ||
| - | - There are no [[dido:public:ra:xapend:xapend.b_stds:tech | Technical]] or [[dido:public:ra:xapend:xapend.b_stds:defact | deFacto standards]] that cover the use of Identities on a DIDO. PII Secure Smart Contract (PIISSC) is theoretical. This doesn't mean that one can not exist and that ll efforts to attain one should be abandoned. Instead, the PIISSC should be used as a starting point. One thing that it is lacking is a direct command interface. Currently, there are two ways to control the PIISSC, using questions and using Rules. | + | - There are no [[dido:public:ra:xapend:xapend.b_stds:tech | Technical]] or [[dido:public:ra:xapend:xapend.b_stds:defact | deFacto standards]] that cover the use of Identities on a DIDO. PII Secure [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contract|Smart Contract]] (PIISSC) is theoretical. This doesn't mean that one can not exist and that ll efforts to attain one should be abandoned. Instead, the PIISSC should be used as a starting point. One thing that it is lacking is a direct command [[dido:public:ra:xapend:xapend.a_glossary:i:interface|interface]]. Currently, there are two ways to control the PIISSC, using questions and using Rules. |
| - | - No government agencies are currently supporting a PIISC. However, the Trusted Traveler programs could help resolve this quickly by using a DIDO to hold the information rather than a server. Servers are subject to [[dido:public:ra:xapend:xapend.a_glossary:s:security_breach]], [[dido:public:ra:xapend:xapend.a_glossary:d:data_breach]], network vulnerabilities such as [[dido:public:ra:xapend:xapend.a_glossary:d:dos]] or [[dido:public:ra:xapend:xapend.a_glossary:d:dil]] environments caused by remotenes, sunspots tr other disruptions to networks. | + | - No government agencies are currently supporting a PIISC. However, the Trusted Traveler programs could help resolve this quickly by using a DIDO to hold the information rather than a [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]]. Servers are subject to [[dido:public:ra:xapend:xapend.a_glossary:s:security_breach]], [[dido:public:ra:xapend:xapend.a_glossary:d:data_breach]], network vulnerabilities such as [[dido:public:ra:xapend:xapend.a_glossary:d:dos]] or [[dido:public:ra:xapend:xapend.a_glossary:d:dil]] environments caused by remotenes, sunspots tr other disruptions to networks. |
| - Adding PIISSC to existing Known Traveler programs such as the USA's TSA Pre, Global Entry, Nexus, Sentri or FAST [[https://github.com/blockchain-etl/ethereum-etl]], Germany's EasyPass [[https://www.cntraveler.com/story/how-to-get-through-european-customs-quickly]], the UK's ePassport, Netherlands Fast Low-Risk Universal Crossing (FLUX, Australia's SmartGate System, Korea's Smart Entry Service, Asia-Pacific Economic Cooperation US APEC Business Travel Card Program. (( | - Adding PIISSC to existing Known Traveler programs such as the USA's TSA Pre, Global Entry, Nexus, Sentri or FAST [[https://github.com/blockchain-etl/ethereum-etl]], Germany's EasyPass [[https://www.cntraveler.com/story/how-to-get-through-european-customs-quickly]], the UK's ePassport, Netherlands Fast Low-Risk Universal Crossing (FLUX, Australia's SmartGate System, Korea's Smart Entry Service, Asia-Pacific Economic Cooperation US APEC Business Travel Card Program. (( | ||
| Lori Zaino, | Lori Zaino, | ||