Skip to content

Adding a new "hyper" protocol - #2

Draft
martinheidegger wants to merge 1 commit into
mainfrom
hyper-protocol
Draft

Adding a new "hyper" protocol#2
martinheidegger wants to merge 1 commit into
mainfrom
hyper-protocol

Conversation

@martinheidegger

Copy link
Copy Markdown
Owner

While developing hyper-dns I noticed a two things that were problematic:

  • No prefix for domains. Learning lessons from dnslink here that uses _dnslink.<name> to look up names initially instead of <name> to support CNAME and ALIAS entries on the main entry. This proposal prefixes domains with hyper-dns because - unfortunately - dnslink's implementations don't support multiple dnslink= text entries per domain. I am not sure how important a fallback to <name> really is, if hyper-dns.<name> is given?
  • Immediate well-known lookups. Right now there is no way to tell if a name does not support dat without doing a https request. The vast majority of domains out there do not support dat and looking up those domains may make us seem like a bad actor. The solution proposed in this PR is to only use well-known lookups if a special key is set, specifically hyper=well-known.

@martinheidegger
martinheidegger marked this pull request as draft April 15, 2021 02:20
@martinheidegger

Copy link
Copy Markdown
Owner Author

After conversations around this yesterday I still need to work on it, some more tests needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant