Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021
summary
The gist
Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021 is a study that analyzes and compares three major credential management standards—IEEE 1609…
In short
This study compares three credential management standards (IEEE 1609, ETSI, and YD/T 3957-2021) for V2X networks. It analyzes certificate structures, signed message formats, and cryptographic methods to find compatibility issues. The research provides a reference for building secure systems by comparing performance on actual devices.
Key concepts
- Certificate Structures
- This refers to the format used to identify V2X devices. The study notes that the CertificateBase format from IEEE 1609 is adopted, categorizing certificates into enrollment (for legal ID) and authorization (for sending signed messages).
- Signed Message Formats
- This describes how data packets are secured for V2X communication. Standards like Ieee1609Dot2Data-Signed define fields such as hashId, tbsData, signer, and signature. Different systems use different signing algorithms (e.g., ECDSA or SM2) to create these secure messages.
- Cryptographic Method Efficiency
- This evaluates how fast different mathematical operations are when used for security tasks like signing and encryption. The analysis shows that SM2-256 can be slower than NIST P-256 for signing, while SM3-256 is computationally faster than SHA-256 for hashing.
- Certificate Application Processes
- This examines how systems handle the process of using certificates. A key difference found is that SCMS uses implicit certificates, which requires reconstructing an ACA public key and takes longer to verify packets compared to CCMS or C-SCMS which use explicit certificates.
Terminology used across episodes
This episode discusses
- Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021 · Paper Radio
The paper
Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021 · Read on arXiv
Chunghwa Telecom Laboratorie
DOI: 10.1007/978-3-032-28532-4_10
Transcript
Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.
Nadia: I'm Nadia.
Elias: And I'm Elias, here with Priya.
Nadia: We're looking at the paper: "Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021".
Title and authors: Nadia: So, we've talked about what the paper is titled and why it matters—it’s about comparing IEEE, ETSI, and YD/T three thousand nine hundred fifty-seven-two thousand twenty-one to find compatibility issues <ref:2603.03376#pg1,IEEE, ETSI, and YD/T 3957-2021>. Now let's look at what the actual summary of this work says.
Elias: The summary boils down to analyzing three main things: the certificate formats, the signed message formats, and how those requests are handled between different standards. It sets up a baseline for developing a secure system that can handle all three environments simultaneously.
Priya: That sounds like the core challenge for anyone trying to deploy V2X technology across different regions or partners; you need a way to make sure your device works everywhere, right?
Nadia: Exactly. The paper explains that they're not just listing standards side-by-side; they are actively comparing how the structure of those signed messages looks and what cryptographic methods are being used underneath them.
Elias: They specifically look at the Ieee1609 Dot2 Data format for signed messages, and how different systems use things like SHA256 with ECDSA versus SM2 with SM2-two hundred fifty-six <ref:2603.03376#pg1>. That’s a lot of detail packed into that comparison.
The paper's summary: Nadia: To break down the summary, the authors show how they categorize certificates into enrollment and authorization types, and they explain that in both SCMS and C-SCMS, you use an enrollment certificate to ask an Authorization Certificate Authority for a signed message key.
Elias: That's a key point. Then they highlight that the way this request is made—whether it’s through SCMS or CCMS—can default to using implicit certificates or explicit certificates, which changes how verification happens later on.
Priya: I wonder if that difference in certificate type is important for privacy or security testing? If one system defaults to explicit and another to implicit, that means the verification steps are fundamentally different.
Nadia: It definitely matters because it affects how much data is exposed during the request process. And they also look at the cryptographic efficiency of the methods used, like comparing NIST P-two hundred fifty-six against SM2-two hundred fifty-six for signing speed and computation time <ref:2603.03376#pg1>.
Elias: They found that while key generation times might be similar between curves like NIST P-two hundred fifty-six and SM2-two hundred fifty-six the actual signature creation takes more time with SM2 because it needs an extra hashing calculation <ref:2603.03376#pg1,NIST P-256 and SM2-256>.
The paper's improvements: Nadia: So, what do the authors suggest to make this comparison better than just a simple list? They propose looking at how the standards themselves evolve and what changes they are making to their protocols.
Elias: They suggest that future work could focus on implementing implicit certificates in both CCMS and C-SCMS so they can compare systems using that same default certificate type across all three standards.
Priya: That would give us a much more complete picture of the actual performance trade-offs when you are trying to deploy these systems in the real world, not just theoretical comparisons.
Nadia: Right. They also hint that they should look at how different cryptographic methods scale with different message sizes, which is a big practical concern for V2X devices handling everything from small safety messages to larger data packets.
Elias: And they point out that the variations in parameters—like using SM4-one hundred twenty-eight versus AES-one hundred twenty-eight for encryption—show that efficiency isn't just about the curve, but about which specific algorithm you pick for different tasks <ref:2603.03376#pg1>.
Conclusion: Nadia: So, to wrap up this look at the paper "Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T three thousand nine hundred fifty-seven-two thousand twenty-one" it seems the main finding is that while standards are moving toward compatibility in certificate formats, the differences really boil down to those specific cryptographic choices and how they handle request processes <ref:2603.03376#pg1,Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI>.
Elias: That's right. The paper shows that when you look at efficiency, things like SM3-two hundred fifty-six actually show better computational performance than standard SHA-two hundred fifty-six for hashing tasks <ref:2603.03376#pg1>.
Priya: So, for a system designer looking at this, the implication is that choosing the right cryptographic method isn't just about what looks secure on paper; it’s about how fast the device can actually process those signatures in real time while maintaining a certain level of security.
Nadia: Right. And they also noted that SCMS uses implicit certificates by default, which requires an extra step involving the Authorization Certificate Authority public key reconstruction, leading to longer computation times when verifying packets.
Elias: That's the practical catch for those systems—the implicit certificate model introduces a dependency on a pre-existing public key that adds latency during verification.
Priya: So, ultimately, this research gives us a reference point to decide which system structure is best suited for our deployment goals based on performance metrics and security requirements.
Nadia: That’s the gist of it. We looked at how IEEE one thousand six hundred nine ETSI, and YD/T three thousand nine hundred fifty-seven-two thousand twenty-one stack up in terms of certificates, messages, and crypto efficiency using this paper as our guide <ref:2603.03376#pg1,ETSI, and YD/T 3957-2021>.
Elias: It's a solid comparison for anyone building cross-standard V2X solutions who needs to understand the performance cost of choosing one cryptographic signature over another.
More episodes
- 2608.27496-ROPE: Routed Origin Policy Enforcement against Indirect Prompt Injection
- Daily Summary for 2026-11-19
- 2607.07085-Is Randomness Necessary for Adaptive Data Analysis?
- The day in conversation for 2026-11-19
- Daily Summary for 2026-11-19
- 2609.10601-Threshold Choice, Not Sample Size, Bounds Trustless Verification of Nondeterministic Compound AI Workflows
- 2610.38786-Adversarial Process Disturbances at a Deployable Alarm Budget: Detector Evaluation on a Simulator and a Real Plant
- 2511.08660-Binary and Multiclass Cyberattack Classification on GeNIS Dataset
- 2604.27302-Static Attribution of Android Residential Proxy Malware Using Graph Kernels
- Daily Summary for 2026-11-18