Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handles: consider clarifying that TXT data could be comma-separated #320

Closed
bnewbold opened this issue Jul 3, 2024 · 1 comment
Closed
Labels

Comments

@bnewbold
Copy link
Contributor

bnewbold commented Jul 3, 2024

The value (data) of a handle resolution DNS TXT record is currently did= followed by the DID itself, eg did=did:plc:abc123.

This follows a somewhat-common syntax for DNS data which can be a list of key/value pairs separated by comma (no whitespace). If we want that syntax for handle resolution, we should clarify it in the specs. Specifically that there might be multiple values, and that the DID might not be the first value.

Relatedly, we might want to make the did= be optional if there is only a single value.

Had these thoughts while reading through: https://datatracker.ietf.org/doc/draft-ietf-dnsop-domain-verification-techniques/

@bnewbold bnewbold added the specs label Jul 3, 2024
@bnewbold
Copy link
Contributor Author

bnewbold commented Oct 3, 2024

thought this through at some point, and think these changes would be bad/non-sensical. closing.

@bnewbold bnewbold closed this as completed Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant