Move whois out of spec to supplement folder #166
+3
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kentbull
commented
Nov 18, 2025
| Applying the concepts of KEL, BADA-RUN, and KRAM to `did:webs` | ||
|
|
||
| This section is informative. Lets explore the implications of applying these concepts to various `did:webs` elements. | ||
| Using [[ref: KEL]] backed elements in a DID doc simplifies the security concerns. However, future discovery features related to endpoints might consider BADA-RUN. For instance, 'whois' data could be used with [[ref: BADA-RUN]] whereas did:web aliases should not because it could lead to an impersonation attack. We could have a DID document that uses BADA-RUN if we modify the DID CRUD semantics to be RUN semantics without necessarily changing the verbs but by changing the semantics of the verbs. Then any data that fits the security policy of BADA (i.e. where BADA is secure enough) can be stored in a DID document as a database in the sky. For sure this includes service endpoints for discovery. One can sign with [[ref: CESR]] or JWS signatures. The payloads are essentially KERI reply messages in terms of the fields (with modifications as needed to be more palatable), but are semantically the same. The DID doc just relays those replies. Anyone reading from the DID document is essentially getting a KERI reply message, and they then should apply the BADA rules to their local copy of the reply message. |
Contributor
Author
There was a problem hiding this comment.
whois was used in the second sentence here so I reworded the sentence.
kentbull
commented
Nov 18, 2025
| </td> | ||
| <td>specs.json</td> | ||
| <td> | ||
| specs.json is valid but has 2 warning(s) |
Contributor
Author
There was a problem hiding this comment.
In this file there was a whois HTML list item <li> that I removed.
Signed-off-by: Kent Bull <[email protected]>
kentbull
force-pushed
the
whois-removal
branch
from
99a8d07 to
c433799
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today on the did:webs task force meeting it was moved and decided to remove the
whoissection from the specification and to relocate it to a supplementary folder for future reference. This PR does that.