RPC Message Integrity Check via Block Checksum Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data transmission protocols, such as those using RPCs in storage systems, face significant computational overhead and latency due to the need for hashing and encrypting entire procedure-specific parameters for security, which reduces processing resources and increases data retrieval time.
Innovation Solution
A system and method that generate block checksums within the control portion of RPCs, using conventional checksumming procedures, and hash these checksums for encryption to create a message integrity check, allowing for end-to-end data protection without re-checksumming data, thus reducing computational overhead and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entire procedure-specific parameters are hashed and encrypted for security, then data integrity and confidentiality are improved, but computational overhead and latency increase
Solution Approach 1:
The procedure-specific parameters are divided into multiple data blocks, and checksums are calculated for each block individually rather than hashing the entire parameter set. This segmentation reduces the computational burden per operation while maintaining data integrity verification capability.
Solution Approach 2:
Only the essential checksum information is extracted and transmitted, rather than transmitting and processing the entire procedure-specific parameter set. This extraction approach reduces the amount of data that requires hashing and encryption operations.
2Reliability
If entire procedure-specific parameters are hashed and encrypted for security, then data confidentiality is improved, but processing resources are reduced
Solution Approach 1:
The data is segmented into blocks with individual checksums, allowing selective processing and verification. This segmentation enables more efficient use of processing resources by focusing computational effort only on critical verification operations rather than full-parameter hashing.
Solution Approach 2:
Checksums serve as intermediary values that represent the integrity state of data blocks without requiring the full computational overhead of hashing and encrypting the entire parameter set. These checksums act as a lightweight verification mechanism.
3Productivity
If block checksums are generated and hashed for message integrity check, then computational overhead is reduced, but data transmission complexity increases
Solution Approach 1:
Only the essential checksum values are extracted and included in the RPC message, rather than transmitting redundant verification data. This extraction simplifies the message structure while maintaining integrity verification capability.
Solution Approach 2:
The approach changes the verification parameter from full-parameter hashing to block-level checksum verification. This parameter change reduces computational complexity while maintaining adequate integrity verification for the data transmission protocol.
Data Source
AI summary
A system and method generates a message integrity check. The message integrity check value is computed by hashing one or more block checksums from procedure specific parameters of an RPC and then encrypting the resulting hash value. The one or more block checksums may be quickly computed using conventional data checksumming procedures for the data contained within the RPC. As such, the computations to hash the block checksums is minimal. The computed message integrity check is appended to the RPC to thereby provide a level of security approaching or equal to the level of Integrity defined by the RPCSEC_GSS protocol specification.