[DNSOP] Re: [dtn] Re: Re: IPN and CLA RRTYPEs to support Bundle Protocol RFC9171

Rick Taylor <rick@tropicalstormsoftware.com> Wed, 26 June 2024 23:07 UTC

Return-Path: <rick@tropicalstormsoftware.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 C1F57C14F714; Wed, 26 Jun 2024 16:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 N1mXgZnPbCiv; Wed, 26 Jun 2024 16:07:19 -0700 (PDT)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4659BC14E513; Wed, 26 Jun 2024 16:07:17 -0700 (PDT)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi id 14.03.0513.000; Thu, 27 Jun 2024 00:07:14 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Mark Andrews <marka@isc.org>
Thread-Topic: [DNSOP] [dtn] Re: Re: IPN and CLA RRTYPEs to support Bundle Protocol RFC9171
Thread-Index: AQHayB0AA5eimck28kKG7pXoGXq1yrHaqn2g
Date: Wed, 26 Jun 2024 23:07:13 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F98027373934B@tss-server1.home.tropicalstormsoftware.com>
References: <fa28794e-d02b-aa93-56c8-082a3472c6e4@spacelypackets.com> <44BBD57B-752B-47FA-B5A5-D4F37BE60E9A@isc.org> <b3f42856-9460-2fa2-1088-185fda441f51@spacelypackets.com> <F2BD591F-8512-4E3E-ABA2-3DF3F34372CB@isc.org> <16835c41-0e6c-bde4-d197-847928171e55@spacelypackets.com> <047a01dac6b8$43d70ca0$cb8525e0$@gmail.com> <57ca71b8-aa29-8a07-5154-e6b9c44bc64a@spacelypackets.com> <AC5B89B2-DD53-4A36-9B87-4136EC288851@isc.org> <2dec1732-841e-dd38-85a8-3263b1c59885@spacelypackets.com> <C363E260-22EA-43E9-97B6-D7A403C205ED@isc.org> <98976a58-b976-e82c-4b12-76edce92e691@spacelypackets.com> <CAMGpriUVcoJu1CWWLapwREN2NaHJFnVkGUpF45TJotm7uyAxyg@mail.gmail.com> <3cfc8b7c-9128-46b5-c458-ac0ebb9c79bc@spacelypackets.com> <38A5475DE83986499AEACD2CFAFC3F980273735D06@tss-server1.home.tropicalstormsoftware.com> <b3ee82da-ae38-5781-77eb-bab292d5c113@spacelypackets.com> <cca98f92-27ee-d372-b419-81c63777033b@spacelypackets.com> <38A5475DE83986499AEACD2CFAFC3F980273739166@tss-server1.home.tropicalstormsoftware.com> <0910E1D8-C678-498C-BAB5-AC3AA4C75750@isc.org>
In-Reply-To: <0910E1D8-C678-498C-BAB5-AC3AA4C75750@isc.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.10.0.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: OOJ4AQZNG7BWASSPNPMB6LM2R3RHICZY
X-Message-ID-Hash: OOJ4AQZNG7BWASSPNPMB6LM2R3RHICZY
X-MailFrom: rick@tropicalstormsoftware.com
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: Scott Johnson <scott@spacelypackets.com>, Erik Kline <ek.ietf@gmail.com>, dnsop <dnsop@ietf.org>, "sburleig.sb@gmail.com" <sburleig.sb@gmail.com>, "dtn@ietf.org" <dtn@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: [dtn] Re: Re: IPN and CLA RRTYPEs to support Bundle Protocol RFC9171
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JG0DgL_Bhctvyr0t0G8Oq4HMvmk>
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>

Thanks for the clarification Mark,

Rick


> -----Original Message-----
> From: Mark Andrews [mailto:marka@isc.org]
> Sent: 27 June 2024 00:03
> To: Rick Taylor
> Cc: Scott Johnson; Erik Kline; dnsop; sburleig.sb@gmail.com; dtn@ietf.org
> Subject: Re: [DNSOP] [dtn] Re: Re: IPN and CLA RRTYPEs to support Bundle
> Protocol RFC9171
> 
> 
> 
> > On 27 Jun 2024, at 03:11, Rick Taylor <rick@tropicalstormsoftware.com>
> wrote:
> >
> > Hi Scott,
> >
> > Thanks for the updated doc.   I've been thinking through what I understand is
> your use-case, and I wonder whether new RRTYPEs is really the right way to go.
> As I see it, the less one has to update the DNS infrastructure of the Internet the
> better, so would this alternative mechanism work for you?:
> 
> Adding a new RRTYPE requires zero infrastructure upgrades.  It’s a database
> entry at IANA.  Every DNS server on the planet should handle these
> transparently.  That was required by RFC 1034 and RFC 1035.  You can even
> add them to zones before the parsing software is updated using unknown type
> representation (RFC 3597) which was one thing that was missing from RFC
> 1035 that would have made adding new types easier.  Nameservers and stub
> resolvers were always required to treat unknown records as opaque objects.
> 
> This doesn’t mean that there weren’t mis-implementations of the standards
> which failed to handle unknown types correctly but there have been 78 types
> added since RFC 1034 and RFC 1035.  That’s 2-3 per year.  Nameserver
> developers know how to add new record types quickly.
> 
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org