[nasr] Scope: Forwarding AND Routing or JUST Forwarding?

Luigi Iannone <ggx@gigix.net> Tue, 08 October 2024 11:36 UTC

Return-Path: <ggx@gigix.net>
X-Original-To: nasr@ietfa.amsl.com
Delivered-To: nasr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 644BEC180B64 for <nasr@ietfa.amsl.com>; Tue, 8 Oct 2024 04:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=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=gigix-net.20230601.gappssmtp.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 EPR5blRbvRU6 for <nasr@ietfa.amsl.com>; Tue, 8 Oct 2024 04:36:51 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4DB2C180B67 for <nasr@ietf.org>; Tue, 8 Oct 2024 04:36:51 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-42cb60aff1eso56882345e9.0 for <nasr@ietf.org>; Tue, 08 Oct 2024 04:36:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20230601.gappssmtp.com; s=20230601; t=1728387409; x=1728992209; darn=ietf.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=DQBntGWcrbrbYwNcflmf8Icdu22qhpdEUj5uYoPHRVY=; b=aa2WB0ywFA7salBmgY2AEi7zj8UjkaPJoCHwl5sFLsxTQeV4GplEH8BOmf+MbfMMiS 7UqRHTE81hqEe1cQTw0oc45lCEhH/HogHa5WMdDBDwaAUFARTsGD21bHjSKRmRmMlA93 Ck3lua9r7unemUorClVuaYJ+EJjBzL1pkebtvIL7/PikdZiPGJI5SEsre8GPnLtgb9c2 Y2wnyFbpJXGbFWsUzcJ7hqXRj1MsdSIxkk8vyDc5iST70XH1XfukjV7eUoFozFDV48Lt Ics2X8hcXH8oYVUAeGJac+wJaJ3SfR314aEhK1tY1M8hroAdgNoOzVpLdL0jmlDaUqgW Bxjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728387409; x=1728992209; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=DQBntGWcrbrbYwNcflmf8Icdu22qhpdEUj5uYoPHRVY=; b=Cz9519cFZqu1jaA380vCSGtflNroXwuxCYlcR0jR8gWIOp+Pk7tpeaiHvdqZQJ6Vk9 0JGzsJYbPN5gFTTmrjqBMkrVM2EAb0XHnM8gXrKjCP2LTBtU99jt+VQeeYQL3A/tHa3f tRKbE3+S5lTGDZwA2uzzVy1EZitUD6QBK8DRlutayZdhKeeG1gVWevHgpBGJLiVzz6qE czKVgRQMlTYz+PE2LpZucGpWnsHLBsTmu+jFXJOe8G0oBfdns3IBkcPvzxPpSQeHDwMc eLax/FhYqzt0NgPPqkLmoRQ+KDA1ougLuQJ300zmN2hhy6wHikbQWx0EWDjc4OQRo1yE TZlQ==
X-Gm-Message-State: AOJu0YyZRJ6nBsZTmxVDSSwjt+yQU99U3V3ojJ1Ioy2V1KE+RhQ/RG8L VdmPvYmz03D8nuO/wxMgVdn8fKabmzbhyL5/wjrDcONc1ai1BqGHOYwV60ToOtIVTfi/dHlxBY6 PwIOP/g==
X-Google-Smtp-Source: AGHT+IEHNI2tEe89KQrOpIKSxL0UlaDxnYsDqlHr5/Di99SPetABrDgxX3na2dYuogevKmNy8rCiuw==
X-Received: by 2002:a05:600c:4691:b0:42c:b309:8d1a with SMTP id 5b1f17b1804b1-42f85aa8172mr112647085e9.13.1728387409094; Tue, 08 Oct 2024 04:36:49 -0700 (PDT)
Received: from smtpclient.apple (91-167-176-17.subs.proxad.net. [91.167.176.17]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-42f89ec61f7sm108426095e9.32.2024.10.08.04.36.48 for <nasr@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Oct 2024 04:36:48 -0700 (PDT)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
Message-Id: <3FDB94A5-A84E-44D7-8AEB-28343025169B@gigix.net>
Date: Tue, 08 Oct 2024 13:36:17 +0200
To: nasr <nasr@ietf.org>
X-Mailer: Apple Mail (2.3818.100.11.1.3)
Message-ID-Hash: 4OO6ZUHC6WB3BUOQ22AC43QZA6ULL4R5
X-Message-ID-Hash: 4OO6ZUHC6WB3BUOQ22AC43QZA6ULL4R5
X-MailFrom: ggx@gigix.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [nasr] Scope: Forwarding AND Routing or JUST Forwarding?
List-Id: Network Attestation for Secure Routing <nasr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nasr/PYXBts2kMtp4sbTN0IK6n3C-p18>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nasr>
List-Help: <mailto:nasr-request@ietf.org?subject=help>
List-Owner: <mailto:nasr-owner@ietf.org>
List-Post: <mailto:nasr@ietf.org>
List-Subscribe: <mailto:nasr-join@ietf.org>
List-Unsubscribe: <mailto:nasr-leave@ietf.org>

Hello NASRers,

One of the topic that we can tackle on the mailing list and finalize during the interim is about the scope of NASR in particular about “Routing vs Forwarding”.

During the BoF, several persons pointed out that we are not clear on whether NASR is about:

1) Fowarding: being able to audit a path and obtain a proof of transit. Building the path being out of scope.

2)  Routing: This is forawarding + Building the path by distributing trust and  reachability information.

In my personal opinion I see NASR more on the forwarding side, hence focusing on the auditing tools. 

Extending routing solution to distribute relevant information for NASR to work can be done in the future and not necessarily in the NASR WG but as an extension of other protocols, hence in their respective WGs.

Anyone to share more thoughts on this point?   

L.