IETF Logo Mail Archive

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

刘鹏辉 <liupenghui1982@163.com> Tue, 13 August 2024 02:30 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 6E297C1E0D78 for <nasr@ietfa.amsl.com>; Mon, 12 Aug 2024 19:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.842
X-Spam-Level:
X-Spam-Status: No, score=-1.842 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_L3=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 SnbXq5k1TARc for <nasr@ietfa.amsl.com>; Mon, 12 Aug 2024 19:30:35 -0700 (PDT)
Received: from m16.mail.163.com (m16.mail.163.com [117.135.210.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8D193C1DFD29 for <nasr@ietf.org>; Mon, 12 Aug 2024 19:30:32 -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=/gSyGmvCheIC63rFAvI4+wf2ojP9giiOekxlTx+xzbY=; b=q MBkEnMy9ytLDEsNl0HXZwDR4yISHUS/gZYUglyS95FHb5Fdqi2it5e2kJzD4h4R5 1vHdNE/RjU6B+i4px/eLxY9myxBW6+CKX0HF7IdQ/eQxuxsjoPs1Dg2fBKJcib+l 8d9LFBN6n7sIHVs+MP7K0OLy1OIhOY+Z1wwnMWzs0I=
Received: from liupenghui1982$163.com ( [218.17.115.213] ) by ajax-webmail-wmsvr-40-138 (Coremail) ; Tue, 13 Aug 2024 10:30:22 +0800 (CST)
X-Originating-IP: [218.17.115.213]
Date: Tue, 13 Aug 2024 10:30:22 +0800
From: 刘鹏辉 <liupenghui1982@163.com>
To: Meiling Chen <chenmeiling@chinamobile.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: <202408091800065008405@chinamobile.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>
X-CM-CTRLMSGS: fGJm7XRyYWNlS2V5PXByZV9jYWM2YWExMzlkODhmZDQ2MjBhZThmYzZmYWNhY WU5Yg==
X-NTES-SC: AL_Qu2ZAfmauUop5CSYZukfmkwXhuo8WcuzvfUl24RUNpt4jBDo+j49VGBqFGrG6cG3GxyMkzG+TQdI5thrXbhUeqE0v1pha+AqDMNb0Mr8U3txdw==
Content-Type: multipart/alternative; boundary="----=_Part_35584_1554090924.1723516222411"
MIME-Version: 1.0
Message-ID: <744c46d5.25b2.19149927bcb.Coremail.liupenghui1982@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD3H8g+xbpmFqYcAA--.54105W
X-CM-SenderInfo: xolx1v5qjk3xarzyjqqrwthudrp/xtbB0gY6xmWXzrEuQAADsI
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Message-ID-Hash: 424GK6NFYMP5VAQIODPRB24STGYJUTZY
X-Message-ID-Hash: 424GK6NFYMP5VAQIODPRB24STGYJUTZY
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: 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/0cUaiZ05IoIavT0oFirLWYzl7kY>
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>

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    [

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