IETF Logo Mail Archive

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

刘鹏辉 <liupenghui1982@163.com> Wed, 24 July 2024 03:54 UTC

Return-Path: <liupenghui1982@163.com>
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 D3A95C14F71D for <nasr@ietfa.amsl.com>; Tue, 23 Jul 2024 20:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.448
X-Spam-Level:
X-Spam-Status: No, score=-5.448 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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_BLOCKED=0.001, 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 (1024-bit key) header.d=163.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 qTtz2jZsI0b1 for <nasr@ietfa.amsl.com>; Tue, 23 Jul 2024 20:54:38 -0700 (PDT)
Received: from m15.mail.163.com (m15.mail.163.com [45.254.50.220]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED50C14CE3B for <nasr@ietf.org>; Tue, 23 Jul 2024 20:54:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:Content-Type:MIME-Version: Message-ID; bh=J1g3YPWvOcW+DlpMt3dQLJEzqqeeKtYm84ON4APL/MY=; b=d MivYBIMmv+dtc902+py1KToJizWmfsVcsK4cypCL1NIUydiIulJBT5Pmb0KkeLdM dldUKdqeSl3agACdBF7cDEPsorRD0gkb3h7+pvlhzl9E2T9sNrKCti8AXnp3skvO iIBgeBf3/awzsRpp3Hl81IZ9mwp/oXeGVQ5o8DerFY=
Received: from liupenghui1982$163.com ( [218.17.115.213] ) by ajax-webmail-wmsvr-40-127 (Coremail) ; Wed, 24 Jul 2024 11:54:26 +0800 (CST)
X-Originating-IP: [218.17.115.213]
Date: Wed, 24 Jul 2024 11:54:26 +0800
From: 刘鹏辉 <liupenghui1982@163.com>
To: Meiling Chen <chenmeiling@chinamobile.com>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.14 build 20230109(dcb5de15) Copyright (c) 2002-2024 www.mailtech.cn 163com
In-Reply-To: <202407231553159277592@chinamobile.com>
References: <202407231553159277592@chinamobile.com>
X-CM-CTRLMSGS: OEVwhXRyYWNlS2V5PXByZV83ZTU5ZTJlYzc1Yjc0ZjJlMmNhNGM4ZTc2MzE2Y TVlMg==
X-NTES-SC: AL_Qu2ZA/uSvEot4ymRY+kfmk0Tge87WcO5uvoj1YZUPJ5+jA/p+hE7WkJqBHzu1M+ABgCctzG+fz5KyPpWTZhBUI0EtDAypQLG3xf6hGfIJVB++A==
Content-Type: multipart/related; boundary="----=_Part_57757_1153958447.1721793266001"
MIME-Version: 1.0
Message-ID: <514b701e.3dbe.190e2e04151.Coremail.liupenghui1982@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wDnj5vyeqBmRdZYAA--.9458W
X-CM-SenderInfo: xolx1v5qjk3xarzyjqqrwthudrp/1tbiqQgmxmVOBtvXYQABsA
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Message-ID-Hash: 63OKDQXDF3VJF3YKBWLP55WMZRNTUZR6
X-Message-ID-Hash: 63OKDQXDF3VJF3YKBWLP55WMZRNTUZR6
X-MailFrom: liupenghui1982@163.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: Luigi IANNONE <luigi.iannone=40huawei.com@dmarc.ietf.org>, "nasr@ietf.org" <nasr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [nasr] 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/zZTH2VXBC_3E81xjhIzVZaHygNY>
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 Meiling,




Your case is very reasonable, clarifies what data rquired to be forwarded through the network characterized by the specific path selection requirement of NASR.


If we could provide one or more citations to prove the existence of this requirement "Data not going abroad", then this use case would be more convincing. 




There was once a news that the US government hoped to build a clean network plan where data would only pass through designated networks" clean path", see https://2017-2021.state.gov/the-clean-network/ .  Is this unamiable example used to prove this use case? NASR could sove this problem?  just my two cents, hope this helps....



















At 2024-07-23 15:53:16, "Meiling Chen" <chenmeiling@chinamobile.com> wrote:

Hi Luigi,


Secure Routing Path Consideration, Please find my slides attached.




Best,
Meiling

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