On Mo, 14.10.24 22:53, Petr Menšík (pemensik@xxxxxxxxxx) wrote: > I think struct addrinfo used by getaddrinfo() is basically good output even > for HTTPS record. But it needs in addition also key=value metadata with > additional parameters. Similar for SRV. The end result is still ordered list > of addresses. But we need a way to extract ALPN, ECH and other parameters. > > Do you have good recommendation, where to discuss this? I am not convinced that in 2024 it's really worth discussing a new C level API. The world is not purely C anymore, and various programming languages these days try to avoid just being libc wrappers. Moreover, the complex protocols involved should not be implemented in-process anymore, there should be process isolation in between. Hence, I am pretty sure you have to focus on some form of local IPC API between client and resolver. I certainly have answered the questions you raised for *myself*, though I am pretty sure you are not going to like my answer: I think the Varlink IPC APIs that systemd-resolved implements are the way to go. There's work going on to add ALPN and stuff hooked into systemd-resolved already. It provides simple SRV resolution APIs already, asynchronously. Lennart -- Lennart Poettering, Berlin -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
