IETF Logo Mail Archive

[DNSOP] Re: [Ext] Re: what problem are we trying to solve, was Call for Adoption: draft-davies-internal-tld

Paul Hoffman <paul.hoffman@icann.org> Tue, 06 May 2025 20:56 UTC

Return-Path: <paul.hoffman@icann.org>
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 A3926259CDCF for <dnsop@mail2.ietf.org>; Tue, 6 May 2025 13:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Wz3UVbAma8Qk for <dnsop@mail2.ietf.org>; Tue, 6 May 2025 13:56:06 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) by mail2.ietf.org (Postfix) with ESMTP id 2A70F259CDCA for <dnsop@ietf.org>; Tue, 6 May 2025 13:56:06 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa2.lax.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 546Ku1QE032291 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 6 May 2025 20:56:02 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 6 May 2025 13:56:01 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1544.011; Tue, 6 May 2025 13:56:01 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Ted Lemon <mellon@fugue.com>
Thread-Topic: [DNSOP] [Ext] Re: what problem are we trying to solve, was Call for Adoption: draft-davies-internal-tld
Thread-Index: AQHbvsf0RhkrBc3xEkClwxAS1QopvrPGilMA
Date: Tue, 06 May 2025 20:56:01 +0000
Message-ID: <6A290954-DB0D-447A-851C-3F74F64C900D@icann.org>
References: <C3487997-B656-4A6D-A069-752077629957@icann.org> <D4177A34-3EF6-45D9-8076-49A12BFCE81F@isc.org> <7935F96B-C006-4D9A-B65B-59652630B46A@fugue.com>
In-Reply-To: <7935F96B-C006-4D9A-B65B-59652630B46A@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12E60515CA1F5D40A89EEB198E4A22F9@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.0.736,FMLib:17.12.80.40 definitions=2025-05-06_08,2025-05-06_01,2025-02-21_01
Message-ID-Hash: SBY6QBD6TOGM3EG5VIE2V4QS6BSXNTKW
X-Message-ID-Hash: SBY6QBD6TOGM3EG5VIE2V4QS6BSXNTKW
X-MailFrom: paul.hoffman@icann.org
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
CC: "dnsop@ietf.org" <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [Ext] Re: what problem are we trying to solve, was 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/74EBTSCSz-y5Fr9SNkRTo3287oU>
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 May 6, 2025, at 13:45, Ted Lemon <mellon@fugue.com> wrote:
> 
> The Apple resolver at least clears the cache whenever it detects a network transition. So the problem Paul is describing wouldn't happen. Dunno what other mobile devices do.
> 
> I think its worth documenting this behavior if the working group wants to do that work.

A big +1 on documenting this (if it is indeed what the WG comes to consensus on). It would greatly reduce the sharp corners being discussed.

--Paul Hoffman

v2.31.3 | Report a Bug | By Email | System Status