mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] mDNS in musl
Date: Thu, 7 Mar 2024 22:47:40 -0500	[thread overview]
Message-ID: <20240308034740.GL4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPDSy+6wtOeE8MPhmzwcUBmQkCeo1EdjSNu3MA5cSC8VzDniTQ@mail.gmail.com>

On Thu, Mar 07, 2024 at 07:34:33PM -0800, David Schinazi wrote:
> Hmmm. The cleaner option with the new config option and support for
> querying on all interfaces probably reaches a level of complexity where
> running a resolver on localhost might be best. And I honestly agree with
> your point that overloading the config option isn't great design. So
> perhaps "not doing it at all" is the answer then. I'll think about it some
> more, and discuss it with some mDNS experts at the next IETF meeting in a
> couple weeks. I'll report back if someone has a clever idea that wouldn't
> violate the design principles we've discussed in this thread. But if not, I
> want to say thanks for thinking through this with me.

I don't think the conclusion of this thread is necessarily "don't".
The right form of config option, especially if there's consensus on
what it should look like, is a very viable path, and the IP_PKTINFO
thing you found makes the implementation a lot simpler.

Having input from experts on the mDNS side would be most welcome and
sounds like a good next step to figuring out if this makes sense.

Rich

  reply	other threads:[~2024-03-08  3:47 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 [this message]
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
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=20240308034740.GL4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=dschinazi.ietf@gmail.com \
    --cc=musl@lists.openwall.com \
    /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).