IETF Logo Mail Archive

[nasr] Re: 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 04 October 2024 15:04 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 5D582C1D8769 for <nasr@ietfa.amsl.com>; Fri, 4 Oct 2024 08:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 rW6qFFga0Yi7 for <nasr@ietfa.amsl.com>; Fri, 4 Oct 2024 08:04:08 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24FE0C1D6FB8 for <nasr@ietf.org>; Fri, 4 Oct 2024 08:04:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D572B1800D; Fri, 4 Oct 2024 11:04:06 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id swZCZCy1fXvb; Fri, 4 Oct 2024 11:04:06 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1728054246; bh=5TJM1sHsboTpq0BERgjUZQQhPv1tg6t0ZdPFEFHbXPg=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=bMzAZTGHRn/ZlNybjCRB0kXU7NaPUeRWce5kwpfbItzZ0TiRhQnyJHC5lDDdOPGZH Z6ZNe/Y9AVP7bd+tttb1+CBLRnFUcY3ZU6JlsfDkIIt381RCplk6sLd4Y1Y4IfnVf8 XK9T1MWzn2fDd/6dOVP/0omD4tMO4WFP8hfU7j7qPLKaPEL1A6l62PiHvh+/eWr5QO p8520xzSeo/4wA4PPxDthmbYLG+NDwm7XY4HQtf/KUXdm8B/fegzv8Ak0F4VJ6cS7E IWPdUop6FtmfXsC9Ebgnif1/Jx2xB1KO4XAQCYXE+mId2c158R48LrmSzbyYRFZhpb XVygcNLaUWP4w==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0AC891800C; Fri, 4 Oct 2024 11:04:06 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 009A211E; Fri, 4 Oct 2024 11:04:05 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: junzhang <junzhang1@huawei.com>
In-Reply-To: <bcb2832ba5f24192be84c5c596ae41dd@huawei.com>
References: <fe9299737de2469da894ed6e55a53bf1@huawei.com> <5aaf2f9d.1c92.19110d4dea0.Coremail.liupenghui1982@163.com> <17219.1722798809@obiwan.sandelman.ca> <202408091800065008405@chinamobile.com> <744c46d5.25b2.19149927bcb.Coremail.liupenghui1982@163.com> <ca7257d77709444a914c402f419ad0b0@huawei.com> <630665a9.436d.1914a2e2fc7.Coremail.liupenghui1982@163.com> <c15aa26cea984239baf9d2d96b6ed5a7@huawei.com> <ZvyK4n-BI9S-SF94@faui48e.informatik.uni-erlangen.de> <24175.1727974451@obiwan.sandelman.ca> <Zv7t5QNKYiBXkLYf@faui48e.informatik.uni-erlangen.de> <5925.1727990783@obiwan.sandelman.ca> <bcb2832ba5f24192be84c5c596ae41dd@huawei.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 04 Oct 2024 11:04:05 -0400
Message-ID: <28215.1728054245@obiwan.sandelman.ca>
Message-ID-Hash: 7ZZ7TK5GAQISCNZQRV64I3YEZOVVA7A3
X-Message-ID-Hash: 7ZZ7TK5GAQISCNZQRV64I3YEZOVVA7A3
X-MailFrom: mcr+ietf@sandelman.ca
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: Toerless Eckert <tte@cs.fau.de>, "Liuchunchi(Peter)" <liuchunchi@huawei.com>, =?utf-8?B?5YiY6bmP6L6J?= <liupenghui1982@163.com>, Meiling Chen <chenmeiling@chinamobile.com>, "nasr@ietf.org" <nasr@ietf.org>
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [nasr] Re: 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120
List-Id: Network Attestation for Secure Routing <nasr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nasr/QHApKYPRXMdkhamjz1n41JGYLzs>
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>

junzhang <junzhang1@huawei.com> wrote:
    > (1) encrypt the data such that it is computationally prohibitive to
    > decrypt the data without the decryption key,

Assuming you can trust this, and assuming that there are no backups, then
maybe you can make a claim within some constraints.  That's what remote attestation is above.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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