On Thu, 20 Feb 2025, Niall O'Reilly wrote:
Possible name: getBETTERinfo
Goal: design data structure and related APIs for making HTTPS/SVCB data, as
well as what getaddrinfo() provides, available, as simply as possible, to
an application.
Isn't this pretty much what is already being attempted by getdns, libunbound,
c-ares and the likes?
But yes, a worthy project it sounds like!
Things to take into account (first three are already handled by
getaddrinfo):
- RFC3493 (addrinfo)
- RFC3484 (address selection policy -- ip6addrctl.conf (BSD),
gai.conf(GNU))
- nsswitch
Writing a getaddrinfo drop-in replacement is a task that has been attempted
and failed countless number of times by competent developers.
So even without adding anything extra, doing this "right" is hard.
- RFC9460 (HTTPS/SVCB RRs)
- Happy Eyeballs v3 draft
(https://datatracker.ietf.org/doc/html/draft-pauly-v6ops-happy-eyeballs-v3-02)
Happy Eyeballs v2 is enough of a challenge as it for example does not work
with getaddrinfo due to its limited API. It'll be interesting to see what v3
changes in the mix. I suspect the real complications will probably end up in
the layers outside of pure DNS though.
--
/ daniel.haxx.se || https://rock-solid.curl.dev
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
