IETF Logo Mail Archive

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

"Liuchunchi(Peter)" <liuchunchi@huawei.com> Thu, 01 August 2024 09:25 UTC

Return-Path: <liuchunchi@huawei.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 674CAC15107C for <nasr@ietfa.amsl.com>; Thu, 1 Aug 2024 02:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_02=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
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 ce1TzO980si2 for <nasr@ietfa.amsl.com>; Thu, 1 Aug 2024 02:25:20 -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 ietfa.amsl.com (Postfix) with ESMTPS id BCBCAC151087 for <nasr@ietf.org>; Thu, 1 Aug 2024 02:25:19 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4WZNm10wswz6K9kH for <nasr@ietf.org>; Thu, 1 Aug 2024 17:22:41 +0800 (CST)
Received: from lhrpeml500004.china.huawei.com (unknown [7.191.163.9]) by mail.maildlp.com (Postfix) with ESMTPS id D8A88140257 for <nasr@ietf.org>; Thu, 1 Aug 2024 17:25:16 +0800 (CST)
Received: from dggpeml100017.china.huawei.com (7.185.36.161) by lhrpeml500004.china.huawei.com (7.191.163.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 1 Aug 2024 10:25:15 +0100
Received: from dggpeml100018.china.huawei.com (7.185.36.133) by dggpeml100017.china.huawei.com (7.185.36.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 1 Aug 2024 17:25:13 +0800
Received: from dggpeml100018.china.huawei.com ([7.185.36.133]) by dggpeml100018.china.huawei.com ([7.185.36.133]) with mapi id 15.01.2507.039; Thu, 1 Aug 2024 17:25:13 +0800
From: "Liuchunchi(Peter)" <liuchunchi@huawei.com>
To: Meiling Chen <chenmeiling@chinamobile.com>, 刘鹏辉 <liupenghui1982@163.com>
Thread-Topic: [nasr] 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120
Thread-Index: AQHa474/9p2xR8m+sEe4fN5xtEGfArISIX6g
Date: Thu, 01 Aug 2024 09:25:13 +0000
Message-ID: <fe9299737de2469da894ed6e55a53bf1@huawei.com>
References: <202407231553159277592@chinamobile.com>, <514b701e.3dbe.190e2e04151.Coremail.liupenghui1982@163.com> <202408011054476926448@chinamobile.com>
In-Reply-To: <202408011054476926448@chinamobile.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.114.71]
Content-Type: multipart/related; boundary="_004_fe9299737de2469da894ed6e55a53bf1huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
Message-ID-Hash: U7GS24P4XJO2Y6JJS2ZLR43KOEXEYZPN
X-Message-ID-Hash: U7GS24P4XJO2Y6JJS2ZLR43KOEXEYZPN
X-MailFrom: liuchunchi@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: 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: 回复: 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/FBG--s9ONu8qs19yjic2FHI6WR8>
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>

"Data no going abroad"

Especially when not authorized by data owners :)

From: Meiling Chen <chenmeiling@chinamobile.com>
Sent: Thursday, August 1, 2024 10:55 AM
To: 刘鹏辉 <liupenghui1982@163.com>
Cc: Luigi IANNONE <luigi.iannone=40huawei.com@dmarc.ietf.org>; nasr@ietf.org
Subject: [nasr] 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120

Hi penghui,

"Data no going abroad" such regulations are quite common, like GDPR, CCPA and CPRA, TTDSG and so on.

Best,
Meiling

发件人： 刘鹏辉<mailto:liupenghui1982@163.com>
发送时间： 2024-07-24 11:54
收件人： Meiling Chen<mailto:chenmeiling@chinamobile.com>
抄送： Luigi IANNONE<mailto:luigi.iannone=40huawei.com@dmarc.ietf.org>; nasr@ietf.org<mailto:nasr@ietf.org>
主题： [nasr] Re: Secure Routing Path Consideration- China Mobile-ietf120

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....



[cid:image001.png@01DAE437.C382E2C0]











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

Secure Routing Path Consideration, Please find my slides attached.


Best,
Meiling


[https://count.mail.163.com/beacon/webmail.gif?type=webmail_mailtrace&guid=pre_7e59e2ec75b74f2e2ca4c8e76316a5e2]

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