[nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up
Watson Ladd <watsonbladd@gmail.com> Tue, 20 May 2025 19:39 UTC
Return-Path: <watsonbladd@gmail.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 2340B2ADDF12; Tue, 20 May 2025 12:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2Q_HKmOkkAGg; Tue, 20 May 2025 12:39:34 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 mail2.ietf.org (Postfix) with ESMTPS id C516A2ADDEF9; Tue, 20 May 2025 12:39:34 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id 5b1f17b1804b1-442d146a1aaso57279285e9.1; Tue, 20 May 2025 12:39:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1747769974; x=1748374774; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=nEMbbVEK9Hhli0jRmeVCMVh3XO2rpmWJPm2BxlZee8I=; b=jYxxU7m964IDKXJSYKrHRtkOVlevniwMw3P3h7aGdrq0TciwJKIK/KBTLYj9GyqbBW ho0RrfWaiYEMSE57R7SDLnjBsTPkA6xdfMuC2Sy7PvUFxq45+Sht4FVWjoTMZdq9d8mo 6fkf1wgYb5CdbaxomvfsXCs6xDDs5RDaGVLN2AkOMzjkx3cVI63uYgqWfQA1R7UxDsxU NxAJUlDgt5iv+3rNhOU4BdfpR4uIDrKfCUVN43EnFDv0AW+X8Od2ABJPRoegCyjOq2bC afKxUUJxz9gwFpk8DqiGMonOfsRRhWGdoTyu8Z0ekBnnYJu43JrzbWdS+w33ZHYbW4+O KoTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747769974; x=1748374774; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=nEMbbVEK9Hhli0jRmeVCMVh3XO2rpmWJPm2BxlZee8I=; b=qHST8lpZQ5f2GWDlYgQXpFUK31yAyv6g3ohJxR3mM0EnhZvsmR8WJ8tcmM9FkO8Qoo trWNiX+LaMzHb8Ihey3iW/7rlLAo+y3hjLmRsOe6lZ9cIpSIHOeKiarnbS+hah2Ycoww i4unWBTZJB0tDj7AY3JYmwE8fYz7kogvH+8SiqgNd9RaP3Ov/noODfR4lfzkjeuP8hBT fZz+s2SZM1CKj5x/IAoY/9wnHZTweXfCVCzhb1fElON5sVO/pXGJx3VgZ3wBqV0TOygh YJJgBRfzW8+sUfYqNnSEhei6lE23EO12mMWDzfH5NFSa63o/5E4kIR3lOwKIEpDbGBUh WQpw==
X-Forwarded-Encrypted: i=1; AJvYcCWbOiu3PlX7rpjYPlKao6JWO/nEr/BXusbY7Pl/LK6mMQF/2LczkQeM5cqWWlbX/rR4B+W8@ietf.org, AJvYcCXhsD42zRGpsC4BWvAcomEeuYxQAY9HyiHiT1CIPSXZaINuWFRWlUu1P6UGbKvKpsmIyiqLfg==@ietf.org
X-Gm-Message-State: AOJu0Yy6X+VbsdKg40PoFRoRJ7Duh2OqhQCk6B0xzKIprKgrdjZS0Yhe Qq37KJBaZfh1U9WLfDsJ/33sYSQQmPDRGSZKVWyXc3kZNJN5r1Tq3ydKn1QVLdq6RqU/YJg9mDR GJ/iRTq2CdVGOFstwWyvXV8hauh+Tl1g=
X-Gm-Gg: ASbGnctDpJWC4IhAwt0T8GZDroNVwk3aFlmI0fOOBuvjWxYgvmjiHlpYIJ4MDNdR2Fj dUE+RIaFwZwwTjhLT5qrpLrU1vljLBP9YUOTyeqYA9On35/zg8xAOoZItoysGkOfvD1b/EcqFR4 B/qOi89R+L6jaYHmukjwzm9adM2wI4c+kklcDu09TeIJe2zXb6jNhE3VTgpWyWLh4=
X-Google-Smtp-Source: AGHT+IGVY7YMdtgG+7DfHC/q7sSLMWr5FXJ87J+lweSKqGgoSRlCtrvU5Gp50fef1tLu8E5wsK/Ux7reOUnSyjXiVBs=
X-Received: by 2002:a05:600c:8185:b0:442:dcdc:41c8 with SMTP id 5b1f17b1804b1-442feffc24emr151876715e9.19.1747769973592; Tue, 20 May 2025 12:39:33 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <2025052016324389942321@chinamobile.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Tue, 20 May 2025 15:39:21 -0400
X-Gm-Features: AX0GCFvzbqNcWGVE4lHhz11soiDVCDelmhCIVwY_X69PeJAkZzR_CSZqCitrvjc
Message-ID: <CACsn0cm7r77B-fOwhP4sfOMsvxBhy_75wAYERzG6Fp6co7ZeYA@mail.gmail.com>
To: Meiling Chen <chenmeiling@chinamobile.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: AZFWEWOFAT5KPOVIOHLPNXA22FPE3PHU
X-Message-ID-Hash: AZFWEWOFAT5KPOVIOHLPNXA22FPE3PHU
X-MailFrom: watsonbladd@gmail.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/rcmmnYYv0zNcdEH4t0fCR2xk8IY>
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>
On Tue, May 20, 2025 at 4:32 AM Meiling Chen <chenmeiling@chinamobile.com> wrote: > > Hi Watson, > I'm confused about "nontrivial semantic claims", can you give an example to explain? > > For example, if the operator's customer requires every node to support TEE, then only need to choose from nodes that have TEE functionality. It is not necessary to determine whether the router supports TEE from each configuration and operation directive, and to ensure the authenticity of the claims supporting TEE functionality, that's in the scope of RATS. 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. > > Best, > Meiling > > From: Watson Ladd > Date: 2025-04-19 02:22 > To: Henk Birkholz > CC: Liuchunchi(Peter); Eric Rescorla; Toerless Eckert; nasr@ietf.org; IETF SAAG; Luigi Iannone > Subject: [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up > Dear Henk, > > Your response was very detailed I think helped me at least, understand > the core issue of our disagreement. If I might take some liberties in > summarizing, it sounds like what you want is to provide additional > scaffolding from NASR to enable collection of evidence, and maybe some > standardized ways to represent the evidence, from a chain of routers > that it can be proved some packets transit. The evidence attests to > syntactic properties of the code and configuration at a point in time, > maybe with some kind of history mechanism to understand it. > > However, the properties being claimed are nontrivial semantic claims > dependent on the configuration and the software that uses this > configuration to route packets. There's a big gap here, and I don't > believe it has been solved. To the extent that NASR needs these to be > solved to provide certain things, it won't be able to provide them, > and I think that undermines a lot of the presented rationale. > > Sincerely, > Watson Ladd > -- Astra mortemque praestare gradatim
- [nasr] NASR BOF Follow-Up Liuchunchi(Peter)
- [nasr] Re: [saag] NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Richard Barnes
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Michael Richardson
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Luigi IANNONE
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Liuchunchi(Peter)
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up 刘鹏辉
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Watson Ladd
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Toerless Eckert
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Liuchunchi(Peter)
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Liuchunchi(Peter)
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Watson Ladd
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Watson Ladd
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Watson Ladd
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Michael Richardson
- [nasr] Summary of Discussions So far---Re: [saag]… Meiling Chen
- [nasr] Re: Summary of Discussions So far---Re: [s… Luigi IANNONE
- [nasr] Re: Summary of Discussions So far---Re: [s… Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Watson Ladd
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Luigi IANNONE
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Stephen Farrell
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Luigi IANNONE
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Luigi IANNONE
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Liuchunchi(Peter)
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Toerless Eckert
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Eric Rescorla
- [nasr] Re: [saag] Re: Re: NASR BOF Follow-Up Carsten Bormann
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Richard Barnes
- [nasr] Re: [saag] Re: NASR BOF Follow-Up Michael Richardson
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Henk Birkholz
- [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Liuchunchi(Peter)
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Eric Rescorla
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Adrian Farrel
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Luigi IANNONE
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Meiling Chen
- [nasr] Re: [saag] Re: Re: Re: Re: Re: NASR BOF Fo… Eric Rescorla