Re: [DNSOP] [Ext] on private use TLDS: .interNAL -> .LAN

S Moonesamy <sm+ietf@elandsys.com> Wed, 06 March 2024 13:51 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23CB6C14F5FD for <dnsop@ietfa.amsl.com>; Wed, 6 Mar 2024 05:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level:
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id en686mKAZ2wY for <dnsop@ietfa.amsl.com>; Wed, 6 Mar 2024 05:51:07 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8E6C14F5FA for <dnsop@ietf.org>; Wed, 6 Mar 2024 05:51:07 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.124.197]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 426DoG4i023879 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Mar 2024 05:50:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1709733050; x=1709819450; i=@elandsys.com; bh=zHzP8BXOuYBx0hx3pS6iiEptrrql1hA2HRKHiDCWkk8=; h=Date:To:From:Subject:In-Reply-To:References; b=A0zSv76Dg/gQ+OBAueIx4ifgV3Cz882ZrFgigi6wblsLhhhilvv9cWGU+SKaCibO7 T/qNscy0NhSipJVtfowc2uABDKGFy/fPArnKw9w8kybzWAcWASpqO7iORQPGBU0XeF OZQIjjinNdgiZDGQF7nhyulLHdbNUQNNdegjDqRQ=
Message-Id: <6.2.5.6.2.20240306052251.096cc600@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 06 Mar 2024 05:49:56 -0800
To: Toerless Eckert <tte@cs.fau.de>, dnsop@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <Zd4vlZ0_cICPsss6@faui48e.informatik.uni-erlangen.de>
References: <Zd3CVsp32g8NAQKf@faui48e.informatik.uni-erlangen.de> <0DD00E9E-D34E-4B68-B5B9-5CB8164B0B95@strandkip.nl> <Zd4vlZ0_cICPsss6@faui48e.informatik.uni-erlangen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/U2Ta3tes6KeuHy02wRuH2ASzWTg>
Subject: Re: [DNSOP] [Ext] on private use TLDS: .interNAL -> .LAN
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2024 13:51:12 -0000

Hi Toerless,
At 10:53 AM 27-02-2024, Toerless Eckert wrote:
>I don't think ICANN are the authoritative experts to define how to 
>best operate
>private DNS zones, especially not modifications to configs if not source code
>to automatically filter out DNS requests for that zone to avoid the 
>overload of
>public DNS servers with requests for it - something which ICANN is 
>suggesting is
>what .internal can achieve. And which i think it may not be able to 
>achieve unless
>appropriate operational recommendations exist and are applied. And 
>if i was a DNS
>operator, i would hope IETF would provide those recommendations.

The IETF angle is that there is a Standards Track memo which 
specified what to do when special handling of a DNS label is required.

Regards,
S. Moonesamy