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

刘鹏辉 <liupenghui1982@163.com> Fri, 02 August 2024 02:04 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 718CEC169425 for <nasr@ietfa.amsl.com>; Thu, 1 Aug 2024 19:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.841
X-Spam-Level:
X-Spam-Status: No, score=-6.841 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_RATIO_04=0.001, 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_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=unavailable 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 eXz4ZdygpP9R for <nasr@ietfa.amsl.com>; Thu, 1 Aug 2024 19:04:48 -0700 (PDT)
Received: from m15.mail.163.com (m15.mail.163.com [45.254.50.220]) by ietfa.amsl.com (Postfix) with ESMTP id 32AD6C14CE55 for <nasr@ietf.org>; Thu, 1 Aug 2024 19:04:46 -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=t4/B1iDzUL1T2U32CyBWX1hF4yg544BdZBxTRg9BP1A=; b=K ehQ7l3Bl+efNEQ7iX5qN7RJgQf/6uor/6P2NZiHbLonhJOC+hQyrOjfpo+ndcTE0 G3s6N7PxXuUBR5GbY5joWqoj7aOhdxs86RQaFj6BsuG17mYlYUBrSSDInG3ClBfD UughMCEpqKJjhACEx3UjAt7CCpdv1wkh0Z8b4E1B4c=
Received: from liupenghui1982$163.com ( [218.17.115.213] ) by ajax-webmail-wmsvr-40-140 (Coremail) ; Fri, 2 Aug 2024 10:04:31 +0800 (CST)
X-Originating-IP: [218.17.115.213]
Date: Fri, 02 Aug 2024 10:04:31 +0800
From: 刘鹏辉 <liupenghui1982@163.com>
To: "Liuchunchi(Peter)" <liuchunchi@huawei.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: <fe9299737de2469da894ed6e55a53bf1@huawei.com>
References: <202407231553159277592@chinamobile.com>, <514b701e.3dbe.190e2e04151.Coremail.liupenghui1982@163.com> <202408011054476926448@chinamobile.com> <fe9299737de2469da894ed6e55a53bf1@huawei.com>
X-CM-CTRLMSGS: ulJbg3RyYWNlS2V5PXByZV9lMjhmMmM3ZjQ0NjYwMWZlZTAwNmI5YWM3NzE2Y TlkNg==
X-NTES-SC: AL_Qu2ZAPmdu0os5yedYekfmkwXhuo8WcuzvfUl24RUNpt4jB/o+y0kXnhELFTE3uOJKCacsR+QeyJn9MZ4QaJyY4IsZhQkT/UKYZ3m3heJ80kRdQ==
Content-Type: multipart/related; boundary="----=_Part_27125_1782711840.1722564271768"
MIME-Version: 1.0
Message-ID: <5aaf2f9d.1c92.19110d4dea0.Coremail.liupenghui1982@163.com>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: _____wD33+evPqxm17p0AA--.36087W
X-CM-SenderInfo: xolx1v5qjk3xarzyjqqrwthudrp/1tbiqQ8vxmVOB7IQWgAAsb
X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU==
Message-ID-Hash: YAWOEG327BPKTF2KOYTIFGM5DLNNV2PC
X-Message-ID-Hash: YAWOEG327BPKTF2KOYTIFGM5DLNNV2PC
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>, 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/Jw219dGl2Y0pYKG3jZ8byH6PZZw>
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>

GDPR (General Data Protection Regulation) establishes basic principles for the cross-border flow and transmission of personal data, and stipulates the process of cross-border data transfer.

GDPR is an important regulation enacted by the European Union to protect personal data, and the provisions on cross-border data transfer are particularly critical. According to the provisions of GDPR, the cross-border transfer of personal data needs to meet certain conditions and procedures to ensure the protection and security of personal data. The following are some core points of GDPR on cross-border data transfer:

Adequate protection level : GDPR requires that personal data can only be transferred to these regions if the recipient country or region is recognized by the European Commission as providing an equal or higher level of personal data protection than the EU. Currently, some countries and regions, such as Andorra, Argentina, Canada, etc., have obtained the EU's adequacy recognition.

Cross-border data transfer paths : GDPR provides three main cross-border data transfer paths:

The recipient's country or region has obtained adequacy determination (‌Adequacy Decision‌), which is the whitelist mechanism.‌
We ensure appropriate safeguards during data transfer by signing the standard contractual clauses issued by the European Union.
In some cases, data can be anonymized to enable cross-border transfers.

Penalties for non-compliance : GDPR sets high penalties for non-compliant cross-border data transfers to ensure that companies comply with regulations. In recent years, with the increase in law enforcement cases, the amount of penalties has also continued to rise, which provides companies with an incentive to comply.

Standard Contract for the Export of Personal Information : The “Measures for the Standard Contract for the Export of Personal Information” and the “Standard Contract for the Export of Personal Information” issued by the Cyberspace Administration of China (CAC) provide specific guidance for Chinese companies to ensure compliance when transferring personal information across borders.

In summary, GDPR aims to ensure the protection and security of personal data by setting strict rules and conditions for cross-border data transfer, while promoting the legal cross-border flow of data. Companies and organizations need to have a deep understanding of and comply with these regulations to ensure the legality and security of their cross-border data activities.

Cross-border data flow requires companies to take corresponding measures according to the laws of different countries and regions. This usually includes:

Conduct a security assessment
Obtain user consent
Use of standard contractual clauses or internal company rules
Ensure that the recipient has adequate data protection measures in place


作者:Pangolin
链接:https://www.zhihu.com/question/659000073/answer/3534355750
来源:知乎
著作权归作者所有。商业转载请联系作者获得授权,非商业转载请注明出处。















At 2024-08-01 17:25:13, "Liuchunchi(Peter)" <liuchunchi@huawei.com> wrote:

"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

 

发件人: 刘鹏辉

发送时间: 2024-07-24 11:54

收件人: Meiling Chen

抄送: Luigi IANNONE; 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....

 

 

 

 

 

 

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