Re: [DNSOP] Deprecating infrastructure .INT domains

Petr Špaček <> Fri, 12 November 2021 12:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5D7B93A0EA4 for <>; Fri, 12 Nov 2021 04:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.429
X-Spam-Status: No, score=-5.429 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key) header.b=mq+FCrAV; dkim=pass (1024-bit key) header.b=Xrv3JVP1
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id osoJ7oNxmBY8 for <>; Fri, 12 Nov 2021 04:55:19 -0800 (PST)
Received: from ( [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 434C63A0EB3 for <>; Fri, 12 Nov 2021 04:55:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by (Postfix) with ESMTPS id 18B32433F33 for <>; Fri, 12 Nov 2021 12:55:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=ostpay; t=1636721716; bh=GQu3EwOa1HyMT4EjbwfIKcQDuSgYSv/z5ZfHVq+kgjA=; h=Date:Subject:To:References:From:In-Reply-To; b=mq+FCrAVG6JKA3rHm5ErcYDIyDPGffkT9at2T1DqKhhZsv1UWAc8G4u/fXen/8WGL LdgAjT1zqmGysgICChqOKyvsxCxrLhSlMWYprCbPAqa215Z3oeQ4JveDJAiEu7CDzd YydFn7eRBaKH3OeXiOMcVtd6SUeU67WWXDSfu6FI=
Received: from (localhost.localdomain []) by (Postfix) with ESMTPS id 0E4F3F04F55 for <>; Fri, 12 Nov 2021 12:55:16 +0000 (UTC)
Received: from localhost (localhost.localdomain []) by (Postfix) with ESMTP id DB224F06379 for <>; Fri, 12 Nov 2021 12:55:15 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 DB224F06379
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1636721715; bh=fOYMcPyHFrKjwOM4yfVqhgG2gquNtzo4U/M9GUTCKN4=; h=Message-ID:Date:MIME-Version:To:From; b=Xrv3JVP1ptZFmoJtSrNwDUFpztjX70VCCYW914tOjKObb4Tz/SQieHrV2ekyWTfmB yDL4eUbNR8I/sSZHlhSiV1qFZfO6Ss+D6bouMCaHvGDV7OEXvb+ohZxjIzRr2xUCtP 2F3Bu/vt9oL7WOeQJs+d5uYWXYqnLiwKsPNVwink=
Received: from ([]) by localhost ( []) (amavisd-new, port 10026) with ESMTP id eJ9VcgdLmV7J for <>; Fri, 12 Nov 2021 12:55:15 +0000 (UTC)
Received: from [] ( []) by (Postfix) with ESMTPSA id 716DAF04F55 for <>; Fri, 12 Nov 2021 12:55:15 +0000 (UTC)
Message-ID: <>
Date: Fri, 12 Nov 2021 13:55:12 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Content-Language: en-US
References: <YY1G7mWZVJZkZZyx@KIDA-9190.local> <>
From: Petr Špaček <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [DNSOP] Deprecating infrastructure .INT domains
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: Fri, 12 Nov 2021 12:55:24 -0000

On 11. 11. 21 17:56, Joe Abley wrote:
> Hi Kim,
> I like the idea of cleaning this up.
> Choosing as an example, I think it would be useful to either update RFC 1706 to make it clear that the advice in section 6 of that document no longer applies, and that no reverse mapping for NSAP is provided in the DNS. I don't think this is a great operational necessity since I imagine the number of people who expect this to work is approximately zero but it seems good to be tidy.
> [I'd suggest reclassifying 1706 to historic but that'd also affect the specification for the NSAP RRType; maybe that's a good idea too, but it seems outside the scope of what you are trying to achieve, and I don't know how we would confirm that it's a good idea.]
> Similar comment for other domains where there's similar existing advice.

FTR I can't see any problems with that, and suggest to do that in one go 
in this document. We have enough RFCs already and wasting more numbers 
(and work) on simple deprecation does not sound useful to me.

Petr Špaček

> Happy to offer actual text if that seems useful.
> Joe
>> On 11 Nov 2021, at 11:38, Kim Davies <> wrote:
>> Colleagues,
>> I wanted to draw your attention to an Internet Draft we’ve developed,
>> its goal is to formally deprecate a number of historic “.int”
>> domains that were designated for Internet infrastructure purposes
>> decades ago and appear for all intents and purposes obsolete. After some
>> limited consultation on developing the approach so far, it would be
>> useful to get some additional eyes on it so we have greater confidence
>> there is nothing we’ve missed.
>> Datatracker link:
>> It’s a short document, but at its heart we’ve identified the
>> following domains that are referenced in places but seem to be obsolete:
>>    ,,,,,
>> Most of these are not delegated in the int zone any longer, but there
>> are lingering references to them.
>> Thanks in advance for any insight, and apologies if you get this message
>> in duplicate,