Re: [dd] [Ext] Listing of mentioned potential desired extensions to today's DNS delegation
Wes Hardaker <wjhns1@hardakers.net> Thu, 22 February 2024 18:08 UTC
Return-Path: <wjhns1@hardakers.net>
X-Original-To: dd@ietfa.amsl.com
Delivered-To: dd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D811BC1E0733 for <dd@ietfa.amsl.com>; Thu, 22 Feb 2024 10:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
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 JIfikTLZo7TK for <dd@ietfa.amsl.com>; Thu, 22 Feb 2024 10:08:41 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2036C18DB86 for <dd@ietf.org>; Thu, 22 Feb 2024 10:08:40 -0800 (PST)
Received: from localhost (unknown [107.1.187.90]) by mail.hardakers.net (Postfix) with ESMTPA id 406DF20DE8; Thu, 22 Feb 2024 10:08:40 -0800 (PST)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 406DF20DE8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1708625320; bh=xmw/1x2eISfC8UkxxqwGhQ3hbjNygzszEEPSt0Z52JM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=gOonu2cQblHGwq4bTyphblNSE6Mc4Yl3IJmhsu8LieA706dkLghpIYnkFUUn5O3vg 19yrPHN4k+7pw2oRVik30UQguDbeybR33Thx918f4Wy9Zy5WF0wTVbcGkgVRY48Wwz lLJJ9qDAG4SK5rPeOwEvpl0XtG6Z9yG/kKG5aJLA=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Edward Lewis <edward.lewis@icann.org>
Cc: Paul Hoffman <paul.hoffman@icann.org>, "dd@ietf.org" <dd@ietf.org>
In-Reply-To: <89080A71-497A-4A30-91D0-21259D702D2D@icann.org> (Edward Lewis's message of "Thu, 22 Feb 2024 17:34:56 +0000")
References: <89080A71-497A-4A30-91D0-21259D702D2D@icann.org>
Date: Thu, 22 Feb 2024 10:08:39 -0800
Message-ID: <yblplwomkwo.fsf@wx.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/9hcmNRgifxnYTrS0wyBVKsKF630>
Subject: Re: [dd] [Ext] Listing of mentioned potential desired extensions to today's DNS delegation
X-BeenThere: dd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS Delegation <dd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dd>, <mailto:dd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dd/>
List-Post: <mailto:dd@ietf.org>
List-Help: <mailto:dd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dd>, <mailto:dd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2024 18:08:45 -0000
Edward Lewis <edward.lewis@icann.org> writes: > Regarding any chartering conversation - are you seeking a list > restricted to updates of the DNS for which there is a realistic chance > of it being implemented based on current conditions or a list > including "blue-sky" futures? As an example of the latter, migrating > to an entirely different wire-format? IMHO only: IETF BOFs have always had a conversation around how likely is the success of the proposed work? and how soon can it be tractable? The IETF generally takes a heavy evolution vs revolution approach and works towards solutions that don't require a flag day. This often means very slow rollouts (see both IPv6 and DNSSEC) as a result. So the key, IMHO, is to develop a path that makes future changes like wire-formats possible which it really isn't now. From what I gather from the discussions to date is that one goal of the problem space is define how to do other version signaling. EG, a common reason listed for new delegation formats is to specify a different transport (eg TLS), which absolutely is a new wire format too, just not in the DNS part of the messages sent. For the charter (did I mention IMHO), I'd ask not "what can we fit in it that will solve a huge problem?" but rather "what's the next achievable step that will help enable future steps toward a larger goal?". -- Wes Hardaker USC/ISI
- [dd] Listing of mentioned potential desired exten… Paul Hoffman
- Re: [dd] [Ext] Listing of mentioned potential des… Edward Lewis
- Re: [dd] [Ext] Listing of mentioned potential des… Wes Hardaker
- Re: [dd] [Ext] Listing of mentioned potential des… Brian Dickson
- Re: [dd] [Ext] Listing of mentioned potential des… Paul Hoffman