Re: [DNSOP] private-use in-meeting chat comments

Tony Finch <> Tue, 17 November 2020 21:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EDEF23A0A2E for <>; Tue, 17 Nov 2020 13:46:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Bxt5RxCeT2IW for <>; Tue, 17 Nov 2020 13:46:02 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 811943A0992 for <>; Tue, 17 Nov 2020 13:46:02 -0800 (PST)
X-Cam-AntiVirus: no malware found
Received: from ([]:38970) by ( []:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1kf8nX-000NrP-Qy (Exim 4.92.3) (return-path <>); Tue, 17 Nov 2020 21:45:59 +0000
Date: Tue, 17 Nov 2020 21:45:59 +0000
From: Tony Finch <>
To: Brian Dickson <>
cc: " WG" <>
In-Reply-To: <>
Message-ID: <>
References: <>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <>
Subject: Re: [DNSOP] private-use in-meeting chat comments
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Nov 2020 21:46:07 -0000

Brian Dickson <> wrote:

> One potential approach is to say (in the RFC) that one of the two-letter
> reserved codes should avoid name collision by putting a collision-resistant
> second-level label, below .zz and above the private use usage (and use that
> particular two-letter code in that manner exclusively).

This kind of thing, or, is not that different in terms of
usability / ugliness from assigning a unique subdomain under a domain that
has been registered in the normal way.

There's also a privacy leak: if you assign a unique subdomain then when a
device roams and leaks queries for the private domain, the device can be
tracked and correlated with other devices that use the same private

I have a terrible mental conflict trying to weigh this privacy issue
against the horrible consequences of encouraging people to squat on
unassigned domains and use colliding hostnames. The privacy leak probably
needs to be fixed regardless, and if it is fixed then there would be a bit
less pressure in favour of unwise squatting.

f.anthony.n.finch  <>
Biscay: Southerly 3 to 5, veering westerly 5 or 6 later in northwest.
Moderate, occasionally rough in northwest. Rain later. Good, occasionally