IETF Logo Mail Archive

[nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up

Luigi IANNONE <luigi.iannone@huawei.com> Thu, 22 May 2025 07:52 UTC

Return-Path: <luigi.iannone@huawei.com>
X-Original-To: nasr@mail2.ietf.org
Delivered-To: nasr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 61D5E2BAEE2C; Thu, 22 May 2025 00:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9U1TBOTdBpv; Thu, 22 May 2025 00:52:18 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A0AEC2BAEE26; Thu, 22 May 2025 00:52:18 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4b30kN51jrz6GFbS; Thu, 22 May 2025 15:47:24 +0800 (CST)
Received: from frapeml100003.china.huawei.com (unknown [7.182.85.60]) by mail.maildlp.com (Postfix) with ESMTPS id 4FCDF140119; Thu, 22 May 2025 15:52:17 +0800 (CST)
Received: from frapeml500003.china.huawei.com (7.182.85.28) by frapeml100003.china.huawei.com (7.182.85.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 22 May 2025 09:52:17 +0200
Received: from frapeml500003.china.huawei.com ([7.182.85.28]) by frapeml500003.china.huawei.com ([7.182.85.28]) with mapi id 15.01.2507.039; Thu, 22 May 2025 09:52:17 +0200
From: Luigi IANNONE <luigi.iannone@huawei.com>
To: Watson Ladd <watsonbladd@gmail.com>, Meiling Chen <chenmeiling@chinamobile.com>
Thread-Topic: [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up
Thread-Index: AQHbrip5dkZZlM2czkChaYM0lOBosLOl44aAgADEWwCAAR7qAIAB2RMAgDHHesaAAJiPgIACfuIg
Date: Thu, 22 May 2025 07:52:17 +0000
Message-ID: <4cfab84c8bc74efdbb642650638931d7@huawei.com>
References: <87c61c52-839f-f66e-a66a-b737f01ca93f@ietf.contact> <CABcZeBMOvFXkQ2OFBpz2Ri5_Oz-pHGs=2fHvBNptOdjQy9F7ww@mail.gmail.com> <11730e71-f409-bbaf-9bc1-4f88d207bcab@ietf.contact> <CABcZeBMDg9cFGtf6AMwSiq3ZnZnrvwoAc7TjD0Ftq-JC8jWusQ@mail.gmail.com> <d3de69d6-f46b-fe0c-b6dc-8180864bd9b0@ietf.contact> <CABcZeBO15H=+ds0deqvtOzKvX+JvFzCn2pht3fcKYcp7df=UFw@mail.gmail.com> <52b08a1b-45e2-b03b-a0a8-12e55b56bfa8@ietf.contact> <CABcZeBOwZ3=pz=Xz1D3YwJ6_svTidt5azWDFnTwexsE508rmkA@mail.gmail.com> <ee313d5a-967b-c434-804c-097e4777ca20@ietf.contact> <CABcZeBP7-A52XPghkCWa7f15Xa1UvoHKujhNPzvoH+cP+McSWQ@mail.gmail.com> <Z_mZqmJs8Su1Tt2Y@faui48e.informatik.uni-erlangen.de> <CABcZeBMK5kBN2YG4Xev5CTVyk00BXAUWa4P_Ov9Q7K+-b1B5Pw@mail.gmail.com> <52075b58d6f64ef98871f1296a6e347f@huawei.com> <CACsn0c=sfhN+zJ7r7vpCe4gOXbLU8HAA0hwvgxoB3cGmMTH4WQ@mail.gmail.com> <c73fe830-413e-04b8-92f7-28c994034c81@ietf.contact> <CACsn0c=+2b5-x9FnjZHDFWxs31HUyPyd42==DeyKqXuP2SVssg@mail.gmail.com> <59336c94-08ea-2961-6390-50bf70f7befd@ietf.contact> <CACsn0cmGaWNRP6Nrj1F1O8vYeuM2EB9d9Ah6N_Lz-m6cp0y7HQ@mail.gmail.com> <2025052016324389942321@chinamobile.com> <CACsn0cm7r77B-fOwhP4sfOMsvxBhy_75wAYERzG6Fp6co7ZeYA@mail.gmail.com>
In-Reply-To: <CACsn0cm7r77B-fOwhP4sfOMsvxBhy_75wAYERzG6Fp6co7ZeYA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.206.215.61]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: T54JM4TIBPTPEEZRV67T2HJXK6FBEILJ
X-Message-ID-Hash: T54JM4TIBPTPEEZRV67T2HJXK6FBEILJ
X-MailFrom: luigi.iannone@huawei.com
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
CC: Henk Birkholz <henk.birkholz@ietf.contact>, Liuchunchi <liuchunchi=40huawei.com@dmarc.ietf.org>, ekr <ekr@rtfm.com>, Toerless Eckert <tte@cs.fau.de>, "nasr@ietf.org" <nasr@ietf.org>, IETF SAAG <saag@ietf.org>, Luigi Iannone <ggx@gigix.net>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up
List-Id: Network Attestation for Secure Routing <nasr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nasr/peW9rBekHy4OG8OU4RM1GlzQJeU>
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>

Hi Watson,

> 
> Correct. Some claims are easy to verify. Most aren't. Statements that "the
> router supports X" aren't really interesting. Statements that "this
> configuration will never pass your traffic over a bad link" are, but are a lot
> harder to show.
> 
> >

[LI] Agreed. This is a very claim hard show/attest. 
Note however that this is not what NASR is trying to do. 
NASR is more about router has feature X, Y, and Z which is what I want, and that traffic goes through the selected routers that support X, Y and Z.
NASR is not about proving that traffic does not go somewhere else (proof of non-transit is out of scope). 

Ciao

L.

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