<?xml version="1.0" encoding="utf-8"?>
<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" -->
<rfc version="3" ipr="trust200902" docName="draft-wang-data-transmission-security-irii-07" submissionType="IETF" category="std" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" consensus="true">

<front>
<title abbrev="Data Transmission Security of IR">Data Transmission Security of Identity Resolution in Industrial Internet</title><seriesInfo value="draft-wang-data-transmission-security-irii-07" stream="IETF" status="standard" name="Internet-Draft"></seriesInfo>
<author role="editor" initials="B." surname="Wang" fullname="Bin Wang"><organization>Hikvision</organization><address><postal><street>555 Qianmo Road, Binjiang District</street>
<city>Hangzhou</city>
<code>310051</code>
<country>CN</country>
</postal><phone>+86 571 8847 3644</phone>
<email>wbin2006@gmail.com</email>
</address></author>
<author role="editor" initials="K." surname="Lin" fullname="Kezhang Lin"><organization>Hikvision</organization><address><postal><street>555 Qianmo Road, Binjiang District</street>
<city>Hangzhou</city>
<code>310051</code>
<country>CN</country>
</postal><phone>+86 571 8847 3644</phone>
<email>lkz_wz98@163.com</email>
</address></author>
<author role="editor" initials="C." surname="Wang" fullname="Chonghua Wang"><organization>IIE, CAS</organization><address><postal><street></street>
<city>Beijing</city>
<code>100093</code>
<country>CN</country>
</postal><phone>+86 185 1894 5987</phone>
<email>chonghuaw@live.com</email>
</address></author>
<author role="editor" initials="X." surname="Wang" fullname="Xing Wang"><organization>Hikvision</organization><address><postal><street>555 Qianmo Road, Binjiang District</street>
<city>Hangzhou</city>
<code>310051</code>
<country>CN</country>
</postal><phone>+86 571 8847 3644</phone>
<email>xing.wang.email@gmail.com</email>
</address></author>
<author role="editor" initials="H.N." surname="Yan" fullname="Haonan Yan"><organization>Xidian University</organization><address><postal><street>No. 8, Qiannong East Road, Xiaoshan District</street>
<city>Hangzhou</city>
<code>310051</code>
<country>CN</country>
</postal><email>yanhaonan.sec@gmail.com</email>
</address></author>
<author role="editor" initials="Y.H." surname="Xie" fullname="Yinghui Xie"><organization>Hikvision</organization><address><postal><street>555 Qianmo Road, Binjiang District</street>
<city>Hangzhou</city>
<code>310051</code>
<country>CN</country>
</postal><phone>+86 571 8847 3644</phone>
<email>xieyinghui@hikvision.com</email>
</address></author>
<date year="2025" month="May" day="21"></date>
<area>Security</area>
<workgroup>Internet Engineering Task Force</workgroup>
<keyword>Industrial Internet</keyword>
<keyword>Security</keyword>
<keyword>Identity Resolution</keyword>

<abstract>
<t>This draft examines data transmission security in Industrial Internet identity resolution systems. As pivotal infrastructure enabling secure cross-organizational sharing and intelligent correlation of heterogeneous data, these systems require robust security services during resolution processes. The analysis focuses on essential protective measures for identity resolution operations.</t>
</abstract>

</front>

<middle>

<section anchor="introduction"><name>Introduction</name>
<t>Identity resolution system is an important network infrastructure for the
Industrial Internet. It provides codes, registration and resolution services for
industrial equipment, machines, materials, parts and products to achieve
interoperability, secure sharing and intelligent association of heterogeneous
information, which is an important cornerstone for the rapid development of the
Industrial Internet. Typical global identity resolution systems in existence include the
Handle system <xref target="RFC3650"></xref> <xref target="RFC3651"></xref>, the Object Identifier (OID) resolution
system <xref target="OID"></xref>, etc. In order to ensure the security of data transmission
involved in the Industrial Internet identity resolution systems, the security
technical requirements are formulated to enhance the security of the entire
Industrial Internet identity resolution system and reduce the security risk
caused by data leakage. The security technical requirements can be applied to
the planning, construction, operation and management of data transmission
security of Industrial Internet identity resolution systems.</t>
</section>

<section anchor="scope"><name>Scope</name>
<t>This draft specifies the security technical requirements for the transmission of
Industrial Internet identity resolution data.</t>
<t>This draft applies to the planning, construction, operation and management of
the Industrial Internet identity resolution data transmission security of the
relevant parties.</t>
</section>

<section anchor="terms-and-definitions"><name>Terms and Definitions</name>

<section anchor="international-root-node"><name>International Root Node</name>
<t>International root nodes serve as the global top-tier infrastructure for identity resolution systems, operating independently of geographic boundaries. These nodes fulfill dual core functions: delivering universal root-level identity services worldwide while enabling localized data synchronization and registration management for hierarchical nodes across national networks.</t>
</section>

<section anchor="national-root-node"><name>National Root Node</name>
<t>A national root node is the top-level node within a country or a region, which is connected to the international root node and secondary nodes, provides top-level identity resolution services for the whole country.</t>
</section>

<section anchor="secondary-node"><name>Secondary Node</name>
<t>A secondary node is a public node providing identity services for specific industries or multiple industries. Secondary node is responsible for allocating identity and providing identity registration, identity resolution and identity data services for industrial
enterprises. Two types of secondary nodes exist, namely industry secondary nodes and comprehensive secondary nodes.</t>
</section>

<section anchor="enterprise-node"><name>Enterprise Node</name>
<t>An enterprise node is an intra-enterprise identity service node which is able to provide identity registration, identity resolution service and identity data service for a
specific enterprise. An enterprise node should be connected to a secondary node.</t>
</section>

<section anchor="recursive-node"><name>Recursive Node</name>
<t>A recursive node is the key entrance facility of the identity resolution system, whose responsibility is to cache the resolution data in the process of identity resolution, in order to reduce the amount of resolution data processing and improve the efficiency of resolution services.</t>
</section>

<section anchor="transmission-security"><name>Transmission Security</name>
<t>Protect the confidentiality, integrity, availability and timeliness of data transmitted over the network.</t>
</section>

<section anchor="privacy"><name>Privacy</name>
<t>Privacy refers to the authority that individuals have to control their
information, including who collects and stores it and who discloses it.</t>
</section>

<section anchor="personal-data"><name>Personal Data</name>
<t>Personal Data refers to the information that a natural person can
be identified directly through the data, or indirectly through the
data combined with other information.</t>
</section>
</section>

<section anchor="abbreviation"><name>Abbreviation</name>
<table><name>Abbreviation
</name>
<thead>
<tr>
<th>Abbreviation</th>
<th align="right">Full Name</th>
</tr>
</thead>

<tbody>
<tr>
<td>TLS</td>
<td align="right">Transport Layer Security</td>
</tr>

<tr>
<td>IPSec</td>
<td align="right">Internet Protocol Security</td>
</tr>

<tr>
<td>HTTPS</td>
<td align="right">Hypertext Transfer Protocol Secure</td>
</tr>

<tr>
<td>OID</td>
<td align="right">Object Identifier</td>
</tr>

<tr>
<td>DNS</td>
<td align="right">Domain Name System</td>
</tr>

<tr>
<td>ENODE</td>
<td align="right">Enterprise Node</td>
</tr>

<tr>
<td>IIP</td>
<td align="right">Industrial Internet Platform</td>
</tr>

<tr>
<td>HandleID</td>
<td align="right">Unique Identification of Equipment</td>
</tr>
</tbody>
</table></section>

<section anchor="overview"><name>Overview</name>
<t>The Industrial Internet identity resolution and management service system represents a comprehensive platform that supports global traceability management of industrial IoT product data and enables dynamic sharing of information throughout the entire product lifecycle. This system leverages the capabilities of security identity management and resolution to accomplish these objectives. In the context of Industrial Internet identity resolution, data transmission pertains to the technology employed in the Industrial Internet terminal to obtain and transmit information. The security of this transmission involves various dimensions, including the basic security
protection measures in network security, functional domain data transmission within and across domains, and the entirety of the system's lifecycle.</t>
<figure><name>Industrial Internet Identity Resolution and Management Service System
</name>
<artwork>                            +---------------+
              +-------------+ DNS Root Node +----------------+
              |             +---------------+                |
        +-----+-------+                             +--------+------+
        |OID Root Node|  International Root Node    |Ecode Root Node|
        +-----+-------+                             +--------+------+
              |                                              |
              |         +---------------------+              |
              +---------+                     +--------------+
                        |  Handle Root Node   |
            +-----------&gt;                     &lt;----------------+
            |           +---------------------+                |
            |                                                  |
            |                                       +----------v---+
            |                                       |Secondary Node|
      +-----+--------+          +---------+         +------+-------+
      |Recursive Node+----+-----&gt;National |                |
      +-----^--------+    |     |Top Level|        +-------+--------+
            |             |     |Node     |        |                |
            |             |     +---------+   +----+------+ +-------+--+
            |             |                   | Enterprise| |Enterprise|
            |             |                   | Node      | |Node      |
            |             |                   +-----------+ +----------+
            |             |
+-----------+---------+   |    +--------------+
|Identity Resolution  |   +----&gt;Secondary Node|
|Data and Application |        +------+-------+
| +------------+      |               |
| |Industry App|      |       +-------+--------+
| +------------+      |       |                |
| +-----------+       |  +----+------+ +-------+--+
| |Enterprise |       |  | Enterprise| |Enterprise|
| |Information|       |  | Node      | |Node      |
| |System     |       |  +-----------+ +----------+
| +-----------+       |
| +-----------+       |
| |Industrial |       |
| |Internet   |       |
| |Platform   |       |
+-------------+-------+
</artwork>
</figure>
</section>

<section anchor="security-protection-scope"><name>Security Protection Scope</name>
<t>The security protection scope of the Industrial Internet identity resolution and
management service system proposed in this draft mainly means that the identity
is written into the device and is responsible for collecting product information,
including device model, device type, generation batch, generation date,
generation site, device production information link, device description data
link, etc., integrate this information into identity data, and then publish it
to the data exchange system for access by identity resolution enterprise nodes.
Among the identity resolution enterprise node, the identity resolution secondary
node, and the identity resolution root node, the process of data synchronization
between the application scenarios, the collection of data transmission
technologies used, is used to provide security assurance and security support
for the Industrial Internet identity data transmission.</t>
<t>The scope of Industrial Internet identity data transmission security protection
specifically includes the security and the security support of the data
transmission interface within and between the functional domains of the
Industrial Internet identity resolution system. Its role is in the whole life
cycle of the system (planning and design, development and construction,
operation and maintenance , abandonment and exit).</t>
<figure><name>Industrial Internet Identity Resolution and Management Service System
</name>
<artwork>            +--------------------------------------------------------+
            |          Identity Resolution Root Node                 |
            +-------------------------^------------------------------+
                                      |
            +-------------------------v------------------------------+
            |        Identity Resolution Secondary Node              |
            +-------------------------^------------------------------+
 +------------------------------------|--------------------------------+
 |                                    |                                |
 |          +-------------------------v------------------------------+ |
 |          |        Identity Resolution Enterprise Node             | |
 |          +-------------------------^------------------------------+ |
 |Demilitarized                       |                                |
 |   Zone   +-------------------------v------------------------------+ |
 |          |                Data Exchange System                    | |
 |          +-------------------------^------------------------------+ |
 |                                    |                                |
 +------------------------------------|--------------------------------+
 |          +-------------------------|------------------------------+ |
 |          |      Identity Generation and Management System         | |
 |          +------^------------------------------------------^------+ |
 |Enterprise       |                                          |        |
 | Intranet +------v-------+  Enterprise Products ------------v------+ |
 |          |              |  | +-----------------+ +--------------+ | |
 |          |              |  | |Network Hard Disk| |Access Control| | |
 |          |  Enterprise  |  | |Video Recorder   | |    Device    | | |
 |          | Information  |  | +-----------------+ +--------------+ | |
 |          |    System    |  | +------+    +----------+     +---+   | |
 |          |              |  | |Video |    |Industrial|     |...|   | |
 |          |              |  | |Camera|    |   Robot  |     |...|   | |
 |          |              |  | +------+    +----------+     +---+   | |
 |          +--------------+  +--------------------------------------+ |
 +---------------------------------------------------------------------+
</artwork>
</figure>
</section>

<section anchor="security-technical-requirements"><name>Security Technical Requirements</name>
<t>During the transmission of gathered data, it is crucial to verify the identities of the communication parties to confirm that only authorized users are involved in sending or receiving information. This verification is typically accomplished through cryptographic methods like digital signatures. It is also necessary to ensure the data remains confidential and that any attempts at alteration are noticeable throughout the transmission. To maintain the secrecy and integrity of the data in transit, established cryptographic techniques such as encryption, hashing, and digital signatures are utilized.</t>

<section anchor="data-transmission-integrity"><name>Data Transmission Integrity</name>
<t>Data transmission should comply with the following common requirements:</t>
<t>1) Support the information integrity check mechanism during transmission to
realize the transmission integrity protection of management data, authentication
information, sensitive information, important business data and other data (such
as: check code, message abstract, digital signature, etc.).</t>
<t>2) Should have transmission delay and interrupt handling capabilities to
ensure the integrity of the data.</t>
<t>3) Cryptographic technology should be used to protect the integrity of important data in transmit.</t>
<t>4) Measures should be taken to recover the data when data integrity is compromised.</t>
</section>

<section anchor="data-transmission-availability"><name>Data Transmission Availability</name>
<t>The timeliness and accuracy of the data should be guaranteed during data
transmission. Specifically:</t>
<t>1) Timeliness: the feature of identifying historical data received or data
beyond the time limit. Specifically, the data comes from the system using a
unified time allocation/correction mechanism, and the data should include time
stamps, etc.</t>
<t>2) Accuracy: When there is an acceptable error in the data, there is an overload
to ensure the normal acquisition of the data in time.</t>
</section>

<section anchor="data-transmission-confidentiality"><name>Data Transmission Confidentiality</name>
<t>When transferring data, it is necessary to ensure the confidentiality of the
data, including:</t>
<t>1) For important data, authenticate information and important business data such
as user passwords, biometrics, private keys, symmetric keys, product order
information, and unique identity of a device (Handle ID), a certain strength
encryption algorithm or other effective measures should be used to guarantee
confidentiality.</t>
<t>2) Appropriate security protocols (such as HTTPS, SSH, IPSec, TLS, etc.) should be used to
safeguard the data being transmitted.</t>
</section>

<section anchor="data-transmission-authentication"><name>Data Transmission Authentication</name>
<t>Ensure the legitimacy of the identities of both parties in the data
transmission, which means, ensure the identity authentication of the subject to
the object before the interaction, and establish a trusted transmission path.</t>
</section>

<section anchor="data-transmission-strategy"><name>Data Transmission Strategy</name>
<t>Establish a formal transmission strategy to protect the security of all types of
information transmitted through communication facilities, and meet:</t>
<t>1) Clarify the type and scope of information that can be transmitted in plain
text.</t>
<t>2) For sensitive data, such as user passwords, biometrics, private keys,
symmetric keys, etc., an encrypted transmission strategy is required.</t>
</section>

<section anchor="data-transmission-protocol"><name>Data Transmission Protocol</name>
<t>The protocol should address the safe transmission of internal and external
business, and meet:</t>
<t>Cryptographic algorithms such as data abstract, signature, and authentication
shall use the cryptographic algorithms and combinations of abstract, signature,
and authentication required by national regulations or national mandatory
standards.</t>
</section>

<section anchor="maintenance-and-update-of-transmission-protocol"><name>Maintenance and Update of Transmission Protocol</name>
<t>The confidentiality protocol for data transmission should be regularly
maintained and updated so that the procotol should reflect the requirements for
data transmission security protection and meet:</t>
<t>1) The transmission security protocol needs to be reviewed every year to ensure
that the agreement should reflect the requirements for data transmission
security protection</t>
<t>2) When new services are launched or existing services are changed, the
transmission security protocol needs to be audited and updated if necessary</t>
</section>

<section anchor="log-and-audit"><name>Log and Audit</name>
<t>The transmission system shall log and audit the following security failure
events. The content of the log shall at least contains date/time, event type,
event subject, event description, event result information, and meet the
following requirements:</t>
<t>1) The results of data transmission channel creation</t>
<t>2) Transmission device online monitoring abnormalities and alarm events</t>
<t>3) Malicious program intrusion alert event</t>
<t>4) Configuration modification operations caused by
administrators/non-administrators</t>
</section>
</section>

<section anchor="protection-dimension"><name>Protection Dimension</name>
<t>From the perspective of security requirement analysis and protection scheme design, the following implementable protection solutions can be considered.</t>

<section anchor="physical-security"><name>Physical Security</name>
<t>Ensuring physical security encompasses device hardware security, anti-interference measures, and prevention of transmission interception. Qualified devices may also incorporate security chips, encryption, key storage, and device identity authentication capabilities. Without robust physical security measures in place, implementing other security measures becomes challenging.</t>
</section>

<section anchor="authentication-mechanism"><name>Authentication Mechanism</name>
<t>This involves incorporating multiple authentication and access control mechanisms, such as dual-factor authentication and fingerprint scanners, suitable for IoT devices. Enhancing the security of human-machine interaction and machine-machine interface ensures the overall data security.</t>
</section>

<section anchor="system-security"><name>System Security</name>
<t>It involves reinforcing the security of the operating system, including digitally signing the operating system code to prevent tampering. Additionally, the access interfaces (APIs) provided by the system externally need to be secured. Data transmission interfaces should be analyzed to provide encryption and integrity protection functions.</t>
</section>

<section anchor="transmission-security-1"><name>Transmission Security</name>
<t>The protocol design at the transport layer should systematically analyze security and privacy threats and risks, ensuring the derivation of appropriate safety requirements.
Preventing privacy violations should also be considered as one of its primary considerations.</t>
</section>

<section anchor="network-security"><name>Network Security</name>
<t>Traditional network security devices and functions can still serve as means or supplements to Perimeter Security in the Industial Internet. Examples include gateway security, firewalls, antivirus and anti-malware products, intrusion detection systems (IDS), and intrusion prevention systems (IPS).</t>
</section>

<section anchor="application-security"><name>Application Security</name>
<t>IoT application developers must prioritize the security and privacy protection of their applications. When designing IoT systems, a comprehensive analysis of security should be conducted, finding a suitable tradeoff between user experience and protection.</t>
</section>

<section anchor="cloud-security"><name>Cloud Security</name>
<t>Considering the constrained processing power of IoT devices, security solutions for cloud data in the Industrial Internet should take into account the distinctive characteristics of IoT data, including its high volume endpoints and rapid flow.</t>
</section>
</section>

<section anchor="data-full-cycle-security"><name>Data Full Cycle Security</name>

<section anchor="data-collection-security"><name>Data Collection Security</name>
<t>When collecting data, it is necessary to comply with relevant laws and regulations, especially when it comes to personal data, so that users are informed, and must follow the principles of user consent, minimize collection, collect the required data according to need, and clearly set out the scope of collection and the purpose of use in the privacy policy.</t>
</section>

<section anchor="data-transmission-security"><name>Data transmission security</name>
<t>When transmitting the collected data, the identity of the two communicating parties is identified to ensure that the entity receiving or sending the data is a legitimate user, at which time digital signatures and other cryptographic techniques are mainly used to realize identity authentication. During transmission, it must be ensured that the data content will not be leaked and the data can be perceived after being tampered with, i.e., the confidentiality and integrity of the transmitted data must be ensured, which can be realized by using traditional cryptographic algorithms, such as encryption, hash, digital signature, and so on.</t>
</section>

<section anchor="data-storage-security"><name>Data storage security</name>
<t>When storing data, the data should be stored in hierarchical isolation, according to the sensitive level of the data, and the data of different levels can be stored in different hard disks by using physical isolation, or by using logical isolation, using virtualization and other related technologies to achieve isolation between the areas where the data of different levels are located.</t>
</section>
</section>

<section anchor="security-considerations"><name>Security Considerations</name>
<t>This entire memo deals with security issues.</t>
</section>

<section anchor="iana-considerations"><name>IANA Considerations</name>
<t>This documents has no IANA actions.</t>
</section>

</middle>

<back>
<references><name>Informative References</name>
<reference anchor="OID" target="http://www.oid-info.com/introduction.htm">
  <front>
    <title>Introduction to OIDs and the OID Resolution System (ORS)</title>
    <author></author>
    <date year="2020" month="May"></date>
  </front>
</reference>
<reference anchor="RFC3650" target="https://www.rfc-editor.org/info/rfc3650">
  <front>
    <title>Handle System Overview</title>
    <author fullname="S. Sun" initials="S." surname="Sun">
      <organization></organization>
    </author>
    <author fullname="L. Lannom" initials="L." surname="Lannom">
      <organization></organization>
    </author>
    <author fullname="B. Boesch" initials="B." surname="Boesch">
      <organization></organization>
    </author>
    <date year="2003" month="November"></date>
  </front>
  <seriesInfo name="DOI" value="10.17487/RFC3650"></seriesInfo>
</reference>
<reference anchor="RFC3651" target="https://www.rfc-editor.org/info/rfc3651">
  <front>
    <title>Handle System Namespace and Service Definition</title>
    <author fullname="S. Sun" initials="S." surname="Sun">
      <organization></organization>
    </author>
    <author fullname="S. Reilly" initials="S." surname="Reilly">
      <organization></organization>
    </author>
    <author fullname="L. Lannom" initials="L." surname="Lannom">
      <organization></organization>
    </author>
    <date year="2003" month="November"></date>
  </front>
  <seriesInfo name="DOI" value="10.17487/RFC3651"></seriesInfo>
</reference>
</references>

</back>

</rfc>
