IETF Logo Mail Archive

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

Rick Taylor <rick@tropicalstormsoftware.com> Thu, 27 June 2024 11:59 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 E04D8C14F70D; Thu, 27 Jun 2024 04:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7txMEHSNc29U; Thu, 27 Jun 2024 04:59:38 -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 A7C60C14F5E4; Thu, 27 Jun 2024 04:59:37 -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 12:59:35 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: Joe Abley <jabley@strandkip.nl>
Thread-Topic: [DNSOP] [dtn] Re: Re: Re: Re: IPN and CLA RRTYPEs to support Bundle Protocol RFC9171
Thread-Index: AQHayINmlYF8wpVOjUCCc9rdBEBbPrHbgYzg
Date: Thu, 27 Jun 2024 11:59:32 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9802737396BA@tss-server1.home.tropicalstormsoftware.com>
References: <fa28794e-d02b-aa93-56c8-082a3472c6e4@spacelypackets.com> <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> <e364da36-00e3-7c14-30b0-34f20b244f0a@redbarn.org> <6ff67491-30cf-cdc0-5e19-c1122465386c@spacelypackets.com> <38A5475DE83986499AEACD2CFAFC3F9802737395E2@tss-server1.home.tropicalstormsoftware.com> <6AEBB4F7-9724-4828-8C16-F8B9AB562DEF@strandkip.nl>
In-Reply-To: <6AEBB4F7-9724-4828-8C16-F8B9AB562DEF@strandkip.nl>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Message-ID-Hash: 64C4LXE32RHSPZRUWEWGZI7V2OL2WZSP
X-Message-ID-Hash: 64C4LXE32RHSPZRUWEWGZI7V2OL2WZSP
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: 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/74NMNrh6oukt41X6wpAYO1oU0iQ>
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>

Hi Joe,

That definitely allows option 2.  The question is does option 2 work for the DNSOPS Designated Experts and Scott.

Cheers,
Rick

> -----Original Message-----
> From: Joe Abley [mailto:jabley@strandkip.nl]
> Sent: 27 June 2024 12:16
> To: Rick Taylor
> Cc: Scott Johnson; Erik Kline; dnsop; sburleig.sb@gmail.com; dtn@ietf.org
> Subject: Re: [DNSOP] [dtn] Re: Re: Re: Re: IPN and CLA RRTYPEs to support
> Bundle Protocol RFC9171
> 
> Hi Rick,
> 
> On Jun 27, 2024, at 10:46, Rick Taylor <rick@tropicalstormsoftware.com>
> wrote:
> 
> > <chair hat on>
> >
> > I absolutely sympathise with your need to "grab an RRTYPE and make
> progress", but there is a process choice to be made here:
> >
> > * Do DNSOPS want the RRTYPE registrations to integrate with the wider work
> of the DTN working group?  In which case discussion like this must continue,
> and the document should be adopted by the WG.
> > * Or is everyone happy to register the RRTYPEs as "ScottJ and colleagues
> need some unique RRTYPEs for the solution they're working on - no alignment
> with the wider work of the DTN WG implied"?  I would propose calling the
> RRTYPE NODEID not IPN to make this clear, and not have the reference
> specification be an IETF document.
> 
> Speaking only as a recent reader of BCP 42 / RFC 6895, section 3.1 contains the
> guidance you are looking for. Consensus from the dnsop working group is not
> required, although as you have seen opinions are freely available.
> Specifications in the form of IETF documents are also not required to reserve a
> codepoint.
> 
> 
> Joe

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