IETF Logo Mail Archive

Re: [dd] [Ext] Listing of mentioned potential desired extensions to today's DNS delegation

Brian Dickson <brian.peter.dickson@gmail.com> Wed, 28 February 2024 17:24 UTC

Return-Path: <brian.peter.dickson@gmail.com>
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 69B65C14F5E9 for <dd@ietfa.amsl.com>; Wed, 28 Feb 2024 09:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=gmail.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 XQLka-CKNM-l for <dd@ietfa.amsl.com>; Wed, 28 Feb 2024 09:24:30 -0800 (PST)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 A3C87C14F5FA for <dd@ietf.org>; Wed, 28 Feb 2024 09:24:30 -0800 (PST)
Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-1dcafff3c50so330895ad.0 for <dd@ietf.org>; Wed, 28 Feb 2024 09:24:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709141069; x=1709745869; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=ELifXu66D3lcsuus/yOw87edSSocJnec36Z30q9lLSU=; b=JeFZc/6mU4BfOJ5b96rWzSXhCrfG0CCiiWyxzkjcUoUS799PSRdUhpAxFgGeQ3gr7v usC6k3LN4G5m6tF52iApsaydz4CB3mDiSGdshu4w+eJepvKZWW+AJSFjCVU5Gf4mh1gc 53AKH7Z+U2dehMO0nCWyRFWPY5+puZs6woBcH5v+aB3cdZnQDOAcvorrPtChk1t7uOrG 2Br5aIL8NbwGu06/ZkmhtWHlt4X/+uRDpmEPsP7L55OVWe5D9jWezndfMqF+lZYja/it yRW2zqQIX2O6cHDPB2Qh8o9l1SDeDomkhxV/5xfFTTxz8C+n7baUhlvtHC3aXLEYd6jq Qcwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709141069; x=1709745869; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ELifXu66D3lcsuus/yOw87edSSocJnec36Z30q9lLSU=; b=CibDtmfxnfiwLmIO9pOMJbW0VF7/sqH34M45sj9GgyqSxX9lQjgjPLCbMVt6/ypVvQ s7iVUkxyarn5cxU3iv50UoTfTiSqtUlGpWEx8ENL2eh+IiYXk4dKXWJg3ZW5tXzBkqTe YE+RE4wieZwHvYDBEhVmC+pqDxO7lbIcLnOkE/gEVaG1T6gz5FCaTfPfolmHdKtMQ0hh Q7beXsNj3cLhcXYlnBK4baGdELoczTwovjxhP4BW4toFmu1n9l7Um+dMrYQVh47JGc1Z OMcqFRst2bOrO2ta8oB6+dPAcZKvJyfn83w7vPUVVzSgGYE9duo0t/tNvrIRPvArQIYT Lx/w==
X-Forwarded-Encrypted: i=1; AJvYcCUk41jrkGoinSAsa/YV5ZWrZbUy7OCNP+ACSlFzj9cC6+eUnhLZZ3ipX72fxn253nvxL8GASw2wbn8GnA==
X-Gm-Message-State: AOJu0YxDBtSpMG7uLiU2XZZSF4miA/s5MxZax/mYM4JlQfcBFqUTG8aH gUo+cN1m6EpWsXQxqjiGs/KJe2Tn9Mh5L9OoUL9aTPwcqJSriQwK
X-Google-Smtp-Source: AGHT+IGOm2o+BQCUn4bAw7wxKnWJ0urJ7TlWjeMnZ4dNVrTpLMN0SKVsjDRLbziiuj9brJY9JsRCig==
X-Received: by 2002:a17:902:d488:b0:1db:e78e:b38d with SMTP id c8-20020a170902d48800b001dbe78eb38dmr146132plg.18.1709141069583; Wed, 28 Feb 2024 09:24:29 -0800 (PST)
Received: from smtpclient.apple ([2601:646:8800:5b50:a890:c03f:24e2:736d]) by smtp.gmail.com with ESMTPSA id y4-20020a170902d64400b001d54b763995sm3551815plh.129.2024.02.28.09.24.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 28 Feb 2024 09:24:29 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Brian Dickson <brian.peter.dickson@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 28 Feb 2024 09:24:17 -0800
Message-Id: <C6379AE3-2C45-4E70-9675-701F9E64A175@gmail.com>
References: <yblplwomkwo.fsf@wx.hardakers.net>
Cc: Edward Lewis <edward.lewis@icann.org>, Paul Hoffman <paul.hoffman@icann.org>, dd@ietf.org
In-Reply-To: <yblplwomkwo.fsf@wx.hardakers.net>
To: Wes Hardaker <wjhns1@hardakers.net>
X-Mailer: iPhone Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/wlGJsFuCfcci4e_EKLB-DqyO6lM>
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: Wed, 28 Feb 2024 17:24:34 -0000

Sent from my iPhone

> On Feb 22, 2024, at 10:09 AM, Wes Hardaker <wjhns1@hardakers.net> wrote:
> 
> 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.

This is a good observation; thank you Wes.

I would like to use this as a hopefully obvious method, which would provide a path towards a new DNS message wire format: add an optional SVCB parameter for the wire format, with a default value of “classic” (ie if not specified).

The SVCB-based migration would then be to have port+protocol+messageFormat as the tuple, and offer both new format and old format targets during migration.

One example might be newPort+UDP+newFormat in addition to 53+UDP (with implied classic format).

Brian

> 
> 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 mailing list
> dd@ietf.org
> https://www.ietf.org/mailman/listinfo/dd

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