IETF Logo Mail Archive

[DNSOP] Re: [Ext] Revised the application for the WALLET RRTYPE

Paul Hoffman <paul.hoffman@icann.org> Fri, 05 July 2024 15:17 UTC

Return-Path: <paul.hoffman@icann.org>
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 3B3B2C1E7251 for <dnsop@ietfa.amsl.com>; Fri, 5 Jul 2024 08:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 c_wlxiVRGa-7 for <dnsop@ietfa.amsl.com>; Fri, 5 Jul 2024 08:17:09 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8925C09E1AE for <dnsop@ietf.org>; Fri, 5 Jul 2024 08:17:09 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa4.dc.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 465FBEbX006195 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 5 Jul 2024 08:11:15 -0700
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.1258.34; Fri, 5 Jul 2024 08:17:04 -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.1258.034; Fri, 5 Jul 2024 08:17:04 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Petr Špaček <pspacek@isc.org>
Thread-Topic: [DNSOP] [Ext] Revised the application for the WALLET RRTYPE
Thread-Index: AQHazu5kJ1BQltHghEC5ZbF8nr3kKA==
Date: Fri, 05 Jul 2024 15:17:04 +0000
Message-ID: <D452D373-B735-47EA-9EC9-C263BDE06E9E@icann.org>
References: <7FC7E35E-915F-4A29-8AB2-948529F4F1CC@icann.org> <A4681A06-0AAC-4F8A-BB3A-7D61CAB09925@icann.org> <947cb0ad-a1e4-447b-8bdc-214b764b74d7@isc.org>
In-Reply-To: <947cb0ad-a1e4-447b-8bdc-214b764b74d7@isc.org>
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="utf-8"
Content-ID: <A770B4E86BFBCB469E855E182789DC73@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-07-05_10,2024-07-05_01,2024-05-17_01
Message-ID-Hash: EIY6O774ZVXWOWLIGX5RZKD2LWKMFDHE
X-Message-ID-Hash: EIY6O774ZVXWOWLIGX5RZKD2LWKMFDHE
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.9rc4
Precedence: list
Subject: [DNSOP] Re: [Ext] Revised the application for the WALLET RRTYPE
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rLz7jfwwvGPzEmMNrr-af6_MhZs>
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 Jul 5, 2024, at 05:19, Petr Špaček <pspacek@isc.org> wrote:
> 
> I wonder if it needs some words how to handle wallet addresses longer than 255 characters?

To date, every known blockchain uses 256-bit signature keys. Most use truncated hashes of the public key, and all use either hexadecimal or some other ASCII encoding for the wallet address. I have not seen any suggestion that future blockchains would use post-quantum signatures. Thus, 255 characters is more than sufficient for all known and currently-expected wallet addresses.

> Maybe we safely leave this up to the application because the first field should identify the type anyway ... Just thinking aloud.

Exactly. And, if someone comes up with a wallet that needs more than 255 characters, they can define a WALLET2 RRTYPE for those addresses. I find this exceedingly unlikely to happen because space is extremely expensive on blockchains, and every transaction has two wallet addresses. And the interest in blockchains may have subsided before there is any chance of needing post-quantum signatures.

--Paul Hoffman

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