From: Sebastian Moeller <moeller0@gmx.de>
To: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Cc: Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Disappointment on "Best Newcomer Router" front
Date: Mon, 26 Feb 2024 10:47:16 +0100 [thread overview]
Message-ID: <7E95C000-5972-4ED2-B639-DDAEA2B08309@gmx.de> (raw)
In-Reply-To: <20240226092405.GB18166@unix-ag.uni-kl.de>
Mmmh,
> On 26. Feb 2024, at 10:24, Erik Auerswald via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> Hi,
>
> On Sun, Feb 25, 2024 at 06:34:47PM -0500, Rich Brown via Bloat wrote:
>> [...]
>> Then they plug the new router's WAN port into their ISP modem's port,
>> connect their laptop's Ethernet to the LAN port, point their browser to
>> "openwrt.lan"
>
> How about "openwrt.local" to conform to mDNS (RFC 6762) and IANA's
> [special-use domain names][1]? Or perhaps "openwrt.internal" in the
> future?
Or perhaps openwrt.home.arpa...? I think openwrt.local shouldd not be used, because .local is reserved for mDNS, no?
OpenWrt defaults to .lan, and .lan is one of the top ten 'leaking' TLDs already, we should simply< agree never to assign the 10 (or 15 or whatever) highest leaking fake TLD as true TLDs, and problem solved, without requiring any more bike shedding from IANA, ICAN, ARPA, ...
I am sure that, as pragmatic as it might be, is not going to happen... Perhaps because someone intends to convert one/more of the leaking fake TLDs into real TLDs?
> [1]: https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml
>
>> [...]
>
> Br,
> Erik
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2024-02-26 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 22:15 Rich Brown
2024-02-25 22:25 ` Frantisek Borsik
2024-02-25 22:28 ` Sebastian Moeller
2024-02-25 22:38 ` Rich Brown
2024-02-25 22:57 ` David Lang
2024-02-25 23:05 ` Sebastian Moeller
2024-02-25 23:34 ` Rich Brown
2024-02-26 9:24 ` Erik Auerswald
2024-02-26 9:47 ` Sebastian Moeller [this message]
2024-02-26 10:01 ` Erik Auerswald
2024-02-26 14:28 ` [Bloat] mDNS (was Disappointment on "Best Newcomer Router" front) Rich Brown
2024-02-26 23:17 ` Kenneth Porter
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E95C000-5972-4ED2-B639-DDAEA2B08309@gmx.de \
--to=moeller0@gmx.de \
--cc=auerswal@unix-ag.uni-kl.de \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox