[nasr] Re: 回复: Re: Secure Routing Path Consideration- China Mobile-ietf120
刘鹏辉 <liupenghui1982@163.com> Tue, 13 August 2024 02:21 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 28329C14F6EF for <nasr@ietfa.amsl.com>; Mon, 12 Aug 2024 19:21:11 -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_L3=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 clT-l6jbHy5N for <nasr@ietfa.amsl.com>; Mon, 12 Aug 2024 19:21:07 -0700 (PDT)
Received: from m16.mail.163.com (m16.mail.163.com [220.197.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF94C14F6EC for <nasr@ietf.org>; Mon, 12 Aug 2024 19:21:05 -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=jJAZ1axOQqoxth8lIYrhlUAmDUHdGvV5ytzhzHcm6fU=; b=p VZyk+qZSk045EiHCU//1hlHTOq37zpGeBi0ueUTVKM0tGFlqt6YE5MP/9SJMIQde Y0g8Qpi/uGgF/cP0J5BQ+HlaQpM/rAIN7nu2EeyMGdalZ5cSi0Eb5t+RXlYFYBet 4XUCB6jGYbXY/0JqKCrcgrRIeqZY5JiWhorY2v/P3I=
Received: from liupenghui1982$163.com ( [218.17.115.213] ) by ajax-webmail-wmsvr-40-138 (Coremail) ; Tue, 13 Aug 2024 10:21:01 +0800 (CST)
X-Originating-IP: [218.17.115.213]
Date: Tue, 13 Aug 2024 10:21:01 +0800
From: 刘鹏辉 <liupenghui1982@163.com>
To: Michael Richardson <mcr@sandelman.ca>
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: <17219.1722798809@obiwan.sandelman.ca>
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>
X-CM-CTRLMSGS: F4jiXHRyYWNlS2V5PXByZV84M2YwMDBmZDRmZjQyYjZjNzdlODcyNjBiMDA0M GM2MA==
X-NTES-SC: AL_Qu2ZAfmauk4t5yWbZukfmkwXhuo8WcuzvfUl24RUNpt4jBDo+j49VGBqFGrG6cG3GxyMkzG+TQdI5thrXbhUeqE0gq0asakOTC1JFiblf6rzMQ==
Content-Type: multipart/alternative; boundary="----=_Part_32694_1723498022.1723515661541"
MIME-Version: 1.0
Message-ID: <41166e12.22a3.1914989ece6.Coremail.liupenghui1982@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD3n6INw7pmEegaAA--.7705W
X-CM-SenderInfo: xolx1v5qjk3xarzyjqqrwthudrp/1tbiMw45xmXAnIWkUwADsK
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Message-ID-Hash: 6SDYKRJJ2VHFQ5LNTMNGWIB7PN64I34W
X-Message-ID-Hash: 6SDYKRJJ2VHFQ5LNTMNGWIB7PN64I34W
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: "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/ARQkWq-hnuR3H9RzxkJU2M116JM>
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 am not a professional in legal, not sure if the following statement meets the requirements. (107) The Commission may recognise that a third country, a territory or a specified sector within a third country, or an international organisation no longer ensures an adequate level of data protection. Consequently the transfer of personal data to that third country or international organisation should be prohibited, unless the requirements in this Regulation relating to transfers subject to appropriate safeguards, including binding corporate rules, and derogations for specific situations are fulfilled. In that case, provision should be made for consultations between the Commission and such third countries or international organisations. The Commission should, in a timely manner, inform the third country or international organisation of the reasons and enter into consultations with it in order to remedy the situation. More details, you can see https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679&from=en At 2024-08-05 03:13:29, "Michael Richardson" <mcr@sandelman.ca> wrote: > >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