Re: [dtn] BPv7 compliance and handling of unknown EID schemes
RJ A <rja.lists@gmail.com> Wed, 06 March 2024 12:48 UTC
Return-Path: <rja.lists@gmail.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 CE95BC14F609 for <dtn@ietfa.amsl.com>; Wed, 6 Mar 2024 04:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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_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
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 XKxbjkAmeqzd for <dtn@ietfa.amsl.com>; Wed, 6 Mar 2024 04:48:46 -0800 (PST)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 7DDA4C14F604 for <dtn@ietf.org>; Wed, 6 Mar 2024 04:48:46 -0800 (PST)
Received: by mail-qt1-x82d.google.com with SMTP id d75a77b69052e-42e4f706847so47062221cf.2 for <dtn@ietf.org>; Wed, 06 Mar 2024 04:48:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709729325; x=1710334125; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=fOKOuIkkRYQDTNh8ZFfrh0wJMXM57Z+N48lm76gv4Jg=; b=UIe/EBGNnLF0L3aCbhtbliISODLlmFdHO/HR7GkynEvbvUYb4UIu4qgL9Jp31GVlSB NYgPb6m+9+kO/rZxWHVNbVKSWoCeJscYT1BOQPGTpSbKGB02++bkHBMxgqfb1CA8ufv2 kyolTD5moHYonKDzAvVoLck9pzC2lfbKi+3g1o1fjFsdtJfxiBQfpNFXnWQXrvHRxGHr +IpBQ63uy7Hz22UNZ8bl8bKqZA38MnkUGR8w0FW8FeNEXt5WCW3iSKsF1XzF0vSRpScb PlF8NyRKQPA+XPs2h1WiyAcEVprUH3qRctTtou6pu2TxskfMMAruK6hNnTMRsowcvmlK UJjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709729325; x=1710334125; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=fOKOuIkkRYQDTNh8ZFfrh0wJMXM57Z+N48lm76gv4Jg=; b=gEJsKhOTVtrwmp/FaDdT9fsVdFtGydOBTRagWYoQnDfHDpmkxCf3IpqxPgLNy/W8/K JXGJgduszKQRTrW4sA3qGm83gNlYYx/XpWIFktBXkskSEDShgTzA2Lkc4AjEW18gQ55X dKAJloxGZm6RwAofwi15GGnMEDhDZ9iZRTSaJvSfXIZJbaANrwX7P8rSoSx4MjQ5oppB OjAmlwkq9qA9QGpdbGZJnMokKt2uCpxoqQXIXHgtOkJSRwhs1hu87GZn8XSYYV3VRObg YAsB63h9XwOjCSPr41E0TEYBeslqr9ajABqtHmQKYzY+Gahsnw2fNPhJ86mmG5YaLLMu 2S9g==
X-Gm-Message-State: AOJu0Yxl82+2uM3A2Je8J+Loi9J+9vWGpY51BNLQdRYDbVmWsq7fEtq6 xAD9oPef9+aJmGeklgiFDRu0UlgqE58iG6nhgkm3ZxdMhPEBgJ20N6MeXC0k
X-Google-Smtp-Source: AGHT+IEL8hP9SwMBjT/ahfCu3qZGk3Gz9sAtky7sIfeCfruFaWa29HrqcQP+Pj3oYxUpMfKWHse+ug==
X-Received: by 2002:a05:622a:1007:b0:42e:58c6:bc9e with SMTP id d7-20020a05622a100700b0042e58c6bc9emr5405748qte.60.1709729324935; Wed, 06 Mar 2024 04:48:44 -0800 (PST)
Received: from smtpclient.apple (pool-108-28-83-193.washdc.fios.verizon.net. [108.28.83.193]) by smtp.gmail.com with ESMTPSA id c4-20020ac86604000000b0042c7d11e280sm4544684qtp.90.2024.03.06.04.48.44 for <dtn@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Mar 2024 04:48:44 -0800 (PST)
From: RJ A <rja.lists@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Wed, 06 Mar 2024 07:48:33 -0500
References: <ed574adc2549475eb12b9846a3cfe658@jhuapl.edu> <CAMGpriWgrdTGfq4DrWNsa0PRFc8nn=tU0iOm0Qr-TXmoTZfGFg@mail.gmail.com>
To: dtn@ietf.org
In-Reply-To: <CAMGpriWgrdTGfq4DrWNsa0PRFc8nn=tU0iOm0Qr-TXmoTZfGFg@mail.gmail.com>
Message-Id: <96729309-41A9-4682-A7D3-BBAC647F3ABA@gmail.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/DK0wvI4Pu7qBx4_OCN_q4a10ujw>
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 12:48:46 -0000
> 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. I’d suggest splitting the idea above into 2 documents, primarily so that in future they could be separately incremented/revised/advanced as appropriate. A) Implementation Guidance, likely status Informational, likely RFC category IETF B) BPv7 Test Vectors, likely status Standards-Track, likely RFC category IETF Also, I’d suggest that the “Test Vectors” document contain at least 2 different sections. One section would contain known invalid inputs. The other would contain known valid inputs. That would increase the test coverage a bit and likely would help interoperability. Cheers, Ran