From: Michael Richardson <mcr@sandelman.ca>
To: Asmitha Karunanithi <asmithakarun@gmail.com>,
Patrick Williams <patrick@stwcx.xyz>,
openbmc@lists.ozlabs.org
Subject: Re: Resolving service name conflicts
Date: Thu, 03 Sep 2020 08:37:00 -0400 [thread overview]
Message-ID: <2949.1599136620@localhost> (raw)
In-Reply-To: <CANGK-S4gjNiLqnpZcT3bkKTycGEi7u1C-dNW70gMcXb02fS4zA@mail.gmail.com>
Asmitha Karunanithi <asmithakarun@gmail.com> wrote:
> Yup, it would be like "ssh-hostname" because there would be service name
> conflicts, say if there are 100 systems in the network publishing the
> service with the same name, there would be name conflicts for 100 times and
> finally, the service would be published as "ssh#101" to the network.
If I understood correctly.
That goes against what RFC6762/6763 say.
There is a deconflict system is there for a purpose, and avahi handles it
well, and being able to find all the *ssh* services is actually useful.
There can be other information in the PTR/SRV record.
One can ssh to hostname.local if you know the hostname.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2020-09-03 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 5:08 Resolving service name conflicts Asmitha Karunanithi
2020-09-02 15:58 ` Patrick Williams
2020-09-03 7:49 ` Asmitha Karunanithi
2020-09-03 12:37 ` Michael Richardson [this message]
2020-09-03 10:15 ` Jeremy Kerr
2020-09-04 16:37 ` Patrick Williams
2020-09-05 7:35 ` Asmitha Karunanithi
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=2949.1599136620@localhost \
--to=mcr@sandelman.ca \
--cc=asmithakarun@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.