Domain - Revision history

Tom: /* Context */

2022-05-10T17:33:38Z

‎Context

2021-04-25T18:40:23Z

‎Problems

2021-04-25T18:39:14Z

‎Problems

2021-04-25T18:38:51Z

‎Problems

2021-04-25T18:37:34Z

‎Problems

2021-04-25T18:16:37Z

‎Context

2021-04-25T18:14:54Z

‎Context

2021-04-25T18:14:28Z

‎Context

2021-04-25T18:13:37Z

‎Context

2021-04-25T18:12:22Z

‎Context

@@ Line 7: / Line 7: @@
 * The next step for [[Identity Management]] was to create domains that were dedicated to identifying users like '''tom@hotmail.com'''. Those users felt like they "owned" the name, but that was not strictly true.
 * First Card-space, and now the DID-core spec were created to give the users complete control of their own identifiers. Now we are engaged on a great struggle testing whether those sell-issued identifiers, so conceived and so dedicated, can long endure. We are met on a great battle-field of that struggle to show the world that such a scheme can succeed.
 ==Problems==

@@ Line 10: / Line 10: @@
 ==Problems==
 * The domain served a purpose: to bind together a set of users and computers in a domain of trust.  There was a need for that then. And so there is a need for that today.
-* Domainless, or [[Zero Trust Architecture]] solutions focus on removing the domain boundaries. They have not been good at addressing what we need to do to restore the trust boundaries.
+* Domainless, or [[Zero Trust Architecture]] solutions focus on removing the domain boundaries and pushing the [[Authorization]] out to the edges. They have not been good at addressing what we need to do to restore the trust boundaries.
 ==References==
 [[Category: Glossary]]

@@ Line 10: / Line 10: @@
 ==Problems==
 * The domain served a purpose: to bind together a set of users and computers in a domain of trust.  There was a need for that then. And so there is a need for that today.
-* Domainless, or [[Zero Trust Architecture]] solutions focus on removing the domain boundatries. They have not been good at addressing what we need to do to restore the trust boundaries.
+* Domainless, or [[Zero Trust Architecture]] solutions focus on removing the domain boundaries. They have not been good at addressing what we need to do to restore the trust boundaries.
 ==References==
 [[Category: Glossary]]

@@ Line 10: / Line 10: @@
 ==Problems==
 * The domain served a purpose: to bind together a set of users and computers in a domain of trust.  There was a need for that then. And so there is a need for that today.
-* Domainless, or [[Zero Trust]] solutions focus on removing the domain boundatries. They have not been good at addressing what we need to do to restore the trust boundaries.
+* Domainless, or [[Zero Trust Architecture]] solutions focus on removing the domain boundatries. They have not been good at addressing what we need to do to restore the trust boundaries.
 ==References==
 [[Category: Glossary]]

@@ Line 10: / Line 10: @@
 ==Problems==
 * The domain served a purpose: to bind together a set of users and computers in a domain of trust.  There was a need for that then. And so there is a need for that today.
 ==References==
 [[Category: Glossary]]

@@ Line 5: / Line 5: @@
 * The [[Domain Name System]] was the first attempt in the digital age to create a set of [[Identifier]]s that could be associated within a trusted domain. It was a binding between an alphabetic name and an [[IP address]].
 * The next step was to address individuals at one computer system using the '''mailto:''' scheme that is now universal for email address. The address that once identified a user at a computer, now identifies a user at a "domain" of computers.
-* The next step for [[Identity Management]] was to create domains that were dedicated to identifying users like '''tom@hotmail.com'''. Those user felt like they "owned" the name, but that was not strictly true.
+* The next step for [[Identity Management]] was to create domains that were dedicated to identifying users like '''tom@hotmail.com'''. Those users felt like they "owned" the name, but that was not strictly true.
 * First Card-space, and now the DID-core spec were created to give the users complete control of their own identifiers. Now we are engaged on a great struggle testing whether those sell-issued identifiers, so conceived and so dedicated, can long endure. We are met on a great battle-field of that struggle to show the world that such a scheme can succeed.