[DNSOP] Re: Call for Adoption: draft-davies-internal-tld

Michael De Roover <ietf@nixmagic.com> Fri, 09 May 2025 15:08 UTC

Return-Path: <ietf@nixmagic.com>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id ABAF526DF12C for <dnsop@mail2.ietf.org>; Fri, 9 May 2025 08:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHu0JclejoSM for <dnsop@mail2.ietf.org>; Fri, 9 May 2025 08:08:19 -0700 (PDT)
Received: from nixmagic.com (e1.nixmagic.com [116.203.235.171]) by mail2.ietf.org (Postfix) with ESMTP id 1D67226DF123 for <dnsop@ietf.org>; Fri, 9 May 2025 08:08:18 -0700 (PDT)
Received: from thonkpad.lan (thonkpad.lan [192.168.10.23]) by nixmagic.com (Postfix) with ESMTPSA id 16504CA6A3 for <dnsop@ietf.org>; Fri, 9 May 2025 15:08:18 +0000 (UTC)
From: Michael De Roover <ietf@nixmagic.com>
To: dnsop@ietf.org
Date: Fri, 09 May 2025 17:08:17 +0200
Message-ID: <2035475.usQuhbGJ8B@thonkpad.lan>
Organization: thonkpad.lan
In-Reply-To: <m1uCKDf-0000LpC@stereo.hq.phicoh.net>
References: <1C9E8ABA-4399-491B-A9F4-D9ACCB1BA72C@virtualized.org> <449d6030-80c7-460d-93db-73778a257036@app.fastmail.com> <m1uCKDf-0000LpC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart3559261.QJadu78ljV"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: GNJDIBFJYH4SF2JEXSGYJR3BS5P7SDSS
X-Message-ID-Hash: GNJDIBFJYH4SF2JEXSGYJR3BS5P7SDSS
X-MailFrom: ietf@nixmagic.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Call for Adoption: draft-davies-internal-tld
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/urFyOAcQ2Y8AjhHfMRya4K7ODKY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

On Tuesday, 6 May 2025 17:28:30 CEST Philip Homburg wrote:
> > In my experience this is done using regular-expression matching,
> > and that's all. 
> 
> 
> At least for Firefox, I think John is right and it is the PSL.
> 
> If I start typing foo.internal then Firefox suggests visiting the
> domain. If I then continue with foo.internal2 then Firefox only suggests
> searching. Only an explicit list would know about that difference.

I went looking for evidence of this in Firefox' source code, and found it in their repository 
under these links.
https://github.com/mozilla-firefox/firefox/blob/main/netwerk/dns/
effective_tld_names.dat[1]
https://publicsuffix.org/list/public_suffix_list.dat[2]
Interestingly, neither mentions the use of .internal. Maybe it's a distribution-specific thing?

For LibreOffice, I am seeing their source code mentioned at the links below.
https://www.libreoffice.org/about-us/source-code/[3]
I have mirrored this repository into my Gitea instance, under their MPL 2.0 license. It is 
not, however, continuously updating.
https://git.nixmagic.com/mir/libreoffice[4]
Still working on the search there, but if you want to have a kick at it yourself, feel free to 
use my Gitea instance to do so.

For Telegram, I had a chat with some of the people working on Telegram Desktop. They 
mentioned it to be handled on their servers, which is a proprietary component.
https://t.me/TelegramDesktopTalk/132893[5]
But it shouldn't be too difficult to write some code that sends examples for every TLD in 
the PSL and reads back how Telegram formatted them. A well-behaved userbot - one that 
doesn't make it a fire-hose of messages - could easily do that.

-- 
Met vriendelijke groet,
Michael De Roover

Mail: ietf@nixmagic.com
Web: michael.de.roover.eu.org

--------
[1] https://github.com/mozilla-firefox/firefox/blob/main/netwerk/dns/
effective_tld_names.dat
[2] https://publicsuffix.org/list/public_suffix_list.dat
[3] https://www.libreoffice.org/about-us/source-code/
[4] https://git.nixmagic.com/mir/libreoffice
[5] https://t.me/TelegramDesktopTalk/132893