[nasr] Re: 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120
刘鹏辉 <liupenghui1982@163.com> Tue, 13 August 2024 05:20 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 89406C1E640A for <nasr@ietfa.amsl.com>; Mon, 12 Aug 2024 22:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level:
X-Spam-Status: No, score=-1.852 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_MESSAGE=0.001, RCVD_IN_MSPIKE_BL=0.001, RCVD_IN_MSPIKE_L4=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 pfc3WJ_40LrE for <nasr@ietfa.amsl.com>; Mon, 12 Aug 2024 22:20:39 -0700 (PDT)
Received: from m16.mail.163.com (m16.mail.163.com [117.135.210.2]) by ietfa.amsl.com (Postfix) with ESMTP id 094A9C1E0D8F for <nasr@ietf.org>; Mon, 12 Aug 2024 22:20:37 -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=2sm/m2yPnfznGQWE7kqFeLh6m7FIGWkmGur2RR130dk=; b=h JwOq4pyotyp3SwQkML11fiIWJzFmTN7dKYWlFZUbSCobvtjw4bssgWYEI2Q2zT8p on4Cp+0inQ9CuKKcP+c070WOHOQBkb6FdDcVbGCUgmOsZe1V5r5JlOjcy0xk405N ueD762al3E8ClMTMbn/sPmY9HostmNpxZ1heZJ3KZY=
Received: from liupenghui1982$163.com ( [218.17.115.213] ) by ajax-webmail-wmsvr-40-102 (Coremail) ; Tue, 13 Aug 2024 13:20:26 +0800 (CST)
X-Originating-IP: [218.17.115.213]
Date: Tue, 13 Aug 2024 13:20:26 +0800
From: 刘鹏辉 <liupenghui1982@163.com>
To: "Liuchunchi(Peter)" <liuchunchi@huawei.com>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.14 build 20240801(9da12a7b) Copyright (c) 2002-2024 www.mailtech.cn 163com
In-Reply-To: <ca7257d77709444a914c402f419ad0b0@huawei.com>
References: <202407231553159277592@chinamobile.com>, <514b701e.3dbe.190e2e04151.Coremail.liupenghui1982@163.com>, <202408011054476926448@chinamobile.com>, <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>
X-CM-CTRLMSGS: gqUIH3RyYWNlS2V5PXByZV9hZGJmNDE4YjMyMDU0MGFiMThlMDMwODUxYWJhM TliZg==
X-NTES-SC: AL_Qu2ZAfmZuUwp4CWdYOkfmkwXhuo8WcuzvfUl24RUNpt4jCzpxhAwX2doIFL6wcimKSyzqzO8Qj5W9s5BeZJ5TrsEmzzIYyEW4vMD28FtSvsoSQ==
Content-Type: multipart/alternative; boundary="----=_Part_73751_1121060530.1723526426566"
MIME-Version: 1.0
Message-ID: <630665a9.436d.1914a2e2fc7.Coremail.liupenghui1982@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wDXP48a7bpmREcUAA--.11840W
X-CM-SenderInfo: xolx1v5qjk3xarzyjqqrwthudrp/1tbiMwY6xmXAnJQS0gAGsi
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Message-ID-Hash: WRHG4Q6FRLUVUSVMGR3PO5REBPVG55CG
X-Message-ID-Hash: WRHG4Q6FRLUVUSVMGR3PO5REBPVG55CG
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: Meiling Chen <chenmeiling@chinamobile.com>, Michael Richardson <mcr@sandelman.ca>, "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/fOJ-0xJrf5NDaAVS6Hj8DU_2UjY>
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>
I mean beside the usecase for business secret protection, which already can be met by VPN, mybe we need some addtional cases for meeting this kind of law, legal compliance? Anyway, if there would be sufficient protective measures, GPDR allows for the transmission of data across borders. but we have no positive usecase for the “ no go abroad”,the related technology cannot evolve for long time.... At 2024-08-13 11:07:12, "Liuchunchi(Peter)" <liuchunchi@huawei.com> wrote: > What is the exact significance of this demand of NASR, just meet this kind of law?...... It is for leakage prevention purposes, for both business secret protection and legal compliance considerations. > the law may not be written in such detail, personally I think it should be the Terrestrial boundary... By the time of lawmaking I think no technology permitting such promise was available. By terrestrial boundary, I think meiling means it is not the ONLY factor when orchestrating a path—device integrity and free of tampering for example is another key factor should be considered when orchestration. PCL From:刘鹏辉 <liupenghui1982@163.com> Sent: Tuesday, August 13, 2024 10:30 AM To: Meiling Chen <chenmeiling@chinamobile.com> Cc: Michael Richardson <mcr@sandelman.ca>; nasr@ietf.org Subject: [nasr] Re: 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120 Large cloud vendors have different server regions in different countries and operate across borders, the law may not be written in such detail, personally I think it should be the Terrestrial boundary... What is the exact significance of this demand of NASR, just meet this kind of law?...... At 2024-08-09 18:00:06, "Meiling Chen" <chenmeiling@chinamobile.com> wrote: Indeed, after considering the example mentioned by Mic, Terrestrial boundary is not the only determining attribute, need more properties for real no go abroad, right? Best, Meiling From: Michael Richardson Date: 2024-08-05 03:13 To: =?UTF-8?B?5YiY6bmP6L6J?=; nasr@ietf.org Subject: [nasr] Re: 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120 I don't see anything in your summary of GDPR that says that encrypted PII can not cross another territory. At each end the GDPR clearly applies, but for example, I see nothing in your description that prevents data from Geneva to Bern (both in Switzerland) from travelling on fiber to the south of Lake Geneva/Leman. That is, through France. (is that a better route for fiber? Probably not. But a redundant microwave link from mountain to mountain would make a lot of sense) (Or: Zagreb to Bucharest, both EU countries, via Belgrade) Does GDPR really apply here? I'm sure such edicts exist, but if GDPR mandates this, it would be best to have a very specific clause referenced. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
- [nasr] Secure Routing Path Consideration- China M… Meiling Chen
- [nasr] Re: Secure Routing Path Consideration- Chi… Luigi Iannone
- [nasr] Re: Secure Routing Path Consideration- Chi… 刘鹏辉
- [nasr] 回复: Re: Secure Routing Path Consideration-… Meiling Chen
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Liuchunchi(Peter)
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Meiling Chen
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Liuchunchi(Peter)
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Liuchunchi(Peter)
- [nasr] 回复: Re: 回复: Re: Secure Routing Path Consid… Meiling Chen
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Toerless Eckert
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Toerless Eckert
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… junzhang
- [nasr] Re: Secure Routing Path Consideration- Chi… Luigi Iannone
- [nasr] Re: Secure Routing Path Consideration- Chi… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Toerless Eckert
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Toerless Eckert
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Toerless Eckert
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Liuchunchi(Peter)
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Jean-Michel Combes
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Yutaka OIWA
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Luigi IANNONE
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Jean-Michel Combes
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Luigi IANNONE
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Liuchunchi(Peter)
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Luigi IANNONE
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Henk Birkholz
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Michael Richardson
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Meiling Chen
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Liuchunchi(Peter)
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Meiling Chen
- [nasr] Re: Secure Routing Path Consideration- Chi… Luigi Iannone
- [nasr] Re: Secure Routing Path Consideration- Chi… Liuchunchi(Peter)
- [nasr] Re: Secure Routing Path Consideration- Chi… Meiling Chen
- [nasr] Re: Secure Routing Path Consideration- Chi… Luigi IANNONE
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Jean-Michel Combes
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… 刘鹏辉
- [nasr] Re: Secure Routing Path Consideration- Chi… Meiling Chen
- [nasr] Re: 回复: Re: Secure Routing Path Considerat… Jean-Michel Combes