From: Rich Felker <dalias@libc.org>
To: Markus Wichmann <nullplan@gmx.net>
Cc: musl@lists.openwall.com, David Schinazi <dschinazi.ietf@gmail.com>
Subject: Re: [musl] mDNS in musl
Date: Fri, 8 Mar 2024 12:22:38 -0500 [thread overview]
Message-ID: <20240308172238.GO4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <ZesvNmdw-8bzkZ7z@voyager>
On Fri, Mar 08, 2024 at 04:31:02PM +0100, Markus Wichmann wrote:
> Am Wed, Mar 06, 2024 at 04:17:44PM -0800 schrieb David Schinazi:
> > I'm definitely supportive of the slippery slope argument, but I think
> > there's still a real line between mDNS and NetBIOS. mDNS uses a different
> > transport but lives inside the DNS namespace, whereas NetBIOS is really its
> > own thing - NetBIOS names aren't valid DNS hostnames.
>
> One thing that came to me after thinking about it: This really puts a
> wrenchs in the works of the "just proxy it" argument. Not for mDNS, but
> more generally for further possible backends for the list of hosts. If
> you want to support a backend that supports names that DNS can't, then
> proxying isn't a solution.
Who said we want support for names that DNS can't support?
> We may have to look into integrating nscd support into the search for
> host names. We already have it for passwd queries, after all. And then
> of course there are all the attendant questions:
> - Do we query nscd always or only with some config option?
> - Do we query nscd after DNS or vice-versa? Is this not a policy
> question?
> - Is nscd failure authoritative?
> &c., &c.
The nscd wire format for hostnames is just bad. For example it can't
convey scope_id in IPv6 results, while musl's /etc/hosts
implementation can and does, making it actually useful for link-local
addresses. Maybe it could be extended, but I don't see any point in
worrying about this until there's a concrete need, which has not been
shown.
Rich
next prev parent reply other threads:[~2024-03-08 17:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 7:29 David Schinazi
2024-03-06 16:15 ` Rich Felker
2024-03-06 16:45 ` Jeffrey Walton
2024-03-07 0:17 ` David Schinazi
2024-03-07 2:43 ` Rich Felker
2024-03-07 22:50 ` David Schinazi
2024-03-08 0:08 ` Rich Felker
2024-03-08 1:30 ` David Schinazi
2024-03-08 2:06 ` David Schinazi
2024-03-08 2:52 ` Rich Felker
2024-03-08 3:34 ` David Schinazi
2024-03-08 3:47 ` Rich Felker
2024-03-08 4:47 ` David Schinazi
2024-03-08 13:31 ` Rich Felker
2024-03-08 19:15 ` David Schinazi
2024-03-08 20:31 ` Rich Felker
2024-03-08 21:55 ` David Schinazi
2024-03-08 22:54 ` Rich Felker
2024-03-08 23:44 ` David Schinazi
2024-03-21 9:21 ` David Schinazi
2024-03-21 12:07 ` Rich Felker
2024-03-21 13:50 ` David Schinazi
2024-03-21 17:45 ` Luca Barbato
2024-03-21 19:35 ` Rich Felker
2024-03-22 0:10 ` David Schinazi
2024-03-22 0:29 ` Tomas Volf
2024-03-22 0:36 ` David Schinazi
2024-03-22 0:38 ` Rich Felker
2024-03-09 0:23 ` Jeffrey Walton
2024-03-08 15:31 ` Markus Wichmann
2024-03-08 17:22 ` Rich Felker [this message]
2024-03-06 16:15 ` Markus Wichmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240308172238.GO4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=dschinazi.ietf@gmail.com \
--cc=musl@lists.openwall.com \
--cc=nullplan@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).