-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
docs/HTTPSRR.md: initial HTTPS RR documentation #16052
Conversation
Good to see progress on this. Happy to try help as I can. A few thoughts:
|
This is still early days. I'm right now focusing on setting up the architecture so that we can get HTTPS records independently of chosen resolver backend (#16054). To make HTTPS RR support usable outside of DoH. When that works decently, it will be easier to work on extending and improving the receiving and handling of the actual records that are received.
Yes thanks. We of course need a lot of live test servers to try it on. Especially before we have worked out how exactly we should go about and add "normal" tests for this.
I figure we ultimately need to chase them - if this feature is actually used in the real world. If the chasing is not done by the resolvers it feels like it might get a little ineffective and thus might not be what servers want to use.
I agree. For now we don't use the IP hints at all, but we should decide what the best use of them is. Maybe check how some of the already deployed HTTPS RR consumers (browsers?) do.
Yes, that is work to observe and potentially contribute to. It can be worth pondering that we do not support Happy Eyeballs v2 in libcurl (due to API limitations primarily). We also need to consider and think about how HTTPS RR works in conjunction with |
On 21 Jan 2025, at 10:27, Daniel Stenberg wrote:
I figure we ultimately need to chase them - if this feature is
actually used in the real world. If the chasing is not done by the
resolvers it feels like it might get a little ineffective and thus
might not be what servers want to use.
I have opened issues with two well-known resolver developers:
- https://gitlab.isc.org/isc-projects/bind9/-/issues/4810
- NLnetLabs/unbound#1065
I'm not expecting a result any time soon, as no milestone
has been set for either.
I'ld like to open an issue for kresd as well, but it's not
clear to me how best to do that.
|
220c5ef
to
b64086a
Compare
7224adc
to
ba11925
Compare
ba11925
to
7f4f192
Compare
No description provided.