Re: [dtn] BPv7 compliance and handling of unknown EID schemes

Rick Taylor <rick@tropicalstormsoftware.com> Wed, 06 March 2024 17:09 UTC

Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C64C2C14F5E6 for <dtn@ietfa.amsl.com>; Wed, 6 Mar 2024 09:09:54 -0800 (PST)
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 JGDUoDUDuTat for <dtn@ietfa.amsl.com>; Wed, 6 Mar 2024 09:09:50 -0800 (PST)
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 E8D28C14F5FD for <dtn@ietf.org>; Wed, 6 Mar 2024 09:09:49 -0800 (PST)
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; Wed, 6 Mar 2024 17:09:46 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: RJ A <rja.lists@gmail.com>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: [dtn] BPv7 compliance and handling of unknown EID schemes
Thread-Index: AdpvSQ/hqyrZCOcHQFq9lRz5WvvTrQAK1paAABQLqYAACMC1oA==
Date: Wed, 06 Mar 2024 17:09:45 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9802736DEB9E@tss-server1.home.tropicalstormsoftware.com>
References: <ed574adc2549475eb12b9846a3cfe658@jhuapl.edu> <CAMGpriWgrdTGfq4DrWNsa0PRFc8nn=tU0iOm0Qr-TXmoTZfGFg@mail.gmail.com> <96729309-41A9-4682-A7D3-BBAC647F3ABA@gmail.com>
In-Reply-To: <96729309-41A9-4682-A7D3-BBAC647F3ABA@gmail.com>
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/q2xV2LERI6UlfGe2jYHvu4NcU-A>
Subject: Re: [dtn] BPv7 compliance and handling of unknown EID schemes
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2024 17:09:54 -0000

> -----Original Message-----
> From: dtn [mailto:dtn-bounces@ietf.org] On Behalf Of RJ A
> Sent: 06 March 2024 12:49
> To: dtn@ietf.org
> Subject: Re: [dtn] BPv7 compliance and handling of unknown EID schemes
> 
> 
> 
> > On Mar 5, 2024, at 22:14, Erik Kline <ek.ietf@gmail.com> wrote:
> >
> > There are a couple of crypto RFCs that are mostly (entirely?) test
> > vectors.  This obviously makes sense for that specific context, but an
> > "implementation guidance" doc for BPv7 with test vectors accompanying
> > advice would seem like a Good Thing (tm) imho.
> 
> Agree.

+1

> 
> I’d suggest splitting the idea above into 2 documents, primarily so that in
> future they could be separately incremented/revised/advanced as
> appropriate.

I think the split is a good idea.  I can see there being a number of sections in Implementation Guidance beyond "good" vs "bad" test vectors.  E.g.  Which next hop is selected to forward a status report if the ReportTo EID is not in the routing table?   The time taken to write the guidance will probably exceed a first set of test vectors.

> 
> A) Implementation Guidance, likely status Informational, likely RFC category
> IETF
> B) BPv7 Test Vectors, likely status Standards-Track, likely RFC category IETF

I would love some binary test bundles, as I'm currently interop testing against other available implementations and picking the lowest common denominator of functionality.  Jon Postel would be proud, but it's not ideal.

Cheers,

Rick