Traceability Matrix
End-to-end coverage from customer requirement to system requirement, design item, estimation, and Jira candidate.
Traceability Matrix
End-to-end coverage from customer requirement to system requirement, design item, estimation, and Jira candidate.
Traceability Decision Impact
Downstream engineering artifacts remain provisional until customer clarification closure evidence is complete.
Search and Filters
End-to-End Traceability Matrix
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Customer Requirement ID | Customer Requirement Statement / Short Title | System Requirement ID(s) | System Requirement Short Title | Architecture / Design Item ID(s) | Design Type | Estimation ID / Effort | Jira Issue Key | Clarification Status | P1 Decision Status | Security Weak Area | Evidence Status | Coverage Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RFQX-1001379436-P10-000-01-0001 | SummaryStatementThis document contains general cybersecurity requirements. The requirements specified in this document are applicable to all ECUs. The supplier of ECU is responsible to take all the necessary measures and steps to comply with the requirements listed in this document. | None | None | None | None | RFQX-1001379436-P10-000-01-0001 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-1001379436-P10-000-01-0002 | Target readerStatementThe target readers of this specification are ECU suppliers, which can be either internal or external in relation to the vehicle manufacturer. In both cases, whenever the term “ECU supplier” or just “supplier” is used in this specification it refers to the company and organization which is responsible for the implementation and delivery of the ECU according to the requirements in this specification. And in both cases, whenever the term “vehicle manufacturer” is used in this specification this term refers to the system owner (responsible receiver) at the vehicle manufacturer. | None | None | None | None | RFQX-1001379436-P10-000-01-0002 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-1001379436-P10-000-01-0003 | Definition of termsStatementTerm Definition Shall This word, or the term "Required", means that the definition is an absolute requirement of the specification. Threat Analysis and Risk Assessment A structured approach to identify possible threats and evaluate risks with respect to the potential damages and the effort needed for successful attack. Cybersecurity concept A cybersecurity concept is a work product that documents cybersecurity relevant aspects of the product. The cybersecurity concept shall describe the scope of the risk analysis, risks that were identified during the risk analysis, cybe rsecurity goals, cybersecurity requirements, mitigation strategies, validation, and verification strategies, etc. Table 1: Definition of terms | None | None | AD-007 | component | RFQX-1001379436-P10-000-01-0003 / 18h | Not imported | Still Requires Customer Decision | P1 OPEN | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-1001379436-P10-000-01-0004 | Abbreviated termsStatementAbbreviation Description ECU Electronic Control Unit Table 2: Abbreviated terms | None | None | None | None | RFQX-1001379436-P10-000-01-0004 / 56h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0005 | The cybersecurity concept shall describe the scope of the risk analysis, risks that were identified during the risk analysis, cybe rsecurity goals, cybersecurity requirements, mitigation strategies, validation, and verification strategies, etc.StatementThe cybersecurity concept shall describe the scope of the risk analysis, risks that were identified during the risk analysis, cybe rsecurity goals, cybersecurity requirements, mitigation strategies, validation, and verification strategies, etc. | None | None | AD-007 | component | RFQX-1001379436-P10-000-01-0005 / 56h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0006 | Cybersecurity principles are high level requirements that drive development and refinement of functional and technical cybersecurity requirements.StatementCybersecurity principles are high level requirements that drive development and refinement of functional and technical cybersecurity requirements. | None | None | None | None | RFQX-1001379436-P10-000-01-0006 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-1001379436-P10-000-01-0007 | The supplier shall provide documentation describing their strategies and methods for working with embedded systems cybersecurity.StatementThe supplier shall provide documentation describing their strategies and methods for working with embedded systems cybersecurity. | SSR-CON-001 | Security evidence and traceability — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0007 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0008 | The supplier shall perform risk assessment based on a threat and vulnerability analysis for each release, including any vehicle manufacturer-specific adaptations.StatementThe supplier shall perform risk assessment based on a threat and vulnerability analysis for each release, including any vehicle manufacturer-specific adaptations. | SSR-VIH-001 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-007 | component | RFQX-1001379436-P10-000-01-0008 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0009 | Method and scope shall be proposed to and approved by the vehicle manufacturer.StatementMethod and scope shall be proposed to and approved by the vehicle manufacturer. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0009 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0010 | Documentation on the method and results shall be provided to the vehicle manufacturer.StatementDocumentation on the method and results shall be provided to the vehicle manufacturer. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0010 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0011 | Note: The vehicle manufacturer and supplier shall collaboratively define the context of the system or function to enable the supplier performing the risk assessment.StatementNote: The vehicle manufacturer and supplier shall collaboratively define the context of the system or function to enable the supplier performing the risk assessment. | None | None | AD-001 | component | RFQX-1001379436-P10-000-01-0011 / 24h | Not imported | Still Requires Customer Decision | P1 OPEN | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0012 | The supplier shall describe the cybersecurity concept and how it is implemented in hardware and software respectively.StatementThe supplier shall describe the cybersecurity concept and how it is implemented in hardware and software respectively. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0012 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0013 | All risks identified in cybersecurity risk analyses shall be evaluated.StatementAll risks identified in cybersecurity risk analyses shall be evaluated. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0013 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-1001379436-P10-000-01-0014 | For each risk identified in the cybersecurity risk analyses, a risk treatment decision shall be made to avoid, reduce, share, or retain the risk.StatementFor each risk identified in the cybersecurity risk analyses, a risk treatment decision shall be made to avoid, reduce, share, or retain the risk. | None | None | AD-007 | component | RFQX-1001379436-P10-000-01-0014 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0015 | Cybersecurity controls shall sufficiently reduce the risk.StatementCybersecurity controls shall sufficiently reduce the risk. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0015 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-1001379436-P10-000-01-0016 | It shall be possible to verify which cybersecurity controls were derived from which requirements.StatementIt shall be possible to verify which cybersecurity controls were derived from which requirements. | None | None | AD-007 | component | RFQX-1001379436-P10-000-01-0016 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0017 | The cybersecurity concept of the supplier shall contain a documentation of the accepted residual risk and be agreed with the vehicle manufacturer.StatementThe cybersecurity concept of the supplier shall contain a documentation of the accepted residual risk and be agreed with the vehicle manufacturer. | SSR-CON-001 | Security evidence and traceability — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0017 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0018 | The supplier shall provide documentation of the verification and validation methods of cybersecurity features.StatementThe supplier shall provide documentation of the verification and validation methods of cybersecurity features. | SSR-CON-001 | Security evidence and traceability — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0018 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0019 | The supplier shall provide test reports detailing the results from the verification and validation of cybersecurity features.StatementThe supplier shall provide test reports detailing the results from the verification and validation of cybersecurity features. | SSR-CON-001 | Security evidence and traceability — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0019 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0020 | The vehicle manufacturer reserves the right to perform penetration testing on the ECU to identify potential vulnerabilities.StatementThe vehicle manufacturer reserves the right to perform penetration testing on the ECU to identify potential vulnerabilities. | None | None | None | None | RFQX-1001379436-P10-000-01-0020 / 16h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-1001379436-P10-000-01-0021 | An inventory of software and protocols, including their versions, shall be provided by the supplier.StatementAn inventory of software and protocols, including their versions, shall be provided by the supplier. | SSR-CON-003 | Security evidence and traceability — Cybersecurity Concept and Evidence | AD-001 | component | RFQX-1001379436-P10-000-01-0021 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0022 | A BOM containing part numbers and versions of hardware components used in the product shall be provided by the supplier.StatementA BOM containing part numbers and versions of hardware components used in the product shall be provided by the supplier. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-1001379436-P10-000-01-0022 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0023 | The vehicle manufacturer reserves the right to request documentation and evidence as well as to perform or order a compliance audit to determine whether the listed requirements are fulfilled.StatementThe vehicle manufacturer reserves the right to request documentation and evidence as well as to perform or order a compliance audit to determine whether the listed requirements are fulfilled. | None | None | None | None | RFQX-1001379436-P10-000-01-0023 / 16h | Not imported | Still Requires Customer Decision | No P1 link | evidence completeness | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-1001379436-P10-000-01-0024 | The vehicle manufacturer and the supplier shall set up a cybersecurity DIA to agree on the responsibilities for the distributed cybersecurity activities.StatementThe vehicle manufacturer and the supplier shall set up a cybersecurity DIA to agree on the responsibilities for the distributed cybersecurity activities. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0024 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0025 | The ECU shall be able to verify integrity and authenticity of a vehicle manufacturer-specified set of data stored within the ECU.StatementThe ECU shall be able to verify integrity and authenticity of a vehicle manufacturer-specified set of data stored within the ECU. | SSR-DAI-001 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-1001379436-P10-000-01-0025 / 16h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0026 | Methods shall be proposed to and approved by the vehicle manufacturer.StatementMethods shall be proposed to and approved by the vehicle manufacturer. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0026 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0027 | The supplier shall apply methods for isolation of software/hardware components and data to reduce the effect in case of a cybersecurity breach.StatementThe supplier shall apply methods for isolation of software/hardware components and data to reduce the effect in case of a cybersecurity breach. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0027 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0028 | Selection of cryptographic methods and their use shall be agreed upon between the vehicle manufacturer and the supplier.StatementSelection of cryptographic methods and their use shall be agreed upon between the vehicle manufacturer and the supplier. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0028 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0029 | All network services implemented in the ECU shall undergo hardening.StatementAll network services implemented in the ECU shall undergo hardening. | SSR-PROD-001 | Supplier Development and Production Hardening — Supplier Development and Production Hardening | AD-006 | component | RFQX-1001379436-P10-000-01-0029 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0030 | The ECU shall only expose network and communication services that have been agreed upon with the vehicle manufacturer.StatementThe ECU shall only expose network and communication services that have been agreed upon with the vehicle manufacturer. | SSR-COM-001 | OEM/Customer Review Interface — Secure Communication and Boundary Control | AD-006 | component | RFQX-1001379436-P10-000-01-0030 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0031 | Communication interfaces shall use boundary controls such as ingress/egress filtering.StatementCommunication interfaces shall use boundary controls such as ingress/egress filtering. | SSR-COM-002 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-008 | component | RFQX-1001379436-P10-000-01-0031 / 16h | Not imported | No linked clarification | No P1 link | boundary ownership | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0032 | Communication boundary controls shall be configurable by the vehicle manufacturer.StatementCommunication boundary controls shall be configurable by the vehicle manufacturer. | SSR-COM-003 | OEM/Customer Review Interface — Secure Communication and Boundary Control | AD-008 | component | RFQX-1001379436-P10-000-01-0032 / 16h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0033 | Methods shall be proposed and approved by the vehicle manufacturer.StatementMethods shall be proposed and approved by the vehicle manufacturer. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0033 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0034 | Any interfaces used for development purposes shall be removed or disabled in series production.StatementAny interfaces used for development purposes shall be removed or disabled in series production. | SSR-COM-002 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-008 | component | RFQX-1001379436-P10-000-01-0034 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0035 | The details shall be agreed upon between the vehicle manufacturer and the supplier.StatementThe details shall be agreed upon between the vehicle manufacturer and the supplier. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0035 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0036 | Only hardware interfaces and protocols specified by the vehicle manufacturer shall be available in series production.StatementOnly hardware interfaces and protocols specified by the vehicle manufacturer shall be available in series production. | SSR-COM-001 | OEM/Customer Review Interface — Secure Communication and Boundary Control | AD-006 | component | RFQX-1001379436-P10-000-01-0036 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0037 | It shall be possible for the vehicle manufacturer to securely inject data into the product in accordance with the specification provided by the vehicle manufacturer.StatementIt shall be possible for the vehicle manufacturer to securely inject data into the product in accordance with the specification provided by the vehicle manufacturer. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0037 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0038 | Data specified by the vehicle manufacturer shall be protected from manipulations.StatementData specified by the vehicle manufacturer shall be protected from manipulations. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0038 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0039 | Data specified by the vehicle manufacturer shall be protected from disclosure.StatementData specified by the vehicle manufacturer shall be protected from disclosure. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0039 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0040 | Intellectual property of the vehicle manufacturer shall be protected from disclosure.StatementIntellectual property of the vehicle manufacturer shall be protected from disclosure. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0040 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0041 | It shall be possible for the vehicle manufacturer to securely inject key material and other data used for cybersecurity controls into the ECU according to the specification of the vehicle manufacturer.StatementIt shall be possible for the vehicle manufacturer to securely inject key material and other data used for cybersecurity controls into the ECU according to the specification of the vehicle manufacturer. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-1001379436-P10-000-01-0041 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0042 | Secrets, public keys and other data used for cybersecurity controls in production vehicle systems shall be different from those used in pre-production phases.StatementSecrets, public keys and other data used for cybersecurity controls in production vehicle systems shall be different from those used in pre-production phases. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-1001379436-P10-000-01-0042 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0043 | ECUs shall only contain the secrets agreed between the vehicle manufacturer and the supplier.StatementECUs shall only contain the secrets agreed between the vehicle manufacturer and the supplier. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0043 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0044 | ECUs shall conform to the harmonized Security Access specification [1] provided by the vehicle manufacturer.StatementECUs shall conform to the harmonized Security Access specification [1] provided by the vehicle manufacturer. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0044 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0045 | It shall be possible to update the software of the ECU.StatementIt shall be possible to update the software of the ECU. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0045 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0046 | The supplier shall inform the vehicle manufacturer if any cybersecurity patches are available.StatementThe supplier shall inform the vehicle manufacturer if any cybersecurity patches are available. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-1001379436-P10-000-01-0046 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0047 | An incident response process shall be proposed to and approved by the vehicle manufacturer.StatementAn incident response process shall be proposed to and approved by the vehicle manufacturer. | SSR-VIH-002 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-003 | component | RFQX-1001379436-P10-000-01-0047 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0048 | In case of cybersecurity incidents, the incident response process shall be used.StatementIn case of cybersecurity incidents, the incident response process shall be used. | SSR-VIH-001 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-007 | component | RFQX-1001379436-P10-000-01-0048 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0049 | The incident response process shall be maintained for the entire product lifetime.StatementThe incident response process shall be maintained for the entire product lifetime. | SSR-VIH-002 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-003 | component | RFQX-1001379436-P10-000-01-0049 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0050 | The incident response process shall ensure that risk is managed in coordination with the vehicle manufacturer.StatementThe incident response process shall ensure that risk is managed in coordination with the vehicle manufacturer. | SSR-VIH-002 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-003 | component | RFQX-1001379436-P10-000-01-0050 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0051 | Any vulnerabilities that are identified during product lifecycle shall be promptly communicated to the vehicle manufacturer.StatementAny vulnerabilities that are identified during product lifecycle shall be promptly communicated to the vehicle manufacturer. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0051 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0052 | The report shall include information needed to identify the affected vehicles/products.StatementThe report shall include information needed to identify the affected vehicles/products. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0052 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0053 | Methods including the stipulation of a reasonable notification time shall be proposed to and approved by the vehicle manufacturer.StatementMethods including the stipulation of a reasonable notification time shall be proposed to and approved by the vehicle manufacturer. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0053 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0054 | Following each identified and reported vulnerability, the supplier and vehicle manufacturer shall agree on an initial response to the vulnerability.StatementFollowing each identified and reported vulnerability, the supplier and vehicle manufacturer shall agree on an initial response to the vulnerability. | SSR-VIH-003 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-008 | component | RFQX-1001379436-P10-000-01-0054 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0055 | Within adequate time after the initial vulnerability report, the supplier shall provide more information about the identified vulnerability.StatementWithin adequate time after the initial vulnerability report, the supplier shall provide more information about the identified vulnerability. | SSR-VIH-003 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-008 | component | RFQX-1001379436-P10-000-01-0055 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0056 | The information shall contain • the version(s) of affected hardware or software components, • nature of the vulnerability, • description of the affected cybersecurity goal, • technical conditions to exploit the vulnerability, • impact of the exploitation and • possibilities to remove the vulnerability.StatementThe information shall contain • the version(s) of affected hardware or software components, • nature of the vulnerability, • description of the affected cybersecurity goal, • technical conditions to exploit the vulnerability, • impact of the exploitation and • possibilities to remove the vulnerability. | None | None | AD-007 | component | RFQX-1001379436-P10-000-01-0056 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0057 | Methods including the stipulation of a reasonable reporting time shall be proposed to and approved by the vehicle manufacturer.StatementMethods including the stipulation of a reasonable reporting time shall be proposed to and approved by the vehicle manufacturer. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0057 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0058 | The supplier shall have a method for monitoring available vulnerability databases for vulnerabilities that can affect the delivered product.StatementThe supplier shall have a method for monitoring available vulnerability databases for vulnerabilities that can affect the delivered product. | SSR-VIH-004 | Vulnerability and Incident Handling — Vulnerability and Incident Handling | AD-005 | interface | RFQX-1001379436-P10-000-01-0058 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0059 | Identified vulnerabilities shall be considered in all current development projects or projects under field monitoring.StatementIdentified vulnerabilities shall be considered in all current development projects or projects under field monitoring. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0059 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-1001379436-P10-000-01-0060 | An ECU returned from field shall allow for field-return analysis.StatementAn ECU returned from field shall allow for field-return analysis. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-1001379436-P10-000-01-0060 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-1001379436-P10-000-01-0061 | Field-return analysis secrets shall not be operational in the field.StatementField-return analysis secrets shall not be operational in the field. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-1001379436-P10-000-01-0061 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-1001379436-P10-000-01-0062 | An ECU enabled for field-return analysis shall not be possible to use as a spare part.StatementAn ECU enabled for field-return analysis shall not be possible to use as a spare part. | SSR-LIFE-001 | Lifecycle / Field Return / Decommissioning — Lifecycle / Field Return / Decommissioning | AD-006 | component | RFQX-1001379436-P10-000-01-0062 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-1001379436-P10-000-01-0063 | All secrets specified by the vehicle manufacturer shall be protected throughout the lifecycle of the ECU.StatementAll secrets specified by the vehicle manufacturer shall be protected throughout the lifecycle of the ECU. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-1001379436-P10-000-01-0063 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-1001379436-P10-000-01-0064 | End-of-life and decommissioning shall be specifically considered.StatementEnd-of-life and decommissioning shall be specifically considered. | None | None | AD-008 | component | RFQX-1001379436-P10-000-01-0064 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0065 | Notes: a) It shall not be possible for a third party to reuse an ECU without system support from the vehicle manufacturer.StatementNotes: a) It shall not be possible for a third party to reuse an ECU without system support from the vehicle manufacturer. | None | None | AD-006 | component | RFQX-1001379436-P10-000-01-0065 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0066 | b) Decommissioning of an ECU shall not have the potential of causing unacceptable risk to the road user or the vehicle manufacturer.Statementb) Decommissioning of an ECU shall not have the potential of causing unacceptable risk to the road user or the vehicle manufacturer. | None | None | AD-006 | component | RFQX-1001379436-P10-000-01-0066 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-1001379436-P10-000-01-0067 | Security related events shall be identified and logged.StatementSecurity related events shall be identified and logged. | SSR-LOG-001 | Security Logging and Event Handling — Security Logging and Event Handling | AD-007 | component | RFQX-1001379436-P10-000-01-0067 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0001 | The gearbox itself shall be used in all drivetrains and the ECA shall be common and must be complaint to be put on any driveline setup.StatementThe gearbox itself shall be used in all drivetrains and the ECA shall be common and must be complaint to be put on any driveline setup. | None | None | AD-008 | component | RFQX-3299216-1-0001 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0002 | The clutch actuator shall be electrically drivenStatementThe clutch actuator shall be electrically driven | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0002 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0003 | The actuator is placed outside of the gearboxStatementThe actuator is placed outside of the gearbox | None | None | None | None | RFQX-3299216-1-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0004 | The ECA (Electric Clutch Actuator) must have its own internal ECU for manoeuvring and error handling.StatementThe ECA (Electric Clutch Actuator) must have its own internal ECU for manoeuvring and error handling. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-3299216-1-0004 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0005 | The actuator will be controlled by a position and speed demand by CAN-busStatementThe actuator will be controlled by a position and speed demand by CAN-bus | None | None | None | None | RFQX-3299216-1-0005 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0006 | The actuator will be controlled by a position and speed demand by a 1kHz PWM signal on wake up connectionStatementThe actuator will be controlled by a position and speed demand by a 1kHz PWM signal on wake up connection | None | None | None | None | RFQX-3299216-1-0006 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0007 | The ECA units shall be manufactured with marking variants according to the requirements in Scania STD19 (Ref 14.17).StatementThe ECA units shall be manufactured with marking variants according to the requirements in Scania STD19 (Ref 14.17). The variant type shall be based on delivery agreement and Brand involved. Variant 1: For Scania units, wordmark variant C1 Part number (7 digits). Variant 2: For MAN units, wordmark variant Z1. Part number (13 digits). Variant 3: For International units, wordmark variant X1. Part number (8 digits) Variant 4 Tentik wordmark variant W. Part number (9 digits, two spaces in format: 12 345 6789). Common marking requirements that must be fulfilled for each marking variant are: Marking method: MA1 Marking height: 3 mm Date format: YYMMDD A unique serial number A DMC according to Scania STD 4562 (Ref 14.18) that contains the part number and serial number information. The marking shall not be visible when the ECA is mounted on a gearbox. The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0007 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0008 | The variant type shall be based on delivery agreement and Brand involved.StatementThe variant type shall be based on delivery agreement and Brand involved. | None | None | AD-008 | component | RFQX-3299216-1-0008 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0009 | Common marking requirements that must be fulfilled for each marking variant are: Marking method: MA1 Marking height: 3 mm Date format: YYMMDD A unique serial number A DMC according to Scania STD 4562 (Ref 14.18) that contains the part number and serial number information.StatementCommon marking requirements that must be fulfilled for each marking variant are: Marking method: MA1 Marking height: 3 mm Date format: YYMMDD A unique serial number A DMC according to Scania STD 4562 (Ref 14.18) that contains the part number and serial number information. | None | None | AD-008 | component | RFQX-3299216-1-0009 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0010 | The marking shall not be visible when the ECA is mounted on a gearbox.StatementThe marking shall not be visible when the ECA is mounted on a gearbox. | None | None | AD-008 | component | RFQX-3299216-1-0010 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0011 | The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible.StatementThe ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible. | None | None | AD-008 | component | RFQX-3299216-1-0011 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0012 | The rubber cover (See req.StatementThe rubber cover (See req. 4.16) shall be marked according to the requirements in Scania STD19 (Ref 14.17) Tentik, wordmark variant W Part number (9 digits, two spaces in format 12 345 6789) Marking method: CAS Marking height: 2-6 mm. Date dial: CVM. Alternative design: CXM or equivalent combination of date dial and date field The rubber cover marking shall not be visible when the ECA is mounted on a gearbox | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0012 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0013 | The ECA shall be designed with Remanufacturing and/or Refurbishment in mind with possibility of swapping out larger electronic assemblies/components.StatementThe ECA shall be designed with Remanufacturing and/or Refurbishment in mind with possibility of swapping out larger electronic assemblies/components. Details to be agreed with Traton | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0013 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0014 | The mechanics shall also be tested and verified, in an overall durability test as stated in Appendix B etc.StatementThe mechanics shall also be tested and verified, in an overall durability test as stated in Appendix B etc. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0014 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0015 | 4.16) shall be marked according to the requirements in Scania STD19 (Ref 14.17) Tentik, wordmark variant W Part number (9 digits, two spaces in format 12 345 6789) Marking method: CAS Marking height: 2-6 mm.Statement4.16) shall be marked according to the requirements in Scania STD19 (Ref 14.17) Tentik, wordmark variant W Part number (9 digits, two spaces in format 12 345 6789) Marking method: CAS Marking height: 2-6 mm. | None | None | AD-008 | component | RFQX-3299216-1-0015 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0016 | Details to be agreed with Traton 2.9 Traton shall be invited to participate in electrical and mechanical design reviews.StatementDetails to be agreed with Traton 2.9 Traton shall be invited to participate in electrical and mechanical design reviews. | None | None | AD-008 | component | RFQX-3299216-1-0016 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0017 | 2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification.Statement2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification. | None | None | AD-008 | component | RFQX-3299216-1-0017 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0018 | 2.12 Traton requires: - Documentation of the product, i.e.Statement2.12 Traton requires: - Documentation of the product, i.e. | None | None | AD-008 | component | RFQX-3299216-1-0018 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0019 | Should the PP be fully calculated from the AP-sensor, then this offset should not exist.StatementShould the PP be fully calculated from the AP-sensor, then this offset should not exist. | None | None | AD-006 | component | RFQX-3299216-1-0019 / 56h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0020 | The maximum release stroke is 22,4 mm from FCCPStatementThe maximum release stroke is 22,4 mm from FCCP | None | None | None | None | RFQX-3299216-1-0020 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0021 | The total stroke of the actuator shall be 85 mmStatementThe total stroke of the actuator shall be 85 mm | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0021 / 9h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0022 | The clutch actuator shall be able to reach the extreme positions A and B in with the center of the pushrod end.StatementThe clutch actuator shall be able to reach the extreme positions A and B in with the center of the pushrod end. Dimensions measured on the ECA. See Figure 3 - Pushrod positions. Figure 3 - Pushrod positions | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0022 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0023 | The gearbox flange designated to the ECA has three different surfaces, see Figure 5 Gearbox flange.StatementThe gearbox flange designated to the ECA has three different surfaces, see Figure 5 Gearbox flange. Surface A, which is machined pressure die cast aluminium that can act both as a heat source and heat sink for the ECA Surface B which is a raw pressure die casted surface. Surface C which is a rubber grommet, that does not require any different interface compared to the surrounding surface A. | None | None | None | None | RFQX-3299216-1-0023 / 8h | Not imported | Still Requires Customer Decision | No P1 link | evidence completeness | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0024 | When the ECA is assembled, it shall not be possible to insert an object larger than Ø0,2 mm (A wire could be used as test object) between the ECA and gearbox flange, so that the object enters the space behind the ECA.StatementWhen the ECA is assembled, it shall not be possible to insert an object larger than Ø0,2 mm (A wire could be used as test object) between the ECA and gearbox flange, so that the object enters the space behind the ECA. The rubber grommet at the lower part of the flange can have the same interface as the surrounding aluminum flange. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-3299216-1-0024 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0025 | When the ECA is assembled, a gap of 3,5 mm towards surface B with a profile tolerance of ±1 mm to the nominal dimensions shall be provided.StatementWhen the ECA is assembled, a gap of 3,5 mm towards surface B with a profile tolerance of ±1 mm to the nominal dimensions shall be provided. The surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0025 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0026 | The ECA shall be adapted for 6 pcs M8 flange screws described by Scania STD4435StatementThe ECA shall be adapted for 6 pcs M8 flange screws described by Scania STD4435 | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0026 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0027 | P 1 Page 4.4 ECA shall not interfere with any geometry in the 3D envelope -1 1_RFQ2030.stp except where interference fits or other types of functional contacts are required.StatementP 1 Page 4.4 ECA shall not interfere with any geometry in the 3D envelope -1 1_RFQ2030.stp except where interference fits or other types of functional contacts are required. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0027 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0028 | The surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm.StatementThe surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm. | None | None | AD-008 | component | RFQX-3299216-1-0028 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0029 | The ECA shall be adapted for 2 pcs 10 mm guide pins Figure 5 - Gearbox flangeStatementThe ECA shall be adapted for 2 pcs 10 mm guide pins Figure 5 - Gearbox flange | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0029 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0030 | The guide pin holes in the ECA shall be Ø 10,1±0.05 mm and at least 12 mm deep.StatementThe guide pin holes in the ECA shall be Ø 10,1±0.05 mm and at least 12 mm deep. The holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing. Both depths measured from the center of the oval hole in the Gearbox/ECA flange. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0030 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0031 | The ECA shall be able to be held by the guide pins only while being exposed to the max clutch load, (req.StatementThe ECA shall be able to be held by the guide pins only while being exposed to the max clutch load, (req. 4.22) up to 50 times. The clutch load will be removed and the screw interface tightened between every load occasion. Surface indents in the contacts are allowed as long as the structural integrity is unaffected | SSR-DAI-002 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-005 | interface | RFQX-3299216-1-0031 / 16h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0032 | The pushrod end that makes contact with the clutch lever shall be a Ø15,93±0,07 mm steel sphere.StatementThe pushrod end that makes contact with the clutch lever shall be a Ø15,93±0,07 mm steel sphere. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0032 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0033 | It shall be possible to pull the pushrod 50 times with a force of 300 N without risk for it to come loose from the ECA.StatementIt shall be possible to pull the pushrod 50 times with a force of 300 N without risk for it to come loose from the ECA. Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-3299216-1-0033 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0034 | The ECA shall allow space for external tools according to the cylinders in the 3D envelope attached.StatementThe ECA shall allow space for external tools according to the cylinders in the 3D envelope attached. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0034 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0035 | The ECA shall have a window where the volume shown in Figure 6 – Snap in tool space, could pass through(See req.StatementThe ECA shall have a window where the volume shown in Figure 6 – Snap in tool space, could pass through(See req. 4.4). | SSR-TOOL-001 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-004 | component | RFQX-3299216-1-0035 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0036 | The ECA shall provide a support for a clutch snap in tool on the marked surface in Figure 4 ISO view of 3D envelope.StatementThe ECA shall provide a support for a clutch snap in tool on the marked surface in Figure 4 ISO view of 3D envelope. The maximum force is 1kN. Surface indents are allowed as long as it does not affect other requirements or the structural integrity of the ECA. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-3299216-1-0036 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0037 | The holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing.StatementThe holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing. | None | None | AD-008 | component | RFQX-3299216-1-0037 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0038 | Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand.StatementAlternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. | None | None | AD-002 | component | RFQX-3299216-1-0038 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0039 | The hole shall be equipped with a cover possible to assemble and disassemble at least 50 times without tools.StatementThe hole shall be equipped with a cover possible to assemble and disassemble at least 50 times without tools. If an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature. It shall still remain intac t and keep tightness after vibration testing (See req.10.5) | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0039 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0040 | When the cover is assembled it shall not be possible to insert an object larger than Ø0,2 mm into the gearbox housing between the cover and ECA.StatementWhen the cover is assembled it shall not be possible to insert an object larger than Ø0,2 mm into the gearbox housing between the cover and ECA. A wire could be used as test object. Figure 6 - Snap in tool space | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0040 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0041 | The ECA shall have a loop or similar feature where the cable can be fixated with a cable tie Optionally an M8 screw thread and rotation stop for a sheet metal bracket indicated in Figure 4 - ISO view of 3D envelope, can be provided.StatementThe ECA shall have a loop or similar feature where the cable can be fixated with a cable tie Optionally an M8 screw thread and rotation stop for a sheet metal bracket indicated in Figure 4 - ISO view of 3D envelope, can be provided. The loop or Scania assembled bracket shall be located close to the centre ( ± 20 mm) of the cable section between the connector and last cable fixation point on the gearbox | SSR-COM-005 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-006 | component | RFQX-3299216-1-0041 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0042 | The connector for communication and power shall be positioned as indicated in Figure 4 ISO view of 3D envelope, when connected.StatementThe connector for communication and power shall be positioned as indicated in Figure 4 ISO view of 3D envelope, when connected. Details regarding actual length and positioning tolerances shall be agreed in design phase. | SSR-COM-005 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-006 | component | RFQX-3299216-1-0042 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0043 | If the ECA is powered up with the PP in the utmost forward position (for example when not connected to the clutch lever) it shall move AP to its utmost reversed position.StatementIf the ECA is powered up with the PP in the utmost forward position (for example when not connected to the clutch lever) it shall move AP to its utmost reversed position. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0043 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0044 | If an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature.StatementIf an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature. | None | None | AD-008 | component | RFQX-3299216-1-0044 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0045 | Details regarding actual length and positioning tolerances shall be agreed in design phase.StatementDetails regarding actual length and positioning tolerances shall be agreed in design phase. | None | None | AD-008 | component | RFQX-3299216-1-0045 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0046 | The clutch force acting on the pushrod is defined in Appendix AStatementThe clutch force acting on the pushrod is defined in Appendix A | None | None | None | None | RFQX-3299216-1-0046 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0047 | The actuator shall apply a preload force for the release bearing.StatementThe actuator shall apply a preload force for the release bearing. The preload force measured on the push rod shall be 150N to 250N independent of the clutch position | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0047 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0048 | The pushrod position when clutch is at rest and only preload force is applied, will vary randomly within 2 mm (± 1mm from FCCP).StatementThe pushrod position when clutch is at rest and only preload force is applied, will vary randomly within 2 mm (± 1mm from FCCP). | None | None | None | None | RFQX-3299216-1-0048 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0049 | It must be possible to assemble the actuator independent of the lever position without any power connection.StatementIt must be possible to assemble the actuator independent of the lever position without any power connection. This means that the push rod shall be possible to move by hand. Maximum force allowed is 300N. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0049 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0050 | This means that the push rod shall be possible to move by hand.StatementThis means that the push rod shall be possible to move by hand. | None | None | AD-008 | component | RFQX-3299216-1-0050 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0051 | 4.26 When the clutch is fully engaged, the active control mode is position or torque control mode and there is no active request to extract the pushrod (clutch opening motion), the ECA shall not apply a force outside of limits in preload force defined in req.Statement4.26 When the clutch is fully engaged, the active control mode is position or torque control mode and there is no active request to extract the pushrod (clutch opening motion), the ECA shall not apply a force outside of limits in preload force defined in req. | None | None | AD-008 | component | RFQX-3299216-1-0051 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0052 | P 1 Page 5 Clutch engage and disengage 5.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to ,and max speed set to 125mm/s (seeStatementP 1 Page 5 Clutch engage and disengage 5.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to ,and max speed set to 125mm/s (see | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0052 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0053 | ) Time is measured according to Figure 7 – Max disengage time, where the dashed line is the position request as it becomes available on the CAN bus, and the full line is the actual PP.Statement) Time is measured according to Figure 7 – Max disengage time, where the dashed line is the position request as it becomes available on the CAN bus, and the full line is the actual PP. | None | None | None | None | RFQX-3299216-1-0053 / 19h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0054 | This shall be measured against the maximum disengage force (See Appendix A) Figure 7 – Maximum disengage timeStatementThis shall be measured against the maximum disengage force (See Appendix A) Figure 7 – Maximum disengage time | None | None | AD-008 | component | RFQX-3299216-1-0054 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0055 | P 1 Page 5.2 It shall be possible to engage the clutch in 180ms (=Ts) with accuracy according to re q.5.10, and the max speed set to 125mm/s (see ).StatementP 1 Page 5.2 It shall be possible to engage the clutch in 180ms (=Ts) with accuracy according to re q.5.10, and the max speed set to 125mm/s (see ). | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0055 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0056 | This shall be measured against the minimum engage force (See Appendix A) Figure 8 - Maximum engage timeStatementThis shall be measured against the minimum engage force (See Appendix A) Figure 8 - Maximum engage time | None | None | AD-008 | component | RFQX-3299216-1-0056 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0057 | The clutch actuator shall report the absolute position of the current actuator stroke (AP) (Ref 14.14).StatementThe clutch actuator shall report the absolute position of the current actuator stroke (AP) (Ref 14.14). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0057 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0058 | It shall also report the position that corresponds to a fully closed clutch position (FCCP), expressed in absolute position of the actuator stroke and relative to the absolute zero position (See req.StatementIt shall also report the position that corresponds to a fully closed clutch position (FCCP), expressed in absolute position of the actuator stroke and relative to the absolute zero position (See req. 6.5). | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0058 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0059 | The clutch actuator shall be equipped with a displacement sensor measuring the movement of the push rod, (Ref 14.14)StatementThe clutch actuator shall be equipped with a displacement sensor measuring the movement of the push rod, (Ref 14.14) | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-3299216-1-0059 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0060 | The actuator must be able to determine the pushrod position according to the following Accuracy (maximum difference between measured pushrod position and actual pushrod position): +/- 1.6mm.StatementThe actuator must be able to determine the pushrod position according to the following Accuracy (maximum difference between measured pushrod position and actual pushrod position): +/- 1.6mm. Resolution (smallest discernible unit of change along the X axis): 0.0125mm. Repeatability (maximum variation between measurements at the same position and in the same unit, with equal environmental conditions): +/- 0.1mm. Range: 85mm (AP) | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0060 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0061 | For each stroke that the actuator performs it shall adjust to the current wear of the clutch.StatementFor each stroke that the actuator performs it shall adjust to the current wear of the clutch. This means that is shall be possible to request a relative stroke from the fully closed clutch position and achieve the step accuracy as defined in req. 5.10. The implementation can be either a pure mechanical solution or it can be implemented using a software based solution. | SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-001 | component | RFQX-3299216-1-0061 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0062 | The maximum stationary position error relative to real FCCP (i e self-adjustment error + step response error) shall be ±0.15mm.StatementThe maximum stationary position error relative to real FCCP (i e self-adjustment error + step response error) shall be ±0.15mm. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0062 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0063 | This means that is shall be possible to request a relative stroke from the fully closed clutch position and achieve the step accuracy as defined in req.StatementThis means that is shall be possible to request a relative stroke from the fully closed clutch position and achieve the step accuracy as defined in req. | None | None | AD-008 | component | RFQX-3299216-1-0063 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0064 | The FCCP after a clutch engage shall be updated to 90% of the step within 0,2 s per mm that the FCCP have changed during the stroke.StatementThe FCCP after a clutch engage shall be updated to 90% of the step within 0,2 s per mm that the FCCP have changed during the stroke. | None | None | AD-008 | component | RFQX-3299216-1-0064 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0065 | P 1 Page 5.10 The actuator shall move the pushrod according to the following points: Actuator maximum speed: The maximum achievable speed of the pushrod shall be at least 125 mm/s.StatementP 1 Page 5.10 The actuator shall move the pushrod according to the following points: Actuator maximum speed: The maximum achievable speed of the pushrod shall be at least 125 mm/s. | None | None | AD-008 | component | RFQX-3299216-1-0065 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0066 | The actuator shall move the pushrod at the highest possible speed, limited only by its maximum achievable speed and the maximum speed request.StatementThe actuator shall move the pushrod at the highest possible speed, limited only by its maximum achievable speed and the maximum speed request. | None | None | AD-008 | component | RFQX-3299216-1-0066 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0067 | 6.4) Dynamics start of movement: The requested speed (or 125mm/s, if requested speed > 125mm/s) shall be achieved within 50ms from when a new value for requested position is sent.Statement6.4) Dynamics start of movement: The requested speed (or 125mm/s, if requested speed > 125mm/s) shall be achieved within 50ms from when a new value for requested position is sent. | None | None | AD-008 | component | RFQX-3299216-1-0067 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0068 | Dynamics end of movement: The requested speed shall be kept until 2 mm from the target position.StatementDynamics end of movement: The requested speed shall be kept until 2 mm from the target position. | None | None | AD-008 | component | RFQX-3299216-1-0068 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0069 | 100ms after reaching 2 mm from target, the maximum position error should be ±0.1mm.Statement100ms after reaching 2 mm from target, the maximum position error should be ±0.1mm. | None | None | AD-008 | component | RFQX-3299216-1-0069 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | MISSING SYSTEM REQUIREMENT |
| RFQX-3299216-1-0070 | Maximum overshoot is 0.2 mm When a new position is requested, but the stroke is too short to reach requested speed, the ECA shall complete the stroke in minimum time with dynamic in compliance with the , 5.2 and this section.StatementMaximum overshoot is 0.2 mm When a new position is requested, but the stroke is too short to reach requested speed, the ECA shall complete the stroke in minimum time with dynamic in compliance with the , 5.2 and this section. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-3299216-1-0070 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0071 | Req.StatementReq. 5.10 shall be tested with a step response test cycle, according to description and Figure 10 - Step response test cycle. Step from FCCP to 0.5x fully open position Wait 2 seconds Step to fully open position Wait 2 seconds Step to 0.5x fully open position Wait 2 seconds Step to FCCP Figure 10 - Step response test cycle | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0071 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0072 | 5.10 shall be tested with a step response test cycle, according to description and Figure 10 - Step response test cycle.Statement5.10 shall be tested with a step response test cycle, according to description and Figure 10 - Step response test cycle. | None | None | AD-008 | component | RFQX-3299216-1-0072 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0073 | P 1 Page 5.12 The ECA shall be able to run the 4 second test cycle in Figure 11 - Release frequency test continuously for 5 hours without any degradation or failure.StatementP 1 Page 5.12 The ECA shall be able to run the 4 second test cycle in Figure 11 - Release frequency test continuously for 5 hours without any degradation or failure. | None | None | AD-008 | component | RFQX-3299216-1-0073 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0074 | The test shall be done with the highest operating temperature (see ) and maximum clutch force (See Appendix A) Figure 11 - Release frequency testStatementThe test shall be done with the highest operating temperature (see ) and maximum clutch force (See Appendix A) Figure 11 - Release frequency test | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0074 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0075 | It shall be possible to keep the clutch disengaged continuously without risk of loss of function for 120 min.StatementIt shall be possible to keep the clutch disengaged continuously without risk of loss of function for 120 min. This shall be measured against the maximum disengage force (Appendix A) and an highest operating temperature (see req. 8.1). | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-3299216-1-0075 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0076 | Between 16V and loss of power the ECA shall hold its current position or move towards requested position without any time requirement.StatementBetween 16V and loss of power the ECA shall hold its current position or move towards requested position without any time requirement. | None | None | AD-008 | component | RFQX-3299216-1-0076 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0077 | The strategy shall be disc ussed and approved with Traton.StatementThe strategy shall be disc ussed and approved with Traton. | None | None | AD-008 | component | RFQX-3299216-1-0077 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0078 | This shall be measured against the maximum disengage force (Appendix A) and an highest operating temperature (see req.StatementThis shall be measured against the maximum disengage force (Appendix A) and an highest operating temperature (see req. | None | None | AD-008 | component | RFQX-3299216-1-0078 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0079 | The ECA will be controlled by messages on the CAN bus and by the PWM signal specified in req.StatementThe ECA will be controlled by messages on the CAN bus and by the PWM signal specified in req. 7.24-7.33. The CAN communication messages are specified in PD2497100 (Ref 14.14). It shall be followed to its full extent. If needed, some messages might be complemented with additional checksums and message counters | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-3299216-1-0079 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0080 | Control modeStatementReq. 6.3.1 to 6.3.5 describe the various control modes that can be requested via CAN (Ref 14.14) | None | None | None | None | RFQX-3299216-1-0080 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0081 | P 1 Page 6 SW functionality 6.1 TB4684 shall be applied.StatementP 1 Page 6 SW functionality 6.1 TB4684 shall be applied. | None | None | AD-008 | component | RFQX-3299216-1-0081 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0082 | It shall be followed to its full extent.StatementIt shall be followed to its full extent. | None | None | AD-002 | component | RFQX-3299216-1-0082 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0083 | Description Mode Name EnomStatementWhen requesting Absolute Position Control the actuator shall move to the actuator position defined by the Requested Position (RP). The RP can in this mode correspond to the full wear travel of the clutch (see req. 4.3) It is allowed to control movement to protect the ECA and clutch from hardware damage. Specific cases shall be approved with Traton. Control mode Absolute position 0x01 | SSR-COM-005 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-006 | component | RFQX-3299216-1-0083 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0084 | When requesting Relative PositionStatementControl (RPC) the actuator shall move to an offset that corresponds to the Requested Position from the Fully Closed Clutch Position (FCCP). The RP can be up to a full Release Travel (22,4 mm) in this mode. How the FCCP can be identified is described in 6.5. When RP = 0 the actuator is allowed to have a position that is less than the FCCP but not more, since this would open the clutch. Control mode Relative position 0x02 | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0084 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0085 | When requesting Absolute Position Control the actuator shall move to the actuator position defined by the Requested Position (RP).StatementWhen requesting Absolute Position Control the actuator shall move to the actuator position defined by the Requested Position (RP). | None | None | AD-008 | component | RFQX-3299216-1-0085 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0086 | Specific cases shall be approved with Traton.StatementSpecific cases shall be approved with Traton. | None | None | AD-008 | component | RFQX-3299216-1-0086 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0087 | Control mode Relative position 0x02 6.3.3 When requesting Torque Control (TC) the actuator shall actuate the requested motor torque.StatementControl mode Relative position 0x02 6.3.3 When requesting Torque Control (TC) the actuator shall actuate the requested motor torque. | None | None | AD-008 | component | RFQX-3299216-1-0087 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0088 | Maximum speedStatementA maximum allowed speed of the actuator is sent as a separate signal on CAN. If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-3299216-1-0088 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0089 | No update of the FCCP is allowedStatementThe value shall be frozen at the last identified position and used for RPC. Self-adjustment disabled 0x3 | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0089 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0090 | 6.3.4 When requesting Test Mode, the actuator shall perform tests to detect latent faults.Statement6.3.4 When requesting Test Mode, the actuator shall perform tests to detect latent faults. | None | None | AD-008 | component | RFQX-3299216-1-0090 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0091 | ECA behavior and additional requirements for this mode can be found in (Ref 14.16) Control mode Test mode 0x04 6.3.5 When this Control Mode is sent the actuator shall behave as if the power supply was cut with aspect to control of the actuator.StatementECA behavior and additional requirements for this mode can be found in (Ref 14.16) Control mode Test mode 0x04 6.3.5 When this Control Mode is sent the actuator shall behave as if the power supply was cut with aspect to control of the actuator. | None | None | AD-005 | interface | RFQX-3299216-1-0091 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0092 | CAN communication shall still be active.StatementCAN communication shall still be active. | None | None | AD-005 | interface | RFQX-3299216-1-0092 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0093 | If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit.StatementIf the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit. | None | None | AD-002 | component | RFQX-3299216-1-0093 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0094 | 6.5 Self-adjustment The self-adjustment signal defines the restrictions of how the FCCP shall be identified.Statement6.5 Self-adjustment The self-adjustment signal defines the restrictions of how the FCCP shall be identified. | None | None | AD-005 | interface | RFQX-3299216-1-0094 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0095 | ).Statement). | None | None | None | None | RFQX-3299216-1-0095 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0096 | The value of the FCCP shall be reported via CAN(Ref 14.14) Req.StatementThe value of the FCCP shall be reported via CAN(Ref 14.14) Req. | None | None | AD-005 | interface | RFQX-3299216-1-0096 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0097 | The value shall be frozen at the last identified position and used for RPC.StatementThe value shall be frozen at the last identified position and used for RPC. | None | None | AD-008 | component | RFQX-3299216-1-0097 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0098 | Accuracy modeStatementAccuracy mode | None | None | None | None | RFQX-3299216-1-0098 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0099 | Vehicle identification number(VINStatementNot applicable. | None | None | None | None | RFQX-3299216-1-0099 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0100 | FeedbackStatementFeedback from the ECA will also be sent via CAN. Specific error reporting as per req. 6.13. Message contents to be agreed with Traton | None | None | None | None | RFQX-3299216-1-0100 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0101 | ECA identification numberStatementThe ECA shall report a unique ECA individual identification number | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0101 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0102 | Supplier codeStatementThe ECA shall report supplier code 5 via CAN. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0102 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0103 | SW numberStatementThe ECA shall report a complete SW version number. The number is decided by the supplier and can be in the range 0-64255. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0103 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0104 | HW numberStatementThe ECA shall report a complete HW version number. The number is decided by the supplier and can be in the range 0-64255. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0104 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0105 | System stateStatementThe ECA shall report its current System State. Valid states are explained in requirements 6.14.1 - 6.14.9. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0105 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0106 | 6.6.1 When low accuracy mode is requested, the maximum push rod position(PP) error can be ±0.5mm Accuracy mode Low accuracy 0x0 6.6.2 Accuracy according to 5.10 shall be fulfilled.Statement6.6.1 When low accuracy mode is requested, the maximum push rod position(PP) error can be ±0.5mm Accuracy mode Low accuracy 0x0 6.6.2 Accuracy according to 5.10 shall be fulfilled. | None | None | AD-005 | interface | RFQX-3299216-1-0106 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0107 | 6.13 Error State Diagnostic - ESD and Error State Action - ESA The ECA shall send a bit field via CAN containing errors present Additionally, see ,Statement6.13 Error State Diagnostic - ESD and Error State Action - ESA The ECA shall send a bit field via CAN containing errors present Additionally, see , | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-3299216-1-0107 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0108 | ,req.Statement,req. | None | None | None | None | RFQX-3299216-1-0108 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0109 | ESA definition( Ref 14.16) The supplier shall provide documentation for the ESD bits and related faults .StatementESA definition( Ref 14.16) The supplier shall provide documentation for the ESD bits and related faults . | None | None | AD-008 | component | RFQX-3299216-1-0109 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0110 | Absolute Position ControlStatementThis value shall be sent when the ECA is actuating Absolute Position Control. 0x1 | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0110 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0111 | Relative Position ControlStatementThis value shall be sent when the ECA is actuating Relative Position Control. 0x2 | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0111 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0112 | Torque ControlStatementThis value shall be sent when the ECA is actuating Torque Control. The torque being controlled is the torque of the motor. 0x4 | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0112 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0113 | Self-AdjustmentStatementThis value shall be sent when the ECA is performing a Self-Adjustment procedure that is not part of a RPC or TC request (i.e. passing FCCP). 0x5 | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0113 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0114 | InitializingStatementThis value shall be sent when the ECA is performing its initiation routine and is not yet available for control. 0xA | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0114 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0115 | Debug / TestStatementThis value shall be sent when the actuator is in debug or test control state. 0xC | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0115 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0116 | Motor Brake SimulationStatementThis value shall be sent when the actuator is performing a motor brake simulation. 0xD | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0116 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0117 | 6.14.1 Boot Mode If the actuator is in boot mode, 0x00 shall be reported as active state.Statement6.14.1 Boot Mode If the actuator is in boot mode, 0x00 shall be reported as active state. | None | None | AD-008 | component | RFQX-3299216-1-0117 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0118 | 0xA 6.14.7 Shut down This value shall be sent when the ECA is performing its shut down routing and is not available for control.Statement0xA 6.14.7 Shut down This value shall be sent when the ECA is performing its shut down routing and is not available for control. | None | None | AD-008 | component | RFQX-3299216-1-0118 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0119 | System TemperatureStatementThe ECA shall report the current system temperature.(Ref 14.14) | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0119 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0120 | Torque FeedbackStatementThe ECA shall calculate and report the actuator motor torque. (Ref 14.14) | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0120 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0121 | Current feedbackStatementThe ECA shall report the current for each phase of the actuator. These values shall be calculated using a moving mean filter. The filter time shall equal the update frequency . (Ref 14.14) | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0121 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0122 | Supply Voltage FeedbackStatementThe ECA shall report the current system voltage. (input voltage) (Ref 14.14) | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0122 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0123 | Operational hoursStatementThe ECA shall store and report its accumulated operational hours. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0123 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0124 | Total travelled lengthStatementThe ECA shall report its accumulated lifetime travel length. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0124 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0125 | DiagnosisStatementCVS120 shall be applied (Ref 14.12). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0125 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0126 | Cyber SecurityStatementCybersecurity shall be considered through a separate process with the latest Traton workflow in mind. The following apply: Mandatory: TRATON secure updates - CVS31,CVS32,CVS123-2,CVS154 TRATON secure diagnostics - CVS31,CVS32,CVS151 TRATON Specification on Unified diagnostic Services CVS124 Other applicable documents considered as supporting specifications: CVS30, CVS33, CVS34,CVS121,CVS122,SecureBoot,Vehicle Baseline Requirements, ECU Baseline Requirements Additional standards/documents will be made available, if applicable. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-3299216-1-0126 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0127 | Minimum diagnostic feedbackStatementMinimum diagnostic feedback described in req. 6.22.1 - 6.22.11. | None | None | None | None | RFQX-3299216-1-0127 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0128 | Wrong rotation directionStatementWrong rotation direction | None | None | None | None | RFQX-3299216-1-0128 / 56h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0129 | Short circuit / open load on the phasesStatementShort circuit / open load on the phases | None | None | None | None | RFQX-3299216-1-0129 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0130 | Motor rotation feedback, short circuit / open loadStatementMotor rotation feedback, short circuit / open load | None | None | None | None | RFQX-3299216-1-0130 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0131 | These values shall be calculated using a moving mean filter.StatementThese values shall be calculated using a moving mean filter. | None | None | AD-008 | component | RFQX-3299216-1-0131 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0132 | The filter time shall equal the update frequency .StatementThe filter time shall equal the update frequency . | None | None | AD-008 | component | RFQX-3299216-1-0132 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0134 | Validation and InvalidationStatementThe reported ESD must be able to be validated and invalidated. | SSR-VV-001 | Security evidence and traceability — Verification and Validation | AD-008 | component | RFQX-3299216-1-0134 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0135 | Diagnosis trackingStatementThe gearbox control unit(TCU) shall be responsible for setting DTCs based on received notifications from ECA via ESD, including time-stamps, occurrence counters etc. One unique DTC will be set per bit in the ESD signal. If higher resolution is required for the supplier to properly troubleshoot any individual occurrence, then the ECA is responsible for storing these parameters internally. Internally stored parameters may be accessible only using supplier defined tools . | SSR-DIAG-001 | Diagnostic Services — Diagnostic Services | AD-005 | interface | RFQX-3299216-1-0135 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0136 | Data loggingStatementAny data logged or stored shall be agreed upon together with Traton. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0136 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0137 | Data storageStatementWhen storing data in the device, the supplier shall take measures to prevent corruption of data which can occur for example when suffering power loss during read or write cycles. The supplier shall also ensure that systems are in place that ensure that data corruption is handled without loss of data, or loss of function. This could be designed with for example data mirroring. It is acceptable if purely statistical data (e.g. operation hours) from the active operation cycle is not stored in case of an abnormal shutdown. | SSR-COM-008 | OEM/Customer Review Interface — Secure Communication and Boundary Control | AD-001 | component | RFQX-3299216-1-0137 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0138 | CalibrationStatementThere shall only be one calibration set of the ECA that is delivered to Traton, i.e, the calibration shall not be dependent of installation variants. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0138 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0139 | ResetStatementIt shall be possible to reset the ECA application with a power off/on cycle after all functional safety events. Handling to be agreed with Traton. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-3299216-1-0139 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0140 | If higher resolution is required for the supplier to properly troubleshoot any individual occurrence, then the ECA is responsible for storing these parameters internally.StatementIf higher resolution is required for the supplier to properly troubleshoot any individual occurrence, then the ECA is responsible for storing these parameters internally. | None | None | AD-008 | component | RFQX-3299216-1-0140 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0141 | Internally stored parameters may be accessible only using supplier defined tools .StatementInternally stored parameters may be accessible only using supplier defined tools . | None | None | None | None | RFQX-3299216-1-0141 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0142 | The supplier shall also ensure that systems are in place that ensure that data corruption is handled without loss of data, or loss of function.StatementThe supplier shall also ensure that systems are in place that ensure that data corruption is handled without loss of data, or loss of function. | None | None | AD-001 | component | RFQX-3299216-1-0142 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0143 | The electrical design must ensure that an internal short circuit through one of H -bridges (“shoot through”) is avoided.StatementThe electrical design must ensure that an internal short circuit through one of H -bridges (“shoot through”) is avoided. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0143 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0144 | A safe boot sequence must be set to prevent unwanted or undefined behavior during or after loss of power, or corruption of stored data.StatementA safe boot sequence must be set to prevent unwanted or undefined behavior during or after loss of power, or corruption of stored data. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0144 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0145 | A safe memory read/write sequence must also be implemented during actuator movement, in order to ensure safe and predictable behavior during operation, or in case of power lo ss.StatementA safe memory read/write sequence must also be implemented during actuator movement, in order to ensure safe and predictable behavior during operation, or in case of power lo ss. Relates to Safety Goals set in PD3339794 (Ref 14.16). | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-3299216-1-0145 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0146 | All external electrical connectors shall be geometrically coded.StatementAll external electrical connectors shall be geometrically coded. If internal components are included in repair kits, the internal electrical connectors shall also be geometrically coded. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0146 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0147 | ECA power and communication connectorStatement2*6.3mm (MCP) 6*2.8mm (MCP) Code A TE part no.: 1-2299782-1 Pin list with: Pin distribution, Pin size (see req. 7.41) | None | None | None | None | RFQX-3299216-1-0147 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0148 | 7.2 Short circuit protection shall be implemented by hardware.Statement7.2 Short circuit protection shall be implemented by hardware. | None | None | AD-006 | component | RFQX-3299216-1-0148 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0149 | If internal components are included in repair kits, the internal electrical connectors shall also be geometrically coded.StatementIf internal components are included in repair kits, the internal electrical connectors shall also be geometrically coded. | None | None | AD-008 | component | RFQX-3299216-1-0149 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0150 | 7.8 ECU tab headers shall comply with TB1787.(Ref 14.6) 7.9 ECU tab headers shall be made of self-extinguishing materials (i.e.Statement7.8 ECU tab headers shall comply with TB1787.(Ref 14.6) 7.9 ECU tab headers shall be made of self-extinguishing materials (i.e. | None | None | AD-006 | component | RFQX-3299216-1-0150 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0151 | 6.3mm Tin, Sn ≥3 μm thick.Statement6.3mm Tin, Sn ≥3 μm thick. ≥1 µm Ni | None | None | None | None | RFQX-3299216-1-0151 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0152 | 2.8mm Gold, Au ≥0,8 μm thick.Statement2.8mm Gold, Au ≥0,8 μm thick. ≥1 µm Ni | None | None | None | None | RFQX-3299216-1-0152 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0153 | The ECA can be connected to the battery+ (30) permanently through the system fuse or through a master switch that physically cuts off power.StatementThe ECA can be connected to the battery+ (30) permanently through the system fuse or through a master switch that physically cuts off power. All power used by the ECA shall be taken from this battery connection. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0153 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0154 | The ECA is connected directly to the battery GND (31).StatementThe ECA is connected directly to the battery GND (31). This ground connection will act as system ground and reference for the entire ECA. The ground shall not be DC connected to the ECA housing. Requirements Power cable dimension: Operating parameters Remark Min Typ. Max. Unit | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0154 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0155 | Power cable length: - - 2*6000 mmStatementPower cable length: - - 2*6000 mm | None | None | None | None | RFQX-3299216-1-0155 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0156 | System fuse: - 601|2StatementA 1. According to ISO 8820-5:2015 SF30 type fuse-links. 2. According to ISO 8820-5:2015 SF51 type fuse-links. | None | None | None | None | RFQX-3299216-1-0156 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0157 | Umax: - - 32/36/48 A Specific test relations TBDStatementUmax: - - 32/36/48 A Specific test relations TBD | None | None | None | None | RFQX-3299216-1-0157 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0158 | Umin: 16 - - VStatementCVS41 limits may go below this value. Valid only for ECU and communication function. For clutch actuation see req. 5.13 | None | None | None | None | RFQX-3299216-1-0158 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0159 | Peak current (Ipeak): - - SeeStatementFigure 133 A 3. Up to 100 kHz | None | None | None | None | RFQX-3299216-1-0159 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0160 | All power used by the ECA shall be taken from this battery connection.StatementAll power used by the ECA shall be taken from this battery connection. | None | None | AD-008 | component | RFQX-3299216-1-0160 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0161 | The ground shall not be DC connected to the ECA housing.StatementThe ground shall not be DC connected to the ECA housing. | None | None | AD-008 | component | RFQX-3299216-1-0161 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0162 | 7.23 Quiescent current: According to CVS41 (Ref 14.2), must be met independent of input and output conditions.Statement7.23 Quiescent current: According to CVS41 (Ref 14.2), must be met independent of input and output conditions. | None | None | AD-008 | component | RFQX-3299216-1-0162 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0163 | It shall be used to control the power up sequence to the µP.StatementIt shall be used to control the power up sequence to the µP. | None | None | AD-002 | component | RFQX-3299216-1-0163 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0164 | The Wake-up signal shall also be connected to a digital input on the µP.StatementThe Wake-up signal shall also be connected to a digital input on the µP. | None | None | AD-005 | interface | RFQX-3299216-1-0164 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0165 | Special precautions shall be taken to prevent direct connection between Wake-up and 30 in case of a single failure.StatementSpecial precautions shall be taken to prevent direct connection between Wake-up and 30 in case of a single failure. | None | None | AD-008 | component | RFQX-3299216-1-0165 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0166 | After the wake-up line goes to high state: The ECA shall communicate on the CAN line within 250ms in case of a normal start -up The ECA shall be ready to open the clutch within 350ms in case of a normal start -up The ECA shall be ready to open the clutch as soon as possible after necessary movements in case of an abnormal start-up.StatementAfter the wake-up line goes to high state: The ECA shall communicate on the CAN line within 250ms in case of a normal start -up The ECA shall be ready to open the clutch within 350ms in case of a normal start -up The ECA shall be ready to open the clutch as soon as possible after necessary movements in case of an abnormal start-up. | None | None | AD-005 | interface | RFQX-3299216-1-0166 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0167 | After movement and reset, the ECA shall communicate on the CAN line within 250ms After movement and reset, the ECA shall be ready to open the clutch within 400ms In the case if the wake-up goes "high" at the same time as U30 signal the ECA should be ready to open the clutch within 3 seconds.StatementAfter movement and reset, the ECA shall communicate on the CAN line within 250ms After movement and reset, the ECA shall be ready to open the clutch within 400ms In the case if the wake-up goes "high" at the same time as U30 signal the ECA should be ready to open the clutch within 3 seconds. | None | None | AD-005 | interface | RFQX-3299216-1-0167 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0168 | Definition ready to open clutch: The actuator position shall be between FCCP and FCCP -3mm and the ECA is capable to move to disengaged clutch directly when requeste d.StatementDefinition ready to open clutch: The actuator position shall be between FCCP and FCCP -3mm and the ECA is capable to move to disengaged clutch directly when requeste d. | None | None | AD-008 | component | RFQX-3299216-1-0168 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0169 | Redundancies due improper shutdown shall be aligned with Traton.StatementRedundancies due improper shutdown shall be aligned with Traton. | None | None | AD-008 | component | RFQX-3299216-1-0169 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0170 | If a signal for disengaging the clutch is received the ECA shall actuate the request regardless of CAN-request.StatementIf a signal for disengaging the clutch is received the ECA shall actuate the request regardless of CAN-request. | None | None | AD-005 | interface | RFQX-3299216-1-0170 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0171 | The ECA has one CAN bus.StatementThe ECA has one CAN bus. Any watchdog circuit shall have no influence on the CAN bus The CAN front end shall be designed to comply with TB1905 (Ref 14.3), with the following additional information in this chapter. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0171 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0172 | The controller and transceiver shall be CAN FD ready Parameter Limit values Unit Remarks Min.StatementThe controller and transceiver shall be CAN FD ready Parameter Limit values Unit Remarks Min. Typ. Max. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0172 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0173 | Baud rate forStatementCAN FD: 4000 - - kbit/s Figure 15 - Reference circuit | None | None | None | None | RFQX-3299216-1-0173 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0174 | Any watchdog circuit shall have no influence on the CAN bus.StatementAny watchdog circuit shall have no influence on the CAN bus. | None | None | AD-005 | interface | RFQX-3299216-1-0174 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0175 | The CAN front end shall be designed to comply with TB1905 (Ref 14.3), with the following additional information in this chapter.StatementThe CAN front end shall be designed to comply with TB1905 (Ref 14.3), with the following additional information in this chapter. | None | None | AD-005 | interface | RFQX-3299216-1-0175 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0176 | 7.36 Termination resistance: - 2 x 60 - Ω 1% resistors shall be used 7.37 Baud rate: 250 500 1000 kbit/s Flashing in production shall be possible with 1000kbit/s.Statement7.36 Termination resistance: - 2 x 60 - Ω 1% resistors shall be used 7.37 Baud rate: 250 500 1000 kbit/s Flashing in production shall be possible with 1000kbit/s. | None | None | AD-008 | component | RFQX-3299216-1-0176 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0177 | NoteStatementThe layout shall always be present on the PCB and the supplier must be flexible in changing/removing the CAN related components in this section. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0177 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0178 | CAN_ShieldStatementCAN shield. Footprint prepared for internal connection to system ground 31_ECA via a resistor and a capacitor in series. The components shall not be populated by default. The CAN front end shall be designed to comply with TB1905. (Ref 14.3) | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-3299216-1-0178 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0179 | The components shall not be populated by default.StatementThe components shall not be populated by default. | None | None | AD-008 | component | RFQX-3299216-1-0179 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0180 | The CAN front end shall be designed to comply with TB1905.StatementThe CAN front end shall be designed to comply with TB1905. | None | None | AD-005 | interface | RFQX-3299216-1-0180 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0181 | VentilationStatementThe air inside the electronics enclosure shall be ventilated with the use of a membrane. The following requirements shall be fulfilled: The unit shall withstand the salt-spray environment, according to CVS40 §6.1.6, without clogging of the membrane. The membrane shall be placed so that it is protected against blunt force, falling dust and dripping salt-water. The design shall be made to prevent accumulation of water on top of the membrane, or in the cavity of the membrane. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0181 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0182 | The quality of the wire bonding and position shall be properly analyzed.StatementThe quality of the wire bonding and position shall be properly analyzed. | None | None | AD-008 | component | RFQX-3299216-1-0182 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0183 | The material shall be lead free and of ”high temperatures solder type”.StatementThe material shall be lead free and of ”high temperatures solder type”. | None | None | AD-008 | component | RFQX-3299216-1-0183 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0184 | The melting point of the soldering material and the composition of the soldering material shall be declared by supplier.StatementThe melting point of the soldering material and the composition of the soldering material shall be declared by supplier. | None | None | AD-008 | component | RFQX-3299216-1-0184 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0185 | The PCB must be supported and must not bent in any direction during the process.StatementThe PCB must be supported and must not bent in any direction during the process. | None | None | AD-003 | component | RFQX-3299216-1-0185 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0186 | Conformal coating or lacquer shall cover the entire PCB and all solder joints.StatementConformal coating or lacquer shall cover the entire PCB and all solder joints. | None | None | AD-008 | component | RFQX-3299216-1-0186 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0187 | The layout of the PCB, including component placement, shall take the applying of conformal coating into consideration so that the aforementioned requirement can be met.StatementThe layout of the PCB, including component placement, shall take the applying of conformal coating into consideration so that the aforementioned requirement can be met. | None | None | AD-005 | interface | RFQX-3299216-1-0187 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0188 | shall be specified in the initial offer.Statementshall be specified in the initial offer. | None | None | AD-008 | component | RFQX-3299216-1-0188 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0189 | The conformal coating process and materials shall apply to the latest versions of IPC/EIA J-STD-001 (with applicable standards as e.g.StatementThe conformal coating process and materials shall apply to the latest versions of IPC/EIA J-STD-001 (with applicable standards as e.g. | None | None | AD-003 | component | RFQX-3299216-1-0189 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0190 | HDBK-001, IPC-CC-830 and HDBK-830) and the visual appearance of the final coating shall be consistent with the latest version of IPC-A-610.StatementHDBK-001, IPC-CC-830 and HDBK-830) and the visual appearance of the final coating shall be consistent with the latest version of IPC-A-610. | None | None | AD-008 | component | RFQX-3299216-1-0190 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0191 | Water based and silicone lacquers shall not be used.StatementWater based and silicone lacquers shall not be used. | None | None | AD-008 | component | RFQX-3299216-1-0191 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0192 | The following requirements shall be fulfilled: The unit shall withstand the salt-spray environment, according to CVS40 §6.1.6, without clogging of the membrane.StatementThe following requirements shall be fulfilled: The unit shall withstand the salt-spray environment, according to CVS40 §6.1.6, without clogging of the membrane. | None | None | AD-008 | component | RFQX-3299216-1-0192 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0193 | The membrane shall be placed so that it is protected against blunt force, falling dust and dripping salt-water.StatementThe membrane shall be placed so that it is protected against blunt force, falling dust and dripping salt-water. | None | None | AD-002 | component | RFQX-3299216-1-0193 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0194 | The design shall be made to prevent accumulation of water on top of the membrane, or in the cavity of the membrane.StatementThe design shall be made to prevent accumulation of water on top of the membrane, or in the cavity of the membrane. | None | None | AD-008 | component | RFQX-3299216-1-0194 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0195 | 7.46 Forbidden components: BGA capsule in any form must not be used.Statement7.46 Forbidden components: BGA capsule in any form must not be used. | None | None | AD-008 | component | RFQX-3299216-1-0195 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0196 | Tantalum capacitors must not be used Serial resistors on power supply circuits must not be used.StatementTantalum capacitors must not be used Serial resistors on power supply circuits must not be used. | None | None | AD-008 | component | RFQX-3299216-1-0196 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0197 | The life length requirement is minimum 3000 operating hours per year for 15 yearsStatementThe life length requirement is minimum 3000 operating hours per year for 15 years | None | None | None | None | RFQX-3299216-1-0197 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0198 | The clutch actuator shall withstand 6 500 000 actuations with the test cycle described in Appendix B.StatementThe clutch actuator shall withstand 6 500 000 actuations with the test cycle described in Appendix B. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0198 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0199 | The ECA must be maintenance free over the whole life timeStatementThe ECA must be maintenance free over the whole life time | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0199 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0200 | The maintenance window cover (See req.StatementThe maintenance window cover (See req. 4.17) shall be provided as a spare part | SSR-LIFE-002 | Lifecycle / Field Return / Decommissioning — Lifecycle / Field Return / Decommissioning | AD-008 | component | RFQX-3299216-1-0200 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0201 | In a situation where the ECA has jammed, and is holding the clutch open, it shall be possible to remove the clutch force by following an instruction documented on the ECA drawing.StatementIn a situation where the ECA has jammed, and is holding the clutch open, it shall be possible to remove the clutch force by following an instruction documented on the ECA drawing. It is allowed to destroy the ECA in the process. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-3299216-1-0201 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0202 | 8.4 Six consecutive units shall run past 6.5M actuations at the supplier, and continue to end of life.Statement8.4 Six consecutive units shall run past 6.5M actuations at the supplier, and continue to end of life. | None | None | AD-008 | component | RFQX-3299216-1-0202 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0203 | Three consecutive units shall run past 6.5M actuations at Scania, and continue to end of life.StatementThree consecutive units shall run past 6.5M actuations at Scania, and continue to end of life. | None | None | AD-008 | component | RFQX-3299216-1-0203 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0204 | 8.6 Failure rate for ECU and electronics shall be less than: 0ppm @ “0” km 200ppm/year during year 1-5 400ppm/year during year 6-10 1000ppm/year during year 11-15 8.7 External vulnerable components might need to be replaceable.Statement8.6 Failure rate for ECU and electronics shall be less than: 0ppm @ “0” km 200ppm/year during year 1-5 400ppm/year during year 6-10 1000ppm/year during year 11-15 8.7 External vulnerable components might need to be replaceable. | None | None | AD-006 | component | RFQX-3299216-1-0204 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0205 | Spare parts or repair kits shall be defined together in agreement.StatementSpare parts or repair kits shall be defined together in agreement. | None | None | AD-008 | component | RFQX-3299216-1-0205 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0206 | 4.17) shall be provided as a spare part.Statement4.17) shall be provided as a spare part. | None | None | AD-008 | component | RFQX-3299216-1-0206 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0207 | The ECA shall fulfil the requirements stated in STD3868 STD3868 is a comprehensive document referring to several underlying standards.StatementThe ECA shall fulfil the requirements stated in STD3868 STD3868 is a comprehensive document referring to several underlying standards. Out of a recycling and environmental perspective the following standards shall be taken under consideration in addition to CVS55(Ref 14.32): STD4158, Chemical substances which shall not be used – Scania Black list. STD4159, Chemical substances with limited use – Scania Grey list. CVS 83, Material declaration according to Scania IMDS reporting std. The different parts of the housing shall be marked according to material content. The ECA shall be lead free. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0207 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0208 | All included parts shall fulfil applicable sections of Part 9 in Annex B to the latest ADR ,as applicable at the time of type approval.StatementAll included parts shall fulfil applicable sections of Part 9 in Annex B to the latest ADR ,as applicable at the time of type approval. For type approval, the vehicle and its components shall comply with ECE Regulation No. 105 and with European Directive 2008/68/EC, as amended. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0208 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0209 | Out of a recycling and environmental perspective the following standards shall be taken under consideration in addition to CVS55(Ref 14.32): STD4158, Chemical substances which shall not be used – Scania Black list.StatementOut of a recycling and environmental perspective the following standards shall be taken under consideration in addition to CVS55(Ref 14.32): STD4158, Chemical substances which shall not be used – Scania Black list. | None | None | AD-008 | component | RFQX-3299216-1-0209 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0210 | The different parts of the housing shall be marked according to material content.StatementThe different parts of the housing shall be marked according to material content. | None | None | AD-008 | component | RFQX-3299216-1-0210 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0211 | The ECA shall be lead free.StatementThe ECA shall be lead free. | None | None | AD-008 | component | RFQX-3299216-1-0211 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0212 | For type approval, the vehicle and its components shall comply with ECE Regulation No.StatementFor type approval, the vehicle and its components shall comply with ECE Regulation No. | None | None | AD-008 | component | RFQX-3299216-1-0212 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0213 | The ECA must fulfil the general requirements for Electronic Control Units (ECUs), which are stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2).StatementThe ECA must fulfil the general requirements for Electronic Control Units (ECUs), which are stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0213 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0214 | The ECA must not be dependent on software for protection against requirements stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2).StatementThe ECA must not be dependent on software for protection against requirements stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2). | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-3299216-1-0214 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0215 | CAN communication shall not be affected.StatementCAN communication shall not be affected. | None | None | AD-005 | interface | RFQX-3299216-1-0215 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0216 | Memory functions shall remain Class A.StatementMemory functions shall remain Class A. | None | None | AD-006 | component | RFQX-3299216-1-0216 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0217 | Accepted behaviour in this case shall be agreed upon between Traton and Supplier.StatementAccepted behaviour in this case shall be agreed upon between Traton and Supplier. | None | None | AD-008 | component | RFQX-3299216-1-0217 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0218 | For this unit, the following definitions of test procedure I and test procedure II shall be used Test procedure I A comprehensive test where all functional requirements are verified.StatementFor this unit, the following definitions of test procedure I and test procedure II shall be used Test procedure I A comprehensive test where all functional requirements are verified. This test shall be performed before and after exposure. Test procedure I (See Figure 17 - Test procedure I) shall at least contain: - Full stroke to evaluate speed - Staircase to evaluate accuracy - Power loss to evaluate safety Figure 17 - Test procedure I Test procedure II A reduced function test where the fundamental requirements are verified. This test shall be possible to perform during exposure. Reduced versions of test procedure II may be agreed and used during various tests. Alternative 1: Test cycle according to Appendix B, frequency 10 to 30 strokes per minute. Alternative 2: Release frequency test according to req. 5.12. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-3299216-1-0218 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0219 | This test shall be performed before and after exposure.StatementThis test shall be performed before and after exposure. | None | None | AD-008 | component | RFQX-3299216-1-0219 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0220 | Test procedure I (See Figure 17 - Test procedure I) shall at least contain: - Full stroke to evaluate speed - Staircase to evaluate accuracy - Power loss to evaluate safety Figure 17 - Test procedure I Test procedure II A reduced function test where the fundamental requirements are verified.StatementTest procedure I (See Figure 17 - Test procedure I) shall at least contain: - Full stroke to evaluate speed - Staircase to evaluate accuracy - Power loss to evaluate safety Figure 17 - Test procedure I Test procedure II A reduced function test where the fundamental requirements are verified. | None | None | AD-001 | component | RFQX-3299216-1-0220 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0221 | This test shall be possible to perform during exposure.StatementThis test shall be possible to perform during exposure. | None | None | AD-008 | component | RFQX-3299216-1-0221 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0222 | Reduced versions of test procedure II may be agreed and used during various tests.StatementReduced versions of test procedure II may be agreed and used during various tests. | None | None | None | None | RFQX-3299216-1-0222 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0223 | CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C YStatementCVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y | None | None | None | None | RFQX-3299216-1-0223 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0224 | CVS40 §5.6 TC-06 Thermal shock YStatementCVS40 §5.6 TC-06 Thermal shock Y | None | None | None | None | RFQX-3299216-1-0224 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0225 | CVS40 §5.7 TC-07 Splash water test YStatementCVS40 §5.7 TC-07 Splash water test Y | None | None | None | None | RFQX-3299216-1-0225 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0226 | CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test YStatementCVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y | None | None | None | None | RFQX-3299216-1-0226 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0227 | CVS40 §5.9 TC-09 Leakage search test YStatementCVS40 §5.9 TC-09 Leakage search test Y | None | None | None | None | RFQX-3299216-1-0227 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0228 | CVS40 §5.10 TC-10 Ingress protection The ECA shall also fulfil IP54 without mounted connectors.StatementCVS40 §5.10 TC-10 Ingress protection The ECA shall also fulfil IP54 without mounted connectors. IP classes to test: IP6K6K, IP6K7, and IP6K9K Y | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0228 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0229 | CVS40 §5.11 TC-11 Corrosion in flowing mixed noxious gas NStatementCVS40 §5.11 TC-11 Corrosion in flowing mixed noxious gas N | None | None | None | None | RFQX-3299216-1-0229 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0230 | CVS40 §5.12 TC-12 Salt spray test YStatementCVS40 §5.12 TC-12 Salt spray test Y | None | None | None | None | RFQX-3299216-1-0230 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0231 | CVS40 §5.13 TC-13 Dirt spray test TBDStatementCVS40 §5.13 TC-13 Dirt spray test TBD | None | None | None | None | RFQX-3299216-1-0231 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0232 | CVS40 §6.2 TM-01 Resonance search YStatementCVS40 §6.2 TM-01 Resonance search Y | None | None | None | None | RFQX-3299216-1-0232 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0233 | CVS40 §6.3 TM-02 Mechanical shock TBDStatementCVS40 §6.3 TM-02 Mechanical shock TBD | None | None | None | None | RFQX-3299216-1-0233 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0234 | CVS40 §6.4 TM-03 Random vibration and thermal cycle P1 Test 2 YStatementCVS40 §6.4 TM-03 Random vibration and thermal cycle P1 Test 2 Y | None | None | None | None | RFQX-3299216-1-0234 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0235 | CVS40 §6.5 TM-04 Gravel bombardment and impact YStatementCVS40 §6.5 TM-04 Gravel bombardment and impact Y | None | None | None | None | RFQX-3299216-1-0235 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0236 | CVS40 §6.6 TM-05 External forces YStatementCVS40 §6.6 TM-05 External forces Y | None | None | None | None | RFQX-3299216-1-0236 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0237 | CVS40 §6.7 TM-06 Drop test – Free fall YStatementCVS40 §6.7 TM-06 Drop test – Free fall Y | None | None | None | None | RFQX-3299216-1-0237 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0238 | CVS40 §7.1 TL-01 Life length As per Chapter 8 YStatementCVS40 §7.1 TL-01 Life length As per Chapter 8 Y | None | None | None | None | RFQX-3299216-1-0238 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0239 | CVS40 §7.2.1 TL-02 Power cycling test YStatementCVS40 §7.2.1 TL-02 Power cycling test Y | None | None | None | None | RFQX-3299216-1-0239 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0240 | CVS40 §7.2.2 TL-03 Extended thermal shock air TBDStatementCVS40 §7.2.2 TL-03 Extended thermal shock air TBD | None | None | None | None | RFQX-3299216-1-0240 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0241 | CVS40 §7.2.3 TL-04 High temperature endurance test TBDStatementCVS40 §7.2.3 TL-04 High temperature endurance test TBD | None | None | None | None | RFQX-3299216-1-0241 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0242 | CVS40 §7.2.4 TL-05 Endurance test / actuation TBDStatementCVS40 §7.2.4 TL-05 Endurance test / actuation TBD | None | None | None | None | RFQX-3299216-1-0242 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0243 | CVS40 §7.3 TL-06 Component specific test TBDStatementCVS40 §7.3 TL-06 Component specific test TBD | None | None | None | None | RFQX-3299216-1-0243 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0244 | CVS40 §7.4 TL-07 Ageing YStatementCVS40 §7.4 TL-07 Ageing Y | None | None | None | None | RFQX-3299216-1-0244 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0245 | CVS40 §8.1 TS-01 Flammability In order to fulfil flammability demands, any plastic materials (i.e.StatementCVS40 §8.1 TS-01 Flammability In order to fulfil flammability demands, any plastic materials (i.e. tab headers) shall be made of self- extinguishing materials (i.e. UL94). Y | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-3299216-1-0245 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-3299216-1-0246 | CVS40 §8.2 TS-02 UV resistance Datasheet sufficient YStatementCVS40 §8.2 TS-02 UV resistance Datasheet sufficient Y | None | None | None | None | RFQX-3299216-1-0246 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0247 | CVS40 §8.3 TS-03 Chemical resistance Application method TBD YStatementCVS40 §8.3 TS-03 Chemical resistance Application method TBD Y | None | None | None | None | RFQX-3299216-1-0247 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0248 | CVS40 §8.4 TE-01 Isolation resistance and Dielectric strength tests N Exceptions and additional information to CVS41 [Y/N]StatementCVS40 §8.4 TE-01 Isolation resistance and Dielectric strength tests N Exceptions and additional information to CVS41 [Y/N] | None | None | None | None | RFQX-3299216-1-0248 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0249 | CVS41 §4 Electrical loads YStatementCVS41 §4 Electrical loads Y | None | None | None | None | RFQX-3299216-1-0249 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0250 | CVS41 §4.1 TE-00 Operating Voltage Class A for ECU and communication.StatementCVS41 §4.1 TE-00 Operating Voltage Class A for ECU and communication. Class B for clutch actuation Y | None | None | None | None | RFQX-3299216-1-0250 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0251 | CVS41 §4.2 TE-01 Operating Voltage (Long-term overvoltage) Umax: 15 min, functional status Class B YStatementCVS41 §4.2 TE-01 Operating Voltage (Long-term overvoltage) Umax: 15 min, functional status Class B Y | None | None | None | None | RFQX-3299216-1-0251 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0252 | CVS41 §4.3 TE-02 Transient Overvoltage YStatementCVS41 §4.3 TE-02 Transient Overvoltage Y | None | None | None | None | RFQX-3299216-1-0252 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0253 | CVS41 §4.4 TE-03 Transient Undervoltage YStatementCVS41 §4.4 TE-03 Transient Undervoltage Y | None | None | None | None | RFQX-3299216-1-0253 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0254 | CVS41 §4.5 TE-04 Jump start YStatementCVS41 §4.5 TE-04 Jump start Y | None | None | None | None | RFQX-3299216-1-0254 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0255 | CVS41 §4.6 TE-05 Load dump, test pulse 5b YStatementCVS41 §4.6 TE-05 Load dump, test pulse 5b Y | None | None | None | None | RFQX-3299216-1-0255 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0256 | tab headers) shall be made of self- extinguishing materials (i.e.Statementtab headers) shall be made of self- extinguishing materials (i.e. | None | None | AD-008 | component | RFQX-3299216-1-0256 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0257 | CVS46 §4.6.6 Test LFM: Low Frequency Magnetic YStatementCVS46 §4.6.6 Test LFM: Low Frequency Magnetic Y | None | None | None | None | RFQX-3299216-1-0257 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0258 | CVS46 §4.7 Test VCB CTE NStatementCVS46 §4.7 Test VCB CTE N | None | None | None | None | RFQX-3299216-1-0258 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0259 | CVS46 §4.8 Test VCB AN and VCB CP NStatementCVS46 §4.8 Test VCB AN and VCB CP N | None | None | None | None | RFQX-3299216-1-0259 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0260 | CVS46 §4.9 Test C-VCB-VCA NStatementCVS46 §4.9 Test C-VCB-VCA N | None | None | None | None | RFQX-3299216-1-0260 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0261 | CVS46 §4.10 Test TSUP VCB A NStatementCVS46 §4.10 Test TSUP VCB A N | None | None | None | None | RFQX-3299216-1-0261 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0262 | CVS46 §4.11 Test TSUP VCB B NStatementCVS46 §4.11 Test TSUP VCB B N | None | None | None | None | RFQX-3299216-1-0262 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0263 | CVS46 §4.12 Test VCB Surge NStatementCVS46 §4.12 Test VCB Surge N | None | None | None | None | RFQX-3299216-1-0263 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0264 | CVS46 §4.13 Test VCB Burst NStatementCVS46 §4.13 Test VCB Burst N | None | None | None | None | RFQX-3299216-1-0264 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0265 | CVS46 §4.14 Test VCB Charging mode NStatementCVS46 §4.14 Test VCB Charging mode N | None | None | None | None | RFQX-3299216-1-0265 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0266 | CVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) YStatementCVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) Y | None | None | None | None | RFQX-3299216-1-0266 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0267 | CVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up YStatementCVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up Y | None | None | None | None | RFQX-3299216-1-0267 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0268 | CVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) YStatementCVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) Y | None | None | None | None | RFQX-3299216-1-0268 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0269 | CVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised YStatementCVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised Y | None | None | None | None | RFQX-3299216-1-0269 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0270 | CVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component.StatementCVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component. Y | None | None | None | None | RFQX-3299216-1-0270 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0271 | CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle YStatementCVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y | None | None | None | None | RFQX-3299216-1-0271 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0272 | CVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle YStatementCVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle Y | None | None | None | None | RFQX-3299216-1-0272 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0273 | CVS46 §5.2.2 Vehicle test RE: Self interference YStatementCVS46 §5.2.2 Vehicle test RE: Self interference Y | None | None | None | None | RFQX-3299216-1-0273 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0274 | CVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode NStatementCVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode N | None | None | None | None | RFQX-3299216-1-0274 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0275 | CVS46 §5.3.1 Vehicle test: AC charging Vehicle in AC charging mode NStatementCVS46 §5.3.1 Vehicle test: AC charging Vehicle in AC charging mode N | None | None | None | None | RFQX-3299216-1-0275 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0276 | CVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode NStatementCVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode N | None | None | None | None | RFQX-3299216-1-0276 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0277 | CVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with YStatementCVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with Y | None | None | None | None | RFQX-3299216-1-0277 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0278 | CVS46 §5.4.1 Vehicle test RI: External interference sources YStatementCVS46 §5.4.1 Vehicle test RI: External interference sources Y | None | None | None | None | RFQX-3299216-1-0278 / 24h | Not imported | Still Requires Customer Decision | No P1 link | evidence completeness | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0279 | P 1 Page 11 Functional safety The ECA is a part of a safety critical system and shall be handled as such.StatementP 1 Page 11 Functional safety The ECA is a part of a safety critical system and shall be handled as such. | None | None | AD-008 | component | RFQX-3299216-1-0279 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0280 | The ECA shall therefore be developed and implemented in accordance with the objectives and requirements of ISO 26262 "Road vehicles - Functional Safety".StatementThe ECA shall therefore be developed and implemented in accordance with the objectives and requirements of ISO 26262 "Road vehicles - Functional Safety". | None | None | AD-003 | component | RFQX-3299216-1-0280 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0281 | The supplier shall analyse risks of individua l HW and SW components, mechanics, and any other technologies, independently of the scope of ISO 26262.StatementThe supplier shall analyse risks of individua l HW and SW components, mechanics, and any other technologies, independently of the scope of ISO 26262. | None | None | AD-003 | component | RFQX-3299216-1-0281 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0282 | For this purpose possible causes must be systematically identified.StatementFor this purpose possible causes must be systematically identified. | None | None | AD-008 | component | RFQX-3299216-1-0282 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0283 | For these analyses at least the methods in ISO 26262 shall be applied.StatementFor these analyses at least the methods in ISO 26262 shall be applied. | None | None | AD-003 | component | RFQX-3299216-1-0283 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0284 | Field test Traton will perform field tests with the unit mounted in trucksStatementField test Traton will perform field tests with the unit mounted in trucks | None | None | None | None | RFQX-3299216-1-0284 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0285 | TestabilityStatementThe supplier of the unit must write software to enable his own testing of the unit during development, production and on any claimed unit. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-3299216-1-0285 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-3299216-1-0286 | ID Verification methods 12.1 Conformance to Requirement Specification A1 The supplier must do conformance test of all external and internal I/O.StatementID Verification methods 12.1 Conformance to Requirement Specification A1 The supplier must do conformance test of all external and internal I/O. | None | None | AD-008 | component | RFQX-3299216-1-0286 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0287 | This test must verify that all internal and external I/O fulfils the requirements in this specification.StatementThis test must verify that all internal and external I/O fulfils the requirements in this specification. | None | None | AD-008 | component | RFQX-3299216-1-0287 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0288 | A2 The supplier must perform full DV (Design Verification at B-sample level) and full PV (Product Validation at C-sample level) environmental test programs according to CVS40 and CVS41 (incl.StatementA2 The supplier must perform full DV (Design Verification at B-sample level) and full PV (Product Validation at C-sample level) environmental test programs according to CVS40 and CVS41 (incl. | None | None | AD-008 | component | RFQX-3299216-1-0288 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0289 | the suppler must carry out two full test rounds according to the Traton test requirements.Statementthe suppler must carry out two full test rounds according to the Traton test requirements. | None | None | AD-008 | component | RFQX-3299216-1-0289 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0290 | Additional tests initiated and performed by the supplier must be discussed with Traton.StatementAdditional tests initiated and performed by the supplier must be discussed with Traton. | None | None | AD-008 | component | RFQX-3299216-1-0290 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0291 | A3 The supplier must test the connectors according to TB1787.StatementA3 The supplier must test the connectors according to TB1787. | None | None | AD-008 | component | RFQX-3299216-1-0291 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0292 | A4 The supplier must do EMC tests with the unit alone.StatementA4 The supplier must do EMC tests with the unit alone. | None | None | AD-008 | component | RFQX-3299216-1-0292 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0293 | The supplier must certify the ECA according to UN ECE R10 (EMC), according to the latest revision with all amendments.StatementThe supplier must certify the ECA according to UN ECE R10 (EMC), according to the latest revision with all amendments. | None | None | AD-008 | component | RFQX-3299216-1-0293 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0294 | A5 The supplier must check that both prototypes and serial units fulfil the dimension requirement according to any relevant Traton supplied drawings.StatementA5 The supplier must check that both prototypes and serial units fulfil the dimension requirement according to any relevant Traton supplied drawings. | None | None | AD-008 | component | RFQX-3299216-1-0294 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0295 | A6 All prototypes and serial ECA’s shall fulfil requirements according to TB1822, IPC/EIA J-STD-001 class 3 and IPC-A-610 class 3.StatementA6 All prototypes and serial ECA’s shall fulfil requirements according to TB1822, IPC/EIA J-STD-001 class 3 and IPC-A-610 class 3. | None | None | AD-008 | component | RFQX-3299216-1-0295 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-3299216-1-0296 | However, dividing sample phases into several generations must be agreed upon between Traton and the supplier.StatementHowever, dividing sample phases into several generations must be agreed upon between Traton and the supplier. | None | None | AD-008 | component | RFQX-3299216-1-0296 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0297 | All samples shall be functionally tested before sent to Traton.StatementAll samples shall be functionally tested before sent to Traton. | None | None | AD-008 | component | RFQX-3299216-1-0297 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0298 | Deviations shall be reported as a part of the sample delivery.StatementDeviations shall be reported as a part of the sample delivery. | None | None | AD-008 | component | RFQX-3299216-1-0298 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0299 | Dimensional checks shall be performed for B and C-samples prior to delivery to Traton.StatementDimensional checks shall be performed for B and C-samples prior to delivery to Traton. | None | None | AD-008 | component | RFQX-3299216-1-0299 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0300 | The supplier must use the sample denominations requested by Traton.StatementThe supplier must use the sample denominations requested by Traton. | None | None | AD-008 | component | RFQX-3299216-1-0300 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0301 | Unless otherwise stated, valid version is the latest available as of 1st May 2026.StatementUnless otherwise stated, valid version is the latest available as of 1st May 2026. | None | None | None | None | RFQX-3299216-1-0301 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-3299216-1-0302 | P 1 Page Appendix B – Life length test The life time testing of the ECA shall consist of 6500000 repetitions of the test cycle described in ”I – Test cycle” Two different test profiles/setups can be used.StatementP 1 Page Appendix B – Life length test The life time testing of the ECA shall consist of 6500000 repetitions of the test cycle described in ”I – Test cycle” Two different test profiles/setups can be used. | None | None | AD-005 | interface | RFQX-3299216-1-0302 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0303 | and 5.2.Statementand 5.2. | None | None | AD-008 | component | RFQX-3299216-1-0303 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | MISSING SYSTEM REQUIREMENT |
| RFQX-3299216-1-0304 | Between the two movements the actuator should remain in the fully disengaged position.StatementBetween the two movements the actuator should remain in the fully disengaged position. | None | None | AD-008 | component | RFQX-3299216-1-0304 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0305 | After the complete engagement the actuator should remain in this position until the next disengagement is requested.StatementAfter the complete engagement the actuator should remain in this position until the next disengagement is requested. | None | None | AD-008 | component | RFQX-3299216-1-0305 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0306 | • A function test rig shall be used for function tests between intervals • At 6.25M cycles a function test at -40C as well as the release frequency test is performed, before the rigs are put into run-to-failure mode • Run-to-failure mode implies cycling at intermediate load and RT/80C until failure • @Temp durability will start with 15/min frequency to verify if 30/min is feasible • One rig at RT shall run at 15/min as a reference unit for cycle acceleration.Statement• A function test rig shall be used for function tests between intervals • At 6.25M cycles a function test at -40C as well as the release frequency test is performed, before the rigs are put into run-to-failure mode • Run-to-failure mode implies cycling at intermediate load and RT/80C until failure • @Temp durability will start with 15/min frequency to verify if 30/min is feasible • One rig at RT shall run at 15/min as a reference unit for cycle acceleration. | None | None | AD-001 | component | RFQX-3299216-1-0306 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0307 | ,Statement, | None | None | None | None | RFQX-3299216-1-0307 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0308 | Normal operation, Class AStatementNormal operation, Class A | None | None | None | None | RFQX-3299216-1-0308 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-3299216-1-0309 | This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed.StatementThis needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed. | None | None | None | None | RFQX-3299216-1-0309 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0001 | TRATON Software Update Variant 2 (SUV2) sequence Foreword This Commercial Vehicle Standard (“CVS123-2”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.StatementTRATON Software Update Variant 2 (SUV2) sequence Foreword This Commercial Vehicle Standard (“CVS123-2”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates. | None | None | None | None | RFQX-CVS123-2-0001 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0002 | Any review of this CVS123-2 shall only be done in agreement with the involved TRATON Group commercial vehicle Affiliates stated in the table below under section “Technical responsibility”.StatementAny review of this CVS123-2 shall only be done in agreement with the involved TRATON Group commercial vehicle Affiliates stated in the table below under section “Technical responsibility”. | None | None | AD-003 | component | RFQX-CVS123-2-0002 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0003 | The User shall apply the latest version of this CVS123-2.StatementThe User shall apply the latest version of this CVS123-2. | None | None | AD-008 | component | RFQX-CVS123-2-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0004 | This document specifies the method to perform software download using Software Update Variant 2 (SUV2).StatementThis document specifies the method to perform software download using Software Update Variant 2 (SUV2). | None | None | None | None | RFQX-CVS123-2-0004 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0005 | The vehicle manufacturer implementation of the Authentication service (0x29) is defined in CVS31 and SecuredDataTransmission service (0x84) is defined in CVS32.StatementThe vehicle manufacturer implementation of the Authentication service (0x29) is defined in CVS31 and SecuredDataTransmission service (0x84) is defined in CVS32. | None | None | None | None | RFQX-CVS123-2-0005 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0006 | While the requirements are applicable for programmable servers, some of the programming steps outlined in this specification (CommunicationControl and ControlDTCSetting) do not primarily target the programmable ECU, but the other ECUs on the same network which need to support the programming of the targeted ECU.StatementWhile the requirements are applicable for programmable servers, some of the programming steps outlined in this specification (CommunicationControl and ControlDTCSetting) do not primarily target the programmable ECU, but the other ECUs on the same network which need to support the programming of the targeted ECU. | None | None | None | None | RFQX-CVS123-2-0006 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0007 | Support for programming as well as support for programming of other ECUs on the same network involves supporting what is referred to as pre- and post-programming steps.StatementSupport for programming as well as support for programming of other ECUs on the same network involves supporting what is referred to as pre- and post-programming steps. | None | None | None | None | RFQX-CVS123-2-0007 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0008 | This specification is based on ISO14229-1:2020 and as such supports a “single server” approach to non-volatile memory programming with the intention to simplify client software development without significantly complicating server software development.StatementThis specification is based on ISO14229-1:2020 and as such supports a “single server” approach to non-volatile memory programming with the intention to simplify client software development without significantly complicating server software development. | None | None | None | None | RFQX-CVS123-2-0008 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0009 | With a single server objective, an ECU will appear to be programmable through communication with a single diagnostic server even if the ECU in fact implements two or more diagnostic servers – one in the boot loader and one in each application – and in reality will be programmed through communication with either one of them or both.StatementWith a single server objective, an ECU will appear to be programmable through communication with a single diagnostic server even if the ECU in fact implements two or more diagnostic servers – one in the boot loader and one in each application – and in reality will be programmed through communication with either one of them or both. | None | None | None | None | RFQX-CVS123-2-0009 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0010 | The reason to why an ECU must implement two or more diagnostic servers is that it needs to support two or more different ECU configurations: one for which no application is installed and one or more for which applications are installed in the ECU.StatementThe reason to why an ECU must implement two or more diagnostic servers is that it needs to support two or more different ECU configurations: one for which no application is installed and one or more for which applications are installed in the ECU. | None | None | AD-007 | component | RFQX-CVS123-2-0010 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0011 | It should be noted that a single server view is not completely achievable and that clients still need to be aware of two physical servers.StatementIt should be noted that a single server view is not completely achievable and that clients still need to be aware of two physical servers. | None | None | AD-002 | component | RFQX-CVS123-2-0011 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0012 | This specification targets ECUs, not clients.StatementThis specification targets ECUs, not clients. | None | None | None | None | RFQX-CVS123-2-0012 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0013 | Clients may prefer to implement programming support using other service parameter values or even another set of programming steps thanStatementClients may prefer to implement programming support using other service parameter values or even another set of programming steps than | None | None | None | None | RFQX-CVS123-2-0013 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0014 | For this reason, only the server is required to support the specified sequence.StatementFor this reason, only the server is required to support the specified sequence. | None | None | AD-002 | component | RFQX-CVS123-2-0014 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0015 | The target readers of this specification are ECU suppliers, which can be either internal or external in relation to the vehicle manufacturer.StatementThe target readers of this specification are ECU suppliers, which can be either internal or external in relation to the vehicle manufacturer. | None | None | None | None | RFQX-CVS123-2-0015 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0016 | In both cases, whenever the term “ECU supplier” or just “supplier” is used in this specification it refers to the company and organization which is responsible for the implementation and delivery of the ECU according to the requirements in this specification.StatementIn both cases, whenever the term “ECU supplier” or just “supplier” is used in this specification it refers to the company and organization which is responsible for the implementation and delivery of the ECU according to the requirements in this specification. | None | None | None | None | RFQX-CVS123-2-0016 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0017 | The following documents are normative and indispensable for the application of this document: • ISO14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements • CVS124, Traton Specification on Unified diagnostic services (UDS) requirements • CVS154, DSC Specification • CVS31, Authenticate 0x29 • CVS36, Secure ECU Parametrization • CVS32, SecuredDataTranmission 0x84 • CVS33, Entity Management Protocol (EMP) • CVS34, Entity Management Protocol (EMP) Basic Entity DefinitionStatementThe following documents are normative and indispensable for the application of this document: • ISO14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements • CVS124, Traton Specification on Unified diagnostic services (UDS) requirements • CVS154, DSC Specification • CVS31, Authenticate 0x29 • CVS36, Secure ECU Parametrization • CVS32, SecuredDataTranmission 0x84 • CVS33, Entity Management Protocol (EMP) • CVS34, Entity Management Protocol (EMP) Basic Entity Definition | None | None | None | None | RFQX-CVS123-2-0017 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0018 | Several terms that are used in this document but not defined in Table 1 are defined by ISO or in the document CVS124.StatementSeveral terms that are used in this document but not defined in Table 1 are defined by ISO or in the document CVS124. | None | None | None | None | RFQX-CVS123-2-0018 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0019 | Application data module (Calibration data) Contains a variant-specific set of parameter values that is required for correct operation of the control unit in a specific vehicle variant.StatementApplication data module (Calibration data) Contains a variant-specific set of parameter values that is required for correct operation of the control unit in a specific vehicle variant. | None | None | AD-001 | component | RFQX-CVS123-2-0019 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0020 | It must be clearly separated from the application software.StatementIt must be clearly separated from the application software. | None | None | AD-001 | component | RFQX-CVS123-2-0020 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0021 | For this reason, it is located in a separate memory area and must also be erasable and programmable independently of the application software.StatementFor this reason, it is located in a separate memory area and must also be erasable and programmable independently of the application software. | None | None | AD-001 | component | RFQX-CVS123-2-0021 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0022 | Application software module Contains all vehicle functions required for the normal server operation.StatementApplication software module Contains all vehicle functions required for the normal server operation. | None | None | AD-001 | component | RFQX-CVS123-2-0022 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0023 | All software parts required for the reprogramming like CAN driver, network layer, diagnostic services, boot operating system, start-up code, low level flash routines (for erasing, writing, reading), EEPROM access routines (read, write functionality), software compatibility checks etc.StatementAll software parts required for the reprogramming like CAN driver, network layer, diagnostic services, boot operating system, start-up code, low level flash routines (for erasing, writing, reading), EEPROM access routines (read, write functionality), software compatibility checks etc. | None | None | AD-007 | component | RFQX-CVS123-2-0023 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0024 | shall be implemented in the boot software code.Statementshall be implemented in the boot software code. | None | None | AD-001 | component | RFQX-CVS123-2-0024 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0025 | The value of this variable (and C2, see below) may be used by the boot manager to determine whether to start the application or the boot loader.StatementThe value of this variable (and C2, see below) may be used by the boot manager to determine whether to start the application or the boot loader. | None | None | None | None | RFQX-CVS123-2-0025 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0026 | C2 Also referred to as “programming request” flag.StatementC2 Also referred to as “programming request” flag. | None | None | None | None | RFQX-CVS123-2-0026 / 32h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0027 | The value of this variable (and C1, see above) may be used by the boot manager to determine whether or not to start the application or the boot loader.StatementThe value of this variable (and C1, see above) may be used by the boot manager to determine whether or not to start the application or the boot loader. | None | None | None | None | RFQX-CVS123-2-0027 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0028 | C3 Also referred to as “reprogrammed” flag.StatementC3 Also referred to as “reprogrammed” flag. | None | None | None | None | RFQX-CVS123-2-0028 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0029 | The value of this variable may be used by the application to determine whether or not initialization is required.StatementThe value of this variable may be used by the application to determine whether or not initialization is required. | None | None | AD-001 | component | RFQX-CVS123-2-0029 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0030 | Satisfied programming precondition A programming precondition agreed between supplier and vehicle manufacturer which, together with other agreed programming preconditions, shall be fulfilled before an ECU is made eligible for programming.StatementSatisfied programming precondition A programming precondition agreed between supplier and vehicle manufacturer which, together with other agreed programming preconditions, shall be fulfilled before an ECU is made eligible for programming. | None | None | AD-006 | component | RFQX-CVS123-2-0030 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0031 | Tester System that controls functions such as test, inspection, monitoring, or diagnosis of an on-vehicle electronic control unit and may be dedicated to a specific type of operator (e.g., an off-board scan tool dedicated to garage mechanics, an off-board test tool dedicated to assembly plants, or an on-board tester) see (1) 3.2 Abbreviated terms Table 2: Abbreviated terms Abbreviation Description NRC Negative Response Code NR Negative Response APP Application software BLF Boot Loader Flash CDTCS Clear DTC Setting CF Consecutive Frame Def Default diagnostic session DIAG Changeable over diagnostics interface DID Data identifier DSC Data Security Container EMP Entity Management Protocol Ext Extended diagnostic session FF First Frame FLASH BOOT Boot loader module stored in flash memory FLASH DATA Data set module stored in flash memoryStatementTester System that controls functions such as test, inspection, monitoring, or diagnosis of an on-vehicle electronic control unit and may be dedicated to a specific type of operator (e.g., an off-board scan tool dedicated to garage mechanics, an off-board test tool dedicated to assembly plants, or an on-board tester) see (1) 3.2 Abbreviated terms Table 2: Abbreviated terms Abbreviation Description NRC Negative Response Code NR Negative Response APP Application software BLF Boot Loader Flash CDTCS Clear DTC Setting CF Consecutive Frame Def Default diagnostic session DIAG Changeable over diagnostics interface DID Data identifier DSC Data Security Container EMP Entity Management Protocol Ext Extended diagnostic session FF First Frame FLASH BOOT Boot loader module stored in flash memory FLASH DATA Data set module stored in flash memory | None | None | None | None | RFQX-CVS123-2-0031 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0032 | Requirements are prefixed “SUV2_REQ”.StatementRequirements are prefixed “SUV2_REQ”. | None | None | None | None | RFQX-CVS123-2-0032 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0033 | Similarly, informative text is prefixed “SUV2_INFO”.StatementSimilarly, informative text is prefixed “SUV2_INFO”. | None | None | None | None | RFQX-CVS123-2-0033 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0034 | The implementation of the client and the server shall be compliant with (ISO14229-1:2020) and the Traton Specification on Unified diagnostic Service (UDS) requirements (CVS124) with the clarifications, extensions and exceptions stated in this specification.StatementThe implementation of the client and the server shall be compliant with (ISO14229-1:2020) and the Traton Specification on Unified diagnostic Service (UDS) requirements (CVS124) with the clarifications, extensions and exceptions stated in this specification. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0034 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0035 | Requirements in (CVS124) which are not explicitly stated to apply to the application only (such as communication parameters) shall apply to the boot loader as well.StatementRequirements in (CVS124) which are not explicitly stated to apply to the application only (such as communication parameters) shall apply to the boot loader as well. | None | None | AD-001 | component | RFQX-CVS123-2-0035 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0036 | All deviations from this specification shall be agreed with the applicable vehicle manufacturer(s).StatementAll deviations from this specification shall be agreed with the applicable vehicle manufacturer(s). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0036 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0037 | The programming requirements in this specification shall apply to the programming of all kinds of software modules (application, application data and boot loader), unless explicitly otherwise stated.StatementThe programming requirements in this specification shall apply to the programming of all kinds of software modules (application, application data and boot loader), unless explicitly otherwise stated. | SSR-BOOT-001 | Secure software update and flash readiness — Bootloader and Application State Handling | AD-001 | component | RFQX-CVS123-2-0037 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0038 | If as a deviation with respect toStatementIf as a deviation with respect to | None | None | None | None | RFQX-CVS123-2-0038 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0039 | an ECU will not support boot loader reprogramming, the boot loader SW shall be in a protected area of the memory.Statementan ECU will not support boot loader reprogramming, the boot loader SW shall be in a protected area of the memory. | SSR-BOOT-002 | Secure software update and flash readiness — Bootloader and Application State Handling | AD-006 | component | RFQX-CVS123-2-0039 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0040 | A SW or HW protection mechanism shall be used to protect the software from being accidentally erased or overwritten.StatementA SW or HW protection mechanism shall be used to protect the software from being accidentally erased or overwritten. | None | None | AD-001 | component | RFQX-CVS123-2-0040 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0041 | If the microcontroller supports HW protection, this shall be used.StatementIf the microcontroller supports HW protection, this shall be used. | None | None | AD-008 | component | RFQX-CVS123-2-0041 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0042 | The server shall support programming of all application software and application data modules and any subset of such modules in a single sequence without any intermediate reset service requests.StatementThe server shall support programming of all application software and application data modules and any subset of such modules in a single sequence without any intermediate reset service requests. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0042 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0043 | Programming of a subset of modules may lead to that the consistency check at the end of a programming sequence fails but shall not lead to that those programmed modules need to be reprogrammed from the beginning.StatementProgramming of a subset of modules may lead to that the consistency check at the end of a programming sequence fails but shall not lead to that those programmed modules need to be reprogrammed from the beginning. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0043 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0044 | Boot loader updating according to this specification shall be supported during development, from A-samples and onwards.StatementBoot loader updating according to this specification shall be supported during development, from A-samples and onwards. | SSR-BOOT-003 | Bootloader and Application State Handling — Bootloader and Application State Handling | AD-008 | component | RFQX-CVS123-2-0044 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0045 | Boot loaders need to be updated by the vehicle manufacturer on aftermarket workshop scenarios or at a test bench during component testing, when the ECU is mounted in a vehicle during system testing or in production to fix bugs.StatementBoot loaders need to be updated by the vehicle manufacturer on aftermarket workshop scenarios or at a test bench during component testing, when the ECU is mounted in a vehicle during system testing or in production to fix bugs. | None | None | None | None | RFQX-CVS123-2-0045 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0046 | A server shall be programmable according to this specification (i.e., not only using supplier tools) regardless of whether one or more DTCs are currently active, or one or more functions are currently degraded.StatementA server shall be programmable according to this specification (i.e., not only using supplier tools) regardless of whether one or more DTCs are currently active, or one or more functions are currently degraded. | SSR-DIAG-002 | Diagnostic Services — Diagnostic Services | AD-002 | component | RFQX-CVS123-2-0046 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0047 | A server shall be programmable while integrated in the vehicle network and as a standalone server without further conditions and without further interventions by the diagnostic tester as per this specification.StatementA server shall be programmable while integrated in the vehicle network and as a standalone server without further conditions and without further interventions by the diagnostic tester as per this specification. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0047 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0048 | The solution for maintaining/reorganizing data (EEPROM data, operational data, adaptive data etc.) before and after reprogramming of software modules shall be discussed and agreed with the vehicle manufacturer.StatementThe solution for maintaining/reorganizing data (EEPROM data, operational data, adaptive data etc.) before and after reprogramming of software modules shall be discussed and agreed with the vehicle manufacturer. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0048 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0049 | The supplier shall provide, for each committed software delivery, a document that describes the programming procedure together with any requirement exceptions and ECU specific behaviours.StatementThe supplier shall provide, for each committed software delivery, a document that describes the programming procedure together with any requirement exceptions and ECU specific behaviours. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0049 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0050 | Normal and worst-case performance values shall be documented for: • Total time for the programming sequence (programming steps prefixed “P1Pro”, see section Programming step of phase #1 – Download of application software and data).StatementNormal and worst-case performance values shall be documented for: • Total time for the programming sequence (programming steps prefixed “P1Pro”, see section Programming step of phase #1 – Download of application software and data). | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0050 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0051 | The supplier shall document the versioning concept for supplier specific DIDs.StatementThe supplier shall document the versioning concept for supplier specific DIDs. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0051 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0052 | System name (DID 0xF197), diagnostic address and bitrate shall be persisted in an application data module dedicated for boot parameters, referred to as “boot parameter module”.StatementSystem name (DID 0xF197), diagnostic address and bitrate shall be persisted in an application data module dedicated for boot parameters, referred to as “boot parameter module”. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0052 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0053 | When this module is programmed the parameter values in it shall override default parameter values persisted in the boot loader software module.StatementWhen this module is programmed the parameter values in it shall override default parameter values persisted in the boot loader software module. | None | None | AD-001 | component | RFQX-CVS123-2-0053 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0054 | The “boot parameter module” permits a generic bootloader to be an ECU application platform (ECU HW + boot loader software).StatementThe “boot parameter module” permits a generic bootloader to be an ECU application platform (ECU HW + boot loader software). | None | None | None | None | RFQX-CVS123-2-0054 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0055 | It should be possible to reuse the generic bootloader for future currently unknown purposes/applications without a need to create a new part number for the platform.StatementIt should be possible to reuse the generic bootloader for future currently unknown purposes/applications without a need to create a new part number for the platform. | SSR-BOOT-004 | Bootloader and Application State Handling — Bootloader and Application State Handling | AD-002 | component | RFQX-CVS123-2-0055 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0056 | When the boot loader software in an ECU has not yet been parameterized (a boot parameter module has not been programmed) the boot loader software shall apply project specific default values, typically: • diagnostic address 0xA7 • baud rate 500 kb/s • DID 0xF197StatementWhen the boot loader software in an ECU has not yet been parameterized (a boot parameter module has not been programmed) the boot loader software shall apply project specific default values, typically: • diagnostic address 0xA7 • baud rate 500 kb/s • DID 0xF197 | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0056 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0057 | For definition of DID 0xF197 see CVS124.StatementFor definition of DID 0xF197 see CVS124. | None | None | None | None | RFQX-CVS123-2-0057 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0058 | Default values for EOL parameters shall be implemented in a dedicated application data module, referred to as “EOL parameters module”.StatementDefault values for EOL parameters shall be implemented in a dedicated application data module, referred to as “EOL parameters module”. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0058 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0059 | The partitioning of the ECU software into modules shall be discussed and agreed with the vehicle manufacturer.StatementThe partitioning of the ECU software into modules shall be discussed and agreed with the vehicle manufacturer. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0059 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0060 | A joint use of program code for communication functions (com stack) by the application and the boot loader is not permitted.StatementA joint use of program code for communication functions (com stack) by the application and the boot loader is not permitted. | None | None | None | None | RFQX-CVS123-2-0060 / 16h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0061 | A software released for integration test, production or service market shall be hashed so its integrity can be verified by the server.StatementA software released for integration test, production or service market shall be hashed so its integrity can be verified by the server. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0061 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0062 | Flash files delivered from the supplier shall never have to be modified by the vehicle manufacturer.StatementFlash files delivered from the supplier shall never have to be modified by the vehicle manufacturer. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0062 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0063 | It is within the scope of this specification that flash files delivered from the supplier can be encrypted by the vehicle manufacturer before storing in the vehicle manufacturer offboard database, but the server decryption of the received data will always restore it to servers memory into original data delivered by the supplier.StatementIt is within the scope of this specification that flash files delivered from the supplier can be encrypted by the vehicle manufacturer before storing in the vehicle manufacturer offboard database, but the server decryption of the received data will always restore it to servers memory into original data delivered by the supplier. | None | None | None | None | RFQX-CVS123-2-0063 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0064 | The supplier shall deliver the necessary information to verify the integrity of the flash files.StatementThe supplier shall deliver the necessary information to verify the integrity of the flash files. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0064 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0065 | In case the supplier delivers encrypted flash files to the vehicle manufacturer, the supplier should also provide the necessary information so the flash files can be verified as part of flash files update procedure.StatementIn case the supplier delivers encrypted flash files to the vehicle manufacturer, the supplier should also provide the necessary information so the flash files can be verified as part of flash files update procedure. | None | None | AD-005 | interface | RFQX-CVS123-2-0065 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0066 | Whether or not the ECU shall be delivered from the supplier to the vehicle manufacturer with a pre-programmed application and pre-programmed application data shall be discussed and agreed with the vehicle manufacturer.StatementWhether or not the ECU shall be delivered from the supplier to the vehicle manufacturer with a pre-programmed application and pre-programmed application data shall be discussed and agreed with the vehicle manufacturer. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0066 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0067 | Regardless of if the ECU will be delivered from the supplier with a pre-programmed application and application data, the corresponding flash files shall be possible to request by vehicle manufacturer to be able to perform software verification at any time in vehicle manufacturer production site.StatementRegardless of if the ECU will be delivered from the supplier with a pre-programmed application and application data, the corresponding flash files shall be possible to request by vehicle manufacturer to be able to perform software verification at any time in vehicle manufacturer production site. | None | None | AD-001 | component | RFQX-CVS123-2-0067 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0068 | When the application module is pre-programmed by the supplier, ECU and software identifiers 0xF187 and 0xF188 shall be set to product specific vehicle manufacturer defined values.StatementWhen the application module is pre-programmed by the supplier, ECU and software identifiers 0xF187 and 0xF188 shall be set to product specific vehicle manufacturer defined values. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0068 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0069 | Otherwise 0xF187 and 0xF188 shall be set to default values, see CVS124.StatementOtherwise 0xF187 and 0xF188 shall be set to default values, see CVS124. | None | None | AD-008 | component | RFQX-CVS123-2-0069 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0070 | Programmable servers shall support the full programming sequence described in this chapter.StatementProgrammable servers shall support the full programming sequence described in this chapter. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0070 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0071 | Non-programmable servers shall support the pre-programming and post-programming steps of the programming sequence described in this chapter (phase 1 and 2).StatementNon-programmable servers shall support the pre-programming and post-programming steps of the programming sequence described in this chapter (phase 1 and 2). | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0071 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0072 | The programming sequence described in this chapter shall be supported when a valid application is present as well as when no valid application is present in the ECU.StatementThe programming sequence described in this chapter shall be supported when a valid application is present as well as when no valid application is present in the ECU. | SSR-BOOT-001 | Secure software update and flash readiness — Bootloader and Application State Handling | AD-001 | component | RFQX-CVS123-2-0072 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0073 | If a valid application is present in the ECU, some of the services described in the programming sequence will be executed in the application.StatementIf a valid application is present in the ECU, some of the services described in the programming sequence will be executed in the application. | None | None | None | None | RFQX-CVS123-2-0073 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0074 | Each programming step will specify an addressing method (physical or functional), an SPRMIB (suppressPosRspMsgIndicationBit) bit value and other parameter values for the service(s) posted by the client.StatementEach programming step will specify an addressing method (physical or functional), an SPRMIB (suppressPosRspMsgIndicationBit) bit value and other parameter values for the service(s) posted by the client. | None | None | None | None | RFQX-CVS123-2-0074 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0075 | The full set of addressing modes, SPRMIB values and other parameter values that the server shall support for each service are specified with implementation requirements in CVS124.StatementThe full set of addressing modes, SPRMIB values and other parameter values that the server shall support for each service are specified with implementation requirements in CVS124. | None | None | AD-001 | component | RFQX-CVS123-2-0075 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0076 | The numbering of the programming sequence steps in this document generally has a well- defined relation to the numbering of the sequence steps in (ISO14229-1:2020).StatementThe numbering of the programming sequence steps in this document generally has a well- defined relation to the numbering of the sequence steps in (ISO14229-1:2020). | None | None | None | None | RFQX-CVS123-2-0076 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0077 | Programming phase #1 is defined to program a server (e.g., download of application software, application data or boot software).StatementProgramming phase #1 is defined to program a server (e.g., download of application software, application data or boot software). | None | None | None | None | RFQX-CVS123-2-0077 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0078 | To enable access to diagnostic services in the programming sequence, an authentication sequence shall be performed between the client and the server by means of the Authentication 0x29 service.StatementTo enable access to diagnostic services in the programming sequence, an authentication sequence shall be performed between the client and the server by means of the Authentication 0x29 service. | SSR-RBAC-002 | Secure software update and flash readiness — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0078 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0079 | The server shall receive a diagnostic service authentication (0x29) with SubFunction deAuthenticate (0x00) message from the client to disable authorized access to diagnostic programming services after an update is considered fulfilled.StatementThe server shall receive a diagnostic service authentication (0x29) with SubFunction deAuthenticate (0x00) message from the client to disable authorized access to diagnostic programming services after an update is considered fulfilled. | SSR-RBAC-002 | Secure software update and flash readiness — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0079 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0080 | For further information on the service details and programming messages structure regarding the SecuredDataTransmission (0x84) service, refer to CVS32.StatementFor further information on the service details and programming messages structure regarding the SecuredDataTransmission (0x84) service, refer to CVS32. | None | None | None | None | RFQX-CVS123-2-0080 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0081 | The sequence shown in the following figure shows the Pre-Programming step of phase #1.StatementThe sequence shown in the following figure shows the Pre-Programming step of phase #1. | None | None | None | None | RFQX-CVS123-2-0081 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0082 | When this step is entered, the ECU is assumed to be in a state which enables it to receive UDS service requests.StatementWhen this step is entered, the ECU is assumed to be in a state which enables it to receive UDS service requests. | None | None | None | None | RFQX-CVS123-2-0082 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0083 | For each server in the network, depending on whether an application has been successfully flashed before, it will run in application or boot mode.StatementFor each server in the network, depending on whether an application has been successfully flashed before, it will run in application or boot mode. | None | None | None | None | RFQX-CVS123-2-0083 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0084 | The client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to DefaultSession and the SPRMIB not set.StatementThe client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to DefaultSession and the SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0084 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0085 | If servers which support wake-up on CAN are not awake before, this request causes them to wake-up.StatementIf servers which support wake-up on CAN are not awake before, this request causes them to wake-up. | None | None | None | None | RFQX-CVS123-2-0085 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0086 | All servers available on the network and their diagnostic addresses are identified from the positive responses to this request.StatementAll servers available on the network and their diagnostic addresses are identified from the positive responses to this request. | None | None | None | None | RFQX-CVS123-2-0086 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0087 | The client then posts physically or functionally addressed ReadDataByIdentifier (0x22) service requests to collect additional identification data from each identified server.StatementThe client then posts physically or functionally addressed ReadDataByIdentifier (0x22) service requests to collect additional identification data from each identified server. | None | None | None | None | RFQX-CVS123-2-0087 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0088 | The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Get (0x01).StatementThe client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Get (0x01). | None | None | None | None | RFQX-CVS123-2-0088 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0089 | In this step, it is client dependent if and what cyber security entities are relevant to be read for performing the remaining steps of the sequence.StatementIn this step, it is client dependent if and what cyber security entities are relevant to be read for performing the remaining steps of the sequence. | None | None | None | None | RFQX-CVS123-2-0089 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0090 | As example, the client may read certificate validity time and/or RBAC configuration file to verify if the appropriate entities are stored in the server.StatementAs example, the client may read certificate validity time and/or RBAC configuration file to verify if the appropriate entities are stored in the server. | None | None | None | None | RFQX-CVS123-2-0090 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0091 | For reference on EMP control routine, see CVS33.StatementFor reference on EMP control routine, see CVS33. | None | None | None | None | RFQX-CVS123-2-0091 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0092 | The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00).StatementThe client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00). | None | None | None | None | RFQX-CVS123-2-0092 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0093 | In this step, the client will set a new SDSC entity, and it is client dependent if and what other entities are relevant to be set/update for performing the remaining steps of the sequence.StatementIn this step, the client will set a new SDSC entity, and it is client dependent if and what other entities are relevant to be set/update for performing the remaining steps of the sequence. | None | None | None | None | RFQX-CVS123-2-0093 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0094 | As example, the client may have identified that the RBAC configuration file requires update and perform the appropriate set to update the entities stored in the server.StatementAs example, the client may have identified that the RBAC configuration file requires update and perform the appropriate set to update the entities stored in the server. | None | None | AD-002 | component | RFQX-CVS123-2-0094 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0095 | Alternatively, it may be a client strategy to always update certain entities prior to a software update.StatementAlternatively, it may be a client strategy to always update certain entities prior to a software update. | None | None | None | None | RFQX-CVS123-2-0095 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0096 | For reference on EMP control routine, see CVS33.StatementFor reference on EMP control routine, see CVS33. | None | None | None | None | RFQX-CVS123-2-0096 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0097 | The client post physically addressed authentication sequence based on CVS31 with SPRMIB not set.StatementThe client post physically addressed authentication sequence based on CVS31 with SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0097 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0098 | The client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to extended diagnostic session and the SPRMIB set.StatementThe client posts a functionally addressed DiagnosticSessionControl (0x10) service request with sessionType equal to extended diagnostic session and the SPRMIB set. | None | None | None | None | RFQX-CVS123-2-0098 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0099 | From this point, onwards (throughout the entire programming sequence) the client posts functionally addressed TesterPresent (0x3E) service requests at regular intervals, with the SPRMIB set, with the purpose to make the server(s) stay in the currently active non-default session and maintain its authenticated state.StatementFrom this point, onwards (throughout the entire programming sequence) the client posts functionally addressed TesterPresent (0x3E) service requests at regular intervals, with the SPRMIB set, with the purpose to make the server(s) stay in the currently active non-default session and maintain its authenticated state. | None | None | None | None | RFQX-CVS123-2-0099 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0100 | The client disables the setting of DTCs in each server by posting a functionally addressed ControlDTCSetting (0x85) service request with the sub-function parameter DTCSettingType set to off and the SPRMIB set.StatementThe client disables the setting of DTCs in each server by posting a functionally addressed ControlDTCSetting (0x85) service request with the sub-function parameter DTCSettingType set to off and the SPRMIB set. | None | None | None | None | RFQX-CVS123-2-0100 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0101 | If the server is executing in the boot loader it will accept the request without performing any action, as DTCs are already disabled (DTC setting not supported by boot loader).StatementIf the server is executing in the boot loader it will accept the request without performing any action, as DTCs are already disabled (DTC setting not supported by boot loader). | None | None | None | None | RFQX-CVS123-2-0101 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0102 | The client disables the transmission of non-diagnostic messages by posting a functionally addressed CommunicationControl (0x28) service request with parameter controlType set to enableRxAndDisableTx, parameter communicationType set to normalCommunicationMessages and SPRMIB set.StatementThe client disables the transmission of non-diagnostic messages by posting a functionally addressed CommunicationControl (0x28) service request with parameter controlType set to enableRxAndDisableTx, parameter communicationType set to normalCommunicationMessages and SPRMIB set. | None | None | None | None | RFQX-CVS123-2-0102 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0103 | If the server is executing in the boot loader when this service request is received no action will be performed by the server as non-diagnostic messages are already disabled.StatementIf the server is executing in the boot loader when this service request is received no action will be performed by the server as non-diagnostic messages are already disabled. | None | None | None | None | RFQX-CVS123-2-0103 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0104 | Link control is only applicable to standalone programming (i.e., when the ECU is not mounted in the vehicle) at vehicle manufacturer premises when no application has been programmed by the supplier, communication network permits baud rate switch (e.g CAN) and only if performance requirement cannot be met without using this service.StatementLink control is only applicable to standalone programming (i.e., when the ECU is not mounted in the vehicle) at vehicle manufacturer premises when no application has been programmed by the supplier, communication network permits baud rate switch (e.g CAN) and only if performance requirement cannot be met without using this service. | None | None | None | None | RFQX-CVS123-2-0104 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0105 | The client posts a physically addressed LinkControl (0x87) service request with parameter linkControlType set to verifyBaudrateTransitionWithFixedParameter, SPRMIB not set and linkControlModeIdentifier set to desired baud rate.StatementThe client posts a physically addressed LinkControl (0x87) service request with parameter linkControlType set to verifyBaudrateTransitionWithFixedParameter, SPRMIB not set and linkControlModeIdentifier set to desired baud rate. | None | None | None | None | RFQX-CVS123-2-0105 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0106 | After reception of a positive response message the client posts a physically addressed LinkControl (0x87) service request with sub-function parameter linkControlType set to transitionMode and the SPRMIB set.StatementAfter reception of a positive response message the client posts a physically addressed LinkControl (0x87) service request with sub-function parameter linkControlType set to transitionMode and the SPRMIB set. | None | None | None | None | RFQX-CVS123-2-0106 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0107 | The client will then switch to the new baud rate and re-establish communication with the ECU considering the maximum specified time it will take for the server to start responding to the newly selected baud rate.StatementThe client will then switch to the new baud rate and re-establish communication with the ECU considering the maximum specified time it will take for the server to start responding to the newly selected baud rate. | None | None | None | None | RFQX-CVS123-2-0107 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0108 | Since Link Control is only applicable in production when no application has been programmed by the supplier, the application may return NRC 0x7F (serviceNotSupportedInActiveSession) to this service request and expect the client to proceed to the next step.StatementSince Link Control is only applicable in production when no application has been programmed by the supplier, the application may return NRC 0x7F (serviceNotSupportedInActiveSession) to this service request and expect the client to proceed to the next step. | None | None | None | None | RFQX-CVS123-2-0108 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0109 | The sequence in Figure 3 shows the programming step of phase #1.StatementThe sequence in Figure 3 shows the programming step of phase #1. | None | None | None | None | RFQX-CVS123-2-0109 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0110 | For the server to verify the integrity of the software, the information to verify shall be available to the server before step P1Pro6: Routine Control (erase Memory).StatementFor the server to verify the integrity of the software, the information to verify shall be available to the server before step P1Pro6: Routine Control (erase Memory). | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0110 / 19h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0111 | The information to verify integrity of the software is contained in software data security container (SDSC), which is transmitted in P1PreB step.StatementThe information to verify integrity of the software is contained in software data security container (SDSC), which is transmitted in P1PreB step. | None | None | None | None | RFQX-CVS123-2-0111 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0112 | If the SW to be updated is encrypted, decryption keys shall be available to the server before step P1Pro9.StatementIf the SW to be updated is encrypted, decryption keys shall be available to the server before step P1Pro9. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0112 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust; certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0113 | If SDSC dictates decryption, the decryption keys are contained in software data security container (SDSC) which is transmitted in P1PreB step.StatementIf SDSC dictates decryption, the decryption keys are contained in software data security container (SDSC) which is transmitted in P1PreB step. | None | None | None | None | RFQX-CVS123-2-0113 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0114 | Before the server executes the TransferData service, the server shall check if the data received during RequestDownload requests needs to be decrypted before writing the received data to non-volatile memory.StatementBefore the server executes the TransferData service, the server shall check if the data received during RequestDownload requests needs to be decrypted before writing the received data to non-volatile memory. | SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-001 | component | RFQX-CVS123-2-0114 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0115 | The client posts a physically addressed DiagnosticSessionControl (0x10) service request with sub-function parameter diagnosticSessionType set to ProgrammingSession and the SPRMIB not set.StatementThe client posts a physically addressed DiagnosticSessionControl (0x10) service request with sub-function parameter diagnosticSessionType set to ProgrammingSession and the SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0115 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0116 | If CommunicationControl has not been previously called in the Extended Diagnostic Session the server rejects the request with negative response code NRC 0x22 (conditionsNotCorrect).StatementIf CommunicationControl has not been previously called in the Extended Diagnostic Session the server rejects the request with negative response code NRC 0x22 (conditionsNotCorrect). | None | None | None | None | RFQX-CVS123-2-0116 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0117 | Implementation hint: If the server is executing the application the server sets a “programming request” flag (C2, see section Boot software session requirements).StatementImplementation hint: If the server is executing the application the server sets a “programming request” flag (C2, see section Boot software session requirements). | None | None | None | None | RFQX-CVS123-2-0117 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0118 | If the server is executing the application the server responds to the request with one or more negative response codes NRC 0x78 (requestCorrectlyReceived-ResponsePending) and triggers a server restart.StatementIf the server is executing the application the server responds to the request with one or more negative response codes NRC 0x78 (requestCorrectlyReceived-ResponsePending) and triggers a server restart. | None | None | None | None | RFQX-CVS123-2-0118 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0119 | The boot manager notes the programming request and starts the boot loader.StatementThe boot manager notes the programming request and starts the boot loader. | None | None | None | None | RFQX-CVS123-2-0119 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0120 | Implementation hint: The boot manager recognizes the programming request by checking the “programming request” flag (C2).StatementImplementation hint: The boot manager recognizes the programming request by checking the “programming request” flag (C2). | None | None | None | None | RFQX-CVS123-2-0120 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0121 | Implementation hint: The boot manager or the boot loader resets the “programming request” flag (C2).StatementImplementation hint: The boot manager or the boot loader resets the “programming request” flag (C2). | None | None | None | None | RFQX-CVS123-2-0121 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0122 | Finally, the boot loader sends a positive response.StatementFinally, the boot loader sends a positive response. | None | None | None | None | RFQX-CVS123-2-0122 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0123 | The client post physically addressed authentication sequence based on Authenticate 0x29 with SPRMIB not set.StatementThe client post physically addressed authentication sequence based on Authenticate 0x29 with SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0123 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0124 | The client posts a physically addressed RoutineControl (0x31) (eraseMemory) service request with a memory start address and a memory size value set for parameter RoutineControlOptionRecord and the SPRMIB not set.StatementThe client posts a physically addressed RoutineControl (0x31) (eraseMemory) service request with a memory start address and a memory size value set for parameter RoutineControlOptionRecord and the SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0124 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0125 | Implementation hint: The server resets the “application valid” flag (C1, see CVS124StatementImplementation hint: The server resets the “application valid” flag (C1, see CVS124 | None | None | None | None | RFQX-CVS123-2-0125 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0126 | ) before the erase process starts, to ensure that the server will start in boot loader mode if the programming gets interrupted or if the programming is faulty.Statement) before the erase process starts, to ensure that the server will start in boot loader mode if the programming gets interrupted or if the programming is faulty. | None | None | None | None | RFQX-CVS123-2-0126 / 32h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0127 | The server erases the applicable SW identification DIDs, see Erase Memory routine requirements in 8.3.StatementThe server erases the applicable SW identification DIDs, see Erase Memory routine requirements in 8.3. | None | None | None | None | RFQX-CVS123-2-0127 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0128 | The client posts physically addressed RequestDownload (0x34) service requests with the SPRMIB not set.StatementThe client posts physically addressed RequestDownload (0x34) service requests with the SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0128 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0129 | If the boot software module is updated in this step, DID 0xF180 (bootSoftwareIdentificationDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the boot software module.StatementIf the boot software module is updated in this step, DID 0xF180 (bootSoftwareIdentificationDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the boot software module. | None | None | None | None | RFQX-CVS123-2-0129 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0130 | If the application software module is updated in this step, DID 0xF181 (applicationSoftwareIdentificationDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application software module.StatementIf the application software module is updated in this step, DID 0xF181 (applicationSoftwareIdentificationDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application software module. | None | None | None | None | RFQX-CVS123-2-0130 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0131 | If the application data module is updated in this step DID 0xF182 (applicationDataIdentificationDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application data module.StatementIf the application data module is updated in this step DID 0xF182 (applicationDataIdentificationDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application data module. | None | None | None | None | RFQX-CVS123-2-0131 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0132 | If the application software module is updated in this step, DID 0xF187 (vehicleManufacturerSparePartNumberDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application data module.StatementIf the application software module is updated in this step, DID 0xF187 (vehicleManufacturerSparePartNumberDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application data module. | None | None | None | None | RFQX-CVS123-2-0132 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0133 | If the application software module is updated in this step, DID 0xF188 (vehicleManufacturerECUSoftwareNumberDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application software module.StatementIf the application software module is updated in this step, DID 0xF188 (vehicleManufacturerECUSoftwareNumberDataIdentifier) will be automatically updated as well as this ID will be implemented as part of the application software module. | None | None | None | None | RFQX-CVS123-2-0133 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0134 | It is client specific if P1Pro10 will be sent as part of programming phase #1.StatementIt is client specific if P1Pro10 will be sent as part of programming phase #1. | None | None | None | None | RFQX-CVS123-2-0134 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0135 | This routineIdentifier is supported to allow process improvement during the software update since it allows client to react as soon as a corruption is identified in the transferred module data.StatementThis routineIdentifier is supported to allow process improvement during the software update since it allows client to react as soon as a corruption is identified in the transferred module data. | None | None | None | None | RFQX-CVS123-2-0135 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0136 | The client posts a physically addressed RoutineControl (0x31) (checkMemory) service request with the SPRMIB not set.StatementThe client posts a physically addressed RoutineControl (0x31) (checkMemory) service request with the SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0136 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0137 | According toStatementAccording to | None | None | None | None | RFQX-CVS123-2-0137 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0138 | , this routineIdentifier allows the server to verify if the transferred data is correct (has not been corrupted) by calculating a checksum and comparing this checksum with the checksum transferred as part of the data (via transferData).Statement, this routineIdentifier allows the server to verify if the transferred data is correct (has not been corrupted) by calculating a checksum and comparing this checksum with the checksum transferred as part of the data (via transferData). | None | None | None | None | RFQX-CVS123-2-0138 / 18h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0139 | The response of this routineIdentifier allows the client to identify if the specific transferred block is corrupted.StatementThe response of this routineIdentifier allows the client to identify if the specific transferred block is corrupted. | None | None | None | None | RFQX-CVS123-2-0139 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0140 | According toStatementAccording to | None | None | None | None | RFQX-CVS123-2-0140 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0141 | , as a part of the consistency check the server verifies the integrity of the programmed software.Statement, as a part of the consistency check the server verifies the integrity of the programmed software. | None | None | None | None | RFQX-CVS123-2-0141 / 5h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0142 | According toStatementAccording to | None | None | None | None | RFQX-CVS123-2-0142 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0143 | , the check on consistency can produce a positive result only if the integrity verification is valid, the software was successfully installed and the installed software are compatible between all software module and the software is compatible with the ECU hardware.Statement, the check on consistency can produce a positive result only if the integrity verification is valid, the software was successfully installed and the installed software are compatible between all software module and the software is compatible with the ECU hardware. | None | None | None | None | RFQX-CVS123-2-0143 / 18h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0144 | As part of the routine checks, the server will use the information defined in SDSC to perform the software verification, see 9.2.StatementAs part of the routine checks, the server will use the information defined in SDSC to perform the software verification, see 9.2. | None | None | None | None | RFQX-CVS123-2-0144 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0145 | Implementation hint: The integrity information may contain parts of memory not programmed, regardless of this the server verifies the integrity according to the supplied information on SDSC, see 9.StatementImplementation hint: The integrity information may contain parts of memory not programmed, regardless of this the server verifies the integrity according to the supplied information on SDSC, see 9. | None | None | None | None | RFQX-CVS123-2-0145 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0146 | The sequence shown in the following figure shows the post-programming step of phase #1.StatementThe sequence shown in the following figure shows the post-programming step of phase #1. | None | None | None | None | RFQX-CVS123-2-0146 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0147 | After the consistency check (independent of the result), the client initiates a server restart by posting a physically addressed ECUReset (0x11) (hardReset) service request with the SPRMIB not set.StatementAfter the consistency check (independent of the result), the client initiates a server restart by posting a physically addressed ECUReset (0x11) (hardReset) service request with the SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0147 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0148 | The server responds positively to the request before the reset takes place.StatementThe server responds positively to the request before the reset takes place. | None | None | None | None | RFQX-CVS123-2-0148 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0149 | After reset, if the ECU hardware/software is deemed to be consistent and all software and data identification DIDs in CVS124 which have been flashed or written as part of the programmingStatementAfter reset, if the ECU hardware/software is deemed to be consistent and all software and data identification DIDs in CVS124 which have been flashed or written as part of the programming | None | None | None | None | RFQX-CVS123-2-0149 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0150 | The application reads and applies the boot parameter values from the boot parameter module.StatementThe application reads and applies the boot parameter values from the boot parameter module. | None | None | None | None | RFQX-CVS123-2-0150 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0151 | Implementation hint: The boot manager checks the “application valid” flag (C1) to see if the ECU hardware/software is consistent and all software and data identification DIDs in CVS124 contain non-default values.StatementImplementation hint: The boot manager checks the “application valid” flag (C1) to see if the ECU hardware/software is consistent and all software and data identification DIDs in CVS124 contain non-default values. | None | None | None | None | RFQX-CVS123-2-0151 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0152 | If the application was started, it checks if application initialization is required.StatementIf the application was started, it checks if application initialization is required. | None | None | AD-001 | component | RFQX-CVS123-2-0152 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0153 | If so, the server performs the required checks/reorganization measures for the data structures (EEPROM data, operational data, adaptive data etc.), executes the self-test and stores event memory entries, default values, DIDs F1AB, F1AA, F1A9 etc.StatementIf so, the server performs the required checks/reorganization measures for the data structures (EEPROM data, operational data, adaptive data etc.), executes the self-test and stores event memory entries, default values, DIDs F1AB, F1AA, F1A9 etc. | None | None | AD-006 | component | RFQX-CVS123-2-0153 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0154 | Implementation hint: The ECU application checks the reprogrammed flag (C3, see programming step P1Pro11) to see if application initialization is required.StatementImplementation hint: The ECU application checks the reprogrammed flag (C3, see programming step P1Pro11) to see if application initialization is required. | None | None | AD-001 | component | RFQX-CVS123-2-0154 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0155 | Implementation hint: If the “application valid” flag (C1) indicates that the ECU application state is not valid, the boot manager will execute the boot loader.StatementImplementation hint: If the “application valid” flag (C1) indicates that the ECU application state is not valid, the boot manager will execute the boot loader. | None | None | None | None | RFQX-CVS123-2-0155 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0156 | If the boot loader is executed and a boot parameter module exists, the boot loader reads and applies the boot parameter values from this module.StatementIf the boot loader is executed and a boot parameter module exists, the boot loader reads and applies the boot parameter values from this module. | None | None | None | None | RFQX-CVS123-2-0156 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0157 | According toStatementAccording to | None | None | None | None | RFQX-CVS123-2-0157 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0158 | , the client post physically addressed authentication (0x29) request with subfunction deAuthenticate (0x00) based on CVS31 with SPRMIB not set.Statement, the client post physically addressed authentication (0x29) request with subfunction deAuthenticate (0x00) based on CVS31 with SPRMIB not set. | None | None | None | None | RFQX-CVS123-2-0158 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0159 | The client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00).StatementThe client post physically addressed RoutineControl (0x31) (EMP) service request with SPRMIB not set and operation-type set to Set (0x00). | None | None | None | None | RFQX-CVS123-2-0159 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0160 | In this step, it is client dependent if and what entities are relevant to be set after updating the software.StatementIn this step, it is client dependent if and what entities are relevant to be set after updating the software. | None | None | None | None | RFQX-CVS123-2-0160 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0161 | As example, the client may have identified that the new software requires an updated RBAC configuration file and therefore set the entity on the server via EMP.StatementAs example, the client may have identified that the new software requires an updated RBAC configuration file and therefore set the entity on the server via EMP. | None | None | AD-001 | component | RFQX-CVS123-2-0161 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0162 | For reference on EMP control routine, see CVS33.StatementFor reference on EMP control routine, see CVS33. | None | None | None | None | RFQX-CVS123-2-0162 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0163 | The programming phase #2 (server configuration or also known as parametrization) as defined in ISO 14229-2 is defined in CVS36.StatementThe programming phase #2 (server configuration or also known as parametrization) as defined in ISO 14229-2 is defined in CVS36. | None | None | None | None | RFQX-CVS123-2-0163 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0164 | ECUs that will be programmed stand-alone at the vehicle manufacturer over DoCAN shall support 1 Mbit transfer speed.StatementECUs that will be programmed stand-alone at the vehicle manufacturer over DoCAN shall support 1 Mbit transfer speed. | SSR-UPD-003 | Secure software update and flash readiness — Software Update / Flashing | AD-002 | component | RFQX-CVS123-2-0164 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0165 | Whether or not the ECU shall support stand-alone programming at the vehicle manufacturer premises shall be discussed and agreed with the vehicle manufacturer.StatementWhether or not the ECU shall support stand-alone programming at the vehicle manufacturer premises shall be discussed and agreed with the vehicle manufacturer. | SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | AD-006 | component | RFQX-CVS123-2-0165 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0166 | A server that is running in the application shall respond with the same diagnostic address after a switch to boot.StatementA server that is running in the application shall respond with the same diagnostic address after a switch to boot. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0166 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0167 | It shall be possible to downgrade server software modules as long as the programmed modules are compatible with each other and with the hardware configuration.StatementIt shall be possible to downgrade server software modules as long as the programmed modules are compatible with each other and with the hardware configuration. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0167 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0168 | Application software and application data modules shall be programmable in any order.StatementApplication software and application data modules shall be programmable in any order. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0168 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0169 | The server shall be able to update an individual module independently from any other module.StatementThe server shall be able to update an individual module independently from any other module. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0169 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0170 | This is to keep the programming time to a minimum.StatementThis is to keep the programming time to a minimum. | None | None | None | None | RFQX-CVS123-2-0170 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0171 | If the performance requirementsStatementIf the performance requirements | None | None | None | None | RFQX-CVS123-2-0171 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0172 | orStatementor | None | None | None | None | RFQX-CVS123-2-0172 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0173 | cannot be met, a compression method shall be implemented.Statementcannot be met, a compression method shall be implemented. | SSR-COM-002 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS123-2-0173 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0174 | This is to shorten the time for the data transfer from the tester to the ECU to be programmed.StatementThis is to shorten the time for the data transfer from the tester to the ECU to be programmed. | None | None | None | None | RFQX-CVS123-2-0174 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0175 | The LZSS algorithm with a dictionary size of 1 023 bytes or a newer compression/decompression method with a higher compression ratio shall be used as the compression/decompression algorithm.StatementThe LZSS algorithm with a dictionary size of 1 023 bytes or a newer compression/decompression method with a higher compression ratio shall be used as the compression/decompression algorithm. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0175 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0176 | The use of alternative compression/decompression algorithms shall be agreed with the vehicle manufacturer.StatementThe use of alternative compression/decompression algorithms shall be agreed with the vehicle manufacturer. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0176 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0177 | It shall be possible to program the same software version repeatedly.StatementIt shall be possible to program the same software version repeatedly. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0177 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0178 | If at startup the ECU hardware/software is consistent and a programming request is not pending, the boot manager shall start and execute the application.StatementIf at startup the ECU hardware/software is consistent and a programming request is not pending, the boot manager shall start and execute the application. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0178 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0179 | Otherwise if at startup the ECU hardware/software is inconsistent the boot manager shall start and execute the boot loader and reset DIDs 0xF181, 0xF187 and 0xF188 and 0xF1A1 to default values.StatementOtherwise if at startup the ECU hardware/software is inconsistent the boot manager shall start and execute the boot loader and reset DIDs 0xF181, 0xF187 and 0xF188 and 0xF1A1 to default values. | SSR-BOOT-005 | Bootloader and Application State Handling — Bootloader and Application State Handling | AD-001 | component | RFQX-CVS123-2-0179 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0180 | In case of e.g., flash interruption resetting the DIDs to default values will enable the client to identify the ECU as not having a valid application.StatementIn case of e.g., flash interruption resetting the DIDs to default values will enable the client to identify the ECU as not having a valid application. | None | None | None | None | RFQX-CVS123-2-0180 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0181 | If at startup the boot manager starts and executes the application, the application shall read and apply the parameter values persisted in the boot parameter module.StatementIf at startup the boot manager starts and executes the application, the application shall read and apply the parameter values persisted in the boot parameter module. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0181 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0182 | Otherwise if at startup the boot manager starts and executes the boot loader and a valid boot parameter module has been successfully programmed, the boot loader shall read and apply these parameter values from the boot parameter module.StatementOtherwise if at startup the boot manager starts and executes the boot loader and a valid boot parameter module has been successfully programmed, the boot loader shall read and apply these parameter values from the boot parameter module. | None | None | AD-008 | component | RFQX-CVS123-2-0182 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0183 | Otherwise if no boot parameter module has been successfully programmed, the boot loader shall apply the corresponding parameter values persisted in the boot loader module.StatementOtherwise if no boot parameter module has been successfully programmed, the boot loader shall apply the corresponding parameter values persisted in the boot loader module. | None | None | AD-008 | component | RFQX-CVS123-2-0183 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0184 | After reprogramming, the application shall store DIDs F1AB, F1AA, F1A9.StatementAfter reprogramming, the application shall store DIDs F1AB, F1AA, F1A9. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0184 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0185 | The technical implementation of the programming preconditions shall be agreed between the supplier and the vehicle manufacturer.StatementThe technical implementation of the programming preconditions shall be agreed between the supplier and the vehicle manufacturer. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0185 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0186 | A programmable server shall guarantee re-programmability within the normal operating voltage range specified by [11] for 24V systems or [12] for 12V systems.StatementA programmable server shall guarantee re-programmability within the normal operating voltage range specified by [11] for 24V systems or [12] for 12V systems. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0186 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0187 | A server that is restarted for any reason or thrown back to DefaultSession due to lack of TesterPresent or unfulfilled preconditions shall always support programming from the start of the programming sequence (programming step P1Pre), i.e., shall not depend on any state from an interrupted programming sequence.StatementA server that is restarted for any reason or thrown back to DefaultSession due to lack of TesterPresent or unfulfilled preconditions shall always support programming from the start of the programming sequence (programming step P1Pre), i.e., shall not depend on any state from an interrupted programming sequence. | SSR-UPD-003 | Secure software update and flash readiness — Software Update / Flashing | AD-002 | component | RFQX-CVS123-2-0187 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0188 | The server shall guarantee re-programmability in the event of error conditions during the programming process regardless of cause.StatementThe server shall guarantee re-programmability in the event of error conditions during the programming process regardless of cause. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0188 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0189 | The causes specified in (ISO14229-1:2020) shall be regarded as examples.StatementThe causes specified in (ISO14229-1:2020) shall be regarded as examples. | None | None | AD-008 | component | RFQX-CVS123-2-0189 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0190 | The server shall be re-programmable (standalone and in the vehicle) regardless of whether the application and application data is valid or has been corrupted.StatementThe server shall be re-programmable (standalone and in the vehicle) regardless of whether the application and application data is valid or has been corrupted. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0190 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0191 | This means, for example, that loss of application server specific diagnostic address, -bitrate or - system name as a result of a failure during boot parameter module programming in the workshop is not acceptable.StatementThis means, for example, that loss of application server specific diagnostic address, -bitrate or - system name as a result of a failure during boot parameter module programming in the workshop is not acceptable. | None | None | None | None | RFQX-CVS123-2-0191 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0192 | Diagnostic services support shall be as per CVS124.StatementDiagnostic services support shall be as per CVS124. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0192 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0193 | Additionally, the services specified in Table 3 shall be supported.StatementAdditionally, the services specified in Table 3 shall be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0193 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0194 | In case of divergences between CVS124 and Table 3, this document takes precedence.StatementIn case of divergences between CVS124 and Table 3, this document takes precedence. | None | None | None | None | RFQX-CVS123-2-0194 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0195 | For a server, it is the combination of services support in CVS124 and Table 3 that will constitute the complete picture of supported services.StatementFor a server, it is the combination of services support in CVS124 and Table 3 that will constitute the complete picture of supported services. | None | None | None | None | RFQX-CVS123-2-0195 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0196 | ECU identification data support shall be as per CVS124.StatementECU identification data support shall be as per CVS124. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-CVS123-2-0196 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0197 | When programmed in the vehicle manufacturer’s production facility the total time for programming of all modules shall not exceed 90 seconds with the programming sequence described in chapter Programming phase #1 – Download of application software and/or application data (phase #1 and phase #2).StatementWhen programmed in the vehicle manufacturer’s production facility the total time for programming of all modules shall not exceed 90 seconds with the programming sequence described in chapter Programming phase #1 – Download of application software and/or application data (phase #1 and phase #2). | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0197 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0198 | This does not apply to ECUs for which all software modules are pre-programmed in supplier premises, even if a software update capability is required in vehicle manufacturer production premises, e.g., for bug fixing.StatementThis does not apply to ECUs for which all software modules are pre-programmed in supplier premises, even if a software update capability is required in vehicle manufacturer production premises, e.g., for bug fixing. | None | None | AD-001 | component | RFQX-CVS123-2-0198 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0199 | When programmed in the workshop the total time for programming of all modules shall not exceed 10 minutes with the programming sequence described in chapter Programming phase #1 – Download of application software and/or application data (phase #1 and phase #2).StatementWhen programmed in the workshop the total time for programming of all modules shall not exceed 10 minutes with the programming sequence described in chapter Programming phase #1 – Download of application software and/or application data (phase #1 and phase #2). | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0199 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0200 | The server shall support the routines specified in Table 4.StatementThe server shall support the routines specified in Table 4. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0200 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0201 | If the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall start erasing the memory area specified with the RequestDownload request.StatementIf the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall start erasing the memory area specified with the RequestDownload request. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-CVS123-2-0201 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0202 | In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint.StatementIn order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint. | None | None | None | None | RFQX-CVS123-2-0202 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0203 | If the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall reset the following identification DIDs to their default values: • If boot software download is requested, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules).StatementIf the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall reset the following identification DIDs to their default values: • If boot software download is requested, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules). | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0203 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0204 | Once the RequestDownload service has started, only services TesterPresent, ECUReset,TransferData and DiagnosticSessionControl shall be permitted until service RequestTransferExit has been called or until any of these services returns an error.StatementOnce the RequestDownload service has started, only services TesterPresent, ECUReset,TransferData and DiagnosticSessionControl shall be permitted until service RequestTransferExit has been called or until any of these services returns an error. | SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-001 | component | RFQX-CVS123-2-0204 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0205 | If a non-permitted service is requested after the RequestDownload service has started and before RequestTransferExit has been called the server shall respond with NRC 0x24StatementIf a non-permitted service is requested after the RequestDownload service has started and before RequestTransferExit has been called the server shall respond with NRC 0x24 | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0205 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0206 | (requestSequenceError) and shall accept programming to proceed from the state at which it was executing before this non-permitted service was requested.Statement(requestSequenceError) and shall accept programming to proceed from the state at which it was executing before this non-permitted service was requested. | None | None | AD-001 | component | RFQX-CVS123-2-0206 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0207 | For each received RequestDownload request, the server shall check if there is a VerificationEntry match in SDSC.StatementFor each received RequestDownload request, the server shall check if there is a VerificationEntry match in SDSC. | SSR-VV-002 | Security evidence and traceability — Verification and Validation | AD-002 | component | RFQX-CVS123-2-0207 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0208 | For more information on SDSC, see chapter 9.StatementFor more information on SDSC, see chapter 9. | None | None | None | None | RFQX-CVS123-2-0208 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0209 | The server shall check whether any part of the received data is encrypted or not by checking the address ranges for a match in EncryptionEntry defined in SDSC.StatementThe server shall check whether any part of the received data is encrypted or not by checking the address ranges for a match in EncryptionEntry defined in SDSC. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0209 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0210 | If an encryptionEntry match is found, see chapter 9.3.StatementIf an encryptionEntry match is found, see chapter 9.3. | None | None | None | None | RFQX-CVS123-2-0210 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0211 | The server shall not execute the new software until it can be verified using routine 0xFF01.StatementThe server shall not execute the new software until it can be verified using routine 0xFF01. | SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS123-2-0211 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0212 | The software to be received over TransferData (0x36) is to be considered NOT_OK until a verification takes place.StatementThe software to be received over TransferData (0x36) is to be considered NOT_OK until a verification takes place. | None | None | None | None | RFQX-CVS123-2-0212 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0213 | The server shall support service request formatted according to Table 5.StatementThe server shall support service request formatted according to Table 5. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0213 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0214 | The server shall support service positive response formatted according to Table 6.StatementThe server shall support service positive response formatted according to Table 6. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0214 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0215 | The server shall support service negative response as per ISO14229-1:2020.StatementThe server shall support service negative response as per ISO14229-1:2020. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0215 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0216 | In case a software is encrypted, the server shall decrypt the software before decompression and software hash comparison verification are performed.StatementIn case a software is encrypted, the server shall decrypt the software before decompression and software hash comparison verification are performed. | SSR-VV-003 | Security evidence and traceability — Verification and Validation | AD-001 | component | RFQX-CVS123-2-0216 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0217 | In case a software is compressed, the server shall decompress the software before software hash comparison verification is performed.StatementIn case a software is compressed, the server shall decompress the software before software hash comparison verification is performed. | SSR-VV-003 | Security evidence and traceability — Verification and Validation | AD-001 | component | RFQX-CVS123-2-0217 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0218 | The server shall verify the software hash after decryption and/or decompression are performed.StatementThe server shall verify the software hash after decryption and/or decompression are performed. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0218 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0219 | Considering that hashing, compression and encryption methods were used prior to transfer a software to the server, the server will decrypt, decompress, and perform software hashing comparison verification in this respective order.StatementConsidering that hashing, compression and encryption methods were used prior to transfer a software to the server, the server will decrypt, decompress, and perform software hashing comparison verification in this respective order. | None | None | None | None | RFQX-CVS123-2-0219 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0220 | The server shall support parameter dataFormatIdentifier formatted according to Table 7.StatementThe server shall support parameter dataFormatIdentifier formatted according to Table 7. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0220 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0221 | Negative ResponseStatementNegative Response | None | None | None | None | RFQX-CVS123-2-0221 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0222 | The server shall support parameter addressAndLengthFormatIdentifier formatted according to Table 8.StatementThe server shall support parameter addressAndLengthFormatIdentifier formatted according to Table 8. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0222 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0223 | Table 8: Service 0x34 addressAndLengthFormatIdentifier Format Bits Description Cvt Values 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 7.1.4.3 Parameter lengthFormatIdentifier The server shall support parameter lengthFormatIdentifier formatted according to Table 9.StatementTable 8: Service 0x34 addressAndLengthFormatIdentifier Format Bits Description Cvt Values 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 7.1.4.3 Parameter lengthFormatIdentifier The server shall support parameter lengthFormatIdentifier formatted according to Table 9. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0223 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0224 | The server shall support request formatted according to ISO14229-1:2020.StatementThe server shall support request formatted according to ISO14229-1:2020. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0224 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0225 | The server shall support positive response formatted according to ISO14229-1:2020.StatementThe server shall support positive response formatted according to ISO14229-1:2020. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0225 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0226 | If for any reason an error occurs during decryption of data, the server shall return NRC 0x10.StatementIf for any reason an error occurs during decryption of data, the server shall return NRC 0x10. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0226 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0227 | The server shall support parameter blockSequenceCounter formatted according to ISO14229-1:2020.StatementThe server shall support parameter blockSequenceCounter formatted according to ISO14229-1:2020. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0227 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0228 | The server shall support parameter transferRequestParameterRecord formatted according to ISO14229-1:2020.StatementThe server shall support parameter transferRequestParameterRecord formatted according to ISO14229-1:2020. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0228 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0229 | The server shall support request formatted according to Table 10.StatementThe server shall support request formatted according to Table 10. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0229 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0230 | The server shall support positive response formatted according to Table 11.StatementThe server shall support positive response formatted according to Table 11. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0230 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0231 | 7.3.4 Service 0x37 Parameters 7.3.4.1 Parameter transferRequestParameterRecordStatement7.3.4 Service 0x37 Parameters 7.3.4.1 Parameter transferRequestParameterRecord | None | None | None | None | RFQX-CVS123-2-0231 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0232 | The server shall not support transferRequestParameterRecord parameter.StatementThe server shall not support transferRequestParameterRecord parameter. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0232 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0233 | The server shall not support transferResponseParameterRecord parameter.StatementThe server shall not support transferResponseParameterRecord parameter. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0233 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0234 | The server shall support service 0x84 according to CVS32.StatementThe server shall support service 0x84 according to CVS32. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0234 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0235 | The server shall support request formatted according to ISO14229-1:2020.StatementThe server shall support request formatted according to ISO14229-1:2020. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0235 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0236 | Negative ResponseStatementNegative Response | None | None | None | None | RFQX-CVS123-2-0236 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0237 | The server shall support positive response formatted according to ISO14229-1:2020.StatementThe server shall support positive response formatted according to ISO14229-1:2020. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0237 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0238 | The server shall support negative response codes according to CVS32.StatementThe server shall support negative response codes according to CVS32. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0238 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0239 | The server shall support parameter Administrative Parameter formatted according to ISO14229-1:2020.StatementThe server shall support parameter Administrative Parameter formatted according to ISO14229-1:2020. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0239 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0240 | The server shall support parameter Signature/Encryption Calculation (SIGENCRYPT) according to CVS32.StatementThe server shall support parameter Signature/Encryption Calculation (SIGENCRYPT) according to CVS32. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS123-2-0240 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0241 | The server shall support parameter Anti-replay Counter (ANTIREPLAYCNT) according to CVS32.StatementThe server shall support parameter Anti-replay Counter (ANTIREPLAYCNT) according to CVS32. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS123-2-0241 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0242 | The server shall support the routine in the diagnosticSession according to Table 12.StatementThe server shall support the routine in the diagnosticSession according to Table 12. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0242 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0243 | The server shall support the routineControlType according to Table 13.StatementThe server shall support the routineControlType according to Table 13. | SSR-CON-002 | Cybersecurity Concept and Evidence — Cybersecurity Concept and Evidence | AD-007 | component | RFQX-CVS123-2-0243 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0244 | Table 13: Routine Support per routineControlType RID Name routineControlType startRoutine (0x01) stopRoutine (0x02) requestRoutineResults (0x03) 0x2202 Check Memory Block M - - 0xFF00 EraseMemory M - - 0xFF01 CheckProgrammingDependencies M - - 0xCAFE Entity Management Protocol (EMP) M - - M = Mandatory 8.1.3 Routine Safe State Requirement The server shall implement diagnostic safe state, as per CVS124, as preconditions to the routines according to Table 14.StatementTable 13: Routine Support per routineControlType RID Name routineControlType startRoutine (0x01) stopRoutine (0x02) requestRoutineResults (0x03) 0x2202 Check Memory Block M - - 0xFF00 EraseMemory M - - 0xFF01 CheckProgrammingDependencies M - - 0xCAFE Entity Management Protocol (EMP) M - - M = Mandatory 8.1.3 Routine Safe State Requirement The server shall implement diagnostic safe state, as per CVS124, as preconditions to the routines according to Table 14. | SSR-RBAC-002 | Secure software update and flash readiness — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0244 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0245 | Table 14: Routine support for Safe State Conditions RID Name Safe State 0x2202 Check Memory Block M 0xFF00 EraseMemory M - 0xFF01 CheckProgrammingDependencies M M 0xCAFE Entity Management Protocol (EMP) M M M = Mandatory 8.2 Routine 0x2202 – Check Memory Block The RoutineIdentifier allows the client to start a server routine which verifies the correctness of a programmed module.StatementTable 14: Routine support for Safe State Conditions RID Name Safe State 0x2202 Check Memory Block M 0xFF00 EraseMemory M - 0xFF01 CheckProgrammingDependencies M M 0xCAFE Entity Management Protocol (EMP) M M M = Mandatory 8.2 Routine 0x2202 – Check Memory Block The RoutineIdentifier allows the client to start a server routine which verifies the correctness of a programmed module. | None | None | None | None | RFQX-CVS123-2-0245 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0246 | The server shall verify the programmed software module by calculating a checksum on the programmed data by matching this checksum with a pre-calculated checksum.StatementThe server shall verify the programmed software module by calculating a checksum on the programmed data by matching this checksum with a pre-calculated checksum. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0246 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0247 | The pre-calculated checksum shall be provided as part of the data submitted with the TransferData service request.StatementThe pre-calculated checksum shall be provided as part of the data submitted with the TransferData service request. | SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-001 | component | RFQX-CVS123-2-0247 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0248 | It is server specific the generator polynomial and initial value to be used.StatementIt is server specific the generator polynomial and initial value to be used. | None | None | None | None | RFQX-CVS123-2-0248 / 18h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0249 | Implementation Hint: The following generator polynomial with the following initial value are suggested to be used for calculation of the checksum: G(X) = x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 Initial value: 0xFFFFFFFF 8.2.1 RequestStatementImplementation Hint: The following generator polynomial with the following initial value are suggested to be used for calculation of the checksum: G(X) = x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 Initial value: 0xFFFFFFFF 8.2.1 Request | None | None | None | None | RFQX-CVS123-2-0249 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0250 | The server shall support the routine request according to Table 15.StatementThe server shall support the routine request according to Table 15. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0250 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0251 | Table 15: Routine 0x2202 Request Format Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0x22 #4 routineIdentifier (LSB) M 0x02 8.2.2 Positive Response The server shall support the routine positive response according to Table 16.StatementTable 15: Routine 0x2202 Request Format Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0x22 #4 routineIdentifier (LSB) M 0x02 8.2.2 Positive Response The server shall support the routine positive response according to Table 16. | SSR-DIAG-002 | Diagnostic Services — Diagnostic Services | AD-002 | component | RFQX-CVS123-2-0251 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0252 | Table 16: Routine 0x2202 Positive Response Format Byte Description Cvt Byte Value #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkMemory [byte#1] M 0x22 #4 routineIdentifier (LSB) checkMemory [byte#2] M 0x02 #5 routineStatus routineResult M 0x00-0xFF 8.2.3 Negative ResponseStatementTable 16: Routine 0x2202 Positive Response Format Byte Description Cvt Byte Value #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkMemory [byte#1] M 0x22 #4 routineIdentifier (LSB) checkMemory [byte#2] M 0x02 #5 routineStatus routineResult M 0x00-0xFF 8.2.3 Negative Response | None | None | None | None | RFQX-CVS123-2-0252 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0253 | SUV2_REQ 4 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.StatementSUV2_REQ 4 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader. | None | None | None | None | RFQX-CVS123-2-0253 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0254 | The server shall support parameter routineStatus routineResult formatted according to Table 17.StatementThe server shall support parameter routineStatus routineResult formatted according to Table 17. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0254 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0255 | This RoutineIdentifier value allows the client to start a routine which erases ECU internal non- volatile memory.StatementThis RoutineIdentifier value allows the client to start a routine which erases ECU internal non- volatile memory. | None | None | None | None | RFQX-CVS123-2-0255 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0256 | The server shall respond with a positive response code without erasing memory if the specified memory area has already been completely erased (or is writable) at the time the service is requested.StatementThe server shall respond with a positive response code without erasing memory if the specified memory area has already been completely erased (or is writable) at the time the service is requested. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0256 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0257 | In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint.StatementIn order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint. | None | None | None | None | RFQX-CVS123-2-0257 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0258 | In case the non volatile memory area is currently hosting a bootloader copy, meaning there is an ongoing bootloader update procedure, the ECU shall ensure that this memory area shall not be erased until a valid bootloader is flashed in the bootloader memory area.StatementIn case the non volatile memory area is currently hosting a bootloader copy, meaning there is an ongoing bootloader update procedure, the ECU shall ensure that this memory area shall not be erased until a valid bootloader is flashed in the bootloader memory area. | SSR-BOOT-002 | Secure software update and flash readiness — Bootloader and Application State Handling | AD-006 | component | RFQX-CVS123-2-0258 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0259 | prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.Statementprevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader. | None | None | None | None | RFQX-CVS123-2-0259 / 26h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0260 | When the addressAndLengthFormatIdentifier parameter is set to a value > 0x00 the server shall reset the following software and data identification DIDs to their default values (see section Software and data identification): • If boot software (any part) is erased, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules).StatementWhen the addressAndLengthFormatIdentifier parameter is set to a value > 0x00 the server shall reset the following software and data identification DIDs to their default values (see section Software and data identification): • If boot software (any part) is erased, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules). | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0260 / 16h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0261 | The erasing of memory shall not prevent the client from starting a data transfer using the TransferData (0x36) service, i.e., the erasing of memory shall proceed in parallel with data transfer in case for ECUs implementing Automatic erase.StatementThe erasing of memory shall not prevent the client from starting a data transfer using the TransferData (0x36) service, i.e., the erasing of memory shall proceed in parallel with data transfer in case for ECUs implementing Automatic erase. | SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-001 | component | RFQX-CVS123-2-0261 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0262 | The server shall support the routine request according to Table 18.StatementThe server shall support the routine request according to Table 18. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0262 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0263 | The server shall support the routine positive response according to Table 19.StatementThe server shall support the routine positive response according to Table 19. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0263 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0264 | 8.3.4 Routine 0xFF00 Parameters 8.3.4.1 Parameter addressAndLengthFormatIdentifierStatement8.3.4 Routine 0xFF00 Parameters 8.3.4.1 Parameter addressAndLengthFormatIdentifier | None | None | None | None | RFQX-CVS123-2-0264 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0265 | The server shall support parameter addressAndLengthFormatIdentifier formatted according to Table 20.StatementThe server shall support parameter addressAndLengthFormatIdentifier formatted according to Table 20. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0265 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0266 | E.g., 02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M C = Mandatory if required to meet the performance requirements &StatementE.g., 02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M C = Mandatory if required to meet the performance requirements & | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0266 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0267 | .Statement. | None | None | None | None | RFQX-CVS123-2-0267 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0268 | When the addressAndLengthFormatIdentifier is set to 0x01 the defined module to index mapping shall apply for the memoryStartAddress according to Table 21.StatementWhen the addressAndLengthFormatIdentifier is set to 0x01 the defined module to index mapping shall apply for the memoryStartAddress according to Table 21. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0268 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0269 | The server shall support parameter routineStatus routineResult formatted according to Table 22.StatementThe server shall support parameter routineStatus routineResult formatted according to Table 22. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0269 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0270 | This RoutineIdentifier value allows the client to start a consistency check of the server.StatementThis RoutineIdentifier value allows the client to start a consistency check of the server. | None | None | None | None | RFQX-CVS123-2-0270 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0271 | This RoutineIdentifier shall be able to execute independent from programming sequenceStatementThis RoutineIdentifier shall be able to execute independent from programming sequence | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS123-2-0271 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0272 | The client may opt to execute this routineIdentifier as a standalone procedure to check to perform a software consistency check.StatementThe client may opt to execute this routineIdentifier as a standalone procedure to check to perform a software consistency check. | None | None | None | None | RFQX-CVS123-2-0272 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0273 | The server shall check whether the individual modules are complete and compatible with one another.StatementThe server shall check whether the individual modules are complete and compatible with one another. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0273 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0274 | In addition, a check shall be made to determine whether the software is compatible with the hardware version (e.g., variants of sensors/actuators) and other data structures (e.g., EEPROM data).StatementIn addition, a check shall be made to determine whether the software is compatible with the hardware version (e.g., variants of sensors/actuators) and other data structures (e.g., EEPROM data). | None | None | AD-001 | component | RFQX-CVS123-2-0274 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0275 | The method used to check compatibility/consistency shall be determined by the supplier in consultation with the vehicle manufacturer.StatementThe method used to check compatibility/consistency shall be determined by the supplier in consultation with the vehicle manufacturer. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0275 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0276 | The consistency check shall be carried out solely by the server.StatementThe consistency check shall be carried out solely by the server. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0276 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0277 | The server shall verify the integrity of the software as a part of the consistency check.StatementThe server shall verify the integrity of the software as a part of the consistency check. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0277 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0278 | The integrity information shall be supplied to the server before the software is updated.StatementThe integrity information shall be supplied to the server before the software is updated. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0278 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0279 | The integrity check shall be carried out solely by the server.StatementThe integrity check shall be carried out solely by the server. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS123-2-0279 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0280 | Details over the integrity check can be found on chapter 9.2.StatementDetails over the integrity check can be found on chapter 9.2. | None | None | None | None | RFQX-CVS123-2-0280 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0281 | The server shall support the routine request according to Table 23.StatementThe server shall support the routine request according to Table 23. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0281 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0282 | The server shall support the routine positive response according to Table 24.StatementThe server shall support the routine positive response according to Table 24. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0282 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0283 | 8.4.4 Routine 0xFF01 Parameters 8.4.4.1 Parameter routineStatus routineResultStatement8.4.4 Routine 0xFF01 Parameters 8.4.4.1 Parameter routineStatus routineResult | None | None | None | None | RFQX-CVS123-2-0283 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0284 | The server shall support parameter routineStatus routineResult formatted according to Table 25.StatementThe server shall support parameter routineStatus routineResult formatted according to Table 25. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0284 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0285 | Table 25: Routine 0xFF01 routineStatus routineResult Format Hex Description Cvt 0x00 correctResult M 0x01 incorrectResult - General Failure M 0x02 incorrectResult error SW – HW M 0x03 incorrectResult error SW – SW M 0x04 IncorrectResult One or more modules are not programmed or are incorrectly programmed M 0x05 incorrectResult One or more modules failed when verifying the integrity of the software M 0x06 – 0xFF Reserved M The server shall set routineResult as 0x00 (correctResult) if the integrity verification is valid, the software was successfully installed and the installed software are compatible between all software module and the software is compatible with the ECU hardware.StatementTable 25: Routine 0xFF01 routineStatus routineResult Format Hex Description Cvt 0x00 correctResult M 0x01 incorrectResult - General Failure M 0x02 incorrectResult error SW – HW M 0x03 incorrectResult error SW – SW M 0x04 IncorrectResult One or more modules are not programmed or are incorrectly programmed M 0x05 incorrectResult One or more modules failed when verifying the integrity of the software M 0x06 – 0xFF Reserved M The server shall set routineResult as 0x00 (correctResult) if the integrity verification is valid, the software was successfully installed and the installed software are compatible between all software module and the software is compatible with the ECU hardware. | SSR-DAI-005 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0285 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0286 | If the server set routineResult as 0x00 (CorrectResult) the server shall reject with NRC 0x24 the following diagnostic services and routines until a new SDSC is providedStatementIf the server set routineResult as 0x00 (CorrectResult) the server shall reject with NRC 0x24 the following diagnostic services and routines until a new SDSC is provided | None | None | AD-007 | component | RFQX-CVS123-2-0286 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0287 | • Routine 0xFF00 Erase MemoryStatement• Routine 0xFF00 Erase Memory | None | None | None | None | RFQX-CVS123-2-0287 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0288 | • Service 0x34 RequestDownloadStatement• Service 0x34 RequestDownload | None | None | None | None | RFQX-CVS123-2-0288 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0289 | • Service 0x36 TransferDataStatement• Service 0x36 TransferData | None | None | None | None | RFQX-CVS123-2-0289 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0290 | • Service 0x37 RequestTransferExit 8.4.4.2 Parameter routineResultProofLengthStatement• Service 0x37 RequestTransferExit 8.4.4.2 Parameter routineResultProofLength | None | None | None | None | RFQX-CVS123-2-0290 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0291 | This parameter consist of the length of the routineResultProof parameter.StatementThis parameter consist of the length of the routineResultProof parameter. | None | None | None | None | RFQX-CVS123-2-0291 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0292 | The server shall hash the receipt number with the routineStatus routineResult parameter, in this respective order.StatementThe server shall hash the receipt number with the routineStatus routineResult parameter, in this respective order. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0292 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0293 | The receipt number is received as part of the EMP message whenever a SDSC is set, please refer to CVS34.StatementThe receipt number is received as part of the EMP message whenever a SDSC is set, please refer to CVS34. | None | None | None | None | RFQX-CVS123-2-0293 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0294 | The hash algorithm shall be SHA512.StatementThe hash algorithm shall be SHA512. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0294 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0295 | The server shall sign the hashed output using the receipt-keys.StatementThe server shall sign the hashed output using the receipt-keys. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0295 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0296 | For information on receipt-keys, please refer to CVS34.StatementFor information on receipt-keys, please refer to CVS34. | None | None | None | None | RFQX-CVS123-2-0296 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0297 | The server shall use ED25519 as signature algorithm.StatementThe server shall use ED25519 as signature algorithm. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS123-2-0297 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0298 | The server shall return in the parameter routineResultProof the signed hash.StatementThe server shall return in the parameter routineResultProof the signed hash. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0298 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0299 | The client shall send the Servers routineStatus routineResult response to the backend.StatementThe client shall send the Servers routineStatus routineResult response to the backend. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0299 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0300 | SDSC is transmitted via EMP, see chapter 9.StatementSDSC is transmitted via EMP, see chapter 9. | None | None | None | None | RFQX-CVS123-2-0300 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0301 | The SDSC content, including the reference hash used for software verification, is signed as part of the set request when transmitted over EMP.StatementThe SDSC content, including the reference hash used for software verification, is signed as part of the set request when transmitted over EMP. | None | None | None | None | RFQX-CVS123-2-0301 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0302 | Once a SDSC has being accepted by the server, the server shall store in the NVM the receipt number sent over as part of the EMP request.StatementOnce a SDSC has being accepted by the server, the server shall store in the NVM the receipt number sent over as part of the EMP request. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0302 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0303 | Once a SDSC has being accepted by the server, the server shall accept the following diagnostic services and routines: • Routine 0xFF00 Erase MemoryStatementOnce a SDSC has being accepted by the server, the server shall accept the following diagnostic services and routines: • Routine 0xFF00 Erase Memory | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS123-2-0303 / 29h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0304 | • Service 0x34 RequestDownloadStatement• Service 0x34 RequestDownload | None | None | None | None | RFQX-CVS123-2-0304 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0305 | • Service 0x36 TransferDataStatement• Service 0x36 TransferData | None | None | None | None | RFQX-CVS123-2-0305 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0306 | • Service 0x37 RequestTransferExitStatement• Service 0x37 RequestTransferExit | None | None | None | None | RFQX-CVS123-2-0306 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0307 | Negative ResponseStatementNegative Response | None | None | None | None | RFQX-CVS123-2-0307 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0308 | The server shall support the routine request according to Table 26.StatementThe server shall support the routine request according to Table 26. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0308 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0309 | Table 26: Routine 0xCAFE Request Format Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xCA #4 routineIdentifier (LSB) M 0xFE #5 … #n EMP Message M 0x00 – 0xFF 8.5.2 Positive Response The server shall support the routine positive response according to Table 27.StatementTable 26: Routine 0xCAFE Request Format Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xCA #4 routineIdentifier (LSB) M 0xFE #5 … #n EMP Message M 0x00 – 0xFF 8.5.2 Positive Response The server shall support the routine positive response according to Table 27. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0309 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0310 | The server shall support the routine negative response according to CVS33.StatementThe server shall support the routine negative response according to CVS33. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0310 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0311 | The server shall support the parameter EMP message according to CVS33.StatementThe server shall support the parameter EMP message according to CVS33. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0311 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0312 | The information required for the server for verifying software integrity and optionally decrypt the transported data from a trusted source, is described in a Software Data Security Container (SDSC).StatementThe information required for the server for verifying software integrity and optionally decrypt the transported data from a trusted source, is described in a Software Data Security Container (SDSC). | None | None | AD-007 | component | RFQX-CVS123-2-0312 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity; evidence completeness | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0313 | The server shall implement SDSC structure as defined in CVS154.StatementThe server shall implement SDSC structure as defined in CVS154. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0313 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0314 | SDSC supports verification entries, encryption entries and items as defined in DSC.StatementSDSC supports verification entries, encryption entries and items as defined in DSC. | None | None | None | None | RFQX-CVS123-2-0314 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0315 | For the context of SDSC, range is defined as: • Start = memory address offset to be verified/decrypted.StatementFor the context of SDSC, range is defined as: • Start = memory address offset to be verified/decrypted. | None | None | None | None | RFQX-CVS123-2-0315 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0316 | The range start field shall be the memory address offset from the dataLocator field.StatementThe range start field shall be the memory address offset from the dataLocator field. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS123-2-0316 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0317 | The range length field shall be the number of bytes to be verified.StatementThe range length field shall be the number of bytes to be verified. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0317 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0318 | For the context of SDSC, dataLocator is defined as an identification the server uses to locate the software module.StatementFor the context of SDSC, dataLocator is defined as an identification the server uses to locate the software module. | None | None | None | None | RFQX-CVS123-2-0318 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0319 | The supplier shall propose for each software module an identification to be used in dataLocator field in SDSC.StatementThe supplier shall propose for each software module an identification to be used in dataLocator field in SDSC. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0319 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0320 | The vehicle manufacturer shall review and accept the proposals for every dataLocator.StatementThe vehicle manufacturer shall review and accept the proposals for every dataLocator. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS123-2-0320 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0321 | The dataLocator field is used to provide to the server the means to identify which module the verification or encryption entries refer to.StatementThe dataLocator field is used to provide to the server the means to identify which module the verification or encryption entries refer to. | None | None | None | None | RFQX-CVS123-2-0321 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0322 | The start address shall be used as an offset in the software module while the length can be utilized to know which areas of the software module are to be verified and/or decrypted.StatementThe start address shall be used as an offset in the software module while the length can be utilized to know which areas of the software module are to be verified and/or decrypted. | None | None | AD-001 | component | RFQX-CVS123-2-0322 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0323 | Before accepting the SDSC as valid, the server shall perform the sanity check of the received SDSC as defined in CVS154.StatementBefore accepting the SDSC as valid, the server shall perform the sanity check of the received SDSC as defined in CVS154. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0323 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0324 | In DSC sanity check, there is a specific area of application sanity check which depends on the context of the general DSC.StatementIn DSC sanity check, there is a specific area of application sanity check which depends on the context of the general DSC. | None | None | None | None | RFQX-CVS123-2-0324 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0325 | If the sanity check returns fail/invalid, the server shall reject SDSC as described in CVS34.StatementIf the sanity check returns fail/invalid, the server shall reject SDSC as described in CVS34. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0325 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0326 | The server shall validate each VerificationEntry found in the SDSC.StatementThe server shall validate each VerificationEntry found in the SDSC. | SSR-VV-003 | Security evidence and traceability — Verification and Validation | AD-001 | component | RFQX-CVS123-2-0326 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0327 | The referenceHash defines the reference hash value to be used in the hash comparison.StatementThe referenceHash defines the reference hash value to be used in the hash comparison. | None | None | None | None | RFQX-CVS123-2-0327 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0328 | Software hashes in the SDSC shall be verified by the server considering the ranges which are stated in the SDSC.StatementSoftware hashes in the SDSC shall be verified by the server considering the ranges which are stated in the SDSC. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0328 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0329 | The Ranges dictates the data range that the server shall begin, and end read from NVM for hashing.StatementThe Ranges dictates the data range that the server shall begin, and end read from NVM for hashing. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS123-2-0329 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0330 | The Ranges can be one or several if there are gaps between memory areas which shall be excluded from the hash calculation for some reason.StatementThe Ranges can be one or several if there are gaps between memory areas which shall be excluded from the hash calculation for some reason. | None | None | AD-006 | component | RFQX-CVS123-2-0330 / 56h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0331 | When hashing software, the whole memory range, including erased-only bytes of a memory module, shall be possible to include in the hash calculation.StatementWhen hashing software, the whole memory range, including erased-only bytes of a memory module, shall be possible to include in the hash calculation. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS123-2-0331 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0332 | Erased-only bytes are parts of the memory module that are not programmed with data.StatementErased-only bytes are parts of the memory module that are not programmed with data. | None | None | None | None | RFQX-CVS123-2-0332 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0333 | The byte value of an erased data byte (typically FF or 00) depends on the MCU/Flash memory and shall be specified by the software supplier as an input for the hashing process.StatementThe byte value of an erased data byte (typically FF or 00) depends on the MCU/Flash memory and shall be specified by the software supplier as an input for the hashing process. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS123-2-0333 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0334 | The server shall be able to verify that erased-only blocks covered in range of memory are erased.StatementThe server shall be able to verify that erased-only blocks covered in range of memory are erased. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS123-2-0334 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0335 | When the server has verified all verificationEntries, a result OK/NOT_OK shall be returned.StatementWhen the server has verified all verificationEntries, a result OK/NOT_OK shall be returned. | SSR-VV-002 | Security evidence and traceability — Verification and Validation | AD-002 | component | RFQX-CVS123-2-0335 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0336 | If NOT_OK is returned, the server shall not accept the new software for execution.StatementIf NOT_OK is returned, the server shall not accept the new software for execution. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0336 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0337 | If OK is returned, the server shall accept that installed software is valid in terms of integrity.StatementIf OK is returned, the server shall accept that installed software is valid in terms of integrity. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS123-2-0337 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0338 | The server may execute other checks to verify the software before concluding if the installed software shall be accepted.StatementThe server may execute other checks to verify the software before concluding if the installed software shall be accepted. | None | None | AD-001 | component | RFQX-CVS123-2-0338 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0339 | For the received data, where a match is found in the EncryptionEntry of the DSC, the server shall initialize a cipher if not previously initialized.StatementFor the received data, where a match is found in the EncryptionEntry of the DSC, the server shall initialize a cipher if not previously initialized. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS123-2-0339 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS123-2-0340 | An initialized data (i.e., cipher scheme) shall be kept active until no more received data matches the current EncryptionEntry.StatementAn initialized data (i.e., cipher scheme) shall be kept active until no more received data matches the current EncryptionEntry. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0340 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0341 | The cipher shall be reinitialized for each new Encryption entry.StatementThe cipher shall be reinitialized for each new Encryption entry. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0341 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0342 | According to best practise received data shall be decrypted “on the fly” before storing to NVM.StatementAccording to best practise received data shall be decrypted “on the fly” before storing to NVM. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS123-2-0342 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS123-2-0343 | Other methods shall be agreed upon with OEM.StatementOther methods shall be agreed upon with OEM. | None | None | AD-008 | component | RFQX-CVS123-2-0343 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS123-2-0344 | The received data to decrypt may only be parts of a software module and it will be based on the range defined.StatementThe received data to decrypt may only be parts of a software module and it will be based on the range defined. | None | None | None | None | RFQX-CVS123-2-0344 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0345 | EncryptionEntries are not present if software is not encrypted.StatementEncryptionEntries are not present if software is not encrypted. | None | None | None | None | RFQX-CVS123-2-0345 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0346 | The Non-volatile server memory programming complete flow can be found in Annex B.StatementThe Non-volatile server memory programming complete flow can be found in Annex B. | None | None | None | None | RFQX-CVS123-2-0346 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0347 | #008AFFFF #Statement#008AFFFF # | None | None | None | None | RFQX-CVS123-2-0347 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0348 | #00BFFFFF #008B0000 #0092FFFF Module hashData #00AFAAAA #00AFAAAB Figure 8 – Memory layoutStatement#00BFFFFF #008B0000 #0092FFFF Module hashData #00AFAAAA #00AFAAAB Figure 8 – Memory layout | None | None | None | None | RFQX-CVS123-2-0348 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS123-2-0349 | Note that more than one Address field can be specified if there are one or more areas within a memory module which must be excluded in the hash due to some logical restrictions (e.g., boot writing internal data to such area during programming).StatementNote that more than one Address field can be specified if there are one or more areas within a memory module which must be excluded in the hash due to some logical restrictions (e.g., boot writing internal data to such area during programming). | None | None | AD-006 | component | RFQX-CVS123-2-0349 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0350 | #00BFFFFF #008B0000 #0092FFFF Module hashData #00AFAAAA #00AFAAAB When ECU recieves data that matches an address range in an EncryptionEntry (here in Module B), the server must decrypt the data received by TransferData request.Statement#00BFFFFF #008B0000 #0092FFFF Module hashData #00AFAAAA #00AFAAAB When ECU recieves data that matches an address range in an EncryptionEntry (here in Module B), the server must decrypt the data received by TransferData request. | SSR-SDT-002 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-006 | component | RFQX-CVS123-2-0350 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS123-2-0351 | Module B is encrypted meaning that when the server receives data within a range (given as address and size in RequestDownload) the server must decrypt the data before storing it.StatementModule B is encrypted meaning that when the server receives data within a range (given as address and size in RequestDownload) the server must decrypt the data before storing it. | None | None | AD-002 | component | RFQX-CVS123-2-0351 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0001 | The User shall apply the latest version of this CVS124.StatementThe User shall apply the latest version of this CVS124. | None | None | AD-008 | component | RFQX-CVS124-0001 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0002 | Foreword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.StatementForeword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable. | None | None | None | None | RFQX-CVS124-0002 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0003 | Any review of CVS124 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”.StatementAny review of CVS124 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”. | None | None | AD-003 | component | RFQX-CVS124-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0004 | • Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch.Statement• Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch. | None | None | AD-002 | component | RFQX-CVS124-0004 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0005 | TermsStatementTable 1 – Definition of Terms Term Definition Shall This word, or the terms "Required" or "Must", means that the definition is an absolute requirement of the specification. Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification. Should This word, or the adjective “Recommended”, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course. Should not This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. May This word, or the adjective “Optional”, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option shall be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option shall be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides). | None | None | AD-002 | component | RFQX-CVS124-0005 / 18h | Not imported | Still Requires Customer Decision | P1 OPEN | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0006 | AbbreviationsStatementTable 2 – Abbreviated terms Abbreviation Description DID Data Identifier EnvCond Environment Condition FMI Failure Mode Indication Def Default diagnostic session DSIV Diagnostic Security Implementation Variant Project specific. Dependent of the security variant implemented in the diagnostic server. DTC Diagnostic Trouble Code ECU Electronic Control Unit Ext Extended diagnostic session UDS Unified Diagnostic Services CAN Controller Area Network | None | None | None | None | RFQX-CVS124-0006 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0007 | Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification.StatementShall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification. | None | None | AD-008 | component | RFQX-CVS124-0007 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0008 | Should This word, or the adjective “Recommended”, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course.StatementShould This word, or the adjective “Recommended”, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course. | None | None | AD-008 | component | RFQX-CVS124-0008 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0009 | Should not This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.StatementShould not This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. | None | None | AD-008 | component | RFQX-CVS124-0009 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0010 | May This word, or the adjective “Optional”, means that an item is truly optional.StatementMay This word, or the adjective “Optional”, means that an item is truly optional. | None | None | None | None | RFQX-CVS124-0010 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0011 | One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item.StatementOne vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. | None | None | AD-002 | component | RFQX-CVS124-0011 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0012 | An implementation which does not include a particular option shall be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality.StatementAn implementation which does not include a particular option shall be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. | None | None | AD-008 | component | RFQX-CVS124-0012 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0013 | In the same vein an implementation which does include a particular option shall be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides).StatementIn the same vein an implementation which does include a particular option shall be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides). | None | None | AD-008 | component | RFQX-CVS124-0013 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0014 | ConventionsStatementTable 3 – Conventions Implementation Description M Mandatory Mandatory data marked as ‘M’ always shall be returned. If valid data is not needed for the use-case and system at hand, default values should be used. E Mandatory for ECUs which shall be compliant with OBD legislation Worldwide like ISO27145,J1979 etc C Conditional U User optional. Shall be agreed between the supplier and the vehicle manufacturer. - (dash) Not supported Table 4 – Definitions of terms Changing Description DIAG Diagnostics - The Data Identifier content can be changed by means of the UDS service 0x2E FLASH BOOT Boot loader module stored in flash memory FLASH APPL Application module stored in flash memory FLASH DATA Dataset download - The Data Identifier content is changed by a dataset download process as per document Harmonized programming (see /11/) SUPPLIER Supplier process - The Data Identifier content is changed at the supplier's facilities by the manufacturing process. INTERNAL ECU software - The Data Identifier content is determined by the server at runtime. | SSR-BOOT-001 | Secure software update and flash readiness — Bootloader and Application State Handling | AD-001 | component | RFQX-CVS124-0014 / 32h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0015 | If valid data is not needed for the use-case and system at hand, default values should be used.StatementIf valid data is not needed for the use-case and system at hand, default values should be used. | None | None | AD-008 | component | RFQX-CVS124-0015 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0016 | E Mandatory for ECUs which shall be compliant with OBD legislation Worldwide like ISO27145,J1979 etc C Conditional U User optional.StatementE Mandatory for ECUs which shall be compliant with OBD legislation Worldwide like ISO27145,J1979 etc C Conditional U User optional. | None | None | AD-008 | component | RFQX-CVS124-0016 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0017 | Shall be agreed between the supplier and the vehicle manufacturer.StatementShall be agreed between the supplier and the vehicle manufacturer. | None | None | AD-008 | component | RFQX-CVS124-0017 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0018 | The implementation of the client and the server shall be compliant with ISO 14229-1 with theStatementThe implementation of the client and the server shall be compliant with ISO 14229-1 with the | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0018 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0019 | All deviations and extensions shall be agreed with the applicable vehicle manufacturer and shall be documented.StatementAll deviations and extensions shall be agreed with the applicable vehicle manufacturer and shall be documented. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0019 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0020 | Table 5 -Data identifiers used at ECU identification DID Description/ Name Application Boot loader Changing Def Non- Def Def Ext Prg Ext 0xF180 bootSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF181 applicationSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF182 applicationDataIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF186 ActiveDiagnosticSessionDataIdentifier ● ● ● ● ● INTERNAL 0xF187 vehicleManufacturerSparePartNumberDataIdentifier ● ○ ● ○ ○ SUPPLIER 0xF188 vehicleManufacturerECUSoftwareNumberDataIdent ifier ● ● ● ● ● SUPPLIER 0xF189 vehicleManufacturerECUSoftwareVersionNumberD ataIdentifier ● ● ● ● ● SUPPLIER 0xF18A systemSupplierIdentifierDataIdentifier ● ● - - - SUPPLIER 0xF18B ECUManufacturingDateDataIdentifier ● ● ● ● ● SUPPLIER 0xF18C ECUSerialNumberDataIdentifier ● ● ● ● ● SUPPLIER 0xF190 VINDataIdentifier ● ○ ● ● ● DIAG 0xF191 vehicleManufacturerECUHardwareNumberDataIde ntifier ● ● ● ● ● SUPPLIER 0xF192 systemSupplierECUHardwareNumberDataIdentifier ● ● - - - SUPPLIER 0xF193 systemSupplierECUHardwareVersionNumberDataI dentifier ● ● - - - SUPPLIER 0xF194 systemSupplierECUSoftwareNumberDataIdentifier ● ● - - - SUPPLIERStatementTable 5 -Data identifiers used at ECU identification DID Description/ Name Application Boot loader Changing Def Non- Def Def Ext Prg Ext 0xF180 bootSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF181 applicationSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF182 applicationDataIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF186 ActiveDiagnosticSessionDataIdentifier ● ● ● ● ● INTERNAL 0xF187 vehicleManufacturerSparePartNumberDataIdentifier ● ○ ● ○ ○ SUPPLIER 0xF188 vehicleManufacturerECUSoftwareNumberDataIdent ifier ● ● ● ● ● SUPPLIER 0xF189 vehicleManufacturerECUSoftwareVersionNumberD ataIdentifier ● ● ● ● ● SUPPLIER 0xF18A systemSupplierIdentifierDataIdentifier ● ● - - - SUPPLIER 0xF18B ECUManufacturingDateDataIdentifier ● ● ● ● ● SUPPLIER 0xF18C ECUSerialNumberDataIdentifier ● ● ● ● ● SUPPLIER 0xF190 VINDataIdentifier ● ○ ● ● ● DIAG 0xF191 vehicleManufacturerECUHardwareNumberDataIde ntifier ● ● ● ● ● SUPPLIER 0xF192 systemSupplierECUHardwareNumberDataIdentifier ● ● - - - SUPPLIER 0xF193 systemSupplierECUHardwareVersionNumberDataI dentifier ● ● - - - SUPPLIER 0xF194 systemSupplierECUSoftwareNumberDataIdentifier ● ● - - - SUPPLIER | None | None | None | None | RFQX-CVS124-0020 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0021 | SUPPLIER in the Changing column means that the DID can be changed only at the supplier premises for non-programmable ECUs.StatementSUPPLIER in the Changing column means that the DID can be changed only at the supplier premises for non-programmable ECUs. Data identifier details. | None | None | None | None | RFQX-CVS124-0021 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0022 | The format in the DID description in the following tables is given in ODX base data types.StatementThe format in the DID description in the following tables is given in ODX base data types. | None | None | None | None | RFQX-CVS124-0022 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0023 | Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier 0xF180 Name : bootSoftwareIdentificationDataIdentifier ByteStatementTable 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier 0xF180 Name : bootSoftwareIdentificationDataIdentifier Byte | None | None | None | None | RFQX-CVS124-0023 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0024 | This DID shall be stored under flash memory module in flash memory.StatementThis DID shall be stored under flash memory module in flash memory. | SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | AD-006 | component | RFQX-CVS124-0024 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0025 | Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier 0xF181 Name : applicationSoftwareIdentificationDataIdentifier Byte Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application software identifier #1: : M 0x7E 0x7E 0x20 : : : #n – 12 : #n Application software identifier #m: : C 0x7E 0x7E 0x20StatementTable 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier 0xF181 Name : applicationSoftwareIdentificationDataIdentifier Byte Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application software identifier #1: : M 0x7E 0x7E 0x20 : : : #n – 12 : #n Application software identifier #m: : C 0x7E 0x7E 0x20 | None | None | None | None | RFQX-CVS124-0025 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0026 | 5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifierStatement5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier | None | None | None | None | RFQX-CVS124-0026 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0027 | Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier 0xF182 Name: applicationDataIdentificationDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application data module part number #1: : 13 Bytes- M : M 0x7E .StatementTable 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier 0xF182 Name: applicationDataIdentificationDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application data module part number #1: : 13 Bytes- M : M 0x7E . | None | None | None | None | RFQX-CVS124-0027 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0028 | This DID shall be stored under dataset module stored in flash memory.StatementThis DID shall be stored under dataset module stored in flash memory. | SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | AD-006 | component | RFQX-CVS124-0028 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0029 | Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier 0xF186 Name: ActiveDiagnosticSessionDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 Diagnostic session type 1-Byte-A_UINT32 M 0x00 – 0xFF 0x01StatementTable 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier 0xF186 Name: ActiveDiagnosticSessionDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 Diagnostic session type 1-Byte-A_UINT32 M 0x00 – 0xFF 0x01 | None | None | None | None | RFQX-CVS124-0029 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0030 | Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier 0xF187 Name: vehicleManufacturerSparePartNumberDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 : #13 Vehicle manufacturer sparepart number : G, M : M 0x7E : 0x7E 0x20StatementTable 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier 0xF187 Name: vehicleManufacturerSparePartNumberDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 : #13 Vehicle manufacturer sparepart number : G, M : M 0x7E : 0x7E 0x20 | None | None | None | None | RFQX-CVS124-0030 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0031 | This DID shall be stored under dataset module stored in flash memory.StatementThis DID shall be stored under dataset module stored in flash memory. | SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | AD-006 | component | RFQX-CVS124-0031 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0032 | Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier 0xF188 Name: vehicleManufacturerECUSoftwareNumberDataIdentifier Byte Data #1 : #13 Vehicle manufacturer ECU (server) software number : M : M : 0x20StatementTable 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier 0xF188 Name: vehicleManufacturerECUSoftwareNumberDataIdentifier Byte Data #1 : #13 Vehicle manufacturer ECU (server) software number : M : M : 0x20 | None | None | None | None | RFQX-CVS124-0032 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0033 | 5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifierStatement5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier | None | None | None | None | RFQX-CVS124-0033 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0034 | Table 12 – Description of DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier 0xF189 Name: vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Byte DataStatementTable 12 – Description of DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier 0xF189 Name: vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Byte Data | None | None | None | None | RFQX-CVS124-0034 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0035 | 5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifierStatement5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifier | None | None | None | None | RFQX-CVS124-0035 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0036 | Table 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier 0xF18A Name: systemSupplierIdentifierDataIdentifier Byte No Description Format Cvt Byte Value Default Data To be specifie d by the Content and format to be specified by the supplier Should be M : M : 5.2.1.9 DID 0xF18B ECUManufacturingDateDataIdentifierStatementTable 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier 0xF18A Name: systemSupplierIdentifierDataIdentifier Byte No Description Format Cvt Byte Value Default Data To be specifie d by the Content and format to be specified by the supplier Should be M : M : 5.2.1.9 DID 0xF18B ECUManufacturingDateDataIdentifier | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0036 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0037 | Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier 0xF18B Name: ECUManufacturingDateDataIdentifier Byte Data #1 .StatementTable 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier 0xF18B Name: ECUManufacturingDateDataIdentifier Byte Data #1 . | None | None | None | None | RFQX-CVS124-0037 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0038 | Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier 0xF18C Name: ECUSerialNumberDataIdentifier Byte DataStatementTable 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier 0xF18C Name: ECUSerialNumberDataIdentifier Byte Data | None | None | None | None | RFQX-CVS124-0038 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0039 | Minimum length shall be 8 bytes and the assigned value shall be unique for every unit provided by one supplier per project.StatementMinimum length shall be 8 bytes and the assigned value shall be unique for every unit provided by one supplier per project. | None | None | AD-008 | component | RFQX-CVS124-0039 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0040 | Table 16 – Description of DID 0xF190 VINDataIdentifier 0xF190 Name: VINDataIdentifier Byte Data #1 : #17 VIN number : Byte #17 17-Bytes- M : M : 0x30 .StatementTable 16 – Description of DID 0xF190 VINDataIdentifier 0xF190 Name: VINDataIdentifier Byte Data #1 : #17 VIN number : Byte #17 17-Bytes- M : M : 0x30 . | None | None | None | None | RFQX-CVS124-0040 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0041 | This identifier is used for follow up and quality check at production and service and for legal reasons if applicable.StatementThis identifier is used for follow up and quality check at production and service and for legal reasons if applicable. | None | None | None | None | RFQX-CVS124-0041 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0042 | Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier 0xF191 Name: vehicleManufacturerECUHardwareNumberDataIdentifier Byte DataStatementTable 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier 0xF191 Name: vehicleManufacturerECUHardwareNumberDataIdentifier Byte Data | None | None | None | None | RFQX-CVS124-0042 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0043 | This DID shall be stored under flash memory module in flash memory.StatementThis DID shall be stored under flash memory module in flash memory. | SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | AD-006 | component | RFQX-CVS124-0043 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0044 | Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier 0xF192 Name: systemSupplierECUHardwareNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.14 DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifierStatementTable 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier 0xF192 Name: systemSupplierECUHardwareNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.14 DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier | None | None | None | None | RFQX-CVS124-0044 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0045 | Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier 0xF193 Name: systemSupplierECUHardwareVersionNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.15 DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifierStatementTable 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier 0xF193 Name: systemSupplierECUHardwareVersionNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.15 DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier | None | None | None | None | RFQX-CVS124-0045 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0046 | Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier 0xF194 Name: systemSupplierECUSoftwareNumberDataIdentifier Byte No Description Format Cvt Byte Value Data To be specified by the External SupplierStatementTable 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier 0xF194 Name: systemSupplierECUSoftwareNumberDataIdentifier Byte No Description Format Cvt Byte Value Data To be specified by the External Supplier | None | None | None | None | RFQX-CVS124-0046 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0047 | DID 0xF197 systemNameOrEngineTypeDataIdentifierStatementDID 0xF197 systemNameOrEngineTypeDataIdentifier | None | None | None | None | RFQX-CVS124-0047 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0048 | Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier 0xF195 Name: systemSupplierECUSoftwareVersionNumberDataIdentifier Byte Data To be specified by the External supplier 5.2.1.17 DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifierStatementTable 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier 0xF195 Name: systemSupplierECUSoftwareVersionNumberDataIdentifier Byte Data To be specified by the External supplier 5.2.1.17 DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier | None | None | None | None | RFQX-CVS124-0048 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0049 | Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier 0xF196 Name: exhaustRegulationOrTypeApprovalNumberDataIdentifier Cvt: E Byte Data #1 : #10 Exhaust regulation or type approval 10-Bytes- M : M : 0000000 000 5.2.1.18 DID 0xF197 systemNameOrEngineTypeDataIdentifierStatementTable 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier 0xF196 Name: exhaustRegulationOrTypeApprovalNumberDataIdentifier Cvt: E Byte Data #1 : #10 Exhaust regulation or type approval 10-Bytes- M : M : 0000000 000 5.2.1.18 DID 0xF197 systemNameOrEngineTypeDataIdentifier | None | None | None | None | RFQX-CVS124-0049 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0050 | Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier 0xF197 Name: systemNameOrEngineTypeDataIdentifier Byte Data #1 : #22 System name or engine type 6-to-22-Bytes- G, M : C : 0x20 .StatementTable 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier 0xF197 Name: systemNameOrEngineTypeDataIdentifier Byte Data #1 : #22 System name or engine type 6-to-22-Bytes- G, M : C : 0x20 . | None | None | None | None | RFQX-CVS124-0050 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0051 | The format should follow the pattern: Appl: <Diag.family> <Diag.generation> Boot: <Diag.family> <Diag.generation>_BOOTStatementThe format should follow the pattern: Appl: <Diag.family> <Diag.generation> Boot: <Diag.family> <Diag.generation>_BOOT | None | None | AD-008 | component | RFQX-CVS124-0051 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0052 | DID 0xF198 SoftwareItemSemanticDataIdentifiersStatementDID 0xF198 SoftwareItemSemanticDataIdentifiers | None | None | None | None | RFQX-CVS124-0052 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0053 | Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s 0xF199 Name: SoftwareAssemblySemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01StatementTable 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s 0xF199 Name: SoftwareAssemblySemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01 | None | None | None | None | RFQX-CVS124-0053 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0054 | Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers 0xF19A Name: HardwareSemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01 #4 : #n+3 HardwareSemantic Data Identifier #1: : byte #n* A_ASCIISTR ING, zero M 0x00, 0x20 – 0x7E : : : : : : : HardwareSemantic Data Identifier #m: : byte #q* A_ASCIISTR ING, zero C 0x00, 0x20 – 0x7E *depends on the SoftwareItemSemanticDataIdentifiers length.StatementTable 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers 0xF19A Name: HardwareSemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01 #4 : #n+3 HardwareSemantic Data Identifier #1: : byte #n* A_ASCIISTR ING, zero M 0x00, 0x20 – 0x7E : : : : : : : HardwareSemantic Data Identifier #m: : byte #q* A_ASCIISTR ING, zero C 0x00, 0x20 – 0x7E *depends on the SoftwareItemSemanticDataIdentifiers length. | None | None | None | None | RFQX-CVS124-0054 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0055 | Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier 0xF19D Name: ECUInstallationDateDataIdentifier Byte DataStatementTable 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier 0xF19D Name: ECUInstallationDateDataIdentifier Byte Data | None | None | None | None | RFQX-CVS124-0055 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0056 | Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber 0xF1A5 Name: vehicleManufacturerECUHardwareWithoutBootNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufactur er ECU Hardware Number Byte #2 : 13-Byte- M : M : Project 5.2.1.24 DID 0xF1A6 engineNumberStatementTable 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber 0xF1A5 Name: vehicleManufacturerECUHardwareWithoutBootNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufactur er ECU Hardware Number Byte #2 : 13-Byte- M : M : Project 5.2.1.24 DID 0xF1A6 engineNumber | None | None | None | None | RFQX-CVS124-0056 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0057 | Table 29 – Description of DID 0xF1A6 engineNumber 0xF1A6 Name: engineNumber Byte Data #1 : #14 Engine number 14-Bytes- A_ASCIISTRING MM : 0x20 C = Applicable only for TRATON standalone engine solutionsStatementTable 29 – Description of DID 0xF1A6 engineNumber 0xF1A6 Name: engineNumber Byte Data #1 : #14 Engine number 14-Bytes- A_ASCIISTRING MM : 0x20 C = Applicable only for TRATON standalone engine solutions | None | None | None | None | RFQX-CVS124-0057 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0058 | This DID shall contain a snapshot of the mandatory lifetime ECU-runtime operational dataStatementThis DID shall contain a snapshot of the mandatory lifetime ECU-runtime operational data | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS124-0058 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0059 | Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp 0xF1A9 Name: lifetimeECUruntimeAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Lifetime ECU- runtime at software update stamp Unit: s A_UINT32 M : M : 0xFFFFFFFF C = mandatory for TRATON Standalone and External engines 5.2.1.26 DID 0xF1AA Mileage at software update stampStatementTable 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp 0xF1A9 Name: lifetimeECUruntimeAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Lifetime ECU- runtime at software update stamp Unit: s A_UINT32 M : M : 0xFFFFFFFF C = mandatory for TRATON Standalone and External engines 5.2.1.26 DID 0xF1AA Mileage at software update stamp | None | None | None | None | RFQX-CVS124-0059 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0060 | This DID shall report a snapshot of the mileage of the vehicle as received on CAN or other ECU-external source at the first reception of the signal with a good signal status after a software update.StatementThis DID shall report a snapshot of the mileage of the vehicle as received on CAN or other ECU-external source at the first reception of the signal with a good signal status after a software update. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS124-0060 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust; evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0061 | Table 31 – Description of DID 0xF1AA Mileage at software update stamp ID Description 0xF1AA Name: mileageAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Mileage at software update stamp Unit: km Formula: 0,005*X 4-Bytes- A_UINT32 M : M : 0xFFFFFFFF C = Mandatory for ECUs that store Operational data and have access to Vehicle milage information.StatementTable 31 – Description of DID 0xF1AA Mileage at software update stamp ID Description 0xF1AA Name: mileageAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Mileage at software update stamp Unit: km Formula: 0,005*X 4-Bytes- A_UINT32 M : M : 0xFFFFFFFF C = Mandatory for ECUs that store Operational data and have access to Vehicle milage information. | None | None | None | None | RFQX-CVS124-0061 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0062 | The current date as received on CAN or other ECU-external source at first reception of a valid signal after a software update.StatementThe current date as received on CAN or other ECU-external source at first reception of a valid signal after a software update. | None | None | None | None | RFQX-CVS124-0062 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; evidence completeness | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0063 | Table 32 – Description of DID 0xF1AB Date at software update stamp 0xF1AB Name: dateAtSoftwareUpdateStamp Byte DataStatementTable 32 – Description of DID 0xF1AB Date at software update stamp 0xF1AB Name: dateAtSoftwareUpdateStamp Byte Data | None | None | None | None | RFQX-CVS124-0063 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0064 | Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier 0xF1AD Name: activeECUSoftwareDataIdentifier Byte Data #1 : #2 Active ECU Software 2-Bytes- A_BYTEFIEL D M : M Boot loader: 0x0000 Application Software: 0x0002 No information: 0xFFFF Not applicabl e 5.2.1.29 DID 0xF1AF NodeUIDStatementTable 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier 0xF1AD Name: activeECUSoftwareDataIdentifier Byte Data #1 : #2 Active ECU Software 2-Bytes- A_BYTEFIEL D M : M Boot loader: 0x0000 Application Software: 0x0002 No information: 0xFFFF Not applicabl e 5.2.1.29 DID 0xF1AF NodeUID | None | None | None | None | RFQX-CVS124-0064 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0065 | Table 34 – Description of DID 0xF1AF NodeUID 0xF1AF Name: NodeUID Byte Data #1 : #8 NodeUID 8-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00StatementTable 34 – Description of DID 0xF1AF NodeUID 0xF1AF Name: NodeUID Byte Data #1 : #8 NodeUID 8-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 | None | None | None | None | RFQX-CVS124-0065 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0066 | This identifier is used to link a ECU HW to its specialized security attributes.StatementThis identifier is used to link a ECU HW to its specialized security attributes. | None | None | None | None | RFQX-CVS124-0066 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0067 | The value to be stored is fetched from TRATON backend system in production.StatementThe value to be stored is fetched from TRATON backend system in production. | None | None | None | None | RFQX-CVS124-0067 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0068 | Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber 0xF1B9 Name: RBACCIdentifierNumber Byte Data #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00StatementTable 35 – Description of DID 0xF1B9 RBACCIdentifierNumber 0xF1B9 Name: RBACCIdentifierNumber Byte Data #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 | None | None | None | None | RFQX-CVS124-0068 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0069 | Information on RBACC can be found in CVS151.StatementInformation on RBACC can be found in CVS151. | None | None | None | None | RFQX-CVS124-0069 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0070 | Table 36 – Description of DID 0xF1BA RBACCStructureVersion 0xF1BA Name: RBACCStructureVersion Byte Data #1 : #2 RBACC Structure Version 2-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00StatementTable 36 – Description of DID 0xF1BA RBACCStructureVersion 0xF1BA Name: RBACCStructureVersion Byte Data #1 : #2 RBACC Structure Version 2-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 | None | None | None | None | RFQX-CVS124-0070 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0071 | Information on RBACC can be found in CVS151.StatementInformation on RBACC can be found in CVS151. | None | None | None | None | RFQX-CVS124-0071 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0072 | Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier 0xF1D1 Name: RootCertificateIdentifier Byte DataStatementTable 37 – Description of DID 0xF1D1 RootCertificateIdentifier 0xF1D1 Name: RootCertificateIdentifier Byte Data | None | None | None | None | RFQX-CVS124-0072 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | COMPLETE |
| RFQX-CVS124-0073 | Table 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber 0xF1E1 Name: vehicleManufacturerECUBootSoftwareNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufacturer ECUBootSoftwareNu mber Byte #2 : 13-Byte- G, M : M : ProjectStatementTable 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber 0xF1E1 Name: vehicleManufacturerECUBootSoftwareNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufacturer ECUBootSoftwareNu mber Byte #2 : 13-Byte- G, M : M : Project | None | None | None | None | RFQX-CVS124-0073 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0074 | This DID shall be stored under flash memory module in flash memory.StatementThis DID shall be stored under flash memory module in flash memory. | SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | AD-006 | component | RFQX-CVS124-0074 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0075 | A default diagnostic session shall be supported.StatementA default diagnostic session shall be supported. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0075 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0076 | The default diagnostic session is referred to as “defaultSession”.StatementThe default diagnostic session is referred to as “defaultSession”. | None | None | None | None | RFQX-CVS124-0076 / 26h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0077 | A non-default diagnostic session referred to as “extendedDiagnosticSession” shall be supported.StatementA non-default diagnostic session referred to as “extendedDiagnosticSession” shall be supported. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0077 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0078 | Diagnostic sessions not defined in this document shall be agreed with the vehicle manufacturer.StatementDiagnostic sessions not defined in this document shall be agreed with the vehicle manufacturer. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0078 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0079 | Of a marked service, an execution shall be implemented for the specified session as perTable 39.StatementOf a marked service, an execution shall be implemented for the specified session as perTable 39. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0079 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0080 | Table 39 – Diagnostic service support Service according to ISO 14229-1 Addressin g mode Application Boot loaderStatementTable 39 – Diagnostic service support Service according to ISO 14229-1 Addressin g mode Application Boot loader | None | None | None | None | RFQX-CVS124-0080 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0081 | In Table 39, bootloader sessions should only be applicable to Software updateable ECUs.StatementIn Table 39, bootloader sessions should only be applicable to Software updateable ECUs. | None | None | AD-001 | component | RFQX-CVS124-0081 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0082 | The mapping of RoutineControl service routines to sessions shall be discussed and agreed with the vehicle manufacturer.StatementThe mapping of RoutineControl service routines to sessions shall be discussed and agreed with the vehicle manufacturer. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0082 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0083 | The server shall implement support for RBAC (Role Based Access Control) based on CVS151.StatementThe server shall implement support for RBAC (Role Based Access Control) based on CVS151. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS124-0083 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0084 | CVS31 and CVS32 requirements preconditions per service shall be defined by the RBAC Configuration file in the ECU.StatementCVS31 and CVS32 requirements preconditions per service shall be defined by the RBAC Configuration file in the ECU. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS124-0084 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0085 | Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services.StatementDiagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services. | None | None | None | None | RFQX-CVS124-0085 / 26h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0086 | The conditions that shall be checked are • Vehicle speed ~ 0 • Engine speed ~ 0 (for vehicles with IC engines) • High Voltage system disengaged ( for vehicles with high Voltage battery system) • Gear Box in neutral • Parking brake engaged Diagnostics safe state is not intended for ensuring the vehicle safety rather its conditions that are checked to prevent executing Diagnostics services during vehicle operationStatementThe conditions that shall be checked are • Vehicle speed ~ 0 • Engine speed ~ 0 (for vehicles with IC engines) • High Voltage system disengaged ( for vehicles with high Voltage battery system) • Gear Box in neutral • Parking brake engaged Diagnostics safe state is not intended for ensuring the vehicle safety rather its conditions that are checked to prevent executing Diagnostics services during vehicle operation | None | None | AD-008 | component | RFQX-CVS124-0086 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0087 | Diagnostics safe state shall be checked before executing the diagnostics services as per Table 40.StatementDiagnostics safe state shall be checked before executing the diagnostics services as per Table 40. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0087 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0088 | The server implementation shall comply with the following state diagram and the following stateStatementThe server implementation shall comply with the following state diagram and the following state | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0088 / 32h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0089 | The session transitions stated below shall be possible to request both physically or functionallyStatementThe session transitions stated below shall be possible to request both physically or functionally | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0089 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0090 | .Statement. Default transition for the start of the software in the server after power-up/wake-up. | None | None | None | None | RFQX-CVS124-0090 / 4h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0091 | Description of the individual transitions as per Figure 2 -State Diagram is explained fromStatementDescription of the individual transitions as per Figure 2 -State Diagram is explained from | None | None | None | None | RFQX-CVS124-0091 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0092 | toStatementto | None | None | None | None | RFQX-CVS124-0092 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0093 | .Statement. | None | None | None | None | RFQX-CVS124-0093 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0094 | .Statement. The initialization routine is started. | None | None | None | None | RFQX-CVS124-0094 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0095 | .Statement. If a valid application software is available in the server (applValid P1 == true) and there is no programming request (progRequest P2 == false), the server changes to the DefaultSession in the application software. | None | None | None | None | RFQX-CVS124-0095 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0096 | .Statement. If a programming request is active (progRequest P2 == true), the server activates the programming session in the bootloader module. | None | None | None | None | RFQX-CVS124-0096 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0097 | .Statement. If there is no programming request (progRequest P2 == false) and no valid application software is available (applValid P1 == false), the server changes to the DefaultSession in the boot loader. | None | None | None | None | RFQX-CVS124-0097 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0098 | .Statement. If the client posts a physical service request to change session from DefaultSession to ProgrammingSession in the application software, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). Applies to non-reprogrammable servers: If the client requests a change to the ProgrammingSession in the DefaultSession in the application software, the server | None | None | None | None | RFQX-CVS124-0098 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0099 | .Statement. If the client requests a change to the ExtendedSession in the DefaultSession in the application software, the session is changed. | None | None | None | None | RFQX-CVS124-0099 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0100 | .Statement. If the client does not send any requests during a time period defined by S3Server in the ExtendedSession in the application software, the server falls back into the DefaultSession in the application software. | None | None | None | None | RFQX-CVS124-0100 / 4h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0101 | .Statement. If the client requests a change to the DefaultSession in the ExtendedSession in the application software, the session is changed. | None | None | None | None | RFQX-CVS124-0101 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0102 | .Statement. If the client requests a change to the ProgrammingSession in the ExtendedSession in the application software, the server sets the progRequest flag to "true", so that after restarting it can be seen, that changing to the ProgrammingSession has been requested. If the SPRMIB was not set a positive response is sent from the application before the transition to Bootloader. The request is only sent physically. | None | None | None | None | RFQX-CVS124-0102 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0103 | .Statement. If the client requests a change to the ExtendedSession in ExtendedSession in the application software, the server accepts the request. | None | None | None | None | RFQX-CVS124-0103 / 4h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0104 | 2.Statement2. | None | None | None | None | RFQX-CVS124-0104 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0105 | .Statement. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the boot loader ExtendedSession or ProgrammingSession, the reset is performed. | None | None | None | None | RFQX-CVS124-0105 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0106 | .Statement. If the client requests a change to the DefaultSession in the boot loader ExtendedSession or ProgrammingSession, the reset is performed. | None | None | None | None | RFQX-CVS124-0106 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0107 | .Statement. If the client does not send any requests during a time period defined by S3Server in a Non-DefaultSession in the boot loader, the server performs a reset. | None | None | None | None | RFQX-CVS124-0107 / 4h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0108 | .Statement. If the client requests a change to the DefaultSession in the DefaultSession in the boot loader, the server accepts the request. | None | None | None | None | RFQX-CVS124-0108 / 4h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0109 | .Statement. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the DefaultSession in the boot loader, the reset is performed. | None | None | None | None | RFQX-CVS124-0109 / 4h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0110 | .Statement. If the client requests the ExtendedSession in the DefaultSession in the boot loader, the session is changed. | None | None | None | None | RFQX-CVS124-0110 / 4h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0111 | .Statement. If the client posts a physical service request to change session from DefaultSession to ProgrammingSession in the boot loader, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). | None | None | None | None | RFQX-CVS124-0111 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0112 | .Statement. If the client requests the ExtendedSession in the ExtendedSession in the boot loader, the server accepts the request. | None | None | None | None | RFQX-CVS124-0112 / 4h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0113 | .Statement. If the client requests the ProgrammingSession in the ExtendedSession in the boot loader, the session is changed regardless of whether the programming preconditions are fulfilled or not. The request is only sent physically. | None | None | None | None | RFQX-CVS124-0113 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0114 | .Statement. If the client requests a change to the ProgrammingSession in ProgrammingSession in the boot loader, the server accepts the request. The request is only sent physically. | None | None | None | None | RFQX-CVS124-0114 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0115 | .Statement. If the client posts a physical service request to change session from ProgrammingSession to ExtendedSession in the boot loader, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). | None | None | None | None | RFQX-CVS124-0115 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0116 | .Statement. If the client requests the DefaultSession in the DefaultSession in the application, the server accepts the request. | None | None | None | None | RFQX-CVS124-0116 / 4h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0117 | 12.Statement12. | None | None | None | None | RFQX-CVS124-0117 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0118 | .Statement. Applies to terminal 15 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the ExtendedSession in the application software, a restart is performed. | None | None | None | None | RFQX-CVS124-0118 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0119 | .Statement. Applies to terminal 15 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the application software, a restart is performed. | None | None | None | None | RFQX-CVS124-0119 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0120 | .Statement. If a server exchanges diagnostic messages with the client within the ExtendedSession and state terminal 15 ON, the following step is performed if there is a change to terminal 15 OFF and response in progress was finished: Return to DefaultSession after an already started response message has been completely sent to the client. | None | None | None | None | RFQX-CVS124-0120 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0121 | .Statement. If there is a state change from terminal 15 ON to terminal 15 OFF while a server exchanges diagnostic messages with the client within the DefaultSession, the server stops the communications with the client after sending the complete response to the last request. | None | None | None | None | RFQX-CVS124-0121 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0122 | .Statement. Applies to terminal 30 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the ExtendedSession in the application software, a change to the DefaultSession is performed. | None | None | None | None | RFQX-CVS124-0122 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0123 | .Statement. Applies to terminal 30 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the application software, the server accepts the request and remains in the DefaultSession. | None | None | None | None | RFQX-CVS124-0123 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0124 | .Statement. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in a DefaultSession in the application software, a restart is performed. | None | None | None | None | RFQX-CVS124-0124 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0125 | .Statement. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the ExtendedSession in the application software a restart is performed. | None | None | None | None | RFQX-CVS124-0125 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0126 | .Statement. If the client requests an ECUReset (0x11) with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the boot loader, the reset is performed. | None | None | None | None | RFQX-CVS124-0126 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0127 | .Statement. If the client requests an ECUReset (0x11) with the sub-function KeyOffOnReset (0x02) in a Non-DefaultSession in the boot loader, the reset is performed. | None | None | None | None | RFQX-CVS124-0127 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0128 | 24.Statement24. | None | None | None | None | RFQX-CVS124-0128 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0129 | Project specific DID shall be added to ranges defined as system supplier specific in ISO 14229StatementProject specific DID shall be added to ranges defined as system supplier specific in ISO 14229 | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0129 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0130 | Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which shall only be implemented in agreement with the vehicle manufacturer.StatementTable 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which shall only be implemented in agreement with the vehicle manufacturer. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS124-0130 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0131 | Table 41 – Data identifier (DID) ranges Byte value Description 0x0611-0x0620 Reserved for collective data identifiers 0xB000 – 0xB1FF Reserved for TRATON 0xCF00 – 0xCFFF TRATON data field identifiers 0xF010 disableDiagnosticClient 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Refer to VehSec_IVD_ECU for detailed requirements on Integrity Validation Data (IVD) for ECUs which need to be compliant to UNECE R156 regulation.StatementTable 41 – Data identifier (DID) ranges Byte value Description 0x0611-0x0620 Reserved for collective data identifiers 0xB000 – 0xB1FF Reserved for TRATON 0xCF00 – 0xCFFF TRATON data field identifiers 0xF010 disableDiagnosticClient 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Refer to VehSec_IVD_ECU for detailed requirements on Integrity Validation Data (IVD) for ECUs which need to be compliant to UNECE R156 regulation. | None | None | None | None | RFQX-CVS124-0131 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0132 | These ECUs shall implement the following DIDs according to Table 42.StatementThese ECUs shall implement the following DIDs according to Table 42. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0132 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0133 | The SPRMIB shall be supported for services as specified in (ISO 14229-1).StatementThe SPRMIB shall be supported for services as specified in (ISO 14229-1). | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0133 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0134 | Negative response codes specified in ISO 14229-1 Annex A.1 shall only be supported if explicitly specified by this specification or its normative references.StatementNegative response codes specified in ISO 14229-1 Annex A.1 shall only be supported if explicitly specified by this specification or its normative references. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0134 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0135 | Negative response code 0x22, conditionsNotCorrect , shall be used if a service request is denied due to insufficient rights according to the RBACC check.StatementNegative response code 0x22, conditionsNotCorrect , shall be used if a service request is denied due to insufficient rights according to the RBACC check. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS124-0135 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0136 | 5.5.1.1.1 Request parameter diagnosticSessionTypeStatement5.5.1.1.1 Request parameter diagnosticSessionType | None | None | None | None | RFQX-CVS124-0136 / 26h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0137 | A DiagnosticSessionControl service request with parameter diagnosticSessionType set to ProgrammingSession shall be processed only if normal communication is currently switched off as a result of a previous call to the Communication Control service.StatementA DiagnosticSessionControl service request with parameter diagnosticSessionType set to ProgrammingSession shall be processed only if normal communication is currently switched off as a result of a previous call to the Communication Control service. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS124-0137 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0138 | The application shall respond with NRC 0x22 (conditionsNotCorrect) if communication has not been switched off.StatementThe application shall respond with NRC 0x22 (conditionsNotCorrect) if communication has not been switched off. | None | None | AD-001 | component | RFQX-CVS124-0138 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0139 | Table 43 – Service 0x10 request parameter diagnosticSessionType description Hex (bit 6-0) Description Cvt 0x01 defaultSession M 0x02 ProgrammingSession M 0x03 extendedDiagnosticSession MStatementTable 43 – Service 0x10 request parameter diagnosticSessionType description Hex (bit 6-0) Description Cvt 0x01 defaultSession M 0x02 ProgrammingSession M 0x03 extendedDiagnosticSession M | None | None | None | None | RFQX-CVS124-0139 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0140 | Following an accepted request to switch to the ProgrammingSession, the application shall make all preparations to guarantee trouble-free programming operation.StatementFollowing an accepted request to switch to the ProgrammingSession, the application shall make all preparations to guarantee trouble-free programming operation. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS124-0140 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0141 | In this process, it shall end all routines and functions that influence programming and ensure that the server checked for safe state conditions at minimal.StatementIn this process, it shall end all routines and functions that influence programming and ensure that the server checked for safe state conditions at minimal. | None | None | AD-002 | component | RFQX-CVS124-0141 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0142 | Before switching to programming session, the server shall ensure the applicable conditions as per Table 76 - Programming preconditions is checked to ensure the vehicle is in safe condition.StatementBefore switching to programming session, the server shall ensure the applicable conditions as per Table 76 - Programming preconditions is checked to ensure the vehicle is in safe condition. | SSR-UPD-003 | Secure software update and flash readiness — Software Update / Flashing | AD-002 | component | RFQX-CVS124-0142 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0143 | Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer.StatementIts upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer. | None | None | None | None | RFQX-CVS124-0143 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0144 | Positive responseStatementPositive response | None | None | None | None | RFQX-CVS124-0144 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0145 | Positive response shall be sent before the actual switch in case switching to Programming session.StatementPositive response shall be sent before the actual switch in case switching to Programming session. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0145 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0146 | Response parameter diagnosticSessionType shall be as per ISO 14229-1.StatementResponse parameter diagnosticSessionType shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0146 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0147 | Response parameter sessionParameterRecord shall be as per ISO 14229-1.StatementResponse parameter sessionParameterRecord shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0147 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0148 | 5.5.2 ECUReset (0x11) serviceStatement5.5.2 ECUReset (0x11) service | None | None | None | None | RFQX-CVS124-0148 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0149 | An ECUReset shall not be executed if the vehicle safety can be compromised.StatementAn ECUReset shall not be executed if the vehicle safety can be compromised. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS124-0149 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0150 | ECU shall execute the reset only after sending a positive response to the ECU reset serviceStatementECU shall execute the reset only after sending a positive response to the ECU reset service | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0150 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0151 | After a final positive response has been sent for ECUReset the server is not allowed to respond to any diagnostic service requests (except ECU identification) until it has restarted and been re- initialized.StatementAfter a final positive response has been sent for ECUReset the server is not allowed to respond to any diagnostic service requests (except ECU identification) until it has restarted and been re- initialized. | None | None | None | None | RFQX-CVS124-0151 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0152 | The server shall be available for ECU identification within one second after sending positive response message to an ECUReset request.StatementThe server shall be available for ECU identification within one second after sending positive response message to an ECUReset request. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS124-0152 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0153 | After ECU reset, ECU shall be restarted and re-initialized within 2sec.StatementAfter ECU reset, ECU shall be restarted and re-initialized within 2sec. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS124-0153 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0154 | The maximum time it takes from the positive response is sent from the server until it responds to new requests shall be agreed with vehicle manufacturer and documented.StatementThe maximum time it takes from the positive response is sent from the server until it responds to new requests shall be agreed with vehicle manufacturer and documented. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0154 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0155 | 5.5.2.1.1 Request parameter resetTypeStatement5.5.2.1.1 Request parameter resetType | None | None | None | None | RFQX-CVS124-0155 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0156 | Table 44 – Service 0x11 request parameter resetType description Hex (bit 6-0) Description Cvt 0x01 hardReset M 0x02 keyOffOnReset C C = If the server is connected to the ignition keyStatementTable 44 – Service 0x11 request parameter resetType description Hex (bit 6-0) Description Cvt 0x01 hardReset M 0x02 keyOffOnReset C C = If the server is connected to the ignition key | None | None | None | None | RFQX-CVS124-0156 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0157 | The ECUReset service with requestParameter value 0x01 (hardReset) shall simulate the power-on / start-up sequence performed after a server has been previously disconnected from its power supply (i.e.StatementThe ECUReset service with requestParameter value 0x01 (hardReset) shall simulate the power-on / start-up sequence performed after a server has been previously disconnected from its power supply (i.e. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0157 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0158 | the disconnect from the battery shall not be simulated.Statementthe disconnect from the battery shall not be simulated. | None | None | AD-008 | component | RFQX-CVS124-0158 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0159 | The implementation of hardReset shall first ensure that data corruption will not occur.StatementThe implementation of hardReset shall first ensure that data corruption will not occur. | None | None | AD-008 | component | RFQX-CVS124-0159 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0160 | The ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall simulate the turning of the ignition key off and back on and shall ensure that the values of non-volatile memory locations are preserved and the volatile memory will be initialized.StatementThe ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall simulate the turning of the ignition key off and back on and shall ensure that the values of non-volatile memory locations are preserved and the volatile memory will be initialized. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS124-0160 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0161 | The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that every server task is finished prior sending a positive response.StatementThe implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that every server task is finished prior sending a positive response. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0161 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0162 | The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that the volatile memory buffered data is stored into non volatile memory prior sending a positive response.StatementThe implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that the volatile memory buffered data is stored into non volatile memory prior sending a positive response. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0162 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0163 | The server shall send an ECUReset positive response message after the server tasks above are finished but before the server performs the actual resetType.StatementThe server shall send an ECUReset positive response message after the server tasks above are finished but before the server performs the actual resetType. | None | None | AD-002 | component | RFQX-CVS124-0163 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0164 | Table 45 – Service 0x11 positive response parameter description 1 ECUReset Response SID M 2 resetType MStatementTable 45 – Service 0x11 positive response parameter description 1 ECUReset Response SID M 2 resetType M | None | None | None | None | RFQX-CVS124-0164 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0165 | Response parameter resetType shall be as per ISO 14229-1.StatementResponse parameter resetType shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0165 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0166 | 5.5.2.3.1 Supported negative response codesStatement5.5.2.3.1 Supported negative response codes | None | None | None | None | RFQX-CVS124-0166 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0167 | Table 46 – Service 0x11 negative response codes NRC Description and scenario 0x12 sub-functionNotSupported Refer to ISO 14229-1 for scenario.StatementTable 46 – Service 0x11 negative response codes NRC Description and scenario 0x12 sub-functionNotSupported Refer to ISO 14229-1 for scenario. | None | None | None | None | RFQX-CVS124-0167 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0168 | Servers involved in engine start shall not process CommunicationControl service requests until 2 seconds after terminal 15 goes active.StatementServers involved in engine start shall not process CommunicationControl service requests until 2 seconds after terminal 15 goes active. | SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS124-0168 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0169 | If a request is received before this time has passed the server shall respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) (and process the request and send a final response when 2 seconds have passed) or NRC 0x22 (conditionsNotCorrect).StatementIf a request is received before this time has passed the server shall respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) (and process the request and send a final response when 2 seconds have passed) or NRC 0x22 (conditionsNotCorrect). | None | None | AD-002 | component | RFQX-CVS124-0169 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0170 | This requirement mitigates DOS (Denial Of Service) attacksStatementThis requirement mitigates DOS (Denial Of Service) attacks | None | None | None | None | RFQX-CVS124-0170 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0171 | When receiving CommunicationControl service request, Gateway server applications shall ensure quieting down of network to ECUs without diagnostic server which are present in their sub-busesStatementWhen receiving CommunicationControl service request, Gateway server applications shall ensure quieting down of network to ECUs without diagnostic server which are present in their sub-buses | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0171 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0172 | Safety conditions are project specific and shall be checked before accepting a request to disable communication.StatementSafety conditions are project specific and shall be checked before accepting a request to disable communication. | SSR-COM-002 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS124-0172 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0173 | After receiving CommunicationControl service request, ECUs could still keep sending some networks messages/signals to keep a healthy vehicle system.StatementAfter receiving CommunicationControl service request, ECUs could still keep sending some networks messages/signals to keep a healthy vehicle system. | None | None | None | None | RFQX-CVS124-0173 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0174 | Negative responseStatementNegative response | None | None | None | None | RFQX-CVS124-0174 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0175 | Communication control service should not only be used to improve the bandwidth situation during flashing /parametrisation but also for inhibiting systems in vehicle (like engine start) to ensure safety.StatementCommunication control service should not only be used to improve the bandwidth situation during flashing /parametrisation but also for inhibiting systems in vehicle (like engine start) to ensure safety. | None | None | AD-001 | component | RFQX-CVS124-0175 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0176 | Table 47 – Service 0x28 request parameter description 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M 5.5.3.1.1 Request parameter controlTypeStatementTable 47 – Service 0x28 request parameter description 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M 5.5.3.1.1 Request parameter controlType | None | None | None | None | RFQX-CVS124-0176 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0177 | Table 48 – Service 0x28 request parameter controlType description Hex (bit 6-0) Description Cvt 0x00 enableRxAndTx M 0x01 enableRxAndDisableTx M 0x40 – 0x5F vehicleManufacturerSpecific U 5.5.3.1.2 Request parameter communicationTypeStatementTable 48 – Service 0x28 request parameter controlType description Hex (bit 6-0) Description Cvt 0x00 enableRxAndTx M 0x01 enableRxAndDisableTx M 0x40 – 0x5F vehicleManufacturerSpecific U 5.5.3.1.2 Request parameter communicationType | None | None | None | None | RFQX-CVS124-0177 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0178 | Table 49 – Service 0x28 request parameter communicationType description Bits Value (Hex) Description Cvt 0 -1 1 normalCommunicationMessages M 4 – 7 0 Disable / Enable specified communicationType M 5.5.3.2 Positive responseStatementTable 49 – Service 0x28 request parameter communicationType description Bits Value (Hex) Description Cvt 0 -1 1 normalCommunicationMessages M 4 – 7 0 Disable / Enable specified communicationType M 5.5.3.2 Positive response | None | None | None | None | RFQX-CVS124-0178 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0179 | 5.5.3.3 Negative responseStatement5.5.3.3 Negative response | None | None | None | None | RFQX-CVS124-0179 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0180 | If the parameter suppressPosRespMsgIndicationBit = true in a functionally addressed request message, the service request shall not influence any ongoing physically addressed serviceStatementIf the parameter suppressPosRespMsgIndicationBit = true in a functionally addressed request message, the service request shall not influence any ongoing physically addressed service | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0180 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0181 | A functionally addressed TesterPresent may arrive at any time during another request.StatementA functionally addressed TesterPresent may arrive at any time during another request. | None | None | None | None | RFQX-CVS124-0181 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0182 | Request format and parameter shall be as per ISO 14229-1.StatementRequest format and parameter shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0182 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0183 | 5.5.4.4 Negative responseStatement5.5.4.4 Negative response | None | None | None | None | RFQX-CVS124-0183 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0184 | 5.5.5 ControlDTCSetting (0x85) serviceStatement5.5.5 ControlDTCSetting (0x85) service | None | None | None | None | RFQX-CVS124-0184 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0185 | Servers shall reject a ControlDTCSetting service request (DTC setting type = off) with NRC 0x22 (conditionsNotCorrect) if programming preconditions are not satisfied.StatementServers shall reject a ControlDTCSetting service request (DTC setting type = off) with NRC 0x22 (conditionsNotCorrect) if programming preconditions are not satisfied. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS124-0185 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0186 | The execution of this service in the application shall only impact the DTC setting - diagnostic tests for safety and degradations shall not be impacted (shall work as normal).StatementThe execution of this service in the application shall only impact the DTC setting - diagnostic tests for safety and degradations shall not be impacted (shall work as normal). | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0186 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0187 | Refer to ISO 14229-1 for request format.StatementRefer to ISO 14229-1 for request format. | None | None | None | None | RFQX-CVS124-0187 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0188 | Refer to ISO 14229-1 for request parameter DTCSettingType.StatementRefer to ISO 14229-1 for request parameter DTCSettingType. | None | None | None | None | RFQX-CVS124-0188 / 16h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0189 | Request parameter DTCSettingControlOptionRecordStatementRequest parameter DTCSettingControlOptionRecord | None | None | None | None | RFQX-CVS124-0189 / 16h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0190 | Refer to ISO 14229-1 for positive response format and parameter.StatementRefer to ISO 14229-1 for positive response format and parameter. | None | None | None | None | RFQX-CVS124-0190 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0191 | Refer to ISO 14229-1 for negative response format and codes.StatementRefer to ISO 14229-1 for negative response format and codes. | None | None | None | None | RFQX-CVS124-0191 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0192 | The server shall be able to switch baud rate within one second.StatementThe server shall be able to switch baud rate within one second. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0192 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0193 | The boot loader shall inherit the selected baud rate if the LinkControl service request was received when the server was executing in the application.StatementThe boot loader shall inherit the selected baud rate if the LinkControl service request was received when the server was executing in the application. | SSR-BOOT-005 | Bootloader and Application State Handling — Bootloader and Application State Handling | AD-001 | component | RFQX-CVS124-0193 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0194 | Link Control (0x87) service is only applicable to CAN & CAN FD.StatementLink Control (0x87) service is only applicable to CAN & CAN FD. | None | None | None | None | RFQX-CVS124-0194 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0195 | Positive response shall be sent before the actual switch of the baud-rate takes place.StatementPositive response shall be sent before the actual switch of the baud-rate takes place. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0195 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0196 | RequestStatementRequest | None | None | None | None | RFQX-CVS124-0196 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0197 | Table 50 – Service 0x87 request parameter linkControlType description Byte Value Description Cvt 0x01 verifyModeTransitionWithFixedParameter M 0x03 transitionMode M 0x40-0x5F vehicleManufacturerSpecific U 5.5.6.2.1 Request parameter linkControlModeIdentifierStatementTable 50 – Service 0x87 request parameter linkControlType description Byte Value Description Cvt 0x01 verifyModeTransitionWithFixedParameter M 0x03 transitionMode M 0x40-0x5F vehicleManufacturerSpecific U 5.5.6.2.1 Request parameter linkControlModeIdentifier | None | None | None | None | RFQX-CVS124-0197 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0198 | Table 51 – Service 0x87 request parameter linkControlModeIdentifier description Byte Value Description Cvt 0x11 CAN250000Baud C 0x12 CAN500000Baud C 0x13 CAN1000000Baud C C = Baud rates shall be defined by the Project representative.StatementTable 51 – Service 0x87 request parameter linkControlModeIdentifier description Byte Value Description Cvt 0x11 CAN250000Baud C 0x12 CAN500000Baud C 0x13 CAN1000000Baud C C = Baud rates shall be defined by the Project representative. | SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS124-0198 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0199 | 5.5.6.4 Negative ResponseStatement5.5.6.4 Negative Response | None | None | None | None | RFQX-CVS124-0199 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0200 | 5.5.7 ReadDataByIdentifier (0x22) service 5.5.7.1 RequestStatement5.5.7 ReadDataByIdentifier (0x22) service 5.5.7.1 Request | None | None | None | None | RFQX-CVS124-0200 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0201 | If ECU supports request containing more than one data identifier it shall be documented (like in CDD, ODX etc).StatementIf ECU supports request containing more than one data identifier it shall be documented (like in CDD, ODX etc). | SSR-DIAG-005 | Diagnostic Services — Diagnostic Services | AD-006 | component | RFQX-CVS124-0201 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0202 | DataIdentifier parameter definition shall be as per ISO 14229-1.StatementDataIdentifier parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0202 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0203 | The data identifier ranges specified in Table 41 shall be followed.StatementThe data identifier ranges specified in Table 41 shall be followed. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0203 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0204 | Positive responseStatementPositive response | None | None | None | None | RFQX-CVS124-0204 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0205 | 5.5.7.3 Negative responseStatement5.5.7.3 Negative response | None | None | None | None | RFQX-CVS124-0205 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0206 | 5.5.8 WriteDataByIdentifier (0x2E) serviceStatement5.5.8 WriteDataByIdentifier (0x2E) service | None | None | None | None | RFQX-CVS124-0206 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0207 | The sequence of writing data records with service 0x2E WriteDataByIdentifier shall be independent of any specific orderStatementThe sequence of writing data records with service 0x2E WriteDataByIdentifier shall be independent of any specific order | SSR-DIAG-006 | Diagnostic Services — Diagnostic Services | AD-001 | component | RFQX-CVS124-0207 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0208 | The range of a requested dataRecord value has to be checked by the server if the DID is safety relevant.StatementThe range of a requested dataRecord value has to be checked by the server if the DID is safety relevant. | None | None | None | None | RFQX-CVS124-0208 / 16h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0209 | All changed data shall be valid and stored into non-volatile memory at the latest after an ECU Reset(0x11) subfunction 0x02 requested from client.StatementAll changed data shall be valid and stored into non-volatile memory at the latest after an ECU Reset(0x11) subfunction 0x02 requested from client. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS124-0209 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0210 | If it is necessary to force an explicit transfer of buffered data into non-volatile memory then this shall be supported both with ECU-Reset Service subfunction 0x02 and ignition (IGN) key Off/On (power cycle).StatementIf it is necessary to force an explicit transfer of buffered data into non-volatile memory then this shall be supported both with ECU-Reset Service subfunction 0x02 and ignition (IGN) key Off/On (power cycle). | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS124-0210 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0211 | Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed.StatementAdditional client requests which start copying RAM buffer data into non-volatile memory are not allowed. | None | None | None | None | RFQX-CVS124-0211 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0212 | If this action is necessary then it shall be integrated implicitly into ECU Reset (0x11) Service subfunction 0x02.StatementIf this action is necessary then it shall be integrated implicitly into ECU Reset (0x11) Service subfunction 0x02. | None | None | AD-001 | component | RFQX-CVS124-0212 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0213 | Request format and parameter shall be as per ISO 14229-1.StatementRequest format and parameter shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0213 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0214 | 5.5.9 ClearDiagnosticInformation (0x14) service 5.5.9.1 RequestStatement5.5.9 ClearDiagnosticInformation (0x14) service 5.5.9.1 Request | None | None | None | None | RFQX-CVS124-0214 / 26h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0215 | 5.5.9.1.1 Request parameter groupOfDTCStatement5.5.9.1.1 Request parameter groupOfDTC | None | None | None | None | RFQX-CVS124-0215 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0216 | groupOfDTC parameter definition shall be as per ISO 14229-1.StatementgroupOfDTC parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0216 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0217 | 5.5.9.3 Negative responseStatement5.5.9.3 Negative response | None | None | None | None | RFQX-CVS124-0217 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0218 | 5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 RequestStatement5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 Request | None | None | None | None | RFQX-CVS124-0218 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0219 | 5.5.10.1.1 Request parameter reportTypeStatement5.5.10.1.1 Request parameter reportType | None | None | None | None | RFQX-CVS124-0219 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0220 | Table 52 – Service 0x19 request parameter reportType description 0x01 reportNumberOfDTCByStatusMask M 0x02 reportDTCByStatusMask M 0x03 reportDTCSnapshotIdentification M 0x04 reportDTCSnapshotRecordByDTCNumber M 0x06 reportDTCExtendedDataRecordByDTCNumber M 0x0F reportMirrorMemoryDTCByStatusMask UStatementTable 52 – Service 0x19 request parameter reportType description 0x01 reportNumberOfDTCByStatusMask M 0x02 reportDTCByStatusMask M 0x03 reportDTCSnapshotIdentification M 0x04 reportDTCSnapshotRecordByDTCNumber M 0x06 reportDTCExtendedDataRecordByDTCNumber M 0x0F reportMirrorMemoryDTCByStatusMask U | None | None | None | None | RFQX-CVS124-0220 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0221 | Legislated OBD relevant ECUs have to support legislated OBD standards.StatementLegislated OBD relevant ECUs have to support legislated OBD standards. | None | None | None | None | RFQX-CVS124-0221 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0222 | ReportNumberOfDTCByStatusMask parameter format shall be as per ISO 14229-1.StatementReportNumberOfDTCByStatusMask parameter format shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0222 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0223 | DTCStatusMask parameter format shall be as per ISO 14229-1.StatementDTCStatusMask parameter format shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0223 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0224 | Table 53 – Service 0x19 request parameter DTCMaskRecord description Byte Description Cvt High Definition according to either ISO 15031-6, ISO 14229 vehicle- manufacturer-defined, SAE J1939-73 M Middle M Low MStatementTable 53 – Service 0x19 request parameter DTCMaskRecord description Byte Description Cvt High Definition according to either ISO 15031-6, ISO 14229 vehicle- manufacturer-defined, SAE J1939-73 M Middle M Low M | None | None | None | None | RFQX-CVS124-0224 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0225 | It shall be mandatory to utilize SPNs & FMIs according to SAE J1939.StatementIt shall be mandatory to utilize SPNs & FMIs according to SAE J1939. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0225 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0226 | DTCSnapshotRecordNumber parameter format shall be as per ISO 14229-1.StatementDTCSnapshotRecordNumber parameter format shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0226 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0227 | Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M 5.5.10.1.7 Request parameter FunctionalGroupIdentifierStatementTable 54 – Service 0x19 request parameter DTCExtDataRecordNumber description 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M 5.5.10.1.7 Request parameter FunctionalGroupIdentifier | None | None | None | None | RFQX-CVS124-0227 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0228 | Response parameter FunctionalGroupIdentifier shall be as per ISO 14229-1.StatementResponse parameter FunctionalGroupIdentifier shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0228 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0229 | DTCSeverityMaskRecord parameter format shall be as per ISO 14229-1.StatementDTCSeverityMaskRecord parameter format shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0229 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0230 | DTCSeverityMask parameter format shall be as per ISO 14229-1.StatementDTCSeverityMask parameter format shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0230 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0231 | 5.5.10.2.1 Response parameter DTCStatusAvailabilityMaskStatement5.5.10.2.1 Response parameter DTCStatusAvailabilityMask | None | None | None | None | RFQX-CVS124-0231 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0232 | Response parameter DTCStatusAvailabilityMask shall be as per ISO 14229-1.StatementResponse parameter DTCStatusAvailabilityMask shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0232 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0233 | Response parameter DTCFormatIdentifier shall be as per ISO 14229-1.StatementResponse parameter DTCFormatIdentifier shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0233 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0234 | Response parameter DTCCount shall be as per ISO 14229-1.StatementResponse parameter DTCCount shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0234 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0235 | Response parameter DTCAndStatusRecord shall be as per ISO 14229-1.StatementResponse parameter DTCAndStatusRecord shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0235 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0236 | Response parameter DTCRecord shall be as per ISO 14229-1.StatementResponse parameter DTCRecord shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0236 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0237 | 5.5.10.2.6 Response parameter reportDTCSnapshotRecordByDTCNumber The snapshot data sub-function (0x04) shall have positive response message data and format as specified in Table 67.Statement5.5.10.2.6 Response parameter reportDTCSnapshotRecordByDTCNumber The snapshot data sub-function (0x04) shall have positive response message data and format as specified in Table 67. | None | None | AD-001 | component | RFQX-CVS124-0237 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0238 | Table 55 – Snapshot data sub-function (0x04) positive response message content and format Range tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = [ reportDTCSnapshotRecordByDTCNumber ] = 0x04 M #3 : #6 DTCAndStatusRecord[] = [ Byte 1: DTCHighByte Byte 2: DTCMiddleByte Byte 3: DTCLowByte Byte 4: statusOfDTC 0xFF 0xFF 0xFF 0xFF M M M M #7 DTCSnapshotRecordNumber#1 This byte shall be set to value 0x01.StatementTable 55 – Snapshot data sub-function (0x04) positive response message content and format Range tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = [ reportDTCSnapshotRecordByDTCNumber ] = 0x04 M #3 : #6 DTCAndStatusRecord[] = [ Byte 1: DTCHighByte Byte 2: DTCMiddleByte Byte 3: DTCLowByte Byte 4: statusOfDTC 0xFF 0xFF 0xFF 0xFF M M M M #7 DTCSnapshotRecordNumber#1 This byte shall be set to value 0x01. | SSR-DIAG-006 | Diagnostic Services — Diagnostic Services | AD-001 | component | RFQX-CVS124-0238 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0239 | If a mechanic is working on the vehicle, the driveline shall report Not Ready and place the vehicle in the state PropulsionNotReady.StatementIf a mechanic is working on the vehicle, the driveline shall report Not Ready and place the vehicle in the state PropulsionNotReady. | None | None | AD-008 | component | RFQX-CVS124-0239 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0240 | Range tion #54 ECU start-up and alive reasons Bits 0-3 (start-up reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6-0xE: Reserved 0xF: Not available Bits 4-7 (alive reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6: Stay alive 0x7-0xE: Reserved 0xF: Not available Note 1: While the reason for keeping the ECU alive may change during execution startup reason and alive reason are always identical at ECU startup.StatementRange tion #54 ECU start-up and alive reasons Bits 0-3 (start-up reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6-0xE: Reserved 0xF: Not available Bits 4-7 (alive reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6: Stay alive 0x7-0xE: Reserved 0xF: Not available Note 1: While the reason for keeping the ECU alive may change during execution startup reason and alive reason are always identical at ECU startup. | None | None | None | None | RFQX-CVS124-0240 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0241 | dependent depend ent depende nt U #65+N+M- #66+N+M dataIdentifier 0x0000 – #67+N+M +P Data required by law or regulations Signal dependent depend ent depende nt C1 #68+N+M +P DTCSnapshotRecordNumber#2 (Latest Snapshot captured) 0x02 M #69+N+M +P DTCSnapshotRecordNumberOfIdentifiers#2 0x00 : 0xFF M #70+N+M +P : #70+2*(N +M+P) See specification for DTCSnapshotRecord[]#1 This latest snapshot shall contain the same type of data and format as DTCSnapshotRecord[]#1.Statementdependent depend ent depende nt U #65+N+M- #66+N+M dataIdentifier 0x0000 – #67+N+M +P Data required by law or regulations Signal dependent depend ent depende nt C1 #68+N+M +P DTCSnapshotRecordNumber#2 (Latest Snapshot captured) 0x02 M #69+N+M +P DTCSnapshotRecordNumberOfIdentifiers#2 0x00 : 0xFF M #70+N+M +P : #70+2*(N +M+P) See specification for DTCSnapshotRecord[]#1 This latest snapshot shall contain the same type of data and format as DTCSnapshotRecord[]#1. | None | None | AD-005 | interface | RFQX-CVS124-0241 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0242 | DTCSnapshotRecordNumber#1 & DTCSnapshotRecordNumber#2 shall correspond to first time DTC happened and latest time DTC happened correspondingly.StatementDTCSnapshotRecordNumber#1 & DTCSnapshotRecordNumber#2 shall correspond to first time DTC happened and latest time DTC happened correspondingly. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0242 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0243 | Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M 5.5.10.2.8 Response parameter DTCExtDataRecordStatementTable 56 – Service 0x19 response parameter DTCExtDataRecordNumber description 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M 5.5.10.2.8 Response parameter DTCExtDataRecord | None | None | None | None | RFQX-CVS124-0243 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0244 | The extended data sub-function (0x06) shall have the positive response message data and format specified in Table 68.StatementThe extended data sub-function (0x06) shall have the positive response message data and format specified in Table 68. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0244 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0245 | Table 57 – Extended data sub-function (0x06) positive response message content and format Byte Description Range Resolu tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = reportDTCExtDataRecordByDTCNumber 0x06 M #3 : #6 DTCAndStatusRecord[] = [ DTCHighByte DTCMiddleByte DTCLowByte statusOfDTC ] M #7 DTCExtDataRecordNumber#1 This byte shall be set to value 0x11.StatementTable 57 – Extended data sub-function (0x06) positive response message content and format Byte Description Range Resolu tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = reportDTCExtDataRecordByDTCNumber 0x06 M #3 : #6 DTCAndStatusRecord[] = [ DTCHighByte DTCMiddleByte DTCLowByte statusOfDTC ] M #7 DTCExtDataRecordNumber#1 This byte shall be set to value 0x11. | None | None | AD-001 | component | RFQX-CVS124-0245 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0246 | Byte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #9 Occurrence counter OCC, as described in section 5.7.2 [unsigned integer] 0..127 0 M #10 DTC priority 1 – Highest priority 2 - Second highest priority 3 – Lowest priority 255 – Unknown 1..3, 255 0xFF M #11..#16 Time/Date of the first DTC activation See Table 98 but without byte #7 and #8 M #17..#22 Time/Date of the latest DTC activation M #23..#26 ECU Operational hours at the first DTC activation [4-byte int, big endian] as described in section 5.7.5.2.StatementByte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #9 Occurrence counter OCC, as described in section 5.7.2 [unsigned integer] 0..127 0 M #10 DTC priority 1 – Highest priority 2 - Second highest priority 3 – Lowest priority 255 – Unknown 1..3, 255 0xFF M #11..#16 Time/Date of the first DTC activation See Table 98 but without byte #7 and #8 M #17..#22 Time/Date of the latest DTC activation M #23..#26 ECU Operational hours at the first DTC activation [4-byte int, big endian] as described in section 5.7.5.2. | None | None | AD-006 | component | RFQX-CVS124-0246 / 56h | Not imported | Still Requires Customer Decision | P1 OPEN | boundary ownership | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0247 | For these ECUs these bytes shall contain default value 0xFF (all bytes).StatementFor these ECUs these bytes shall contain default value 0xFF (all bytes). | None | None | AD-008 | component | RFQX-CVS124-0247 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0248 | Byte Description Range Resolu tion 0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m #35..#38 Total vehicle distance at the latest DTC activation [4-byte int, big endian] in section 5.7.4.1 Not used for TRATON External engine and marine ECUsFor these ECUs these bytes shall contain default value 0xFF (all bytes).StatementByte Description Range Resolu tion 0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m #35..#38 Total vehicle distance at the latest DTC activation [4-byte int, big endian] in section 5.7.4.1 Not used for TRATON External engine and marine ECUsFor these ECUs these bytes shall contain default value 0xFF (all bytes). | None | None | AD-008 | component | RFQX-CVS124-0248 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0249 | 0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m 0xFFF FFFFF 5 m/bit 0xFF (all bytes) C #41+(2p+1) +1 DTCExtDataRecordNumber#4 This byte shall be set to value 0x14.Statement0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m 0xFFF FFFFF 5 m/bit 0xFF (all bytes) C #41+(2p+1) +1 DTCExtDataRecordNumber#4 This byte shall be set to value 0x14. | None | None | AD-008 | component | RFQX-CVS124-0249 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0250 | Response parameter FunctionalGroupIdentifier shall be as per ISO 14229-1.StatementResponse parameter FunctionalGroupIdentifier shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0250 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0251 | Response parameter DTCSeverityAvailabilityMask shall be as per ISO 14229-1.StatementResponse parameter DTCSeverityAvailabilityMask shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0251 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0252 | Response parameter DTCAndSeverityRecord shall be as per ISO 14229-1.StatementResponse parameter DTCAndSeverityRecord shall be as per ISO 14229-1. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0252 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0253 | 5.5.10.3.1 Supported negative response codesStatement5.5.10.3.1 Supported negative response codes | None | None | None | None | RFQX-CVS124-0253 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0254 | Negative response codes shall be as per ISO 14229-1.StatementNegative response codes shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0254 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0255 | 5.5.11.1.1 Request parameter dataIdentifierStatement5.5.11.1.1 Request parameter dataIdentifier | None | None | None | None | RFQX-CVS124-0255 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0256 | The data identifier ranges specified in ISO 14229-1 shall be followed.StatementThe data identifier ranges specified in ISO 14229-1 shall be followed. | SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | AD-003 | component | RFQX-CVS124-0256 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0257 | Table 58 – Service 0x2F request parameter controlOptionRecord description 1 inputOutputControlParameter M 2 ..StatementTable 58 – Service 0x2F request parameter controlOptionRecord description 1 inputOutputControlParameter M 2 .. | None | None | None | None | RFQX-CVS124-0257 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0258 | Table 59 – Service 0x2F request parameter inputOutputControlParameter description 0x00 returnControlToECU Refer to ISO 14229-1 for parameter description.StatementTable 59 – Service 0x2F request parameter inputOutputControlParameter description 0x00 returnControlToECU Refer to ISO 14229-1 for parameter description. | None | None | None | None | RFQX-CVS124-0258 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0259 | ControlEnableMaskRecord parameter format shall be as per ISO 14229-1.StatementControlEnableMaskRecord parameter format shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0259 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0260 | 5.5.11.3 Negative responseStatement5.5.11.3 Negative response | None | None | None | None | RFQX-CVS124-0260 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0261 | 5.5.12 RoutineControl (0x31) service 5.5.12.1 RequestStatement5.5.12 RoutineControl (0x31) service 5.5.12.1 Request | None | None | None | None | RFQX-CVS124-0261 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0262 | 5.5.12.1.1 Request parameter RoutineControlTypeStatement5.5.12.1.1 Request parameter RoutineControlType | None | None | None | None | RFQX-CVS124-0262 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0263 | Table 60 – Service 0x31 request parameter RoutineControlType description 0x01 startRoutine M 0x02 stopRoutine C 0x03 requestRoutineResults C C = Mandatory for routines implemented according to Method “A”.StatementTable 60 – Service 0x31 request parameter RoutineControlType description 0x01 startRoutine M 0x02 stopRoutine C 0x03 requestRoutineResults C C = Mandatory for routines implemented according to Method “A”. | None | None | None | None | RFQX-CVS124-0263 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0264 | Request parameter routineIdentifier shall be as per ISO 14229-1.StatementRequest parameter routineIdentifier shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0264 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0265 | The routine IDs as listed in Table 61 are reserved by TRATON and shall not be used by the system supplier.StatementThe routine IDs as listed in Table 61 are reserved by TRATON and shall not be used by the system supplier. | None | None | AD-008 | component | RFQX-CVS124-0265 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0266 | Table 61 – Service 0x31 request parameter RoutineIdentifier description 0x02B2 0x02B3 0x02B4 ReadStatusOfDiagnosticEventCodesStatementTable 61 – Service 0x31 request parameter RoutineIdentifier description 0x02B2 0x02B3 0x02B4 ReadStatusOfDiagnosticEventCodes | None | None | None | None | RFQX-CVS124-0266 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0267 | Request parameter routineControlOptionRecord shall be as per ISO 14229-1.StatementRequest parameter routineControlOptionRecord shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0267 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0268 | 5.5.12.3 Negative responseStatement5.5.12.3 Negative response | None | None | None | None | RFQX-CVS124-0268 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0269 | 5.5.13 Request Download Service (0x34)Statement5.5.13 Request Download Service (0x34) | None | None | None | None | RFQX-CVS124-0269 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0270 | If the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall start erasing the memory area specified with the RequestDownload request.StatementIf the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall start erasing the memory area specified with the RequestDownload request. | SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | AD-006 | component | RFQX-CVS124-0270 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0271 | In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint.StatementIn order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint. | None | None | None | None | RFQX-CVS124-0271 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0272 | If the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall reset the following identification DIDs to their default values: • If boot software download is requested, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules).StatementIf the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall reset the following identification DIDs to their default values: • If boot software download is requested, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules). | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0272 / 16h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0273 | Once the RequestDownload service has started, only services TesterPresent, ECUReset,TransferData and DiagnosticSessionControl shall be permitted until service RequestTransferExit has been called or until any of these services returns an error.StatementOnce the RequestDownload service has started, only services TesterPresent, ECUReset,TransferData and DiagnosticSessionControl shall be permitted until service RequestTransferExit has been called or until any of these services returns an error. | SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-001 | component | RFQX-CVS124-0273 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0274 | If a non-permitted service is requested after the RequestDownload service has started and before RequestTransferExit has been called the server shall respond with NRC 0x12 (subStatementIf a non-permitted service is requested after the RequestDownload service has started and before RequestTransferExit has been called the server shall respond with NRC 0x12 (sub | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0274 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0275 | The server shall support service request formatted according to Table 62.StatementThe server shall support service request formatted according to Table 62. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0275 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0276 | Table 63 – Service 0x34 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xFStatementTable 63 – Service 0x34 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF | None | None | None | None | RFQX-CVS124-0276 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0277 | Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 5.5.13.4 Positive responseStatementTable 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 5.5.13.4 Positive response | None | None | None | None | RFQX-CVS124-0277 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0278 | Table 65 – Positive response parameter description #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier M 0x20 #3..StatementTable 65 – Positive response parameter description #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier M 0x20 #3.. | None | None | None | None | RFQX-CVS124-0278 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0279 | Table 66 – Service 0x34 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.StatementTable 66 – Service 0x34 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved. | None | None | None | None | RFQX-CVS124-0279 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0280 | Table 67 – Service 0x35 request parameter description 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier M 4 ..StatementTable 67 – Service 0x35 request parameter description 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier M 4 .. (m-1)+4 | None | None | None | None | RFQX-CVS124-0280 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0281 | Table 68 – Service 0x35 request parameter dataFormatIdentifier description Bytes Description Cvt Values compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1StatementTable 68 – Service 0x35 request parameter dataFormatIdentifier description Bytes Description Cvt Values compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 | None | None | None | None | RFQX-CVS124-0281 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0282 | RequestStatementRequest | None | None | None | None | RFQX-CVS124-0282 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0283 | Table 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 5.5.14.1.3 Request parameter memoryAddressStatementTable 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 5.5.14.1.3 Request parameter memoryAddress | None | None | None | None | RFQX-CVS124-0283 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0284 | MemoryAddress parameter definition shall be as per ISO 14229-1.StatementMemoryAddress parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0284 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0285 | MemorySize parameter definition shall be as per ISO 14229-1.StatementMemorySize parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0285 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0286 | 5.5.14.2.1 Response parameter lengthFormatIdentifierStatement5.5.14.2.1 Response parameter lengthFormatIdentifier | None | None | None | None | RFQX-CVS124-0286 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0287 | Table 70 – Service 0x35 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.StatementTable 70 – Service 0x35 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved. | None | None | None | None | RFQX-CVS124-0287 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0288 | Refer to ISO 14229-1 for negative response format and codes shall be as per ISO 14229-1.StatementRefer to ISO 14229-1 for negative response format and codes shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0288 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0289 | MemoryAddress parameter definition shall be as per ISO 14229-1.StatementMemoryAddress parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0289 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0290 | MemorySize parameter definition shall be as per ISO 14229-1.StatementMemorySize parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0290 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0291 | 5.5.15.3 Negative responseStatement5.5.15.3 Negative response | None | None | None | None | RFQX-CVS124-0291 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0292 | 5.5.15.3.1 Supported negative response codesStatement5.5.15.3.1 Supported negative response codes | None | None | None | None | RFQX-CVS124-0292 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0293 | 5.5.16 RequestTransferExit (0x37) service 5.5.16.1 RequestStatement5.5.16 RequestTransferExit (0x37) service 5.5.16.1 Request | None | None | None | None | RFQX-CVS124-0293 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0294 | Table 71 – Service 0x37 request parameter description 1 RequestTransferExit Request SID M 5.5.16.1.1 Request parameter transferRequestParameterRecordStatementTable 71 – Service 0x37 request parameter description 1 RequestTransferExit Request SID M 5.5.16.1.1 Request parameter transferRequestParameterRecord | None | None | None | None | RFQX-CVS124-0294 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0295 | The transferRequestParameterRecord shall not be supported.StatementThe transferRequestParameterRecord shall not be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0295 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0296 | Table 72 – Service 0x37 positive response parameter description 1 RequestTransferExit Response SID MStatementTable 72 – Service 0x37 positive response parameter description 1 RequestTransferExit Response SID M | None | None | None | None | RFQX-CVS124-0296 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0297 | The transferRequestParameterRecord shall not be supported.StatementThe transferRequestParameterRecord shall not be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0297 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0298 | 5.5.16.3.1 Supported negative response codesStatement5.5.16.3.1 Supported negative response codes | None | None | None | None | RFQX-CVS124-0298 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0299 | 5.5.17 SecuredDataTransmission (0x84) serviceStatement5.5.17 SecuredDataTransmission (0x84) service | None | None | None | None | RFQX-CVS124-0299 / 16h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0300 | This service shall be used when transmitting data in a secured mode, see CVS32.StatementThis service shall be used when transmitting data in a secured mode, see CVS32. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0300 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0301 | 5.5.17.1.1 Request message data-parameter definitionStatement5.5.17.1.1 Request message data-parameter definition | None | None | None | None | RFQX-CVS124-0301 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0302 | Data parameter definition shall be as per ISO 14229-1.StatementData parameter definition shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0302 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0303 | Positive response shall be as per CVS32.StatementPositive response shall be as per CVS32. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0303 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0304 | Negative response shall be as per CVS32 5.5.17.3.1 Supported negative response codesStatementNegative response shall be as per CVS32 5.5.17.3.1 Supported negative response codes | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0304 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0305 | Negative response format shall be as per ISO 14229-1 5.5.18 Authentication (0x29) serviceStatementNegative response format shall be as per ISO 14229-1 5.5.18 Authentication (0x29) service | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS124-0305 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0306 | Authentication (0x29) service shall be used for authentication of client and server.StatementAuthentication (0x29) service shall be used for authentication of client and server. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS124-0306 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0307 | The Authentication (0x29) service shall be implemented according to CVS31 .StatementThe Authentication (0x29) service shall be implemented according to CVS31 . | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS124-0307 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0308 | Refer to CVS31 .StatementRefer to CVS31 . | None | None | None | None | RFQX-CVS124-0308 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0309 | Refer to CVS31 .StatementRefer to CVS31 . | None | None | None | None | RFQX-CVS124-0309 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0310 | Refer to CVS31 .StatementRefer to CVS31 . | None | None | None | None | RFQX-CVS124-0310 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0311 | 5.5.18.4.1 Supported negative response codesStatement5.5.18.4.1 Supported negative response codes | None | None | None | None | RFQX-CVS124-0311 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0312 | Supported negative response codes shall be as per ISO 14229-1, especially the NRC range 0x50 – 0x5D according to Table 73.StatementSupported negative response codes shall be as per ISO 14229-1, especially the NRC range 0x50 – 0x5D according to Table 73. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0312 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0313 | For detailed error cases and the mapping to the corresponding NRCs the Authentication service implementation specification CVS31 shall be used.StatementFor detailed error cases and the mapping to the corresponding NRCs the Authentication service implementation specification CVS31 shall be used. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0313 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0314 | 5.5.19.2 Request Parameter modeOfOperationStatement5.5.19.2 Request Parameter modeOfOperation | None | None | None | None | RFQX-CVS124-0314 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0315 | Table 74 – Service 0x38 request parameter modeOfOperation description Byte value Description Cvt 0x00 ISO Reserved M 0x01 AddFile This value shall be used to add the file (download) defined in the filePathAndName parameter M 0x02 DeleteFile This value shall be used to delete the file defined in the filePathAndName parameter U 0x03 ReplaceFile This value shall be used to replace the file (download) defined in the filePathAndName parameter.StatementTable 74 – Service 0x38 request parameter modeOfOperation description Byte value Description Cvt 0x00 ISO Reserved M 0x01 AddFile This value shall be used to add the file (download) defined in the filePathAndName parameter M 0x02 DeleteFile This value shall be used to delete the file defined in the filePathAndName parameter U 0x03 ReplaceFile This value shall be used to replace the file (download) defined in the filePathAndName parameter. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0315 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0316 | If the file is not stored at the location the file shall be added.StatementIf the file is not stored at the location the file shall be added. | None | None | AD-008 | component | RFQX-CVS124-0316 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0317 | M 0x04 ReadFile This value shall be used to read the file (upload) at the location defined by the filePathAndName parameter.StatementM 0x04 ReadFile This value shall be used to read the file (upload) at the location defined by the filePathAndName parameter. | None | None | AD-008 | component | RFQX-CVS124-0317 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0318 | U 0x05 ReadDir This value shall be used to read the directory defined in the filePathAndName parameter.StatementU 0x05 ReadDir This value shall be used to read the directory defined in the filePathAndName parameter. | None | None | AD-008 | component | RFQX-CVS124-0318 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0319 | U 0x06 ResumeFile This value shall be used to resume downloading the file defined in the filePathAndName parameter at the returned filePosition indicator.StatementU 0x06 ResumeFile This value shall be used to resume downloading the file defined in the filePathAndName parameter at the returned filePosition indicator. | None | None | AD-008 | component | RFQX-CVS124-0319 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0320 | The file specified in the filePathAndName shall already exist in the ECU’s file system.StatementThe file specified in the filePathAndName shall already exist in the ECU’s file system. | None | None | AD-006 | component | RFQX-CVS124-0320 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0321 | Refer to ISO 14229-1 for parameter sub-function format shall be as per ISO 14229-1.StatementRefer to ISO 14229-1 for parameter sub-function format shall be as per ISO 14229-1. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0321 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0322 | Table 75 – Service 0x38 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 5.5.19.5 Positive responseStatementTable 75 – Service 0x38 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 5.5.19.5 Positive response | None | None | None | None | RFQX-CVS124-0322 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0323 | 5.5.19.6 Negative responseStatement5.5.19.6 Negative response | None | None | None | None | RFQX-CVS124-0323 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0324 | 5.5.19.7 Supported negative response codesStatement5.5.19.7 Supported negative response codes | None | None | None | None | RFQX-CVS124-0324 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0325 | Supported negative response codes shall be as per ISO 14229-1.StatementSupported negative response codes shall be as per ISO 14229-1. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0325 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0326 | This RoutineIdentifier enables the client to query the state of the programming preconditions in the server and applicable only for programmable ECUs.StatementThis RoutineIdentifier enables the client to query the state of the programming preconditions in the server and applicable only for programmable ECUs. | None | None | None | None | RFQX-CVS124-0326 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0327 | The programming preconditions shall be agreed with the vehicle manufacturer.StatementThe programming preconditions shall be agreed with the vehicle manufacturer. Preconditions to | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0327 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0328 | Preconditions to be discussed with the vehicle manufacturer shall include but not be limited to Diag safe state conditions.StatementPreconditions to be discussed with the vehicle manufacturer shall include but not be limited to Diag safe state conditions. | None | None | AD-008 | component | RFQX-CVS124-0328 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0329 | The decision on conditions of the programming precondition shall be based on minimum two independent sources of information.StatementThe decision on conditions of the programming precondition shall be based on minimum two independent sources of information. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0329 / 26h | Not imported | No linked clarification | No P1 link | evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0330 | If information is not available for checking a programming precondition the programming precondition shall be considered fulfilled.StatementIf information is not available for checking a programming precondition the programming precondition shall be considered fulfilled. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0330 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0331 | If the ECU received the information related to any of the conditions during the same driving cycle then it shall use that information.StatementIf the ECU received the information related to any of the conditions during the same driving cycle then it shall use that information. | None | None | AD-006 | component | RFQX-CVS124-0331 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0332 | This routine shall be supported in Extended session of both Application and Boot.StatementThis routine shall be supported in Extended session of both Application and Boot. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0332 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0333 | Request parameter RoutineControlOptionRecord shall not be supported.StatementRequest parameter RoutineControlOptionRecord shall not be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0333 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0334 | Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported.StatementRequest parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0334 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0335 | Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingPreconditions [byte#1] M 0x22 #4 routineIdentifier (LSB) checkProgrammingPreconditions [byte#2] M 0x03 #5 routineStatus (byte#1) programmingPreconditionList [byte#1] U 0x00-0xFF #5+m-1 routineStatus (byte#m) programmingPreconditionList [byte#m] U 0x00-0xFFStatementTable 76 – RoutineControl (CheckProgrammingPreconditions) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingPreconditions [byte#1] M 0x22 #4 routineIdentifier (LSB) checkProgrammingPreconditions [byte#2] M 0x03 #5 routineStatus (byte#1) programmingPreconditionList [byte#1] U 0x00-0xFF #5+m-1 routineStatus (byte#m) programmingPreconditionList [byte#m] U 0x00-0xFF | None | None | None | None | RFQX-CVS124-0335 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0336 | Each routineStatus byte shall represent one not satisfied precondition according to Table 18 (see definition of “Satisfied programming precondition”).StatementEach routineStatus byte shall represent one not satisfied precondition according to Table 18 (see definition of “Satisfied programming precondition”). | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0336 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0337 | Which ones of the programming precondition codes in Table 18 that need to be supported shallStatementWhich ones of the programming precondition codes in Table 18 that need to be supported shall | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0337 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0338 | If all preconditions are satisfied, no routineStatus byte shall be reported.StatementIf all preconditions are satisfied, no routineStatus byte shall be reported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0338 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0339 | Programming preconditions that do not map to one of the entries in Table 77 shall be discussed with the vehicle manufacturer.StatementProgramming preconditions that do not map to one of the entries in Table 77 shall be discussed with the vehicle manufacturer. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0339 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0340 | Table 77 – Programming preconditions Hex Description Origin 0x01 Engine speed is not zero Defined by the “manufacturers software initiative” (HIS) 0x02 Engine immobilizer is not released 0x03 Transmission input speed is not zero 0x04 Transmission output speed is not zero 0x05 Vehicle speed is not zero 0x06 Closed-loop control active 0x07 Ignition system off-on required 0x08 No programming voltage 0x09 Ignition (terminal 15) is not turned on 0x0A Supply voltage too low 0x0B Temperature too high 0x0C Temperature too low ..StatementTable 77 – Programming preconditions Hex Description Origin 0x01 Engine speed is not zero Defined by the “manufacturers software initiative” (HIS) 0x02 Engine immobilizer is not released 0x03 Transmission input speed is not zero 0x04 Transmission output speed is not zero 0x05 Vehicle speed is not zero 0x06 Closed-loop control active 0x07 Ignition system off-on required 0x08 No programming voltage 0x09 Ignition (terminal 15) is not turned on 0x0A Supply voltage too low 0x0B Temperature too high 0x0C Temperature too low .. | None | None | AD-001 | component | RFQX-CVS124-0340 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0341 | The server shall respond with a positive response code without erasing memory if the specified memory area has already been completely erased (or is writable) at the time the service is requested.StatementThe server shall respond with a positive response code without erasing memory if the specified memory area has already been completely erased (or is writable) at the time the service is requested. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0341 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0342 | In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint.StatementIn order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint. | None | None | None | None | RFQX-CVS124-0342 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0343 | In case the non volatile memory area is currently hosting a bootloader copy, meaning there is an ongoing bootloader update procedure, the ECU shall ensure that this memory area shall not be erased until a valid bootloader is flashed in the bootloader memory area.StatementIn case the non volatile memory area is currently hosting a bootloader copy, meaning there is an ongoing bootloader update procedure, the ECU shall ensure that this memory area shall not be erased until a valid bootloader is flashed in the bootloader memory area. | SSR-BOOT-002 | Secure software update and flash readiness — Bootloader and Application State Handling | AD-006 | component | RFQX-CVS124-0343 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0344 | SUV2_INFO 114 in CVS123 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader.StatementSUV2_INFO 114 in CVS123 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader. | None | None | None | None | RFQX-CVS124-0344 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0345 | When the addressAndLengthFormatIdentifier parameter is set to a value > 0x00 the server shall reset the following software and data identification DIDs to their default values (seeStatementWhen the addressAndLengthFormatIdentifier parameter is set to a value > 0x00 the server shall reset the following software and data identification DIDs to their default values (see | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0345 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0346 | The erasing of memory shall not prevent the client from starting a data transfer using the TransferData (0x36) service, i.e.StatementThe erasing of memory shall not prevent the client from starting a data transfer using the TransferData (0x36) service, i.e. | SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | AD-001 | component | RFQX-CVS124-0346 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0347 | the erasing of memory shall proceed in parallel with data transfer in case for ECUs implementing Automatic erase.Statementthe erasing of memory shall proceed in parallel with data transfer in case for ECUs implementing Automatic erase. | None | None | AD-006 | component | RFQX-CVS124-0347 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0348 | This routine shall be supported in Programming session.StatementThis routine shall be supported in Programming session. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0348 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0349 | Table 78 – RoutineIdentifier 0xFF00 description #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x00 #5 addressAndLengthFormatIdentifier (XXXXYYYYb) XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter.StatementTable 78 – RoutineIdentifier 0xFF00 description #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x00 #5 addressAndLengthFormatIdentifier (XXXXYYYYb) XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. | None | None | None | None | RFQX-CVS124-0349 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0350 | Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported 5.6.2.2 Request parameter addressAndLengthFormatIdentifierStatementRequest parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported 5.6.2.2 Request parameter addressAndLengthFormatIdentifier | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0350 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0351 | Table 79 – Request parameter addressAndLengthFormatIdentifier values Byte Value Description Cvt 0x00 Automatic erase: Erase is performed by boot loader automatically when RequestDownload is received for each Flash sector in the module.StatementTable 79 – Request parameter addressAndLengthFormatIdentifier values Byte Value Description Cvt 0x00 Automatic erase: Erase is performed by boot loader automatically when RequestDownload is received for each Flash sector in the module. | None | None | None | None | RFQX-CVS124-0351 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0352 | 02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M C = Mandatory if required to meet the performance requirements & &Statement02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M C = Mandatory if required to meet the performance requirements & & | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0352 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0353 | in CVS123.Statementin CVS123. | None | None | None | None | RFQX-CVS124-0353 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0354 | When the addressAndLengthFormatIdentifier is set to 0x01 the following defined module to index mapping shall apply for the memoryStartAddress: 1 – Boot loader 2 – Application 3 – Application Data 4 ...StatementWhen the addressAndLengthFormatIdentifier is set to 0x01 the following defined module to index mapping shall apply for the memoryStartAddress: 1 – Boot loader 2 – Application 3 – Application Data 4 ... | SSR-BOOT-005 | Bootloader and Application State Handling — Bootloader and Application State Handling | AD-001 | component | RFQX-CVS124-0354 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0355 | Table 80 – RoutineControl (EraseMemory) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) eraseMemory [byte#1] M 0xFF #4 routineIdentifier (LSB) eraseMemory [byte#2] M 0x00 #5 routineStatus routineResult M 0x00-0xFFStatementTable 80 – RoutineControl (EraseMemory) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) eraseMemory [byte#1] M 0xFF #4 routineIdentifier (LSB) eraseMemory [byte#2] M 0x00 #5 routineStatus routineResult M 0x00-0xFF | None | None | None | None | RFQX-CVS124-0355 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0356 | The routineResult byte values shall be as specified in Table 81.StatementThe routineResult byte values shall be as specified in Table 81. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0356 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0357 | 5.6.2.5 Message flow example(s) RoutineControl (EraseMemory) Example #1: Request: client → serverStatement5.6.2.5 Message flow example(s) RoutineControl (EraseMemory) Example #1: Request: client → server | None | None | None | None | RFQX-CVS124-0357 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0358 | This is an example where the client requests to erase a module in the server memory by a given memoryStartAddress and memorySize.StatementThis is an example where the client requests to erase a module in the server memory by a given memoryStartAddress and memorySize. | None | None | None | None | RFQX-CVS124-0358 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0359 | This example reports a failure when the erase operation is started, e.g.StatementThis example reports a failure when the erase operation is started, e.g. memory failure. | None | None | None | None | RFQX-CVS124-0359 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0360 | This is an example where the client requests to erase a module with module index 3 in the server’s memory.StatementThis is an example where the client requests to erase a module with module index 3 in the server’s memory. | None | None | None | None | RFQX-CVS124-0360 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0361 | The RoutineIdentifier may verify the authenticity of the received file package.StatementThe RoutineIdentifier may verify the authenticity of the received file package. See CVS123 and | None | None | None | None | RFQX-CVS124-0361 / 18h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0362 | If authenticity verification is valid the server shall initiate all necessary steps for installation of the received file.StatementIf authenticity verification is valid the server shall initiate all necessary steps for installation of the received file. | SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS124-0362 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0363 | The authenticity verification performed by the RoutineIdentifier 0x2401 Software Installation does not exempt the authenticity verification for RoutineIdentifier 0xFF01 – CheckProgrammingDependencies.StatementThe authenticity verification performed by the RoutineIdentifier 0x2401 Software Installation does not exempt the authenticity verification for RoutineIdentifier 0xFF01 – CheckProgrammingDependencies. | None | None | None | None | RFQX-CVS124-0363 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0364 | The server shall send a response to RoutineIdentifier 0x2401 Software Installation without any further inputs from the client.StatementThe server shall send a response to RoutineIdentifier 0x2401 Software Installation without any further inputs from the client. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS124-0364 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0365 | If authenticity verification fails the server shall send the positive response with AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) set to 0x02 (Authenticity Verification Failed) and SoftwareInstallationStatus bit 7-6 (InstallationStatus) set to 0x02 (Installation Failed).StatementIf authenticity verification fails the server shall send the positive response with AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) set to 0x02 (Authenticity Verification Failed) and SoftwareInstallationStatus bit 7-6 (InstallationStatus) set to 0x02 (Installation Failed). | SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS124-0365 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0366 | This routine shall be supported in Programming session.StatementThis routine shall be supported in Programming session. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0366 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0367 | Request parameter RoutineControlOptionRecord shall not be supported.StatementRequest parameter RoutineControlOptionRecord shall not be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0367 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0368 | Positive responses to RoutineControl (Software Installation) service requests shall be formattedStatementPositive responses to RoutineControl (Software Installation) service requests shall be formatted | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0368 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0369 | Description Cvt Values #1 RoutineControl Request SID M 0x71 #2 routineControlType (requestRoutineResults) M 0x03 #3 routineIdentifier (MSB) M 0x24 #4 routineIdentifier (LSB) M 0x01 #5 AuthenticityVerificationStatus M 0x00 – 0xFF #6 SoftwareInstallationStatus M 0x00 – 0xFF #7 CompletionPercentage M 0x00 – 0x64 #8-#9 TimeRemaningEstimative M 0x0000 – 0xFFFF AuthenticityVerificationStatus shall be formatted according to Table 90.StatementDescription Cvt Values #1 RoutineControl Request SID M 0x71 #2 routineControlType (requestRoutineResults) M 0x03 #3 routineIdentifier (MSB) M 0x24 #4 routineIdentifier (LSB) M 0x01 #5 AuthenticityVerificationStatus M 0x00 – 0xFF #6 SoftwareInstallationStatus M 0x00 – 0xFF #7 CompletionPercentage M 0x00 – 0x64 #8-#9 TimeRemaningEstimative M 0x0000 – 0xFFFF AuthenticityVerificationStatus shall be formatted according to Table 90. | SSR-DAI-007 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-008 | component | RFQX-CVS124-0369 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0370 | AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall remain as 0x0 (Software Authenticity Invalid) until the verification completes.StatementAuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall remain as 0x0 (Software Authenticity Invalid) until the verification completes. | SSR-DAI-005 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS124-0370 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0371 | If no authenticity verification will take place as part of RoutineIdentifier, the AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall be changed to 0x1 (Authenticity Verification Successful).StatementIf no authenticity verification will take place as part of RoutineIdentifier, the AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall be changed to 0x1 (Authenticity Verification Successful). | SSR-DAI-007 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-008 | component | RFQX-CVS124-0371 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0372 | SoftwareInstallationStatus shall be formatted according to Table 91.StatementSoftwareInstallationStatus shall be formatted according to Table 91. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0372 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0373 | SoftwareInstallationStatus bit 7-6 (InstallationStatus) shall remain as 0x0 (Installation On-going) until the installation completes.StatementSoftwareInstallationStatus bit 7-6 (InstallationStatus) shall remain as 0x0 (Installation On-going) until the installation completes. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0373 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0374 | Table 91 – SoftwareInstallationStatus Bit Bit Name Bit Values Description 7-6 InstallationStatus 0x0: Installation On-going 0x1: Installation Successful 0x2: Installation Failed 5 - 3 InstallationFailureType 0x0: No Failures 0x1 – 0x7: Project Specific 2 ResetRequired 0x0: Reset not required 0x1: Reset required 1 - 0 Reserved Note: Shall be kept as 0x0 CompletionPercentage shall inform the progress percentage of the software has been installed in the partition memory area.StatementTable 91 – SoftwareInstallationStatus Bit Bit Name Bit Values Description 7-6 InstallationStatus 0x0: Installation On-going 0x1: Installation Successful 0x2: Installation Failed 5 - 3 InstallationFailureType 0x0: No Failures 0x1 – 0x7: Project Specific 2 ResetRequired 0x0: Reset not required 0x1: Reset required 1 - 0 Reserved Note: Shall be kept as 0x0 CompletionPercentage shall inform the progress percentage of the software has been installed in the partition memory area. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0374 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0375 | Information shall be provided in percentage.StatementInformation shall be provided in percentage. | None | None | AD-008 | component | RFQX-CVS124-0375 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0376 | TimeRemaningEstimative shall inform the time estimative to complete the installation of the file.StatementTimeRemaningEstimative shall inform the time estimative to complete the installation of the file. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0376 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0377 | Information shall be provided in seconds.StatementInformation shall be provided in seconds. | None | None | AD-008 | component | RFQX-CVS124-0377 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0378 | Implementation hint can be seen on Annex B.StatementImplementation hint can be seen on Annex B. | None | None | None | None | RFQX-CVS124-0378 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0379 | Whereas the result of the dependency check is returned as part of a positive response, a negative response code (NRC) shall be returned if the normal conditions according to (ISO 14229-1) (authentication, service request length, parameter range check etc) for performing the service are not correct.StatementWhereas the result of the dependency check is returned as part of a positive response, a negative response code (NRC) shall be returned if the normal conditions according to (ISO 14229-1) (authentication, service request length, parameter range check etc) for performing the service are not correct. | None | None | AD-001 | component | RFQX-CVS124-0379 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0380 | This RoutineIdentifier value allows the client to start a consistency check of the server and should be able to execute independent from programming sequence.StatementThis RoutineIdentifier value allows the client to start a consistency check of the server and should be able to execute independent from programming sequence. | None | None | AD-002 | component | RFQX-CVS124-0380 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0381 | The server shall check whether or not the individual modules are complete and compatible withStatementThe server shall check whether or not the individual modules are complete and compatible with | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0381 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0382 | In addition, a check shall be made to determine whether or not the software is compatible with the hardware version (e.g., variants of sensors/actuators) and other data structures (e.g., EEPROM data).StatementIn addition, a check shall be made to determine whether or not the software is compatible with the hardware version (e.g., variants of sensors/actuators) and other data structures (e.g., EEPROM data). | None | None | AD-001 | component | RFQX-CVS124-0382 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS124-0383 | The method used to check compatibility/consistency shall be determined by the supplier in consultation with the vehicle manufacturer.StatementThe method used to check compatibility/consistency shall be determined by the supplier in consultation with the vehicle manufacturer. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0383 / 8h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0384 | The consistency check shall be carried out solely by the server.StatementThe consistency check shall be carried out solely by the server. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0384 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0385 | The server shall verify the authenticity and integrity of the software as a part of the consistency check.StatementThe server shall verify the authenticity and integrity of the software as a part of the consistency check. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS124-0385 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0386 | The authenticity and integrity information shall be supplied to the server before the software is updated.StatementThe authenticity and integrity information shall be supplied to the server before the software is updated. | SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-001 | component | RFQX-CVS124-0386 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0387 | The authenticity and integrity check shall be carried out solely by the server.StatementThe authenticity and integrity check shall be carried out solely by the server. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS124-0387 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0388 | This routine shall be supported in Programming session.StatementThis routine shall be supported in Programming session. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0388 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0389 | The server shall support RoutineControl (CheckProgrammingDependencies) service request formatted according to Table 92.StatementThe server shall support RoutineControl (CheckProgrammingDependencies) service request formatted according to Table 92. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS124-0389 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0390 | Table 92 – RoutineIdentifier 0xFF01 description Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x01 Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported.StatementTable 92 – RoutineIdentifier 0xFF01 description Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x01 Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0390 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0391 | Positive responses to RoutineControl (CheckProgrammingDependencies) service requests shall be formatted according to Table 93.StatementPositive responses to RoutineControl (CheckProgrammingDependencies) service requests shall be formatted according to Table 93. | SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | AD-001 | component | RFQX-CVS124-0391 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0392 | Table 93 – RoutineControl (CheckProgrammingDependencies) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingDependencies[byte#1] M 0xFF #4 routineIdentifier (LSB) checkProgrammingDependencies [byte#2] M 0x01 #5 routineStatus routineResult M 0x00-0xFF Parameter routineResult shall adopt one of the values specified in Table 94.StatementTable 93 – RoutineControl (CheckProgrammingDependencies) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingDependencies[byte#1] M 0xFF #4 routineIdentifier (LSB) checkProgrammingDependencies [byte#2] M 0x01 #5 routineStatus routineResult M 0x00-0xFF Parameter routineResult shall adopt one of the values specified in Table 94. | SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | AD-008 | component | RFQX-CVS124-0392 / 26h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0393 | Table 94 – CheckProgrammingDependencies routineStatusRecord results 0x00 correctResult M 0x01 incorrectResult M 0x02 incorrectResult error SW – HW M 0x03 incorrectResult error SW – SW M 0x04 IncorrectResult One or more modules are not programmed or are incorrectly programmed M 0x05 incorrectResult One or more modules failed when verifying the authenticity and integrity of the software M 0x06 – 0xFF Reserved 5.6.4.3 Negative response Whereas the result of the dependency check is returned as part of a positive response, a negative response code (NRC) shall be returned if the normal conditions according to (ISO 14229-1)(authentication, service request length, parameter range check etc) for performing the service are not correct.StatementTable 94 – CheckProgrammingDependencies routineStatusRecord results 0x00 correctResult M 0x01 incorrectResult M 0x02 incorrectResult error SW – HW M 0x03 incorrectResult error SW – SW M 0x04 IncorrectResult One or more modules are not programmed or are incorrectly programmed M 0x05 incorrectResult One or more modules failed when verifying the authenticity and integrity of the software M 0x06 – 0xFF Reserved 5.6.4.3 Negative response Whereas the result of the dependency check is returned as part of a positive response, a negative response code (NRC) shall be returned if the normal conditions according to (ISO 14229-1)(authentication, service request length, parameter range check etc) for performing the service are not correct. | None | None | AD-001 | component | RFQX-CVS124-0393 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0394 | This is an example where the client requests CheckProgrammingDependencies to finalize the validation after software download.StatementThis is an example where the client requests CheckProgrammingDependencies to finalize the validation after software download. | None | None | None | None | RFQX-CVS124-0394 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0395 | The checksum was contained in the data stream programmed to the memory.StatementThe checksum was contained in the data stream programmed to the memory. | None | None | None | None | RFQX-CVS124-0395 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0396 | Table 95 – Example: Request: client → server #1 RoutineControl Request SID 0x31 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 Example: Positive response: server → client In this example the routine status indicates that the programming dependencies returned correct result.StatementTable 95 – Example: Request: client → server #1 RoutineControl Request SID 0x31 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 Example: Positive response: server → client In this example the routine status indicates that the programming dependencies returned correct result. | None | None | None | None | RFQX-CVS124-0396 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS124-0397 | Table 96 – Positive response: server → client #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 #5 routineStatus (routineResult) 0x00 5.6.5 Routine 0xCAFE – EMP The request and response shall be implemented according to CVS33.StatementTable 96 – Positive response: server → client #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 #5 routineStatus (routineResult) 0x00 5.6.5 Routine 0xCAFE – EMP The request and response shall be implemented according to CVS33. | SSR-UPD-003 | Secure software update and flash readiness — Software Update / Flashing | AD-002 | component | RFQX-CVS124-0397 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0398 | This routine shall be supported in all sessions of Application and Boot.StatementThis routine shall be supported in all sessions of Application and Boot. | SSR-SYS-003 | System Function — System Function | AD-001 | component | RFQX-CVS124-0398 / 18h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0399 | Table 97 – Fault memory DTC status bits description Bit Description Cvt 0 testFailed M 1 testFailedThisOperationCycle U 2 pendingDTC M 3 confirmedDTC M 4 testNotCompletedSinceLastClear E 5 testFailedSinceLastClear U 6 testNotCompletedThisOperationCycle M 7 warningIndicatorRequested MStatementTable 97 – Fault memory DTC status bits description Bit Description Cvt 0 testFailed M 1 testFailedThisOperationCycle U 2 pendingDTC M 3 confirmedDTC M 4 testNotCompletedSinceLastClear E 5 testFailedSinceLastClear U 6 testNotCompletedThisOperationCycle M 7 warningIndicatorRequested M | None | None | None | None | RFQX-CVS124-0399 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0400 | DTC status bits shall not make use of any vehicle manufacturer specific reset condition (e.g.StatementDTC status bits shall not make use of any vehicle manufacturer specific reset condition (e.g. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0400 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0401 | The occurrence counter is used in DTCExtDataRecords, see section 5.5.10.2.8.StatementThe occurrence counter is used in DTCExtDataRecords, see section 5.5.10.2.8. | None | None | None | None | RFQX-CVS124-0401 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0402 | The occurrence counter minimum value shall be zero (0).StatementThe occurrence counter minimum value shall be zero (0). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0402 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0403 | The occurrence counter maximum value shall be 126.StatementThe occurrence counter maximum value shall be 126. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0403 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0404 | The occurrence counter default value shall be zero (0).StatementThe occurrence counter default value shall be zero (0). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0404 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0405 | The occurrence counter shall increment by one (1) only.StatementThe occurrence counter shall increment by one (1) only. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0405 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0406 | The occurrence counter shall increment if it’s value is not at it’s maximum value already.StatementThe occurrence counter shall increment if it’s value is not at it’s maximum value already. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0406 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0407 | The occurrence counter shall increment at a change of DTC status bits 0 testFailed and 3 confirmedDTC both from 0 to 1.StatementThe occurrence counter shall increment at a change of DTC status bits 0 testFailed and 3 confirmedDTC both from 0 to 1. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0407 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0408 | The occurrence counter shall increment at a change of DTC status bit 0 testFailed from 0 to 1,StatementThe occurrence counter shall increment at a change of DTC status bit 0 testFailed from 0 to 1, | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0408 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0409 | The occurrence counter shall increment at a change of DTC status bit 3 confirmedDTC from 0 to 1, if bit 0 testFailed is 1 already.StatementThe occurrence counter shall increment at a change of DTC status bit 3 confirmedDTC from 0 to 1, if bit 0 testFailed is 1 already. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0409 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0410 | The occurrence counter value 127 shall be defined as "errors with the counter".StatementThe occurrence counter value 127 shall be defined as "errors with the counter". | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0410 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0411 | The timestamp of occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8.StatementThe timestamp of occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8. | None | None | None | None | RFQX-CVS124-0411 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0412 | The timestamp default value shall be a 0xFF in each data.StatementThe timestamp default value shall be a 0xFF in each data. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0412 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0413 | The timestamp is presented in SAE J1939-71 format without local hour/minute offsets.StatementThe timestamp is presented in SAE J1939-71 format without local hour/minute offsets. | None | None | None | None | RFQX-CVS124-0413 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0414 | In SAE J1939-71 section “PGN 65254 Time/Date”, the following format is specified: Table 98 – J1939-71 timestamp format Byte No Length Name Resolutio n Offset Note 1 1 byte Seconds 0.25 s/bit 0 2 1 byte Minutes 1 min/bit 0 3 1 byte Hours 1 hr/bit 0 4 1 byte Month 1 month/bit 0 Value 1 identifies January, value 2 identifies February and so on 5 1 byte Day 0.25 days/bit 0 Values 1,2,3 and 4 identifes first day of month, value 5,6,7,8 identifies second day of month and so on 6 1 byte Year 1 year/bit 1985 Value of 0 identifies year 1985, value of 1 identifes year 1986 and so on 7 1 byte Local minute offset 1 min/bit -125 Not used in DTC timestamps 8 1 byte Local hour offset 1 hr/bit -125 Not used in DTC timestampsStatementIn SAE J1939-71 section “PGN 65254 Time/Date”, the following format is specified: Table 98 – J1939-71 timestamp format Byte No Length Name Resolutio n Offset Note 1 1 byte Seconds 0.25 s/bit 0 2 1 byte Minutes 1 min/bit 0 3 1 byte Hours 1 hr/bit 0 4 1 byte Month 1 month/bit 0 Value 1 identifies January, value 2 identifies February and so on 5 1 byte Day 0.25 days/bit 0 Values 1,2,3 and 4 identifes first day of month, value 5,6,7,8 identifies second day of month and so on 6 1 byte Year 1 year/bit 1985 Value of 0 identifies year 1985, value of 1 identifes year 1986 and so on 7 1 byte Local minute offset 1 min/bit -125 Not used in DTC timestamps 8 1 byte Local hour offset 1 hr/bit -125 Not used in DTC timestamps | None | None | None | None | RFQX-CVS124-0414 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0415 | The latest occurrence shall be updated at a change of DTC status bits 0 (testFailed) and 3StatementThe latest occurrence shall be updated at a change of DTC status bits 0 (testFailed) and 3 | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0415 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0416 | The latest occurrence shall be updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already.StatementThe latest occurrence shall be updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already. | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0416 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0417 | If occurrence counter is set to 1, the timestamp of the latest occurrence shall be set to 0xFF.StatementIf occurrence counter is set to 1, the timestamp of the latest occurrence shall be set to 0xFF. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0417 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0418 | The first occurrence shall be updated at the first change of DTC status bits 0 (testFailed) and 3 5.7.4 Vehicle distance at occurrenceStatementThe first occurrence shall be updated at the first change of DTC status bits 0 (testFailed) and 3 5.7.4 Vehicle distance at occurrence | SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | AD-008 | component | RFQX-CVS124-0418 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0419 | The total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8.StatementThe total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8. | None | None | None | None | RFQX-CVS124-0419 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0420 | The vehicle distance shall be represented by a four byte integer, big endian, with five meter per bit (5m/bit).StatementThe vehicle distance shall be represented by a four byte integer, big endian, with five meter per bit (5m/bit). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0420 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0421 | If all sources of vehicle distance information present no current data, the distance information shall be set to 0xFF at all bytes.StatementIf all sources of vehicle distance information present no current data, the distance information shall be set to 0xFF at all bytes. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0421 / 8h | Not imported | No linked clarification | No P1 link | evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0422 | The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3StatementThe latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3 | None | None | None | None | RFQX-CVS124-0422 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0423 | The latest distance value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already.StatementThe latest distance value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already. | None | None | None | None | RFQX-CVS124-0423 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0424 | The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3StatementThe first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3 | None | None | None | None | RFQX-CVS124-0424 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0425 | The operational hours at occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8.StatementThe operational hours at occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8. | None | None | None | None | RFQX-CVS124-0425 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0426 | The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit).StatementThe operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit). | None | None | None | None | RFQX-CVS124-0426 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0427 | If all sources of operational hours information present no current data, the operational hours information shall be set to 0xFF at all bytes.StatementIf all sources of operational hours information present no current data, the operational hours information shall be set to 0xFF at all bytes. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0427 / 8h | Not imported | No linked clarification | No P1 link | evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0428 | The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.StatementThe latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1. | None | None | None | None | RFQX-CVS124-0428 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0429 | The latest operational hours value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already.StatementThe latest operational hours value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already. | None | None | None | None | RFQX-CVS124-0429 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0430 | The first operational hours value is updated at the first change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.StatementThe first operational hours value is updated at the first change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1. | None | None | None | None | RFQX-CVS124-0430 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0431 | The server shall be available for complete diagnostic communication within two seconds after a power on.StatementThe server shall be available for complete diagnostic communication within two seconds after a power on. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0431 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0432 | If diagnostic data is not available in time the ECU should respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) for maximum allowed time.StatementIf diagnostic data is not available in time the ECU should respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) for maximum allowed time. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS124-0432 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0433 | for Linux based systems still running in boot, the server should indicate with DID 0xF1AD that it is running in boot.Statementfor Linux based systems still running in boot, the server should indicate with DID 0xF1AD that it is running in boot. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS124-0433 / 56h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0434 | For P2Server, the minimum value shall be 0 ms, a maximum value shall be 50 ms.StatementFor P2Server, the minimum value shall be 0 ms, a maximum value shall be 50 ms. | SSR-TOOL-004 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-008 | component | RFQX-CVS124-0434 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0435 | For P2Client, a value of 150 ms shall be used.StatementFor P2Client, a value of 150 ms shall be used. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS124-0435 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0436 | For P2*Server, the minimum value shall be 0ms, the maximum value shall be 4000ms.StatementFor P2*Server, the minimum value shall be 0ms, the maximum value shall be 4000ms. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS124-0436 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0437 | For P2*Client, the value estimation given in ISO 14229-2 shall be used.StatementFor P2*Client, the value estimation given in ISO 14229-2 shall be used. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS124-0437 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS124-0438 | The value for P4_Server_max shall be maximum 30 seconds.StatementThe value for P4_Server_max shall be maximum 30 seconds. | SSR-TOOL-004 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-008 | component | RFQX-CVS124-0438 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0439 | The system supplier shall document the implemented value for P4_Server_max.StatementThe system supplier shall document the implemented value for P4_Server_max. | SSR-TOOL-004 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-008 | component | RFQX-CVS124-0439 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS124-0440 | F197 structure addedStatementF197 structure added | None | None | None | None | RFQX-CVS124-0440 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0441 | F198 Request and response formatStatementF198 Request and response format | None | None | None | None | RFQX-CVS124-0441 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0442 | F199 Request and response formatStatementF199 Request and response format | None | None | None | None | RFQX-CVS124-0442 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0443 | F19A Request and response formatStatementF19A Request and response format | None | None | None | None | RFQX-CVS124-0443 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0444 | NRC for RBACC check failuresStatementNRC for RBACC check failures | None | None | None | None | RFQX-CVS124-0444 / 5h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0445 | ,Statement, | None | None | None | None | RFQX-CVS124-0445 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0446 | ,Statement, | None | None | None | None | RFQX-CVS124-0446 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0447 | ,Statement, | None | None | None | None | RFQX-CVS124-0447 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0448 | ,Statement, | None | None | None | None | RFQX-CVS124-0448 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0449 | ,Statement, | None | None | None | None | RFQX-CVS124-0449 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0450 | ,Statement, | None | None | None | None | RFQX-CVS124-0450 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0451 | Requirements, Request and response formats for the ControlDTCSetting(0x85) added.StatementRequirements, Request and response formats for the ControlDTCSetting(0x85) added. | None | None | None | None | RFQX-CVS124-0451 / 16h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0452 | Added semantic Identifier DIDs, changed the NodeUID DID to INTERNALStatementAdded semantic Identifier DIDs, changed the NodeUID DID to INTERNAL | None | None | None | None | RFQX-CVS124-0452 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0453 | Change in the length of NodeUID(0xF1AF)StatementChange in the length of NodeUID(0xF1AF) | None | None | None | None | RFQX-CVS124-0453 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0454 | Change in the retrieval method for NodeUID(0xF1AF)StatementChange in the retrieval method for NodeUID(0xF1AF) | None | None | None | None | RFQX-CVS124-0454 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0455 | 0xF1B9 RBACCIdentifierNumber is changed to MandatoryStatement0xF1B9 RBACCIdentifierNumber is changed to Mandatory | None | None | None | None | RFQX-CVS124-0455 / 18h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0456 | 0xF1BA RBACCStructureVersion,bit-length changedStatement0xF1BA RBACCStructureVersion,bit-length changed | None | None | None | None | RFQX-CVS124-0456 / 18h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0457 | Changes for service (0x84) and (0x31)StatementChanges for service (0x84) and (0x31) | None | None | None | None | RFQX-CVS124-0457 / 18h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS124-0458 | Updated the document referencesStatementUpdated the document references | None | None | None | None | RFQX-CVS124-0458 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0459 | 0XCAFE and 0xFF02 are updated to MandatoryStatement0XCAFE and 0xFF02 are updated to Mandatory | None | None | None | None | RFQX-CVS124-0459 / 26h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS124-0460 | Modifcations on the bit values and new bit addedStatementModifcations on the bit values and new bit added | None | None | None | None | RFQX-CVS124-0460 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0461 | 0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infosStatement0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos | None | None | None | None | RFQX-CVS124-0461 / 26h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS124-0462 | (0x86) service removedStatement(0x86) service removed | None | None | None | None | RFQX-CVS124-0462 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0463 | ,Statement, | None | None | None | None | RFQX-CVS124-0463 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0464 | Removed the reserved DID ranges and 0xF1C1StatementRemoved the reserved DID ranges and 0xF1C1 | None | None | None | None | RFQX-CVS124-0464 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS124-0465 | 0xF19E ODXFileDataIdentifier is removed 2024-10 First issueStatement0xF19E ODXFileDataIdentifier is removed 2024-10 First issue | None | None | None | None | RFQX-CVS124-0465 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0001 | RBAC for diagnostics Foreword This Commercial Vehicle Standard (“CVS151”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.StatementRBAC for diagnostics Foreword This Commercial Vehicle Standard (“CVS151”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates. | None | None | None | None | RFQX-CVS151-0001 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0002 | Any review of this CVS151 shall only be done in agreement with the involved TRATON Group commercial vehicle Affiliates stated in the table below under section “Technical responsibility”.StatementAny review of this CVS151 shall only be done in agreement with the involved TRATON Group commercial vehicle Affiliates stated in the table below under section “Technical responsibility”. | None | None | AD-003 | component | RFQX-CVS151-0002 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS151-0003 | The User shall apply the latest version of this CVS151.StatementThe User shall apply the latest version of this CVS151. | None | None | AD-008 | component | RFQX-CVS151-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS151-0004 | 1 Scope Concepts such as secure-update (CVS37) requires Role Based Access Control (RBAC) for diagnostics (UDS).Statement1 Scope Concepts such as secure-update (CVS37) requires Role Based Access Control (RBAC) for diagnostics (UDS). | None | None | AD-007 | component | RFQX-CVS151-0004 / 56h | Not imported | No linked clarification | No P1 link | boundary ownership; boot/update trust; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS151-0005 | 3 Technical content 3.1 Overview Server/ECUClient/tester UDS Authorize OK/NOTOK UDS request Is the request allowed, based on the client's access rights i.e., compare the client's role/s against the RBACCOK/NOTOK Figure 1 – Overview Figure 1 shows a highlevel view of the RBAC concept.Statement3 Technical content 3.1 Overview Server/ECUClient/tester UDS Authorize OK/NOTOK UDS request Is the request allowed, based on the client's access rights i.e., compare the client's role/s against the RBACCOK/NOTOK Figure 1 – Overview Figure 1 shows a highlevel view of the RBAC concept. | None | None | None | None | RFQX-CVS151-0005 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0006 | Before a client can execute diagnostics services that are under RBAC, the client must perform some type of authorization procedure towards the server/ECU.StatementBefore a client can execute diagnostics services that are under RBAC, the client must perform some type of authorization procedure towards the server/ECU. | None | None | AD-006 | component | RFQX-CVS151-0006 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS151-0007 | The RBAC logic is typically part of the ECU application- and boot-software.StatementThe RBAC logic is typically part of the ECU application- and boot-software. | None | None | None | None | RFQX-CVS151-0007 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0008 | The RBACC is typically injected into the ECU during production, using a secure protocol.StatementThe RBACC is typically injected into the ECU during production, using a secure protocol. | None | None | None | None | RFQX-CVS151-0008 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0009 | As previously mentioned, each ECU (supporting RBAC) will be programmed with an RBACC, RBAC Configuration, containing the rules to drive the RBAC logic.StatementAs previously mentioned, each ECU (supporting RBAC) will be programmed with an RBACC, RBAC Configuration, containing the rules to drive the RBAC logic. | None | None | None | None | RFQX-CVS151-0009 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0010 | The RBACC contains one or several role-configurations (see Figure 2 for a visual representation).StatementThe RBACC contains one or several role-configurations (see Figure 2 for a visual representation). | None | None | None | None | RFQX-CVS151-0010 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0011 | Each RBACC shall only contain one role-configuration per each supported role.StatementEach RBACC shall only contain one role-configuration per each supported role. | SSR-RBAC-005 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-008 | component | RFQX-CVS151-0011 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0012 | The Role field (in the RBACC) can be seen as a key in a dictionary, which means, two role- configurations cannot contain the same Role value.StatementThe Role field (in the RBACC) can be seen as a key in a dictionary, which means, two role- configurations cannot contain the same Role value. | None | None | None | None | RFQX-CVS151-0012 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0013 | A role-configuration, in its turn, contains one or many rules (see Figure 2 for a visual representation).StatementA role-configuration, in its turn, contains one or many rules (see Figure 2 for a visual representation). | None | None | None | None | RFQX-CVS151-0013 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0014 | If conflicting/overlapping rules are found within a role-configuration, the server shall enforce that deny rule takes precedence over the allow rule.StatementIf conflicting/overlapping rules are found within a role-configuration, the server shall enforce that deny rule takes precedence over the allow rule. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0014 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0015 | Each rule can be of either DENY or ALLOW type.StatementEach rule can be of either DENY or ALLOW type. | None | None | None | None | RFQX-CVS151-0015 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0016 | If a matching allow/deny rule is found and all the rule settings are fulfilled, the server shall accept/deny the request.StatementIf a matching allow/deny rule is found and all the rule settings are fulfilled, the server shall accept/deny the request. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0016 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0017 | Considering all the rule setting fulfilled, for matching rules of allow type the server will accept the request and for matching rules of deny type the server will deny the request.StatementConsidering all the rule setting fulfilled, for matching rules of allow type the server will accept the request and for matching rules of deny type the server will deny the request. | None | None | None | None | RFQX-CVS151-0017 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0018 | If a matching rule is found and not all the rule settings are fulfilled, the server shall consider the request rejected for that rule.StatementIf a matching rule is found and not all the rule settings are fulfilled, the server shall consider the request rejected for that rule. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0018 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0019 | The server shall deny a request if no matching rule is found on RBACC.StatementThe server shall deny a request if no matching rule is found on RBACC. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0019 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0020 | All RBACC ALLOW rules have a setting that dictates if a request, matching the rule, must be 14229-1:2020).StatementAll RBACC ALLOW rules have a setting that dictates if a request, matching the rule, must be 14229-1:2020). | None | None | AD-008 | component | RFQX-CVS151-0020 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS151-0021 | Examples of rules within a single role and their expected behaviour: Example 1: A rule in the RBACC states that a role can execute ReadDataByIdentifier 0x22 (see ISO-14229-1:2020) with Confidentiality off.StatementExamples of rules within a single role and their expected behaviour: Example 1: A rule in the RBACC states that a role can execute ReadDataByIdentifier 0x22 (see ISO-14229-1:2020) with Confidentiality off. | None | None | None | None | RFQX-CVS151-0021 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0022 | The RBAC logic is based on an implicit deny principle; meaning, if the RBACC does not explicitly state that a diagnostic request is allowed or denied, then the request is implicitly denied.StatementThe RBAC logic is based on an implicit deny principle; meaning, if the RBACC does not explicitly state that a diagnostic request is allowed or denied, then the request is implicitly denied. | None | None | None | None | RFQX-CVS151-0022 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0023 | The server shall evaluate each role-configuration independently from each other.StatementThe server shall evaluate each role-configuration independently from each other. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0023 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0024 | If conflicting/overlapping rules are found among multiple role-configuration, the server accepts the request as long within one role-configuration the request is allowed.StatementIf conflicting/overlapping rules are found among multiple role-configuration, the server accepts the request as long within one role-configuration the request is allowed. | None | None | None | None | RFQX-CVS151-0024 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0025 | Examples of two roles with overlapping rules and their expected behaviour: Example 5: The RBACC contains two roles with rules that states how the role can execute ReadDataByIdentifier 0x22 (see ISO-14229-1:2020).StatementExamples of two roles with overlapping rules and their expected behaviour: Example 5: The RBACC contains two roles with rules that states how the role can execute ReadDataByIdentifier 0x22 (see ISO-14229-1:2020). | None | None | None | None | RFQX-CVS151-0025 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0026 | If a client/tester has been assigned several roles (i.e., several role-configurations in the RBACC are applicable for the client/tester), and at least one of the applicable role-configuration explicitly allows a particular request, then the request is allowed, regardless of if another applicable role-configuration explicitly denies it.StatementIf a client/tester has been assigned several roles (i.e., several role-configurations in the RBACC are applicable for the client/tester), and at least one of the applicable role-configuration explicitly allows a particular request, then the request is allowed, regardless of if another applicable role-configuration explicitly denies it. | None | None | None | None | RFQX-CVS151-0026 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0027 | See Annex B for a more detailed example of RBACC.StatementSee Annex B for a more detailed example of RBACC. | None | None | None | None | RFQX-CVS151-0027 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0028 | The server shall require that requests are authenticated for allow rules, using e.g., SecuredDataTransmission 0x84 (see CVS31, ISO-14229-1:2020).StatementThe server shall require that requests are authenticated for allow rules, using e.g., SecuredDataTransmission 0x84 (see CVS31, ISO-14229-1:2020). | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0028 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0029 | Allow rules defined in role 0 are an exception to this requirement, see 3.13.StatementAllow rules defined in role 0 are an exception to this requirement, see 3.13. | None | None | None | None | RFQX-CVS151-0029 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0030 | The server and client shall define the RBACC as per the following ASN.1 definition: RBACC ::= SEQUENCE { version OCTET STRING (SIZE(2)), rbacc-id OCTET STRING (SIZE(16)), role-configurations SEQUENCE (SIZE(0..MAX)) OF Role-configuration } Role-configuration ::= SEQUENCE { role INTEGER(0..MAX), pattern-rules-deny SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(2..MAX)), pattern-rules-allow SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(2..MAX)), did-rules-deny SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)), did-rules-allow SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)), rid-rules-deny SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)), rid-rules-allow SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)) }StatementThe server and client shall define the RBACC as per the following ASN.1 definition: RBACC ::= SEQUENCE { version OCTET STRING (SIZE(2)), rbacc-id OCTET STRING (SIZE(16)), role-configurations SEQUENCE (SIZE(0..MAX)) OF Role-configuration } Role-configuration ::= SEQUENCE { role INTEGER(0..MAX), pattern-rules-deny SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(2..MAX)), pattern-rules-allow SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(2..MAX)), did-rules-deny SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)), did-rules-allow SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)), rid-rules-deny SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)), rid-rules-allow SEQUENCE (SIZE(0...MAX)) OF OCTET STRING (SIZE(3)) } | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0030 / 19h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0031 | The version specifies the structure of RBACC.StatementThe version specifies the structure of RBACC. | None | None | None | None | RFQX-CVS151-0031 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0032 | The server shall support in the version field two octets.StatementThe server shall support in the version field two octets. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0032 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0033 | The server shall support major version value 3 and minor version value 0.StatementThe server shall support major version value 3 and minor version value 0. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0033 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0034 | If other versions shall be supported is out of the scope of this document and shall be agreed upon between projects in Traton.StatementIf other versions shall be supported is out of the scope of this document and shall be agreed upon between projects in Traton. | None | None | AD-008 | component | RFQX-CVS151-0034 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership | No closure evidence required | COMPLETE |
| RFQX-CVS151-0035 | Before RBACC is stored, the server shall verify that the server supports the structure indicated in the version number.StatementBefore RBACC is stored, the server shall verify that the server supports the structure indicated in the version number. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0035 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0036 | If the version number does not comply with the server implementation, the server shall reject storing the data.StatementIf the version number does not comply with the server implementation, the server shall reject storing the data. | None | None | AD-002 | component | RFQX-CVS151-0036 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS151-0037 | The server shall report the currently stored RBACC’s version via diagnostics.StatementThe server shall report the currently stored RBACC’s version via diagnostics. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0037 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0038 | See RBACStructureVersion definition in CVS124.StatementSee RBACStructureVersion definition in CVS124. | None | None | None | None | RFQX-CVS151-0038 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0039 | This field identifies the RBACC using 16 octets.StatementThis field identifies the RBACC using 16 octets. | None | None | None | None | RFQX-CVS151-0039 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0040 | The server shall support 16 octets in the rbacc-id field.StatementThe server shall support 16 octets in the rbacc-id field. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0040 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0041 | The server shall report the currently stored RBACC’s rbacc-id via diagnostics.StatementThe server shall report the currently stored RBACC’s rbacc-id via diagnostics. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0041 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0042 | See RBACIdentifierNumber definition in CVS124.StatementSee RBACIdentifierNumber definition in CVS124. | None | None | None | None | RFQX-CVS151-0042 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0043 | A 32-bit unsigned integer that represents one role.StatementA 32-bit unsigned integer that represents one role. | None | None | None | None | RFQX-CVS151-0043 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0044 | The server shall support role-configurations using 32-bit unsigned integer.StatementThe server shall support role-configurations using 32-bit unsigned integer. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0044 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0045 | The server shall support for every entry in the pattern-rules one octet for the pattern rule settings followed by the diagnostic pattern of variable length.StatementThe server shall support for every entry in the pattern-rules one octet for the pattern rule settings followed by the diagnostic pattern of variable length. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS151-0045 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0046 | The diagnostic pattern identifies the diagnostic request.StatementThe diagnostic pattern identifies the diagnostic request. | None | None | None | None | RFQX-CVS151-0046 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0047 | This type of rule can be used to create rules for all types of diagnostic requests.StatementThis type of rule can be used to create rules for all types of diagnostic requests. | None | None | None | None | RFQX-CVS151-0047 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0048 | The server shall support the pattern-rule setting according to Table 1.StatementThe server shall support the pattern-rule setting according to Table 1. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0048 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0049 | Table 1 – Pattern Rule Settings Bit index Name Description 0 Reserved Reserved 1 UDS 0 == This rule is not valid for a UDS-server 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 3 Confidentiality 0 == No confidentiality is required on the diagnostics request 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules.StatementTable 1 – Pattern Rule Settings Bit index Name Description 0 Reserved Reserved 1 UDS 0 == This rule is not valid for a UDS-server 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 3 Confidentiality 0 == No confidentiality is required on the diagnostics request 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. | None | None | AD-002 | component | RFQX-CVS151-0049 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS151-0050 | The server shall support for every entry in the did-rules one octet which represents the did-rule settings followed by two octets that represent the DID.StatementThe server shall support for every entry in the did-rules one octet which represents the did-rule settings followed by two octets that represent the DID. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0050 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0051 | The byte order for DID shall be big endian.StatementThe byte order for DID shall be big endian. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS151-0051 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS151-0052 | This type of rule can be used to create rules for all types of diagnostic requests that makes use of DIDs e.g., ReadDataByIdentifier, WriteDataByIdentifier, DynamicallyDefineDataIdentifier (see ISO 14429-1:2020) etc.StatementThis type of rule can be used to create rules for all types of diagnostic requests that makes use of DIDs e.g., ReadDataByIdentifier, WriteDataByIdentifier, DynamicallyDefineDataIdentifier (see ISO 14429-1:2020) etc. | None | None | None | None | RFQX-CVS151-0052 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0053 | The server shall support the did-rule setting according to Table 2.StatementThe server shall support the did-rule setting according to Table 2. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0053 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0054 | Table 2 – DID Rule Settings Bit index Name Description 0 Reserved Reserved 1 UDS 0 == This rule is not valid for a UDS-server 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 3 Confidentiality 0 == No confidentiality is required on the diagnostics request 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules.StatementTable 2 – DID Rule Settings Bit index Name Description 0 Reserved Reserved 1 UDS 0 == This rule is not valid for a UDS-server 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 3 Confidentiality 0 == No confidentiality is required on the diagnostics request 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. | None | None | AD-002 | component | RFQX-CVS151-0054 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS151-0055 | 4 Read 0 == This rule is not applicable when the DID is being read 1 == This rule is applicable when the DID is being read 5 Write 0 == This rule is not applicable when the DID is being written 1 == This rule is applicable when the DID is being written 6 IO-control 0 == This rule is not applicable when the DID is being used for IO-control 1 == This rule is applicable when the DID is being used for IO-control 7 N/A Reserved for future use 3.9 rid-rules The server shall support for every entry in the rid-rules one octet which represents the rid-rule settings followed by two octets that represent the RID.Statement4 Read 0 == This rule is not applicable when the DID is being read 1 == This rule is applicable when the DID is being read 5 Write 0 == This rule is not applicable when the DID is being written 1 == This rule is applicable when the DID is being written 6 IO-control 0 == This rule is not applicable when the DID is being used for IO-control 1 == This rule is applicable when the DID is being used for IO-control 7 N/A Reserved for future use 3.9 rid-rules The server shall support for every entry in the rid-rules one octet which represents the rid-rule settings followed by two octets that represent the RID. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0055 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0056 | This type of rule can be used to create rules for all types of diagnostic requests that makes use of RIDs.StatementThis type of rule can be used to create rules for all types of diagnostic requests that makes use of RIDs. | None | None | None | None | RFQX-CVS151-0056 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0057 | The server shall support the rid-rule setting according to Table 3.StatementThe server shall support the rid-rule setting according to Table 3. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0057 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0058 | Table 3 – RID Rule Setting Bit index Name Description 0 Reserved Reserved 1 UDS 0 == This rule is not valid for a UDS-server 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 3 Confidentiality 0 == No confidentiality is required on the diagnostics request 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules.StatementTable 3 – RID Rule Setting Bit index Name Description 0 Reserved Reserved 1 UDS 0 == This rule is not valid for a UDS-server 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 3 Confidentiality 0 == No confidentiality is required on the diagnostics request 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. | None | None | AD-002 | component | RFQX-CVS151-0058 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS151-0059 | 4 Start 0 == This rule is not applicable when the RID is being started 1 == This rule is applicable when the RID is being started 5 Stop 0 == This rule is not applicable when the RID is being stopped 1 == This rule is applicable when the RID is being stopped 6 Read-results 0 == This rule is not applicable when the RID results are being read 1 == This rule is applicable when the RID results are being read 7 N/A Reserved for future use 3.10 Extending the Role Based Access Control Configuration using a certificate It is possible to extend the rules (in the RBACC), by including an extension in the user’s/client’s certificate (when certificate-based authorization is being used).Statement4 Start 0 == This rule is not applicable when the RID is being started 1 == This rule is applicable when the RID is being started 5 Stop 0 == This rule is not applicable when the RID is being stopped 1 == This rule is applicable when the RID is being stopped 6 Read-results 0 == This rule is not applicable when the RID results are being read 1 == This rule is applicable when the RID results are being read 7 N/A Reserved for future use 3.10 Extending the Role Based Access Control Configuration using a certificate It is possible to extend the rules (in the RBACC), by including an extension in the user’s/client’s certificate (when certificate-based authorization is being used). | None | None | None | None | RFQX-CVS151-0059 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0060 | If conflicting/overlapping rules are found between the client certificate D-RBACC extension and any rules in the RBAC-configuration in the RBACC, the server shall enforce the rules in the client certificate D-RBACC extension.StatementIf conflicting/overlapping rules are found between the client certificate D-RBACC extension and any rules in the RBAC-configuration in the RBACC, the server shall enforce the rules in the client certificate D-RBACC extension. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS151-0060 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0061 | A snippet from https://datatracker.ietf.org/doc/html/rfc5280#section-4.1 that specifies the layout of a certificate extension.StatementA snippet from https://datatracker.ietf.org/doc/html/rfc5280#section-4.1 that specifies the layout of a certificate extension. | None | None | None | None | RFQX-CVS151-0061 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0062 | The server shall interpret the extnValue (see snipped above) as of one instance of a RBACC (see 3.3).StatementThe server shall interpret the extnValue (see snipped above) as of one instance of a RBACC (see 3.3). | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0062 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0063 | Inside the extnValue (see snipped above) is one instance of a RBACC (see 3.3).StatementInside the extnValue (see snipped above) is one instance of a RBACC (see 3.3). | None | None | None | None | RFQX-CVS151-0063 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0064 | This feature can be particularly useful if you want to create a custom rule-set (which does not map to a role-configuration in the RBACC) for a client/tester without assigning him/her a specific role.StatementThis feature can be particularly useful if you want to create a custom rule-set (which does not map to a role-configuration in the RBACC) for a client/tester without assigning him/her a specific role. | None | None | None | None | RFQX-CVS151-0064 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0065 | It can also be useful if you want to add or remove access rights from a client/tester, that needs access to one or several roles, but should not have access to everything (or should have more access) specified for the assigned roles.StatementIt can also be useful if you want to add or remove access rights from a client/tester, that needs access to one or several roles, but should not have access to everything (or should have more access) specified for the assigned roles. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS151-0065 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0066 | The server shall exert the RBACC roles based on the ECU-diagnostics-Role extension on the client’s certificate.StatementThe server shall exert the RBACC roles based on the ECU-diagnostics-Role extension on the client’s certificate. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS151-0066 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0067 | Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic.StatementFigure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic. | None | None | None | None | RFQX-CVS151-0067 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0068 | The server shall implement RBAC internal logic as per Figure 4.StatementThe server shall implement RBAC internal logic as per Figure 4. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS151-0068 / 19h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0069 | As previously stated and as show in Figure 4, deny rules takes precedence over allow rules.StatementAs previously stated and as show in Figure 4, deny rules takes precedence over allow rules. | None | None | None | None | RFQX-CVS151-0069 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0070 | The RBAC logic starts the process of finding out if the client has a certificate (that extends the RBAC, see 3.10) and/or any exerted roles.StatementThe RBAC logic starts the process of finding out if the client has a certificate (that extends the RBAC, see 3.10) and/or any exerted roles. | None | None | None | None | RFQX-CVS151-0070 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0071 | The server shall implement RBAC pattern rule evaluation logic as per Figure 5.StatementThe server shall implement RBAC pattern rule evaluation logic as per Figure 5. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS151-0071 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0072 | The “request.conditions COMPLIES_WITH rule.settings” refers to evaluate if the request conditions fulfils the expected rule settings.StatementThe “request.conditions COMPLIES_WITH rule.settings” refers to evaluate if the request conditions fulfils the expected rule settings. | None | None | None | None | RFQX-CVS151-0072 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0073 | E.g: For the evaluate pattern the rule setting Confidentiality is set to 0x01 (Confidentiality is required).StatementE.g: For the evaluate pattern the rule setting Confidentiality is set to 0x01 (Confidentiality is required). | None | None | AD-008 | component | RFQX-CVS151-0073 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS151-0074 | The server shall implement RBAC did rule evaluate as per Figure 6.StatementThe server shall implement RBAC did rule evaluate as per Figure 6. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0074 / 19h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0075 | The server shall implement RBAC rid rule evaluate as per Figure 7.StatementThe server shall implement RBAC rid rule evaluate as per Figure 7. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0075 / 19h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0076 | In Figure 8, the RBAC complete rule evaluation logic is described.StatementIn Figure 8, the RBAC complete rule evaluation logic is described. | None | None | None | None | RFQX-CVS151-0076 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0077 | The role-configuration containing Role 0 is special, it specifies rules that apply to all clients (regardless of whether the client has been assigned a diagnostics role or not).StatementThe role-configuration containing Role 0 is special, it specifies rules that apply to all clients (regardless of whether the client has been assigned a diagnostics role or not). | None | None | None | None | RFQX-CVS151-0077 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0078 | Meaning, role 0 is particularly useful for defining services, DIDs and RIDs that should be available to all clients/users, regardless of their diagnostics role and/or authorization/authentication status.StatementMeaning, role 0 is particularly useful for defining services, DIDs and RIDs that should be available to all clients/users, regardless of their diagnostics role and/or authorization/authentication status. | SSR-RBAC-005 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-008 | component | RFQX-CVS151-0078 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0079 | The server shall allow requests that are contained in role 0 rules regardless of the client authentication state.StatementThe server shall allow requests that are contained in role 0 rules regardless of the client authentication state. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0079 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0080 | The server shall allow request that are contained in role 0 rule regardless if the request is data authenticated e.g over e.g., SecuredDataTransmission 0x84 (See CVS31, ISO 14229-1:2020).StatementThe server shall allow request that are contained in role 0 rule regardless if the request is data authenticated e.g over e.g., SecuredDataTransmission 0x84 (See CVS31, ISO 14229-1:2020). | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0080 / 19h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0081 | The server shall allow request that are contained in role 0 rule regardless of the value of Confidentiality field setting.StatementThe server shall allow request that are contained in role 0 rule regardless of the value of Confidentiality field setting. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS151-0081 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0082 | This means that in role 0 encryption is never required.StatementThis means that in role 0 encryption is never required. | None | None | AD-008 | component | RFQX-CVS151-0082 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS151-0083 | The server shall always allow reception of UDS authenticate 0x29 requests regardless of the RBACC settings.StatementThe server shall always allow reception of UDS authenticate 0x29 requests regardless of the RBACC settings. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS151-0083 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0084 | For 0x29 requests a corresponding matching rule in the RBACC is not required for the server to accept the request.StatementFor 0x29 requests a corresponding matching rule in the RBACC is not required for the server to accept the request. | None | None | AD-002 | component | RFQX-CVS151-0084 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS151-0085 | The server shall evaluate the reported internal service using the RBACC rules whenever it receives a UDS Service 0x84 requests.StatementThe server shall evaluate the reported internal service using the RBACC rules whenever it receives a UDS Service 0x84 requests. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS151-0085 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0086 | The server shall always allow reception of UDS SecuredDataTransmission 0x84 requests regardless of the RBACC settings.StatementThe server shall always allow reception of UDS SecuredDataTransmission 0x84 requests regardless of the RBACC settings. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0086 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0087 | For 0x84 requests a corresponding matching rule in the RBACC is not required for the server to accept the 0x84 request but the server must find a corresponding matching rule for the internal request contained in the 0x84 prior to execute it.StatementFor 0x84 requests a corresponding matching rule in the RBACC is not required for the server to accept the 0x84 request but the server must find a corresponding matching rule for the internal request contained in the 0x84 prior to execute it. | None | None | AD-002 | component | RFQX-CVS151-0087 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS151-0088 | The server shall always allow reception of UDS TesterPresent 0x3E requests regardless of the RBACC settings.StatementThe server shall always allow reception of UDS TesterPresent 0x3E requests regardless of the RBACC settings. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS151-0088 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS151-0089 | For 0x3E requests a corresponding matching rule in the RBACC is not required for the server to accept the request.StatementFor 0x3E requests a corresponding matching rule in the RBACC is not required for the server to accept the request. | None | None | AD-002 | component | RFQX-CVS151-0089 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS151-0090 | Refreshing the S3 timer (see CVS124), e.g., using TesterPresent (0x3E) (see CVS37), is always possible to do outside the secure channel and regardless of the settings in the RBACC role configuration.StatementRefreshing the S3 timer (see CVS124), e.g., using TesterPresent (0x3E) (see CVS37), is always possible to do outside the secure channel and regardless of the settings in the RBACC role configuration. | None | None | None | None | RFQX-CVS151-0090 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS151-0091 | Annex D DynamicallyDefineDataIdentifier When this service is being used, each DID included in the request must be evaluated against the rules that are applicable for the client (the rules in the client’s certificate and in the RBACC).StatementAnnex D DynamicallyDefineDataIdentifier When this service is being used, each DID included in the request must be evaluated against the rules that are applicable for the client (the rules in the client’s certificate and in the RBACC). | None | None | AD-007 | component | RFQX-CVS151-0091 / 56h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure | No closure evidence required | COMPLETE |
| RFQX-CVS151-0092 | The client must have read access for all included DIDs and have access to the service themselves.StatementThe client must have read access for all included DIDs and have access to the service themselves. | None | None | AD-001 | component | RFQX-CVS151-0092 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS151-0093 | When the client is performing the actual read operation (ReadDataByIdentifier [7]), the conditions and rules for all DIDs, aliased by the dynamically defined identifier, must be met, otherwise the request shall be rejected with an appropriate NRC.StatementWhen the client is performing the actual read operation (ReadDataByIdentifier [7]), the conditions and rules for all DIDs, aliased by the dynamically defined identifier, must be met, otherwise the request shall be rejected with an appropriate NRC. | None | None | AD-008 | component | RFQX-CVS151-0093 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS151-0094 | Since reading of DIDs can be allowed by either a pattern-rule (starting with 22 [7]) and/or a DID-rule, both the pattern-rules and the DID-rules must be parsed when evaluating each DID.StatementSince reading of DIDs can be allowed by either a pattern-rule (starting with 22 [7]) and/or a DID-rule, both the pattern-rules and the DID-rules must be parsed when evaluating each DID. | None | None | AD-005 | interface | RFQX-CVS151-0094 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS154-0001 | Data Security Container base definition Foreword This Commercial Vehicle Standard (“CVS154”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.StatementData Security Container base definition Foreword This Commercial Vehicle Standard (“CVS154”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates. | None | None | None | None | RFQX-CVS154-0001 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0002 | Any review of this CVS154 shall only be done in agreement with the involved TRATON Group commercial vehicle Affiliates stated in the table below under section “Technical responsibility”.StatementAny review of this CVS154 shall only be done in agreement with the involved TRATON Group commercial vehicle Affiliates stated in the table below under section “Technical responsibility”. | None | None | AD-003 | component | RFQX-CVS154-0002 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS154-0003 | The User shall apply the latest version of this CVS154.StatementThe User shall apply the latest version of this CVS154. | None | None | AD-008 | component | RFQX-CVS154-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS154-0004 | This document shall be used accompanied with these specifications.StatementThis document shall be used accompanied with these specifications. | None | None | AD-008 | component | RFQX-CVS154-0004 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS154-0005 | See further chapter 3.2 DSC ASN.1 definition for element types.StatementSee further chapter 3.2 DSC ASN.1 definition for element types. | None | None | None | None | RFQX-CVS154-0005 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0006 | The DSC is divided in a metadata header block and three configuration blocks as shown in Figure 2 verificationEntries[..] encryptionEntries[..] itemEntries[..] id version Metadata Figure 2 – DSC structureStatementThe DSC is divided in a metadata header block and three configuration blocks as shown in Figure 2 verificationEntries[..] encryptionEntries[..] itemEntries[..] id version Metadata Figure 2 – DSC structure | None | None | None | None | RFQX-CVS154-0006 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0007 | • version: specifies a version of the DSC structure, namely the DSC ASN.1 definition and its elements within the DSC instance.Statement• version: specifies a version of the DSC structure, namely the DSC ASN.1 definition and its elements within the DSC instance. | None | None | None | None | RFQX-CVS154-0007 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0008 | The server shall support a DSC Metadata block containing version and id fields.StatementThe server shall support a DSC Metadata block containing version and id fields. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0008 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0009 | The server shall support the Major and Minor version as specified in 3.2.StatementThe server shall support the Major and Minor version as specified in 3.2. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0009 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0010 | The server shall support a DSC containing verificationEntries.StatementThe server shall support a DSC containing verificationEntries. | SSR-VV-002 | Security evidence and traceability — Verification and Validation | AD-002 | component | RFQX-CVS154-0010 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0011 | The server shall support a DSC containing encryptionEntries.StatementThe server shall support a DSC containing encryptionEntries. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0011 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0012 | The server shall support a DSC containing itemEntries.StatementThe server shall support a DSC containing itemEntries. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0012 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0013 | The server shall expect an ASN.1 SEQUENCE tag with length zero for verificationEntries that contains no VerificationEntry items in a DSC transmitted by the client.StatementThe server shall expect an ASN.1 SEQUENCE tag with length zero for verificationEntries that contains no VerificationEntry items in a DSC transmitted by the client. | SSR-VV-002 | Security evidence and traceability — Verification and Validation | AD-002 | component | RFQX-CVS154-0013 / 16h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0014 | The server shall expect an ASN.1 SEQUENCE tag with length zero for encryptionEntries that contains no EncryptionEntry items in a DSC transmitted by the client.StatementThe server shall expect an ASN.1 SEQUENCE tag with length zero for encryptionEntries that contains no EncryptionEntry items in a DSC transmitted by the client. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0014 / 16h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0015 | The server shall expect an ASN.1 SEQUENCE tag with length zero for ItemEntries that contains no items in a DSC transmitted by the client.StatementThe server shall expect an ASN.1 SEQUENCE tag with length zero for ItemEntries that contains no items in a DSC transmitted by the client. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0015 / 16h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0016 | The server shall support an empty DSC containing only Metadata (version and id) and the empty sequences for verificationEntries, encryptionEntries and ItemEntries.StatementThe server shall support an empty DSC containing only Metadata (version and id) and the empty sequences for verificationEntries, encryptionEntries and ItemEntries. | SSR-VV-002 | Security evidence and traceability — Verification and Validation | AD-002 | component | RFQX-CVS154-0016 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0017 | An empty DSC issued by client means that in addition to Metadata, the syntax must be correct in accordance with Annex B.StatementAn empty DSC issued by client means that in addition to Metadata, the syntax must be correct in accordance with Annex B. | None | None | AD-008 | component | RFQX-CVS154-0017 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS154-0018 | A DSC containing only version and id states that verification and encryption is not to be performed by the server, although the server shall have the support.StatementA DSC containing only version and id states that verification and encryption is not to be performed by the server, although the server shall have the support. | None | None | AD-002 | component | RFQX-CVS154-0018 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS154-0019 | The VerificationEntry is of ASN.1 type CHOICE, where the choice stipulates the verification strategy for a piece of data.StatementThe VerificationEntry is of ASN.1 type CHOICE, where the choice stipulates the verification strategy for a piece of data. | None | None | None | None | RFQX-CVS154-0019 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0020 | See 3.2 for the context-specific tag number for the VerificationEntry choices.StatementSee 3.2 for the context-specific tag number for the VerificationEntry choices. | None | None | None | None | RFQX-CVS154-0020 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0021 | VerificationEntry hashCmp states that a hash comparison shall be used to verify the data.StatementVerificationEntry hashCmp states that a hash comparison shall be used to verify the data. | SSR-VV-001 | Security evidence and traceability — Verification and Validation | AD-008 | component | RFQX-CVS154-0021 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0022 | When the server is instructed to verify the programmed data, in general the following actions are taken by the server.StatementWhen the server is instructed to verify the programmed data, in general the following actions are taken by the server. | None | None | None | None | RFQX-CVS154-0022 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0023 | However, the instance specification may state specialized actions: • Server processes each VerificationEntry one by one.StatementHowever, the instance specification may state specialized actions: • Server processes each VerificationEntry one by one. | None | None | None | None | RFQX-CVS154-0023 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0024 | Definition of hashCmp fields: Refer to Figure 3 for type definitions of each field.StatementDefinition of hashCmp fields: Refer to Figure 3 for type definitions of each field. | None | None | None | None | RFQX-CVS154-0024 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0025 | • hashAlgorithm: States which HashAlgorithm (see RFC 6234) shall be used for hashing the data to verify.Statement• hashAlgorithm: States which HashAlgorithm (see RFC 6234) shall be used for hashing the data to verify. | None | None | AD-008 | component | RFQX-CVS154-0025 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS154-0026 | • dataRanges: sequence of Range items - Range: Information on which data chunks that shall be verified.Statement• dataRanges: sequence of Range items - Range: Information on which data chunks that shall be verified. | None | None | AD-008 | component | RFQX-CVS154-0026 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS154-0027 | The server shall support the SHA512 HashAlgorithm as referred in 3.2 ASN1 definition.StatementThe server shall support the SHA512 HashAlgorithm as referred in 3.2 ASN1 definition. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0027 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0028 | The encryptionEntry is of ASN.1 type CHOICE stipulating the decryption strategy for a piece of data.StatementThe encryptionEntry is of ASN.1 type CHOICE stipulating the decryption strategy for a piece of data. | None | None | None | None | RFQX-CVS154-0028 / 8h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0029 | For crypto agility reasons, both of the choices shall be supported by the server.StatementFor crypto agility reasons, both of the choices shall be supported by the server. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0029 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0030 | See 3.2 for the context-specific tag number for the EncryptionEntry choices.StatementSee 3.2 for the context-specific tag number for the EncryptionEntry choices. | None | None | None | None | RFQX-CVS154-0030 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0031 | The initial counter value shall be set to 0 (zero).StatementThe initial counter value shall be set to 0 (zero). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS154-0031 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS154-0032 | Range: Information on which data chunks that shall be decrypted.StatementRange: Information on which data chunks that shall be decrypted. | None | None | AD-008 | component | RFQX-CVS154-0032 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS154-0033 | An ItemEntry is of ASN.1 type CHOICE, where the choice stipulates the type of item the ItemEntry holds.StatementAn ItemEntry is of ASN.1 type CHOICE, where the choice stipulates the type of item the ItemEntry holds. | None | None | None | None | RFQX-CVS154-0033 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS154-0034 | The structure version for this document release shall be: Major ‘04’ and Minor ‘00’StatementThe structure version for this document release shall be: Major ‘04’ and Minor ‘00’ | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS154-0034 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS154-0035 | The server shall have support for the ASN.1 contents as defined: DataSecurityContainer ::= SEQUENCE { version OCTET STRING (SIZE(2)), id OCTET STRING (SIZE(16)), verificationEntries SEQUENCE (SIZE(0..MAX)) OF VerificationEntry, encryptionEntries SEQUENCE (SIZE(0..MAX)) OF EncryptionEntry, itemEntries SEQUENCE (SIZE(0..MAX)) OF ItemEntry } VerificationEntry ::= CHOICE { hashCmp [0] EXPLICIT HashCmp }StatementThe server shall have support for the ASN.1 contents as defined: DataSecurityContainer ::= SEQUENCE { version OCTET STRING (SIZE(2)), id OCTET STRING (SIZE(16)), verificationEntries SEQUENCE (SIZE(0..MAX)) OF VerificationEntry, encryptionEntries SEQUENCE (SIZE(0..MAX)) OF EncryptionEntry, itemEntries SEQUENCE (SIZE(0..MAX)) OF ItemEntry } VerificationEntry ::= CHOICE { hashCmp [0] EXPLICIT HashCmp } | None | None | AD-002 | component | RFQX-CVS154-0035 / 19h | Not imported | Still Requires Customer Decision | P1 OPEN | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | SECURITY REVIEW OPEN |
| RFQX-CVS154-0036 | Upon reception of a DSC to the server, before the DSC is stored in NVM, the DSC shall be semantically verified by parsing all its content.StatementUpon reception of a DSC to the server, before the DSC is stored in NVM, the DSC shall be semantically verified by parsing all its content. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS154-0036 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0037 | The length of the version field shall be verified.StatementThe length of the version field shall be verified. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS154-0037 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS154-0038 | The version shall be verified with the servers supported Major and Minor version of the DSC logic for compliancy.StatementThe version shall be verified with the servers supported Major and Minor version of the DSC logic for compliancy. | SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-001 | component | RFQX-CVS154-0038 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0039 | The length of the id field shall be verified.StatementThe length of the id field shall be verified. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS154-0039 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS154-0040 | The hashAlgorithm shall be supported by the server.StatementThe hashAlgorithm shall be supported by the server. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0040 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0041 | The length of every referenceHash shall be consistent with the output size of the hash algorithm specified in the hashAlgorithm.StatementThe length of every referenceHash shall be consistent with the output size of the hash algorithm specified in the hashAlgorithm. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS154-0041 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS154-0042 | The verification of servers support of specified dataRanges in the VerificationEntry, shall be stated for the DSC instance.StatementThe verification of servers support of specified dataRanges in the VerificationEntry, shall be stated for the DSC instance. | None | None | AD-008 | component | RFQX-CVS154-0042 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS154-0043 | The EncryptionEntry algorithm shall be supported by the server.StatementThe EncryptionEntry algorithm shall be supported by the server. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0043 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0044 | The length of key and iv shall be verified accordingly to the algorithm stipulated in EncryptionEntry.StatementThe length of key and iv shall be verified accordingly to the algorithm stipulated in EncryptionEntry. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS154-0044 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0045 | The verification of servers support of specified dataRanges in the EncryptionEntry, shall be stated for the DSC instance.StatementThe verification of servers support of specified dataRanges in the EncryptionEntry, shall be stated for the DSC instance. | None | None | AD-008 | component | RFQX-CVS154-0045 / 56h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS154-0046 | If the DSC instance is rejected by the server (see Annex A) when transmitted with EMP, an error code shall be returned to the client.StatementIf the DSC instance is rejected by the server (see Annex A) when transmitted with EMP, an error code shall be returned to the client. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS154-0046 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS154-0047 | The sequence tags for verificationEntries, encryptionEntries and itemEntries are required but empty (zero length).StatementThe sequence tags for verificationEntries, encryptionEntries and itemEntries are required but empty (zero length). | None | None | AD-008 | component | RFQX-CVS154-0047 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0001 | The User shall apply the latest version of this CVS31.StatementThe User shall apply the latest version of this CVS31. | None | None | AD-008 | component | RFQX-CVS31-0001 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0002 | Foreword This CVS31 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.StatementForeword This CVS31 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable. | None | None | None | None | RFQX-CVS31-0002 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0003 | Any review of CVS31 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”.StatementAny review of CVS31 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”. | None | None | AD-003 | component | RFQX-CVS31-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0004 | The whole standard has been reworked and shall be read in its entirety.StatementThe whole standard has been reworked and shall be read in its entirety. | None | None | AD-008 | component | RFQX-CVS31-0004 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0005 | • Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch.Statement• Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch. | None | None | AD-002 | component | RFQX-CVS31-0005 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0006 | SummaryStatementThe purpose of this document is to clarify vehicle manufacture specific extensions and exceptions to the Authentication 0x29 service specified in ISO 14229-1:2020. CVS150 Cryptographic Specification CVS32 SecuredDataTransmis sion 0x84 CVS151 RBAC CVS33 Entity Management Protocol (EMP) CVS31 Authenticate 0x29 CVS124 Traton Specification on Unified diagnostic services (UDS) CVS30 X.509 Specification CVS34 EMP – Basic Entities Figure 1 – Overview of relation between specifications The following documents are normative and indispensable for the application of this document: • Traton Specification on Unified diagnostic Services (UDS) requirements (CVS124) • ISO 14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements Whenever a requirement in this specification or the Traton Specification on Unified diagnostic Services (UDS) requirements (CVS124) is non-compliant with one or more requirements in ISO 14229-1:2020 the requirements in this specification and (CVS124) take precedence. Any deviations from this specification shall be documented and must be reviewed by the vehicle manufacturer. It is the vehicle manufacturer that decides if a deviation can be accepted or not. Multiple security concepts are available in the Authentication (ISO 14229-1:2020) service, however, only APCE (ISO 14229-1:2020) is supported by the concept described in this document, see Figure 2. | SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS31-0006 / 29h | Not imported | Still Requires Customer Decision | P1 OPEN | boundary ownership; certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | SECURITY REVIEW OPEN |
| RFQX-CVS31-0007 | Any deviations from this specification shall be documented and must be reviewed by the vehicle manufacturer.StatementAny deviations from this specification shall be documented and must be reviewed by the vehicle manufacturer. | None | None | AD-008 | component | RFQX-CVS31-0007 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0008 | Shall be agreed between the supplier and the vehicle manufacturer.StatementShall be agreed between the supplier and the vehicle manufacturer. | None | None | AD-008 | component | RFQX-CVS31-0008 / 24h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0009 | It contains the information required for the server to verify the client’s subsequent request and to generate the corresponding response.StatementIt contains the information required for the server to verify the client’s subsequent request and to generate the corresponding response. | None | None | AD-002 | component | RFQX-CVS31-0009 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0010 | It contains the information required for the server to maintain continuous authenticated communication with the client and to generate authenticated responses.StatementIt contains the information required for the server to maintain continuous authenticated communication with the client and to generate authenticated responses. | None | None | AD-002 | component | RFQX-CVS31-0010 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0011 | This section of the document describes vehicle manufacturer specific requirements regarding the behaviour and content of the subFunctions (ISO 14229-1:2020) found in Table 4.StatementThis section of the document describes vehicle manufacturer specific requirements regarding the behaviour and content of the subFunctions (ISO 14229-1:2020) found in Table 4. | None | None | None | None | RFQX-CVS31-0011 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0012 | The server shall only support subfunctions in Table 4.StatementThe server shall only support subfunctions in Table 4. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0012 / 21h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0013 | In this document, each subFunction (ISO 14229-1:2020) is described in its own sub-section.StatementIn this document, each subFunction (ISO 14229-1:2020) is described in its own sub-section. | None | None | None | None | RFQX-CVS31-0013 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0014 | The server shall not accept an application-layer service 0x29 request when it is received inside an SDT (service 0x84) protected message.StatementThe server shall not accept an application-layer service 0x29 request when it is received inside an SDT (service 0x84) protected message. | SSR-RBAC-006 | Secure communication and freshness protection — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS31-0014 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0015 | If such an encapsulated 0x29 request is detected, the server shall return application-layer NRC 0x39, provided as a correctly formatted SDT positive response.StatementIf such an encapsulated 0x29 request is detected, the server shall return application-layer NRC 0x39, provided as a correctly formatted SDT positive response. | None | None | AD-001 | component | RFQX-CVS31-0015 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0016 | The request for verifyCertificateBidirectional subfunction shall be formatted according toStatementThe request for verifyCertificateBidirectional subfunction shall be formatted according to | SSR-KEY-002 | Key and Certificate Handling — Key and Certificate Handling | AD-008 | component | RFQX-CVS31-0016 / 32h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0017 | Table 5 – verifyCertificateBidirectional Request Field Description Type/Value Cvt Included in proofOfOwnershipServer Authentication Request SID Service ID for Authentication service request 0x29 M Yes verifyCertificateBidirectional] Initiate Authentication by verifying the Certificate and generating a Proof of Ownership from the server 0x02 M Yes communicationConfiguration NOT USED 0x00 M Yes lengthOfCertificateClient Length parameter for certificateClient uint16 M Yes certificateClient The Certificate to verify uint8[] M Yes lengthOfChallengeClient Length parameter for challengeClient uint16 M Yes challengeClient See 3.1.1.1 uint8[] M Yes Upon reception of a verifyCertificateBidirectional request, the server shall determine whether the Authentication delay timer is currently running.StatementTable 5 – verifyCertificateBidirectional Request Field Description Type/Value Cvt Included in proofOfOwnershipServer Authentication Request SID Service ID for Authentication service request 0x29 M Yes verifyCertificateBidirectional] Initiate Authentication by verifying the Certificate and generating a Proof of Ownership from the server 0x02 M Yes communicationConfiguration NOT USED 0x00 M Yes lengthOfCertificateClient Length parameter for certificateClient uint16 M Yes certificateClient The Certificate to verify uint8[] M Yes lengthOfChallengeClient Length parameter for challengeClient uint16 M Yes challengeClient See 3.1.1.1 uint8[] M Yes Upon reception of a verifyCertificateBidirectional request, the server shall determine whether the Authentication delay timer is currently running. | SSR-DAI-001 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS31-0017 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; certificate/key handling; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0018 | For details on Authentication delay timer, refer to chapter 4.8.StatementFor details on Authentication delay timer, refer to chapter 4.8. | None | None | None | None | RFQX-CVS31-0018 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0019 | If upon reception of verifyCertificateBidirectional request the Authentication delay timer is expired, the server shall continue to process the verifyCertificateBidirectional request.StatementIf upon reception of verifyCertificateBidirectional request the Authentication delay timer is expired, the server shall continue to process the verifyCertificateBidirectional request. | SSR-KEY-003 | Key and Certificate Handling — Key and Certificate Handling | AD-002 | component | RFQX-CVS31-0019 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0020 | The column “Included in proofOfOwnershipServer”, present in several message-definition tables, indicates whether the corresponding field shall be covered by the proofOfOwnershipServer signature computed by the server and included in its response.StatementThe column “Included in proofOfOwnershipServer”, present in several message-definition tables, indicates whether the corresponding field shall be covered by the proofOfOwnershipServer signature computed by the server and included in its response. | None | None | AD-002 | component | RFQX-CVS31-0020 / 56h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0021 | If the server verifies the client certificate as valid, the server shall create the requested client authentication pending state.StatementIf the server verifies the client certificate as valid, the server shall create the requested client authentication pending state. | SSR-DAI-001 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS31-0021 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0022 | If an authentication pending state already exists, the server shall replace the existingStatementIf an authentication pending state already exists, the server shall replace the existing | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0022 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0023 | For details in how to validate a client certificate, refer to chapter 4.1.StatementFor details in how to validate a client certificate, refer to chapter 4.1. | None | None | None | None | RFQX-CVS31-0023 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0024 | This field shall consists of 32 octets.StatementThis field shall consists of 32 octets. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0024 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0025 | The challengeClient (ISO 14229-1:2020) shall be generated using a CRNG.StatementThe challengeClient (ISO 14229-1:2020) shall be generated using a CRNG. | SSR-SYS-002 | System Function — System Function | AD-003 | component | RFQX-CVS31-0025 / 10h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0026 | The expected range values of lengthOfCertificateClient shall be from 0x00C8 to 0x0800.StatementThe expected range values of lengthOfCertificateClient shall be from 0x00C8 to 0x0800. | SSR-KEY-002 | Key and Certificate Handling — Key and Certificate Handling | AD-008 | component | RFQX-CVS31-0026 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0027 | The server shall verify the value of lengthOfCertificateClient upon reception of verifyCertificateBidirectional request.StatementThe server shall verify the value of lengthOfCertificateClient upon reception of verifyCertificateBidirectional request. | SSR-KEY-003 | Key and Certificate Handling — Key and Certificate Handling | AD-002 | component | RFQX-CVS31-0027 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0028 | If the lengthOfCertificateClient value is not within the expected range, the server shall send negative response code 0x13 (incorrectMessageLengthOrInvalidFormat).StatementIf the lengthOfCertificateClient value is not within the expected range, the server shall send negative response code 0x13 (incorrectMessageLengthOrInvalidFormat). | SSR-KEY-003 | Key and Certificate Handling — Key and Certificate Handling | AD-002 | component | RFQX-CVS31-0028 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0029 | The response for verifyCertificateBidirectional subfunction shall be formatted according to Table 6.StatementThe response for verifyCertificateBidirectional subfunction shall be formatted according to Table 6. | SSR-KEY-002 | Key and Certificate Handling — Key and Certificate Handling | AD-008 | component | RFQX-CVS31-0029 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0030 | Upon positively responding, the server shall start the Authentication completion timer.StatementUpon positively responding, the server shall start the Authentication completion timer. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0030 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0031 | The challengeServer field shall consists of 32 octets generated using a CRNG.StatementThe challengeServer field shall consists of 32 octets generated using a CRNG. | SSR-TOOL-004 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-008 | component | RFQX-CVS31-0031 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0032 | This field consists of a signature that proves to the client that the server has access to the private key of the provided certificateServer (ISO 14229-1:2020).StatementThis field consists of a signature that proves to the client that the server has access to the private key of the provided certificateServer (ISO 14229-1:2020). Additionally, the field proves that the same message sent by the client has been received by the server and vice-versa. | None | None | None | None | RFQX-CVS31-0032 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0033 | The proof/signature shall be generated according to the pseudo code below.StatementThe proof/signature shall be generated according to the pseudo code below. | SSR-DAI-008 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-008 | component | RFQX-CVS31-0033 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0034 | For obvious reasons, the proofOfOwnershipServer in the VerifyCertificates is not included, in the “concatenation” (see pseudo code above) when the signature/proof is being calculated.StatementFor obvious reasons, the proofOfOwnershipServer in the VerifyCertificates is not included, in the “concatenation” (see pseudo code above) when the signature/proof is being calculated. | None | None | None | None | RFQX-CVS31-0034 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0035 | This field provides the client with the necessary server-side data for the chosen key-exchange scheme/algorithm.StatementThis field provides the client with the necessary server-side data for the chosen key-exchange scheme/algorithm. | None | None | None | None | RFQX-CVS31-0035 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0036 | If upon reception of verifyCertificateBidirectional request the Authentication delay timer is running, the server shall respond to the verifyCertificateBidirectional request with a Negative Response Code (NRC) 0x37, indicating requiredTimeDelayNotExpired.StatementIf upon reception of verifyCertificateBidirectional request the Authentication delay timer is running, the server shall respond to the verifyCertificateBidirectional request with a Negative Response Code (NRC) 0x37, indicating requiredTimeDelayNotExpired. | SSR-KEY-003 | Key and Certificate Handling — Key and Certificate Handling | AD-002 | component | RFQX-CVS31-0036 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0037 | If the server verifies the client certificate as invalid, it shall respond to the verifyCertificateBidirectional request with a Negative Response Code (NRC) 0x10, indicating generalReject.StatementIf the server verifies the client certificate as invalid, it shall respond to the verifyCertificateBidirectional request with a Negative Response Code (NRC) 0x10, indicating generalReject. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0037 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0038 | If the server fails or cannot determine that the authentication pending state was stored, it shall respond to the verifyCertificateBidirectional request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable.StatementIf the server fails or cannot determine that the authentication pending state was stored, it shall respond to the verifyCertificateBidirectional request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable. | SSR-KEY-003 | Key and Certificate Handling — Key and Certificate Handling | AD-002 | component | RFQX-CVS31-0038 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity; evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0039 | This subfunction (ISO 14229-1:2020) serves several purposes – it proves to the server that the client owns the private key of the provided certificateClient (ISO 14229-1:2020).StatementThis subfunction (ISO 14229-1:2020) serves several purposes – it proves to the server that the client owns the private key of the provided certificateClient (ISO 14229-1:2020). | None | None | None | None | RFQX-CVS31-0039 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0040 | The request for proofOfOwnership subfunction shall be defined according to Table 7.StatementThe request for proofOfOwnership subfunction shall be defined according to Table 7. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0040 / 18h | Not imported | No linked clarification | No P1 link | boundary ownership | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0041 | If the client’s proofOfOwnership signature is successfully verified, the server shall establish a new authentication state for the client.StatementIf the client’s proofOfOwnership signature is successfully verified, the server shall establish a new authentication state for the client. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS31-0041 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0042 | Table 7 – proofOfOwnership Request Field Description Type/Value Cvt Included in proofOfOwnershipClient Authentication Request SID Service ID for 0x29 M Yes proofOfOwnership] Verify the Proof of Ownership from the client 0x03 M Yes lengthOfProofOfOwnershipClient This field indicates the length (in octets) of the proofOfOwnershipClient field proofOfOwnershipClient See 3.2.1.1 uint8[] M No lengthOfEphemeralPublicKey Client Length parameter for ephemeralPublicKey Client ephemeralPublicKeyClient See 3.2.1.2 uint16 M Yes The server shall verify whether any existing authentication pending state corresponds to the client submitting the proofOfOwnership request.StatementTable 7 – proofOfOwnership Request Field Description Type/Value Cvt Included in proofOfOwnershipClient Authentication Request SID Service ID for 0x29 M Yes proofOfOwnership] Verify the Proof of Ownership from the client 0x03 M Yes lengthOfProofOfOwnershipClient This field indicates the length (in octets) of the proofOfOwnershipClient field proofOfOwnershipClient See 3.2.1.1 uint8[] M No lengthOfEphemeralPublicKey Client Length parameter for ephemeralPublicKey Client ephemeralPublicKeyClient See 3.2.1.2 uint16 M Yes The server shall verify whether any existing authentication pending state corresponds to the client submitting the proofOfOwnership request. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS31-0042 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; certificate/key handling; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0043 | If an existing authentication pending state is found, the server shall verify if the Authentication completion timer is currently running.StatementIf an existing authentication pending state is found, the server shall verify if the Authentication completion timer is currently running. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0043 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0044 | For details on Authentication completion timer, refer to chapter 4.9.StatementFor details on Authentication completion timer, refer to chapter 4.9. | None | None | None | None | RFQX-CVS31-0044 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0045 | If the Authentication completion timer is currently running, the server shall continue to process the client’s proofOfOwnership request.StatementIf the Authentication completion timer is currently running, the server shall continue to process the client’s proofOfOwnership request. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0045 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0046 | If the client proofOfOwnership signature verification fails, the server shall delete the authentication pending state connected to the client submitting the proofOfOwnership request.StatementIf the client proofOfOwnership signature verification fails, the server shall delete the authentication pending state connected to the client submitting the proofOfOwnership request. | SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS31-0046 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0047 | If the server fails or cannot determine that the authentication state was stored, the server shall delete the authentication pending state connected to the client submitting the proofOfOwnership request.StatementIf the server fails or cannot determine that the authentication state was stored, the server shall delete the authentication pending state connected to the client submitting the proofOfOwnership request. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS31-0047 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0048 | If the client’s proofOfOwnership signature is successfully verified, the server shall establish a new authentication state for the client.StatementIf the client’s proofOfOwnership signature is successfully verified, the server shall establish a new authentication state for the client. | SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS31-0048 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0049 | If an active authentication state already exists, the server shall replace the existing state with the newly established one.StatementIf an active authentication state already exists, the server shall replace the existing state with the newly established one. | None | None | AD-002 | component | RFQX-CVS31-0049 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0050 | The field proofOfOwnershipClient is a signature that proves to the server that the client has access to the private key of the certificateClient (ISO 14229-1:2020).StatementThe field proofOfOwnershipClient is a signature that proves to the server that the client has access to the private key of the certificateClient (ISO 14229-1:2020). | None | None | None | None | RFQX-CVS31-0050 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0051 | The proofOfOwnershipClient shall be generated according to the pseudo code below.StatementThe proofOfOwnershipClient shall be generated according to the pseudo code below. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0051 / 21h | Not imported | No linked clarification | No P1 link | boundary ownership | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0052 | The reason for the concatenation, is to ensure that the full communication (all sent and received requests and responses) has integrity.StatementThe reason for the concatenation, is to ensure that the full communication (all sent and received requests and responses) has integrity. | None | None | None | None | RFQX-CVS31-0052 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0053 | This field provides the server with the necessary client-side data for the chosen key-exchange scheme/algorithm.StatementThis field provides the server with the necessary client-side data for the chosen key-exchange scheme/algorithm. | None | None | None | None | RFQX-CVS31-0053 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0054 | The response for proofOfOwnership subfunction shall be according to Table 8.StatementThe response for proofOfOwnership subfunction shall be according to Table 8. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0054 / 21h | Not imported | No linked clarification | No P1 link | boundary ownership | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0055 | The sessionKeyInfo includes a signature that proves to the client that the server has accepted the proofOfOwnership (ISO 14229-1:2020).StatementThe sessionKeyInfo includes a signature that proves to the client that the server has accepted the proofOfOwnership (ISO 14229-1:2020). | None | None | None | None | RFQX-CVS31-0055 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0056 | The signature shall be generated according to the pseudo code below.StatementThe signature shall be generated according to the pseudo code below. | SSR-DAI-008 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-008 | component | RFQX-CVS31-0056 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0057 | For obvious reasons, the sessionKeyInfo in the ProofOfOwnershipres is not included, in the “concatenation” (see pseudo code above) when the signature is being calculated.StatementFor obvious reasons, the sessionKeyInfo in the ProofOfOwnershipres is not included, in the “concatenation” (see pseudo code above) when the signature is being calculated. | None | None | None | None | RFQX-CVS31-0057 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0058 | If the server determines that the client does not have an existing authentication pending state, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x24, indicating requestSequenceError.StatementIf the server determines that the client does not have an existing authentication pending state, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x24, indicating requestSequenceError. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0058 / 26h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0059 | If the server determines that the client have an existing authentication pending state and the Authentication completion timer is expired, the server shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x24, indicating requestSequenceError.StatementIf the server determines that the client have an existing authentication pending state and the Authentication completion timer is expired, the server shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x24, indicating requestSequenceError. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0059 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0060 | If the server cannot determine if the client does have an existing authentication pending state, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable.StatementIf the server cannot determine if the client does have an existing authentication pending state, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS31-0060 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity; evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0061 | If the server is trying to delete the authentication pending state as consequence of the client proofOfOwnership signature verification failure, and the server determines that the authentication pending state was deleted, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x10, indicating generalReject.StatementIf the server is trying to delete the authentication pending state as consequence of the client proofOfOwnership signature verification failure, and the server determines that the authentication pending state was deleted, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x10, indicating generalReject. | SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS31-0061 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0062 | If the server is trying to delete the authentication pending state as consequence of the client proofOfOwnership signature verification failure, and the server cannot determine that the authentication pending state was deleted, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable.StatementIf the server is trying to delete the authentication pending state as consequence of the client proofOfOwnership signature verification failure, and the server cannot determine that the authentication pending state was deleted, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable. | SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity Verification | AD-002 | component | RFQX-CVS31-0062 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity; evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0063 | If the server is deleting the authentication pending state as consequence of failure to store the authentication state, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable.StatementIf the server is deleting the authentication pending state as consequence of failure to store the authentication state, it shall respond to the proofOfOwnership request with a Negative Response Code (NRC) 0x94, indicating ResourceTemporarilyNotAvailable. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0063 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity; evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0064 | This chapter specifies the behaviour of the deAuthenticate subfunction.StatementThis chapter specifies the behaviour of the deAuthenticate subfunction. | None | None | None | None | RFQX-CVS31-0064 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0065 | The request for deAuthenticate subfunction shall be formatted according to Table 9.StatementThe request for deAuthenticate subfunction shall be formatted according to Table 9. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0065 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0066 | Table 9 – deAuthenticate request message layout Field Description Type/Value Cvt Authentication Request SID Service ID for 0x29 M SubFunction = [AuthenticationTask = deAuthenticate] Subfunction for request to leave the authenticated state 0x00 M 3.3.2 Response The response for deAuthenticate subfunction shall be formatted according to Table 10.StatementTable 9 – deAuthenticate request message layout Field Description Type/Value Cvt Authentication Request SID Service ID for 0x29 M SubFunction = [AuthenticationTask = deAuthenticate] Subfunction for request to leave the authenticated state 0x00 M 3.3.2 Response The response for deAuthenticate subfunction shall be formatted according to Table 10. | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS31-0066 / 26h | Not imported | No linked clarification | No P1 link | diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0067 | The server shall delete/invalidate the client’s authentication prior to positively responding to the deAuthenticate request.StatementThe server shall delete/invalidate the client’s authentication prior to positively responding to the deAuthenticate request. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0067 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0068 | If the server determines that the client is not currently authenticated, it shall respond to the deAuthenticate request with a Negative Response Code (NRC) 0x24, indicating a requestSequenceError.StatementIf the server determines that the client is not currently authenticated, it shall respond to the deAuthenticate request with a Negative Response Code (NRC) 0x24, indicating a requestSequenceError. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0068 / 18h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0069 | The server only responds NRC 0x24 in the case that it can confirm that there is no authentication state connected to the client requesting to deAuthenticate.StatementThe server only responds NRC 0x24 in the case that it can confirm that there is no authentication state connected to the client requesting to deAuthenticate. | None | None | None | None | RFQX-CVS31-0069 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0070 | If the server cannot determine that the client is currently authenticated, it shall respond to the deAuthenticate request with a Negative Response Code (NRC) 0x94, indicating a ResourceTemporarilyNotAvailable.StatementIf the server cannot determine that the client is currently authenticated, it shall respond to the deAuthenticate request with a Negative Response Code (NRC) 0x94, indicating a ResourceTemporarilyNotAvailable. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS31-0070 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity; evidence completeness | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0071 | If the server is unable to delete the client's authentication state or cannot verify its presence, it shall respond to the deAuthenticate request with Negative Response Code (NRC) 0x94,StatementIf the server is unable to delete the client's authentication state or cannot verify its presence, it shall respond to the deAuthenticate request with Negative Response Code (NRC) 0x94, | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS31-0071 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0072 | If the server is unable to delete the client’s authentication state or cannot retrieve it due to internal errors, the server responds NRC 0x94.This informs the client that the authentication state may still exist on the server.StatementIf the server is unable to delete the client’s authentication state or cannot retrieve it due to internal errors, the server responds NRC 0x94.This informs the client that the authentication state may still exist on the server. | None | None | None | None | RFQX-CVS31-0072 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0073 | The signature algorithm used throughout the authentication process shall be ED25519.StatementThe signature algorithm used throughout the authentication process shall be ED25519. | SSR-DAI-001 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS31-0073 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0074 | The client shall use the private key corresponding to the client certificate to generate the signatures.StatementThe client shall use the private key corresponding to the client certificate to generate the signatures. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0074 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0075 | The server shall use the private key corresponding to the server certificate to generate the signatures.StatementThe server shall use the private key corresponding to the server certificate to generate the signatures. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0075 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0076 | The signature algorithm in the client, server and authentication CA certificates are ED25519 (1.3.101.112).StatementThe signature algorithm in the client, server and authentication CA certificates are ED25519 (1.3.101.112). | None | None | None | None | RFQX-CVS31-0076 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0077 | The format and the structure of the certificates shall be based on (CVS30).StatementThe format and the structure of the certificates shall be based on (CVS30). | SSR-KEY-002 | Key and Certificate Handling — Key and Certificate Handling | AD-008 | component | RFQX-CVS31-0077 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0078 | The server shall reject a received client’s certificate, sent using the verifyCertificateBidirectional subFunction, if it matches the server’s own certificate.StatementThe server shall reject a received client’s certificate, sent using the verifyCertificateBidirectional subFunction, if it matches the server’s own certificate. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0078 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0079 | It should not be possible to “unlock” the server using its own key/certificate.StatementIt should not be possible to “unlock” the server using its own key/certificate. | None | None | AD-007 | component | RFQX-CVS31-0079 / 56h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0080 | The server shall verify the client certificate, sent using the verifyCertificateBidirectional subFunction, according to Figure 3.StatementThe server shall verify the client certificate, sent using the verifyCertificateBidirectional subFunction, according to Figure 3. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0080 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0081 | The server shall verify the Signature of the Client certificate using the AUTH-CA EMP entity public key.StatementThe server shall verify the Signature of the Client certificate using the AUTH-CA EMP entity public key. | SSR-DAI-001 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS31-0081 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0082 | • Check if the NodeUID of the server is present in the NodeUIDs extension.Statement• Check if the NodeUID of the server is present in the NodeUIDs extension. | None | None | None | None | RFQX-CVS31-0082 / 19h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0083 | • If the server NodeUID is not found in the NodeUID extension, the server shall reject the certificate and generate NRC 0x10 (generalReject).Statement• If the server NodeUID is not found in the NodeUID extension, the server shall reject the certificate and generate NRC 0x10 (generalReject). | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0083 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0084 | If the NodeUID extension is not detected, the operation shall continue as inStatementIf the NodeUID extension is not detected, the operation shall continue as in | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0084 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0085 | A certificate without NodeUID extension implies that the certificate is applicable for any NodeUID.StatementA certificate without NodeUID extension implies that the certificate is applicable for any NodeUID. | None | None | None | None | RFQX-CVS31-0085 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0086 | The maximum number of elements in the list (number of ids) is limited by the maximum size of the certificate.StatementThe maximum number of elements in the list (number of ids) is limited by the maximum size of the certificate. | None | None | None | None | RFQX-CVS31-0086 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0087 | For the length of NodeUID see (CVS124).StatementFor the length of NodeUID see (CVS124). | None | None | None | None | RFQX-CVS31-0087 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0088 | The ECU-Diagnostic role extension shall be included in the client certificate.StatementThe ECU-Diagnostic role extension shall be included in the client certificate. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0088 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0089 | The roles shall correspond to a bit pattern-octet string.StatementThe roles shall correspond to a bit pattern-octet string. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0089 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0090 | The interpretation of the roles should follow as the example below: • Role 1 -> 0000 0000 0000 0000 0000 0000 0000 0001 – 00 00 00 01 • Role 32 -> 1000 0000 0000 0000 0000 0000 0000 0000 – 80 00 00 00 • Role 2 and 4 -> 0000 0000 0000 0000 0000 0000 0000 1010 – 00 00 00 0A.StatementThe interpretation of the roles should follow as the example below: • Role 1 -> 0000 0000 0000 0000 0000 0000 0000 0001 – 00 00 00 01 • Role 32 -> 1000 0000 0000 0000 0000 0000 0000 0000 – 80 00 00 00 • Role 2 and 4 -> 0000 0000 0000 0000 0000 0000 0000 1010 – 00 00 00 0A. | None | None | AD-008 | component | RFQX-CVS31-0090 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0091 | The D-RBACC extension defines client-specific rules that override the role-based access control configuration in the server.StatementThe D-RBACC extension defines client-specific rules that override the role-based access control configuration in the server. | None | None | None | None | RFQX-CVS31-0091 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0092 | While the ECU-Diagnostic Role extension specifies the roles assigned to a client, the D-RBACC extension may both grant additional permissions and restrict permissions beyond those derived from the client’s roles.StatementWhile the ECU-Diagnostic Role extension specifies the roles assigned to a client, the D-RBACC extension may both grant additional permissions and restrict permissions beyond those derived from the client’s roles. | None | None | None | None | RFQX-CVS31-0092 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0093 | If D-RBACC extension is detected, the server shall overrule the RBACC with the D-RBACC permissions.StatementIf D-RBACC extension is detected, the server shall overrule the RBACC with the D-RBACC permissions. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS31-0093 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0094 | This means that if D-RBACC logic denies/permits certain access, the server shall deny/permit the access regardless of what RBACC logic permits/denies.StatementThis means that if D-RBACC logic denies/permits certain access, the server shall deny/permit the access regardless of what RBACC logic permits/denies. | None | None | AD-001 | component | RFQX-CVS31-0094 / 56h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0095 | • The server shall validate the D-RBACC by parsing all its content.Statement• The server shall validate the D-RBACC by parsing all its content. If content is invalid, | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS31-0095 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0096 | If content is invalid, the certificate is invalid and the server shall return a Negative Response Code (NRC) 0x10, indicating generalReject.StatementIf content is invalid, the certificate is invalid and the server shall return a Negative Response Code (NRC) 0x10, indicating generalReject. | None | None | AD-007 | component | RFQX-CVS31-0096 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0097 | • Parsing means that the server tries to decode the DER encoded D-RBACC structure, which includes checking the decoded results against the server’s supported/known ASN.1 definition.Statement• Parsing means that the server tries to decode the DER encoded D-RBACC structure, which includes checking the decoded results against the server’s supported/known ASN.1 definition. | None | None | None | None | RFQX-CVS31-0097 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0098 | • The server shall verify that the D-RBACC version provided by the client is compatible with the server’s supported D-RBACC version.Statement• The server shall verify that the D-RBACC version provided by the client is compatible with the server’s supported D-RBACC version. | SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-002 | component | RFQX-CVS31-0098 / 16h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0099 | If non-compliant, the certificate is invalid and the server shall return a Negative Response Code (NRC) 0x10, indicating generalReject.StatementIf non-compliant, the certificate is invalid and the server shall return a Negative Response Code (NRC) 0x10, indicating generalReject. | None | None | AD-007 | component | RFQX-CVS31-0099 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS31-0100 | The basicConstraints extension CA field shall be False.StatementThe basicConstraints extension CA field shall be False. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0100 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0101 | The Key Usage extension (RFC 5280) shall be included in the client certificate.StatementThe Key Usage extension (RFC 5280) shall be included in the client certificate. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0101 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0102 | The Key Usage extension shall contain DigitalSignature.StatementThe Key Usage extension shall contain DigitalSignature. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0102 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0103 | The Extended Key Usage extension (RFC 5280) shall be included in the client certificate.StatementThe Extended Key Usage extension (RFC 5280) shall be included in the client certificate. | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0103 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0104 | The extension ExtendedKeyUsage shall contain clientAuth (1.3.6.1.5.5.7.3.2).StatementThe extension ExtendedKeyUsage shall contain clientAuth (1.3.6.1.5.5.7.3.2). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0104 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0105 | The extension SignatureAlgorithm shall contain ED25519 (1.3.101.112).StatementThe extension SignatureAlgorithm shall contain ED25519 (1.3.101.112). | SSR-DAI-008 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | AD-008 | component | RFQX-CVS31-0105 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0106 | The server shall validate the certificate so that: 𝑛𝑜𝑡𝐵𝑒𝑓𝑜𝑟𝑒 ≤ 𝐶𝑒𝑟𝑡𝑖𝑓𝑖𝑐𝑎𝑡𝑒-𝑡𝑖𝑚𝑒 ≤ 𝑛𝑜𝑡𝐴𝑓𝑡𝑒𝑟StatementThe server shall validate the certificate so that: 𝑛𝑜𝑡𝐵𝑒𝑓𝑜𝑟𝑒 ≤ 𝐶𝑒𝑟𝑡𝑖𝑓𝑖𝑐𝑎𝑡𝑒-𝑡𝑖𝑚𝑒 ≤ 𝑛𝑜𝑡𝐴𝑓𝑡𝑒𝑟 | SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | AD-007 | component | RFQX-CVS31-0106 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0107 | The notBefore and notAfter are received as fields in the certificate while Certificate-Time is the EMP entity defined in CVS34.StatementThe notBefore and notAfter are received as fields in the certificate while Certificate-Time is the EMP entity defined in CVS34. | None | None | None | None | RFQX-CVS31-0107 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0108 | • The server is reset (i.e server is power cycled).Statement• The server is reset (i.e server is power cycled). | None | None | None | None | RFQX-CVS31-0108 / 4h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0109 | State-keepingStatementState-keeping | None | None | None | None | RFQX-CVS31-0109 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0110 | • Power failure.Statement• Power failure. | None | None | None | None | RFQX-CVS31-0110 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0111 | If a server reset is triggered by a client request (e.g., UDS service 0x11), the server shall send the corresponding response before invalidating the authentication pending state.StatementIf a server reset is triggered by a client request (e.g., UDS service 0x11), the server shall send the corresponding response before invalidating the authentication pending state. | SSR-DIAG-006 | Diagnostic Services — Diagnostic Services | AD-001 | component | RFQX-CVS31-0111 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0112 | If a request to reset (e.g service 0x11) is received over the service 0x84 (securedDataTransmission) it permits the server to respond before the sessionKey is locked/invalidated.StatementIf a request to reset (e.g service 0x11) is received over the service 0x84 (securedDataTransmission) it permits the server to respond before the sessionKey is locked/invalidated. | None | None | None | None | RFQX-CVS31-0112 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0113 | If a client and server have successfully completed the authentication process, the server shall invalidate the authentication state in the event of: • The server is reset (i.e server is power cycled).StatementIf a client and server have successfully completed the authentication process, the server shall invalidate the authentication state in the event of: • The server is reset (i.e server is power cycled). | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0113 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0114 | • Power failure.Statement• Power failure. | None | None | None | None | RFQX-CVS31-0114 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0115 | • Successful deAuthenticate (see 3.3) subFunction (ISO 14229-1:2020).Statement• Successful deAuthenticate (see 3.3) subFunction (ISO 14229-1:2020). | None | None | None | None | RFQX-CVS31-0115 / 4h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0116 | • A new successful authentication is established.Statement• A new successful authentication is established. | None | None | None | None | RFQX-CVS31-0116 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0117 | • By passive de-authentication, see 4.7.Statement• By passive de-authentication, see 4.7. | None | None | None | None | RFQX-CVS31-0117 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0118 | Authentication state invalidated by the server implies that any unlocked services and sessionKey is locked/invalidated.StatementAuthentication state invalidated by the server implies that any unlocked services and sessionKey is locked/invalidated. | None | None | None | None | RFQX-CVS31-0118 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0119 | If a server reset is triggered by a client request (e.g., UDS service 0x11), the server shall send the corresponding response before invalidating the authentication state.StatementIf a server reset is triggered by a client request (e.g., UDS service 0x11), the server shall send the corresponding response before invalidating the authentication state. | SSR-DIAG-006 | Diagnostic Services — Diagnostic Services | AD-001 | component | RFQX-CVS31-0119 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0120 | The server’s authentication pending state shall contain the minimum of (non-exhaustive list): • Client address that issued the authentication request.StatementThe server’s authentication pending state shall contain the minimum of (non-exhaustive list): • Client address that issued the authentication request. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0120 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0121 | • Authentication completion timer.Statement• Authentication completion timer. | None | None | None | None | RFQX-CVS31-0121 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0122 | • Client’s certificate public keyStatement• Client’s certificate public key | None | None | None | None | RFQX-CVS31-0122 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | COMPLETE |
| RFQX-CVS31-0123 | • Client D-RBACC, if provided in the client’s certificateStatement• Client D-RBACC, if provided in the client’s certificate | None | None | None | None | RFQX-CVS31-0123 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0124 | • Server ephemeral private keyStatement• Server ephemeral private key | None | None | None | None | RFQX-CVS31-0124 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0125 | • H0 hash valueStatement• H0 hash value | None | None | None | None | RFQX-CVS31-0125 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0126 | The server ephemeral private key is the pair of the public key (ephemeralPublicKeyServer) sent as verifyCertificateBidirectional response.StatementThe server ephemeral private key is the pair of the public key (ephemeralPublicKeyServer) sent as verifyCertificateBidirectional response. | None | None | None | None | RFQX-CVS31-0126 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0127 | H0 hash value is calculated as part of proofOfOwnershipServer in verifyCertificateBidirectional response.StatementH0 hash value is calculated as part of proofOfOwnershipServer in verifyCertificateBidirectional response. | None | None | None | None | RFQX-CVS31-0127 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0128 | The server’s authentication state shall contain the minimum of (non-exhaustive list): • SessionKey.StatementThe server’s authentication state shall contain the minimum of (non-exhaustive list): • SessionKey. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0128 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0129 | • A3 Timer for passive de-authentication information.Statement• A3 Timer for passive de-authentication information. | None | None | None | None | RFQX-CVS31-0129 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0130 | • Client address that issued the authentication request.Statement• Client address that issued the authentication request. | None | None | None | None | RFQX-CVS31-0130 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0131 | • Client roles (ECU diagnostic Role extension in client’s certificate)Statement• Client roles (ECU diagnostic Role extension in client’s certificate) | None | None | None | None | RFQX-CVS31-0131 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0132 | • Client D-RBACC, if provided in the client’s certificateStatement• Client D-RBACC, if provided in the client’s certificate | None | None | None | None | RFQX-CVS31-0132 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0133 | The server shall support only one authentication state.StatementThe server shall support only one authentication state. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0133 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0134 | The server shall support only one authentication pending state.StatementThe server shall support only one authentication pending state. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0134 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0135 | The ephemeralPublicKeyClient in the proofOfOwnership-request (from the client) and the ephemeralPublicKeyClient in the verifyCertificate-response (from the server) consists of a Curve25519 [RFC 7748] public key.StatementThe ephemeralPublicKeyClient in the proofOfOwnership-request (from the client) and the ephemeralPublicKeyClient in the verifyCertificate-response (from the server) consists of a Curve25519 [RFC 7748] public key. | None | None | None | None | RFQX-CVS31-0135 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0136 | An overview of the key-exchange process is shown in Figure 4.StatementAn overview of the key-exchange process is shown in Figure 4. | None | None | None | None | RFQX-CVS31-0136 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0137 | The private keys shall be generated using a CRNG.StatementThe private keys shall be generated using a CRNG. | SSR-KEY-002 | Key and Certificate Handling — Key and Certificate Handling | AD-008 | component | RFQX-CVS31-0137 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0138 | The sessionKey shall be generated according to the pseudo code below.StatementThe sessionKey shall be generated according to the pseudo code below. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0138 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0139 | ephemeralPublicKeyServer) ephemeralPublicKeyServer, ephemeralPrivateKeyServer:= Curve25519() sessionKey := X25519(ephemeralPrivateKeyServer, ephemeralPublicKeyClient) sessionKey := X25519(ephemeralPrivateKeyClient , ephemeralPublicKeyServer) ephemeralPublicKeyClient, ephemeralPrivateKeyClient := Curve25519() ProofOfOwnership(...) VerifyCertificate(...) Figure 4 – Overview Ephemeral Diffie-Hellman key-exchange 4.4 External usage of the sessionKey The sessionKey is used outside the Authentication (ISO 14229-1:2020) service and is run through a key derivation function defined in (CVS32) to derive a key that can be used for securedDataTransmission communication.StatementephemeralPublicKeyServer) ephemeralPublicKeyServer, ephemeralPrivateKeyServer:= Curve25519() sessionKey := X25519(ephemeralPrivateKeyServer, ephemeralPublicKeyClient) sessionKey := X25519(ephemeralPrivateKeyClient , ephemeralPublicKeyServer) ephemeralPublicKeyClient, ephemeralPrivateKeyClient := Curve25519() ProofOfOwnership(...) VerifyCertificate(...) Figure 4 – Overview Ephemeral Diffie-Hellman key-exchange 4.4 External usage of the sessionKey The sessionKey is used outside the Authentication (ISO 14229-1:2020) service and is run through a key derivation function defined in (CVS32) to derive a key that can be used for securedDataTransmission communication. | None | None | None | None | RFQX-CVS31-0139 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0140 | The SessionKey is referred as SecuredDataTransmissionKey in (CVS32).StatementThe SessionKey is referred as SecuredDataTransmissionKey in (CVS32). | None | None | None | None | RFQX-CVS31-0140 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0141 | The server shall ensure that the sessionKey is exclusively used for the application responsible for communication over securedDataTransmission (CVS32).StatementThe server shall ensure that the sessionKey is exclusively used for the application responsible for communication over securedDataTransmission (CVS32). | SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS31-0141 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0142 | Solution for a CRNG shall be according to (CVS150).StatementSolution for a CRNG shall be according to (CVS150). | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0142 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0143 | The server shall always allow the Authentication 0x29 service (ISO 14229-1:2020) regardless ofStatementThe server shall always allow the Authentication 0x29 service (ISO 14229-1:2020) regardless of | SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS31-0143 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0144 | Example: If the server’s RBACC is for some reason corrupt or misconfigured this would lock out the client from doing diagnostics (the server will refuse all diagnostics).StatementExample: If the server’s RBACC is for some reason corrupt or misconfigured this would lock out the client from doing diagnostics (the server will refuse all diagnostics). | None | None | None | None | RFQX-CVS31-0144 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0145 | Two passive de-authentication mechanisms are described in (ISO 14229-1:2020).StatementTwo passive de-authentication mechanisms are described in (ISO 14229-1:2020). | None | None | None | None | RFQX-CVS31-0145 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0146 | Only Passive time-based de-authentication shall be supported.StatementOnly Passive time-based de-authentication shall be supported. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0146 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0147 | The server shall start the timer (A3) after a valid proofOfOwnership has been received.StatementThe server shall start the timer (A3) after a valid proofOfOwnership has been received. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0147 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0148 | The server shall restart the timer (A3) every time a request is received by the same client.StatementThe server shall restart the timer (A3) every time a request is received by the same client. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0148 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0149 | For this requirement, “same client” refers to a request that originates from the same tester address as the tester currently authenticated by the server.StatementFor this requirement, “same client” refers to a request that originates from the same tester address as the tester currently authenticated by the server. | None | None | None | None | RFQX-CVS31-0149 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0150 | When a request is received, authenticated or not, the server upon verifying it is from the same client will restart the timer (A3).StatementWhen a request is received, authenticated or not, the server upon verifying it is from the same client will restart the timer (A3). | None | None | None | None | RFQX-CVS31-0150 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0151 | If the A3 timer timeouts before a new request is received (from the same client), the server shall invalidate the authentication state.StatementIf the A3 timer timeouts before a new request is received (from the same client), the server shall invalidate the authentication state. | SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | AD-002 | component | RFQX-CVS31-0151 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0152 | The parameter for passive timeout based deAuthenticate shall be decided in the project.StatementThe parameter for passive timeout based deAuthenticate shall be decided in the project. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0152 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0153 | The A3 timer differs from S3 timer in terms of expected behavior during timeout and should not be implemented as a single timer.StatementThe A3 timer differs from S3 timer in terms of expected behavior during timeout and should not be implemented as a single timer. | None | None | AD-008 | component | RFQX-CVS31-0153 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0154 | The delay timer represents the required minimum time between verifyCertificateBidirectionalStatementThe delay timer represents the required minimum time between verifyCertificateBidirectional | None | None | AD-008 | component | RFQX-CVS31-0154 / 56h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | COMPLETE |
| RFQX-CVS31-0155 | The delay timer shall be set to 1 second.StatementThe delay timer shall be set to 1 second. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0155 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0156 | If the delay timer is not running, the server shall start it as part of verifyCertificateBidirectional request.StatementIf the delay timer is not running, the server shall start it as part of verifyCertificateBidirectional request. | SSR-KEY-003 | Key and Certificate Handling — Key and Certificate Handling | AD-002 | component | RFQX-CVS31-0156 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0157 | If the server can determine that a delay is not running after reset, it shall accept a subsequent authentication request without any delay.StatementIf the server can determine that a delay is not running after reset, it shall accept a subsequent authentication request without any delay. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS31-0157 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0158 | If the server cannot determine that a delay is not running after reset, it shall not accept a subsequent authentication request without any delay.StatementIf the server cannot determine that a delay is not running after reset, it shall not accept a subsequent authentication request without any delay. | SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS31-0158 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS31-0159 | The Authentication completion timer represents the timeframe that the client is allowed to perform proofOfOwnership request after a verifyCertificateBidirectional request.StatementThe Authentication completion timer represents the timeframe that the client is allowed to perform proofOfOwnership request after a verifyCertificateBidirectional request. | None | None | None | None | RFQX-CVS31-0159 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0160 | The Authentication completion timer shall be set to 1 minute.StatementThe Authentication completion timer shall be set to 1 minute. | SSR-SYS-001 | System Function — System Function | AD-008 | component | RFQX-CVS31-0160 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS31-0161 | The Authentication completion timer is started upon positive response for verifyCertificateBidirectional request.StatementThe Authentication completion timer is started upon positive response for verifyCertificateBidirectional request. | None | None | None | None | RFQX-CVS31-0161 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0162 | Migrated Req.StatementMigrated Req. into | None | None | None | None | RFQX-CVS31-0162 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0163 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0163 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0164 | Removed AUTH_REQ 137 since it is covered by AUTH_REQ 135 Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supportedStatementRemoved AUTH_REQ 137 since it is covered by AUTH_REQ 135 Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supported | None | None | None | None | RFQX-CVS31-0164 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0165 | Annex B (informative) Change history Release Date Changes The whole standard has been reworked and shall be read in its entirety.StatementAnnex B (informative) Change history Release Date Changes The whole standard has been reworked and shall be read in its entirety. | None | None | AD-008 | component | RFQX-CVS31-0165 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0166 | toStatementto | None | None | None | None | RFQX-CVS31-0166 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0167 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0167 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0168 | toStatementto | None | None | None | None | RFQX-CVS31-0168 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0169 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0169 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0170 | toStatementto | None | None | None | None | RFQX-CVS31-0170 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0171 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0171 / 21h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0172 | toStatementto | None | None | None | None | RFQX-CVS31-0172 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0173 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0173 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0174 | toStatementto | None | None | None | None | RFQX-CVS31-0174 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0175 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0175 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0176 | toStatementto | None | None | None | None | RFQX-CVS31-0176 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0177 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0177 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0178 | toStatementto | None | None | None | None | RFQX-CVS31-0178 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0179 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0179 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0180 | toStatementto | None | None | None | None | RFQX-CVS31-0180 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0181 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0181 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0182 | toStatementto | None | None | None | None | RFQX-CVS31-0182 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0183 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0183 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0184 | toStatementto | None | None | None | None | RFQX-CVS31-0184 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0185 | Duplicated AUTH_INFO due to typo.StatementDuplicated AUTH_INFO due to typo. | None | None | None | None | RFQX-CVS31-0185 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0186 | toStatementto | None | None | None | None | RFQX-CVS31-0186 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0187 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0187 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0188 | toStatementto | None | None | None | None | RFQX-CVS31-0188 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0189 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0189 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0190 | toStatementto | None | None | None | None | RFQX-CVS31-0190 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0191 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0191 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0192 | toStatementto | None | None | None | None | RFQX-CVS31-0192 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0193 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0193 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0194 | toStatementto | None | None | None | None | RFQX-CVS31-0194 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0195 | Changed tagStatementChanged tag | None | None | None | None | RFQX-CVS31-0195 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0196 | toStatementto | None | None | None | None | RFQX-CVS31-0196 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0197 | Removed Unused reference Fixed wrong cross reference Migrated Annex A “ephemeralPublicKey” into new chapter 3.3 “SessionKey” and added pseudo code for sessionKey Migrated Info intoStatementRemoved Unused reference Fixed wrong cross reference Migrated Annex A “ephemeralPublicKey” into new chapter 3.3 “SessionKey” and added pseudo code for sessionKey Migrated Info into | None | None | None | None | RFQX-CVS31-0197 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0198 | Migrated Info intoStatementMigrated Info into | None | None | None | None | RFQX-CVS31-0198 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0199 | Migrated Req.StatementMigrated Req. | None | None | None | None | RFQX-CVS31-0199 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0200 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0200 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0201 | Added chapter for Certificate validity AddedStatementAdded chapter for Certificate validity Added | None | None | None | None | RFQX-CVS31-0201 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | COMPLETE |
| RFQX-CVS31-0202 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0202 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0203 | Added OID for client authentication ChangedStatementAdded OID for client authentication Changed | None | None | None | None | RFQX-CVS31-0203 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0204 | Fixed typo ChangedStatementFixed typo Changed | None | None | None | None | RFQX-CVS31-0204 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0205 | (Removed “shown in only”) ChangedStatement(Removed “shown in only”) Changed | None | None | None | None | RFQX-CVS31-0205 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0206 | (VerifyCertificateres -> VerifyCertificates) Changed Table 5 (lengthofCertificateClient -> lengthOfCertificateClient) Changed Table 6 (lengthOfCertitifacteServer -> lengthOfCertificateServer) ChangedStatement(VerifyCertificateres -> VerifyCertificates) Changed Table 5 (lengthofCertificateClient -> lengthOfCertificateClient) Changed Table 6 (lengthOfCertitifacteServer -> lengthOfCertificateServer) Changed | None | None | None | None | RFQX-CVS31-0206 / 56h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0207 | (fails -> failure) ChangedStatement(fails -> failure) Changed | None | None | None | None | RFQX-CVS31-0207 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0208 | (fails -> failure) Changed Table 7 (EphemeralPublicKeyClient -> ephemeralPublicKeyClient) Removed ambiguity ChangedStatement(fails -> failure) Changed Table 7 (EphemeralPublicKeyClient -> ephemeralPublicKeyClient) Removed ambiguity Changed | None | None | None | None | RFQX-CVS31-0208 / 24h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | COMPLETE |
| RFQX-CVS31-0209 | RemovedStatementRemoved | None | None | None | None | RFQX-CVS31-0209 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0210 | since it is covered byStatementsince it is covered by | None | None | None | None | RFQX-CVS31-0210 / 4h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0211 | Removed in Annex A the reference to verifyCertificatesUniDirectional since it is not supportedStatementRemoved in Annex A the reference to verifyCertificatesUniDirectional since it is not supported | None | None | None | None | RFQX-CVS31-0211 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0212 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0212 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0213 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0213 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0214 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0214 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0215 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0215 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0216 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0216 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0217 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0217 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0218 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0218 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0219 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0219 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0220 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0220 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0221 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0221 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0222 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0222 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0223 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0223 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0224 | RemovedStatementRemoved | None | None | None | None | RFQX-CVS31-0224 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0225 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0225 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0226 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0226 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0227 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0227 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0228 | andStatementand | None | None | None | None | RFQX-CVS31-0228 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0229 | Updated document quirks chapter Removed the information that italic terms are often clickable.StatementUpdated document quirks chapter Removed the information that italic terms are often clickable. | None | None | None | None | RFQX-CVS31-0229 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0230 | Reformulation for clarity improvement ChangedStatementReformulation for clarity improvement Changed | None | None | None | None | RFQX-CVS31-0230 / 21h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0231 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0231 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0232 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0232 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0233 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0233 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0234 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0234 / 5h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0235 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0235 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0236 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0236 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0237 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0237 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0238 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0238 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0239 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0239 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0240 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0240 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0241 | ChangedStatementChanged | None | None | None | None | RFQX-CVS31-0241 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0242 | Changed Table 3 (Authentication pending state and authentication state) Changed Table 5 (Changed column name POO -> proofOfOwnershipServer) Changed Table 6 (Changed column name POO -> proofOfOwnershipServer) ChangedStatementChanged Table 3 (Authentication pending state and authentication state) Changed Table 5 (Changed column name POO -> proofOfOwnershipServer) Changed Table 6 (Changed column name POO -> proofOfOwnershipServer) Changed | None | None | None | None | RFQX-CVS31-0242 / 24h | Not imported | No linked clarification | No P1 link | boundary ownership; backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS31-0243 | (Changed POO -> proofOfOwnershipServer) RemovedStatement(Changed POO -> proofOfOwnershipServer) Removed | None | None | None | None | RFQX-CVS31-0243 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0244 | (Maximum size of elements is to be defined by max size of certificate) AddedStatement(Maximum size of elements is to be defined by max size of certificate) Added | None | None | None | None | RFQX-CVS31-0244 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0245 | (Maximum size of elements is to be defined by max size of certificate) Updated Figure 3 Reformulation requirements over the length of client certificate RemovedStatement(Maximum size of elements is to be defined by max size of certificate) Updated Figure 3 Reformulation requirements over the length of client certificate Removed | None | None | None | None | RFQX-CVS31-0245 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0246 | Added Chapter 2.1.1.2 lengthOfCertificateClient AddedStatementAdded Chapter 2.1.1.2 lengthOfCertificateClient Added | None | None | None | None | RFQX-CVS31-0246 / 24h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0247 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0247 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0248 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0248 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0249 | Clarified the signature algorithm to be used over the authentication process RemovedStatementClarified the signature algorithm to be used over the authentication process Removed | None | None | None | None | RFQX-CVS31-0249 / 26h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS31-0250 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0250 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0251 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0251 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0252 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0252 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0253 | AddedStatementAdded | None | None | None | None | RFQX-CVS31-0253 / 4h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS31-0254 | 2025-08 CVS31 First edition 2025-05-30 RFQ 2517 Delivery Added authentication delay timer Added Authentication Completion timer Clarified negative responses cases for each subfunctionStatement2025-08 CVS31 First edition 2025-05-30 RFQ 2517 Delivery Added authentication delay timer Added Authentication Completion timer Clarified negative responses cases for each subfunction | None | None | None | None | RFQX-CVS31-0254 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0001 | The User shall apply the latest version of this CVS32.StatementThe User shall apply the latest version of this CVS32. | None | None | AD-008 | component | RFQX-CVS32-0001 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS32-0002 | Foreword This CVS32 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.StatementForeword This CVS32 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable. | None | None | None | None | RFQX-CVS32-0002 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0003 | Any review of CVS32 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”.StatementAny review of CVS32 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”. | None | None | AD-003 | component | RFQX-CVS32-0003 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS32-0004 | • Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch.Statement• Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch. | None | None | AD-002 | component | RFQX-CVS32-0004 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS32-0005 | SummaryStatementThe purpose of this document is to clarify vehicle manufacturer specific extensions and exceptions to the SecuredDataTransmission 0x84 service specified in ISO14229-1:2020 [1]. This specification does not include any redundant requirements of the normative and indispensable documents referenced below. It contains only clarifications of the requirements and recommendations in these documents together with exceptions and additional requirements that apply to this standard in relation to these documents. The following documents are normative and indispensable for the application of this document: • TRATON Specification on Unified diagnostic Services (UDS) requirements [8] • ISO 14229-1:2020, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements [1] | None | None | None | None | RFQX-CVS32-0005 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0006 | Target ReaderStatementThe target readers for this specification are ECU-suppliers and ECU-developers in reference to the server-side requirements, and diagnostic tool developers and back-end service providers regarding the client-side requirements. These “target readers” can be either internal or external in relation to the vehicle manufacturer. | None | None | None | None | RFQX-CVS32-0006 / 56h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0007 | Document QuirksStatementThe mnemonics defined in the ISO14229-1:2020 [1] standard are reused throughout this document. Some paragraphs in this document includes pseudo code. The pseudo code make use of the following notation: 𝑋 || 𝑌 The concatenation of the octet strings 𝑋 and 𝑌 𝑋𝑠𝑒𝑟𝑣𝑒𝑟 𝑋 is owned by the Server 𝑋𝑐𝑙𝑖𝑒𝑛𝑡 𝑋 is owned by the Client The first occurrence of an abbreviation or term in this document will appear italicized to indicate that it is explained in section 1.4 Abbreviations or section 1.5 Terminology. All paragraphs from here on in this document are assigned unique tags, composed of a prefix and an identification number for non-ambiguous identification. SDT_REQ X identifies a requirement, and tag SDT_INFO X is used to denote informational text. Whether a requirement refers to client-side or server-side behavior is clear from the context and the requirement text itself. The keywords “shall”, “should”, “must” and so forth are used in this document and are to be interpreted in accordance with “Key words for use in RFCs to Indicate Requirement Levels” [10]. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0007 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0008 | The keywords “shall”, “should”, “must” and so forth are used in this document and are to be interpreted in accordance with “Key words for use in RFCs to Indicate Requirement Levels” [10].StatementThe keywords “shall”, “should”, “must” and so forth are used in this document and are to be interpreted in accordance with “Key words for use in RFCs to Indicate Requirement Levels” [10]. | None | None | AD-007 | component | RFQX-CVS32-0008 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS32-0009 | The implementation of SDT (SecuredDataTransmission) shall follow the information provided inStatementThe implementation of SDT (SecuredDataTransmission) shall follow the information provided in | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0009 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0010 | Although SDT (service 0x84) is of course part of UDS, in this document, SDT is treated much like a transport layer for other UDS services.StatementAlthough SDT (service 0x84) is of course part of UDS, in this document, SDT is treated much like a transport layer for other UDS services. | None | None | None | None | RFQX-CVS32-0010 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0011 | Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to ISO 14229-1:2020 [1]).StatementFigure 1 shows the layout of an SDT message with its protocol elements (for details refer to ISO 14229-1:2020 [1]). | None | None | None | None | RFQX-CVS32-0011 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0012 | Whenever a requirement in this document deviates from requirements in ISO14229-1 [1] the requirements of this document shall take precedence.StatementWhenever a requirement in this document deviates from requirements in ISO14229-1 [1] the requirements of this document shall take precedence. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0012 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0013 | ECUs with diagnostic servers in multiple execution states, e.g.StatementECUs with diagnostic servers in multiple execution states, e.g. | None | None | None | None | RFQX-CVS32-0013 / 29h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0014 | one diagnostic server in the boot-loader and one in the application, shall support SDT in all execution states.Statementone diagnostic server in the boot-loader and one in the application, shall support SDT in all execution states. | None | None | AD-007 | component | RFQX-CVS32-0014 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS32-0015 | A prerequisite for the SDT service is that a SecuredDataTransmissionKey has been established between client and server using the 0x29 service [6].StatementA prerequisite for the SDT service is that a SecuredDataTransmissionKey has been established between client and server using the 0x29 service [6]. | None | None | None | None | RFQX-CVS32-0015 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0016 | The SDT server shall use the diagnostic tester address of the SDT client to identify the authentication state and hence the SecuredDataTransmissionKey.StatementThe SDT server shall use the diagnostic tester address of the SDT client to identify the authentication state and hence the SecuredDataTransmissionKey. | SSR-RBAC-007 | Secure communication and freshness protection — Secure Diagnostics / RBAC | AD-007 | component | RFQX-CVS32-0016 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0017 | (There may be more than one authentication state).Statement(There may be more than one authentication state). | None | None | None | None | RFQX-CVS32-0017 / 56h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0018 | The number of concurrently active SDT sequences is limited by the number of authentication states that a server is allowed to maintain, refer to [6].StatementThe number of concurrently active SDT sequences is limited by the number of authentication states that a server is allowed to maintain, refer to [6]. | None | None | None | None | RFQX-CVS32-0018 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0019 | The server shall not allow an SDT message with service 0x84 as the application layer service (service 0x84 encapsulated inside another service 0x84).StatementThe server shall not allow an SDT message with service 0x84 as the application layer service (service 0x84 encapsulated inside another service 0x84). | SSR-COM-011 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS32-0019 / 24h | Not imported | No linked clarification | No P1 link | diagnostics exposure; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0020 | The server shall respond with application layer NRC 0x39, i.e.StatementThe server shall respond with application layer NRC 0x39, i.e. | None | None | AD-001 | component | RFQX-CVS32-0020 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | BLOCKED BY CUSTOMER DECISION |
| RFQX-CVS32-0021 | the response shall be a properly formatted SDT positive 3 ISO 14299-1:2020 Clarifications and Deviations 3.1 Anti-replay Protection and Transaction Coherency Anti-replay protection for SDT messages is provided by the ANTIREPLAYCNT protocol element.Statementthe response shall be a properly formatted SDT positive 3 ISO 14299-1:2020 Clarifications and Deviations 3.1 Anti-replay Protection and Transaction Coherency Anti-replay protection for SDT messages is provided by the ANTIREPLAYCNT protocol element. | None | None | AD-005 | interface | RFQX-CVS32-0021 / 24h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0022 | This specification defines two counters, one for the request messages and one for responses.StatementThis specification defines two counters, one for the request messages and one for responses. | None | None | None | None | RFQX-CVS32-0022 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0023 | The reason for the two separate counters is that the UDS standard allows for a request to result in multiple responses, e.g.StatementThe reason for the two separate counters is that the UDS standard allows for a request to result in multiple responses, e.g. | None | None | None | None | RFQX-CVS32-0023 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0024 | The state variables needed to keep track of these counters are called PREQARC (Previous REQuest Anti-Replay Counter) and PRESARC (Previous RESponse Anti-Replay Counter).StatementThe state variables needed to keep track of these counters are called PREQARC (Previous REQuest Anti-Replay Counter) and PRESARC (Previous RESponse Anti-Replay Counter). | None | None | None | None | RFQX-CVS32-0024 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0025 | Both client and server shall maintain instances of the state variables PREQARC and PRESARC.StatementBoth client and server shall maintain instances of the state variables PREQARC and PRESARC. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0025 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0026 | At construction of an SDT request, the client shall increment PREQARC by one (1) and populate the ANTIREPLAYCNT protocol element with the resulting value.StatementAt construction of an SDT request, the client shall increment PREQARC by one (1) and populate the ANTIREPLAYCNT protocol element with the resulting value. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0026 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0027 | At reception of an SDT request, the server shall verify that the value of the ANTIREPLAYCNT protocol element is greater than PREQARC, and if the message can be otherwise verified, update PREQARC to reflect the new value, i.e.StatementAt reception of an SDT request, the server shall verify that the value of the ANTIREPLAYCNT protocol element is greater than PREQARC, and if the message can be otherwise verified, update PREQARC to reflect the new value, i.e. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0027 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0028 | At construction of an SDT response, the server shall increment PRESARC by one (1) and populate the ANTIREPLAYCNT protocol element with the resulting value.StatementAt construction of an SDT response, the server shall increment PRESARC by one (1) and populate the ANTIREPLAYCNT protocol element with the resulting value. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0028 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0029 | At reception of an SDT response, the client shall verify that the value of the ANTIREPLAYCNT protocol element is greater than PRESARC, and if the message can be otherwise verified, update PRESARC to reflect the new value, i.e.StatementAt reception of an SDT response, the client shall verify that the value of the ANTIREPLAYCNT protocol element is greater than PRESARC, and if the message can be otherwise verified, update PRESARC to reflect the new value, i.e. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0029 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0030 | The client should populate the ANTIREPLAYCNT protocol element of the first request of anStatementThe client should populate the ANTIREPLAYCNT protocol element of the first request of an | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0030 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0031 | The server should populate the ANTIREPLAYCNT protocol element of the first response of an SDT sequence with the value zero (0), and set PRESARC accordingly.StatementThe server should populate the ANTIREPLAYCNT protocol element of the first response of an SDT sequence with the value zero (0), and set PRESARC accordingly. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0031 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0032 | It is good practise to start a sequence with ANTIREPLAYCNT set to zero (0), but this is not something that is enforced by the recipient of the message, be it the first request or response.StatementIt is good practise to start a sequence with ANTIREPLAYCNT set to zero (0), but this is not something that is enforced by the recipient of the message, be it the first request or response. | None | None | None | None | RFQX-CVS32-0032 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0033 | If either PREQARC or PRESARC reaches the maximum value 65535 (0xFFFF), the client shall re-authenticate if it wishes to send more messages.StatementIf either PREQARC or PRESARC reaches the maximum value 65535 (0xFFFF), the client shall re-authenticate if it wishes to send more messages. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0033 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0034 | The server handles the exhaustion of PREQARC and PRESARC with its “normal behavior”.StatementThe server handles the exhaustion of PREQARC and PRESARC with its “normal behavior”. | None | None | None | None | RFQX-CVS32-0034 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0035 | ).Statement). | None | None | None | None | RFQX-CVS32-0035 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0036 | ).Statement). | None | None | None | None | RFQX-CVS32-0036 / 19h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | COMPLETE |
| RFQX-CVS32-0037 | The requirements above are illustrated in Figure 2.StatementThe requirements above are illustrated in Figure 2. | None | None | None | None | RFQX-CVS32-0037 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0038 | Apart from ensuring that old messages are not replayed, it is also necessary for the client to be able to determine that an incoming response is actually a response to the request that is currently outstanding.StatementApart from ensuring that old messages are not replayed, it is also necessary for the client to be able to determine that an incoming response is actually a response to the request that is currently outstanding. | None | None | None | None | RFQX-CVS32-0038 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0039 | Since any CipherScheme supported by this specification will at least authenticate messages, there will always be a TAG (MAC or similar) populated in the SIGMACBYTE protocol element of all SDT messages.StatementSince any CipherScheme supported by this specification will at least authenticate messages, there will always be a TAG (MAC or similar) populated in the SIGMACBYTE protocol element of all SDT messages. This TAG is used to guarantee request/response coherency and the corresponding state variable is called PREQTAG (Previous REQuest TAG). | None | None | None | None | RFQX-CVS32-0039 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0040 | The client shall maintain the state variable PREQTAG.StatementThe client shall maintain the state variable PREQTAG. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0040 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0041 | The requirements regarding PREQTAG are detailed in sections 3.2.2 and 3.2.3 since they differ slightly between CipherSchemes.StatementThe requirements regarding PREQTAG are detailed in sections 3.2.2 and 3.2.3 since they differ slightly between CipherSchemes. | None | None | None | None | RFQX-CVS32-0041 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0042 | Figure 3 illustrates transaction coherency and the use of PREQTAG.StatementFigure 3 illustrates transaction coherency and the use of PREQTAG. | None | None | None | None | RFQX-CVS32-0042 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0043 | The authenticity, and optionally confidentiality, of an SDT message is provided by the CipherScheme with which the SDT message is authenticated/encrypted.StatementThe authenticity, and optionally confidentiality, of an SDT message is provided by the CipherScheme with which the SDT message is authenticated/encrypted. | None | None | None | None | RFQX-CVS32-0043 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0044 | The CipherScheme used when constructing an SDT message shall be indicated by the SIGENCRYPT protocol element according to Table 2.StatementThe CipherScheme used when constructing an SDT message shall be indicated by the SIGENCRYPT protocol element according to Table 2. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0044 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0045 | The supported CipherSchemes SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305 [9] are described in sections 3.2.2 and 3.2.3 respectively.StatementThe supported CipherSchemes SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305 [9] are described in sections 3.2.2 and 3.2.3 respectively. The two CipherSchemes require different key material. The Key Derivation Function (KDF) is described in section 3.2.1. | None | None | None | None | RFQX-CVS32-0045 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0046 | The CipherSchemes SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305 shall be supported.StatementThe CipherSchemes SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305 shall be supported. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0046 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0047 | At SDT message reception, the recipient shall verify/decrypt the message using the CipherScheme indicated by the SIGENCRYPT protocol element.StatementAt SDT message reception, the recipient shall verify/decrypt the message using the CipherScheme indicated by the SIGENCRYPT protocol element. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0047 / 18h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0048 | In case of a positive SDT response, the server shall respond to a client request with the same CipherScheme used in the request.StatementIn case of a positive SDT response, the server shall respond to a client request with the same CipherScheme used in the request. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0048 / 26h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0049 | The client may alter the CipherScheme between SDT requests within the same SDT sequence.StatementThe client may alter the CipherScheme between SDT requests within the same SDT sequence. | None | None | None | None | RFQX-CVS32-0049 / 18h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0050 | Since the two CipherSchemes require different key material, the KDF has to be re-run if the CipherScheme changes.StatementSince the two CipherSchemes require different key material, the KDF has to be re-run if the CipherScheme changes. | None | None | None | None | RFQX-CVS32-0050 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0051 | Client and server should keep state variables that indicate which CipherScheme, and resulting key, was used in the previous SDT transaction.StatementClient and server should keep state variables that indicate which CipherScheme, and resulting key, was used in the previous SDT transaction. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0051 / 26h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0052 | In the following, these state variables are called PSIGENCRYPT (Previous SIGENCRYPT) and PKEY (Previous KEY).StatementIn the following, these state variables are called PSIGENCRYPT (Previous SIGENCRYPT) and PKEY (Previous KEY). | None | None | None | None | RFQX-CVS32-0052 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0053 | At construction of an SDT request, if SIGENCRYPT is different from PSIGENCRYPT, the client should re-run the KDF, and if and only if the authentication/encryption succeeds, update the state variables PSIGENCRYPT and PKEY with the new values.StatementAt construction of an SDT request, if SIGENCRYPT is different from PSIGENCRYPT, the client should re-run the KDF, and if and only if the authentication/encryption succeeds, update the state variables PSIGENCRYPT and PKEY with the new values. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0053 / 32h | Not imported | No linked clarification | No P1 link | boot/update trust; certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0054 | At reception of an SDT request, if SIGENCRYPT is different from PSIGENCRYPT, the server should re-run the KDF, and if and only if the verification/decryption succeeds, update the state variables PSIGENCRYPT and PKEY with the new values.StatementAt reception of an SDT request, if SIGENCRYPT is different from PSIGENCRYPT, the server should re-run the KDF, and if and only if the verification/decryption succeeds, update the state variables PSIGENCRYPT and PKEY with the new values. | SSR-VV-004 | Secure communication and freshness protection — Verification and Validation | AD-002 | component | RFQX-CVS32-0054 / 32h | Not imported | No linked clarification | No P1 link | boot/update trust; certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0055 | Figure 4 illustrates the switching of CipherSchemes within an SDT sequence.StatementFigure 4 illustrates the switching of CipherSchemes within an SDT sequence. The client has previously used CipherScheme 3, and for request X+1, switches to 2. The server reacts on the different SIGENCRYPT and updates its state accordingly. Client Server PREQARC = X | None | None | None | None | RFQX-CVS32-0055 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0056 | Client Server PREQARC = X PREQTAG=TAG_X PSIGENCRYPT=3 PKEY=p..p Check: ANTIREPLAYCNT > PREQARC SIGENCRYPT != PSIGENCRYPT: KDF(..) -> r..r decrypt(data, TAG_X+1)->ok Check: ANTIREPLAYCNT > PRESARC decrypt(data||PREQTAG, TAG_Y+1)->ok PRESARC = Y+1 PRESARC = Y+1 PREQARC = X PSIGENCRYPT=3 PKEY=p..p encrypt(data)->TAG_X+1 encrypt(data||TAG_X+1)->TAG_Y+1 S1 S2 S3 C1 C2 C3 SIGENCRYPT != PSIGENCRYPT: KDF(..) -> r..r Figure 4 – Change of CipherScheme mid sequence 3.2.1 HKDF Key Derivation Client and server shall support the HKDF [2] key derivation function using HMAC-SHA512 [3].StatementClient Server PREQARC = X PREQTAG=TAG_X PSIGENCRYPT=3 PKEY=p..p Check: ANTIREPLAYCNT > PREQARC SIGENCRYPT != PSIGENCRYPT: KDF(..) -> r..r decrypt(data, TAG_X+1)->ok Check: ANTIREPLAYCNT > PRESARC decrypt(data||PREQTAG, TAG_Y+1)->ok PRESARC = Y+1 PRESARC = Y+1 PREQARC = X PSIGENCRYPT=3 PKEY=p..p encrypt(data)->TAG_X+1 encrypt(data||TAG_X+1)->TAG_Y+1 S1 S2 S3 C1 C2 C3 SIGENCRYPT != PSIGENCRYPT: KDF(..) -> r..r Figure 4 – Change of CipherScheme mid sequence 3.2.1 HKDF Key Derivation Client and server shall support the HKDF [2] key derivation function using HMAC-SHA512 [3]. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0056 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0057 | ikm : The ikm argument to the HKDF function shall be the octet string containing the SecuredDataTransmissionKey from the service 0x29 authentication state.Statementikm : The ikm argument to the HKDF function shall be the octet string containing the SecuredDataTransmissionKey from the service 0x29 authentication state. | SSR-RBAC-006 | Secure communication and freshness protection — Secure Diagnostics / RBAC | AD-001 | component | RFQX-CVS32-0057 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0058 | salt: The salt argument to the HKDF function shall be set as the zero length octet string (null).Statementsalt: The salt argument to the HKDF function shall be set as the zero length octet string (null). | SSR-COM-011 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS32-0058 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0059 | info: The info argument to the HKDF function shall be set as the concatenation of the “SDT_0x84_KEY” octet string and the CipherScheme identifier.Statementinfo: The info argument to the HKDF function shall be set as the concatenation of the “SDT_0x84_KEY” octet string and the CipherScheme identifier. | SSR-COM-011 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS32-0059 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; diagnostics exposure | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0060 | Example: “SDT_0x84_KEY” = 5344545F307838345F4B4559 (UTF-8 encoded hex) CipherScheme = 02 (SDT_AEAD_CHACHA20_POLY1305) ➔ info := 5344545F307838345F4B455902StatementExample: “SDT_0x84_KEY” = 5344545F307838345F4B4559 (UTF-8 encoded hex) CipherScheme = 02 (SDT_AEAD_CHACHA20_POLY1305) ➔ info := 5344545F307838345F4B455902 | None | None | None | None | RFQX-CVS32-0060 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0061 | L: The L argument determines the length of okm and is determined by whichever CipherScheme to be used, see sections 3.2.2 and 3.2.3.StatementL: The L argument determines the length of okm and is determined by whichever CipherScheme to be used, see sections 3.2.2 and 3.2.3. | None | None | None | None | RFQX-CVS32-0061 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0062 | okm is the output key material octet string of length L.Statementokm is the output key material octet string of length L. | None | None | None | None | RFQX-CVS32-0062 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0063 | This section describes a CipherScheme based on AEAD_CHACHA20_POLY1305 [9].StatementThis section describes a CipherScheme based on AEAD_CHACHA20_POLY1305 [9]. | None | None | None | None | RFQX-CVS32-0063 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0064 | The L argument to the HKDF function shall be set to 64.StatementThe L argument to the HKDF function shall be set to 64. | SSR-COM-011 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS32-0064 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0065 | Octets 0-31 of the okm shall be used as key by the client to encrypt, and the server to decrypt, the request.StatementOctets 0-31 of the okm shall be used as key by the client to encrypt, and the server to decrypt, the request. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0065 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0066 | Octets 32-63 of the okm shall be used as key by the server to encrypt, and the client to decrypt, the response.StatementOctets 32-63 of the okm shall be used as key by the server to encrypt, and the client to decrypt, the response. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0066 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0067 | The above requirements are visualized in Figure 5.StatementThe above requirements are visualized in Figure 5. | None | None | None | None | RFQX-CVS32-0067 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0068 | Figure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305 In subsequent sections (3.2.2.1 and 3.2.2.2) the following requirements shall be met: 𝐾: The 𝐾 argument shall be the key octet string of 32 octets.StatementFigure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305 In subsequent sections (3.2.2.1 and 3.2.2.2) the following requirements shall be met: 𝐾: The 𝐾 argument shall be the key octet string of 32 octets. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0068 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0069 | 𝑁: The 𝑁 shall be an octet string of length 12, constructed as follows: - the first 10 octets shall be set to 6E6F6E73656E73652121, and - the remaining 2 octets shall be ANTIREPLAYCNT.Statement𝑁: The 𝑁 shall be an octet string of length 12, constructed as follows: - the first 10 octets shall be set to 6E6F6E73656E73652121, and - the remaining 2 octets shall be ANTIREPLAYCNT. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0069 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0070 | 𝑃: The 𝑃 (Plaintext) argument shall be the octet string that is the concatenation of the INTMSGREQID and SRVSPECPARAM.Statement𝑃: The 𝑃 (Plaintext) argument shall be the octet string that is the concatenation of the INTMSGREQID and SRVSPECPARAM. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0070 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0071 | 𝐶: When injected into, or extracted from an SDT message, the first octet of 𝐶 shall correspond to INTMSGREQID, and the remaining octets to SRVSPECPARAM.Statement𝐶: When injected into, or extracted from an SDT message, the first octet of 𝐶 shall correspond to INTMSGREQID, and the remaining octets to SRVSPECPARAM. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0071 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0072 | The plaintext (𝑃) and ciphertext (𝐶) octet strings are of the same length and a concatenation of the INTMSGREQID and SRVSPECPARAM protocol elements.StatementThe plaintext (𝑃) and ciphertext (𝐶) octet strings are of the same length and a concatenation of the INTMSGREQID and SRVSPECPARAM protocol elements. | None | None | None | None | RFQX-CVS32-0072 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0073 | The client shall encrypt and authenticate the SDT request with the 𝐴 argument set to theStatementThe client shall encrypt and authenticate the SDT request with the 𝐴 argument set to the | SSR-DAI-009 | Secure communication and freshness protection — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS32-0073 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0074 | The client shall populate the APAR protocol element in the request so that bits 0, 4, 5 and 6 are set to true.StatementThe client shall populate the APAR protocol element in the request so that bits 0, 4, 5 and 6 are set to true. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0074 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0075 | The client shall populate the SIGLEN protocol element in the request with 16 (0x0010).StatementThe client shall populate the SIGLEN protocol element in the request with 16 (0x0010). | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0075 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0076 | The client shall populate the SIGMACBYTE protocol element in the request with 𝑇𝐴𝐺.StatementThe client shall populate the SIGMACBYTE protocol element in the request with 𝑇𝐴𝐺. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0076 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0077 | The client shall store 𝑇𝐴𝐺 in its state variable PREQTAG.StatementThe client shall store 𝑇𝐴𝐺 in its state variable PREQTAG. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0077 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0078 | 𝐶𝐻𝐴𝐶𝐻𝐴20-POLY1305𝑑𝑒𝑐𝑟𝑦𝑝𝑡(𝐾, 𝑁, 𝐴, 𝐶, 𝑇𝐴𝐺) → 𝑜𝑘/𝑛𝑜𝑘, 𝑃 The client shall decrypt and verify the SDT response with: the 𝐴 argument set to the concatenated octet string comprised of the SDTPR, APAR, SIGENCRYPT, SIGLEN, ANTIREPLAYCNT protocol elements of the response and the value stored in the state variable PREQTAG.Statement𝐶𝐻𝐴𝐶𝐻𝐴20-POLY1305𝑑𝑒𝑐𝑟𝑦𝑝𝑡(𝐾, 𝑁, 𝐴, 𝐶, 𝑇𝐴𝐺) → 𝑜𝑘/𝑛𝑜𝑘, 𝑃 The client shall decrypt and verify the SDT response with: the 𝐴 argument set to the concatenated octet string comprised of the SDTPR, APAR, SIGENCRYPT, SIGLEN, ANTIREPLAYCNT protocol elements of the response and the value stored in the state variable PREQTAG. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0078 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0079 | element of the response.Statementelement of the response. | None | None | None | None | RFQX-CVS32-0079 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0080 | The server shall decrypt and verify the SDT request with the 𝐴 argument set to the concatenated octet string comprised of the SDT, APAR, SIGENCRYPT, SIGLEN and ANTIREPLAYCNT protocol elements.StatementThe server shall decrypt and verify the SDT request with the 𝐴 argument set to the concatenated octet string comprised of the SDT, APAR, SIGENCRYPT, SIGLEN and ANTIREPLAYCNT protocol elements. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0080 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0081 | element of the request.Statementelement of the request. | None | None | None | None | RFQX-CVS32-0081 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0082 | 𝐶𝐻𝐴𝐶𝐻𝐴20-POLY1305𝑒𝑛𝑐𝑟𝑦𝑝𝑡(𝐾, 𝑁, 𝐴, 𝑃) → 𝐶, 𝑇𝐴𝐺 The server shall encrypt and authenticate the SDT response with: the 𝐴 argument set to the concatenated octet string comprised of the SDTPR, APAR, SIGENCRYPT, SIGLEN and ANTIREPLAYCNT protocol elements of the response and the octet string carried by the SIGMACBYTE protocol element of the corresponding request.Statement𝐶𝐻𝐴𝐶𝐻𝐴20-POLY1305𝑒𝑛𝑐𝑟𝑦𝑝𝑡(𝐾, 𝑁, 𝐴, 𝑃) → 𝐶, 𝑇𝐴𝐺 The server shall encrypt and authenticate the SDT response with: the 𝐴 argument set to the concatenated octet string comprised of the SDTPR, APAR, SIGENCRYPT, SIGLEN and ANTIREPLAYCNT protocol elements of the response and the octet string carried by the SIGMACBYTE protocol element of the corresponding request. | SSR-DAI-009 | Secure communication and freshness protection — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS32-0082 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0083 | The server shall populate the APAR protocol element in the response so that bits 4 and 5 are set to true.StatementThe server shall populate the APAR protocol element in the response so that bits 4 and 5 are set to true. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0083 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0084 | The server shall populate the SIGLEN protocol element in the request with 16 (0x0010).StatementThe server shall populate the SIGLEN protocol element in the request with 16 (0x0010). | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0084 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0085 | The server shall populate the SIGMACBYTE protocol element in the request with 𝑇𝐴𝐺.StatementThe server shall populate the SIGMACBYTE protocol element in the request with 𝑇𝐴𝐺. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0085 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0086 | 0x84 0x02 xx x X+1 SDT APAR 0x84 0x02 xx x X+1 0xC4 0x02 xxxxxxxxxx x Y+1 0xC4 0x02 xxxxxxxxxx x Y+1 SDTPR APAR RDBI SNOETDID 0 633132 KeyrequestHKDF(ikm, salt, info, 64) -> C TAG || CHACHA20-POLY1305enrypt(Keyrequest, N, A, P)-> CHACHA20-POLY1305decrypt(Keyrequest, N, A, C, TAG)-> S Keyresponse SecuredDataTransmissionKey (ikm) from 0x29 service Client s state variables PREQTAG=TAG_X Server s state variables C 0x22 || Application layer P A || || RDBI0x22 Application layer SNOETDID S C TAG P A CHACHA20-POLY1305enrypt(Keyresponse, N, A, P)-> RDBIPR0x62 0xF19743564320435 64331 SNOETDID Application layer || C TAG S C 6 A || CHACHA20-POLY1305decrypt(Keyresponse, N, A, C, TAG)-> || || RDBIPR SNOETDID 0x62 0xF19743564320435 64331 Application layer S P P ||X+1 N ||X+1 N Y+1 || N ||Y+1 Figure 6 – Example of client and server's behavior using SDT_AEAD_CHACHA20_POLY1305 The example in Figure 6 shows an AEAD_CHACHA20_POLY1305 authenticated and encrypted SDT transaction.Statement0x84 0x02 xx x X+1 SDT APAR 0x84 0x02 xx x X+1 0xC4 0x02 xxxxxxxxxx x Y+1 0xC4 0x02 xxxxxxxxxx x Y+1 SDTPR APAR RDBI SNOETDID 0 633132 KeyrequestHKDF(ikm, salt, info, 64) -> C TAG || CHACHA20-POLY1305enrypt(Keyrequest, N, A, P)-> CHACHA20-POLY1305decrypt(Keyrequest, N, A, C, TAG)-> S Keyresponse SecuredDataTransmissionKey (ikm) from 0x29 service Client s state variables PREQTAG=TAG_X Server s state variables C 0x22 || Application layer P A || || RDBI0x22 Application layer SNOETDID S C TAG P A CHACHA20-POLY1305enrypt(Keyresponse, N, A, P)-> RDBIPR0x62 0xF19743564320435 64331 SNOETDID Application layer || C TAG S C 6 A || CHACHA20-POLY1305decrypt(Keyresponse, N, A, C, TAG)-> || || RDBIPR SNOETDID 0x62 0xF19743564320435 64331 Application layer S P P ||X+1 N ||X+1 N Y+1 || N ||Y+1 Figure 6 – Example of client and server's behavior using SDT_AEAD_CHACHA20_POLY1305 The example in Figure 6 shows an AEAD_CHACHA20_POLY1305 authenticated and encrypted SDT transaction. | None | None | None | None | RFQX-CVS32-0086 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0087 | The encircled “||” denotes concatenation and the concatenation order is top to bottom in the figure.StatementThe encircled “||” denotes concatenation and the concatenation order is top to bottom in the figure. | None | None | None | None | RFQX-CVS32-0087 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0088 | one octet, and the rest should go in the SRVSPECPARAM protocol element.Statementone octet, and the rest should go in the SRVSPECPARAM protocol element. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0088 / 8h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | MISSING JIRA LINK |
| RFQX-CVS32-0089 | Encrypted data in the figure is denoted “x..x”, one “x” denotes one encrypted octet.StatementEncrypted data in the figure is denoted “x..x”, one “x” denotes one encrypted octet. | None | None | None | None | RFQX-CVS32-0089 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0090 | This section describes a CipherScheme based on the AEAD_CHACHA20_POLY1305 [9] algorithm.StatementThis section describes a CipherScheme based on the AEAD_CHACHA20_POLY1305 [9] algorithm. Note that in this CipherScheme we only use the authentication properties of AEAD_CHACHA20_POLY1305 i.e., no encryption/decryption. The requirements in this section are visualized with an example in Figure 8. | None | None | None | None | RFQX-CVS32-0090 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0091 | The L argument to the HKDF function shall be set to 64.StatementThe L argument to the HKDF function shall be set to 64. | SSR-COM-011 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-001 | component | RFQX-CVS32-0091 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0092 | Octets 0-31 of the okm shall be used as key by the client to authenticate, and the server to verify, the request.StatementOctets 0-31 of the okm shall be used as key by the client to authenticate, and the server to verify, the request. | SSR-DAI-009 | Secure communication and freshness protection — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS32-0092 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0093 | Octets 32-63 of the okm shall be used as key by the server to authenticate, and the client to verify, the response.StatementOctets 32-63 of the okm shall be used as key by the server to authenticate, and the client to verify, the response. | SSR-DAI-009 | Secure communication and freshness protection — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS32-0093 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0094 | The above requirements are visualized in Figure 7.StatementThe above requirements are visualized in Figure 7. | None | None | None | None | RFQX-CVS32-0094 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0095 | Figure 7 – Use of HKDF output key material (okm) with SDT_POLY1305 In subsequent sections (3.2.3.1 and 3.2.3.2), the following requirements shall be met: 𝐾: The 𝐾 argument shall be the key octet string of 32 octets.StatementFigure 7 – Use of HKDF output key material (okm) with SDT_POLY1305 In subsequent sections (3.2.3.1 and 3.2.3.2), the following requirements shall be met: 𝐾: The 𝐾 argument shall be the key octet string of 32 octets. | SSR-KEY-004 | Secure communication and freshness protection — Key and Certificate Handling | AD-007 | component | RFQX-CVS32-0095 / 29h | Not imported | No linked clarification | No P1 link | certificate/key handling | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0096 | 𝑁: The 𝑁 shall be an octet string of length 12, constructed as follows: - the first 10 octets shall be set to 6E6F6E73656E73652121, and - the remaining 2 octets shall be ANTIREPLAYCNT.Statement𝑁: The 𝑁 shall be an octet string of length 12, constructed as follows: - the first 10 octets shall be set to 6E6F6E73656E73652121, and - the remaining 2 octets shall be ANTIREPLAYCNT. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0096 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0097 | 𝑃: The 𝑃 (Plaintext) is a zero length octet string (null).Statement𝑃: The 𝑃 (Plaintext) is a zero length octet string (null). | None | None | None | None | RFQX-CVS32-0097 / 19h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0098 | 𝐶: The 𝐶 (Ciphertext) is a zero length octet string (null).Statement𝐶: The 𝐶 (Ciphertext) is a zero length octet string (null). | None | None | None | None | RFQX-CVS32-0098 / 19h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0099 | The client shall authenticate the SDT request with the 𝐴 argument set to the octet stringStatementThe client shall authenticate the SDT request with the 𝐴 argument set to the octet string | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0099 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0100 | The client shall populate the APAR protocol element in the request so that bits 0, 5 and 6 are set to true.StatementThe client shall populate the APAR protocol element in the request so that bits 0, 5 and 6 are set to true. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0100 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0101 | The client shall populate the SIGLEN protocol element in the request with 16 (0x0010).StatementThe client shall populate the SIGLEN protocol element in the request with 16 (0x0010). | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0101 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0102 | The client shall populate the SIGMACBYTE protocol element in the request with 𝑇𝐴𝐺.StatementThe client shall populate the SIGMACBYTE protocol element in the request with 𝑇𝐴𝐺. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0102 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0103 | The client shall store 𝑇𝐴𝐺 in its state variable PREQTAG.StatementThe client shall store 𝑇𝐴𝐺 in its state variable PREQTAG. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0103 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0104 | The client shall verify the SDT response with the 𝐴 argument set to the octet string comprised of all protocol elements of the SDT response, excluding the SIGMACBYTE protocol element, concatenated with the octet string stored in the state variable PREQTAG.StatementThe client shall verify the SDT response with the 𝐴 argument set to the octet string comprised of all protocol elements of the SDT response, excluding the SIGMACBYTE protocol element, concatenated with the octet string stored in the state variable PREQTAG. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0104 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0105 | element of the response.Statementelement of the response. | None | None | None | None | RFQX-CVS32-0105 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0106 | The server shall verify the SDT request with the 𝐴 argument set to the octet string comprised of all protocol elements of the SDT response, excluding the SIGMACBYTE protocol element.StatementThe server shall verify the SDT request with the 𝐴 argument set to the octet string comprised of all protocol elements of the SDT response, excluding the SIGMACBYTE protocol element. | SSR-COM-012 | OEM/Customer Review Interface — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0106 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0107 | element of the request.Statementelement of the request. | None | None | None | None | RFQX-CVS32-0107 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0108 | The server shall authenticate the SDT response with the 𝐴 argument set to the octet string comprised of all protocol elements of the SDT response, excluding the SIGMACBYTE protocol element, concatenated with the octet string carried by the SIGMACBYTE protocol element of the corresponding request.StatementThe server shall authenticate the SDT response with the 𝐴 argument set to the octet string comprised of all protocol elements of the SDT response, excluding the SIGMACBYTE protocol element, concatenated with the octet string carried by the SIGMACBYTE protocol element of the corresponding request. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0108 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0109 | The server shall populate the APAR protocol element in the response so that bit 5 is set to true.StatementThe server shall populate the APAR protocol element in the response so that bit 5 is set to true. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0109 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0110 | The server shall populate the SIGLEN protocol element in the response with 16 (0x0010).StatementThe server shall populate the SIGLEN protocol element in the response with 16 (0x0010). | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0110 / 16h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0111 | The client shall populate the SIGMACBYTE protocol element in the response with 𝑇𝐴𝐺.StatementThe client shall populate the SIGMACBYTE protocol element in the response with 𝑇𝐴𝐺. | SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | AD-005 | interface | RFQX-CVS32-0111 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0112 | 0x84 0x03 0x22 X+1 SDT APAR 0x84 0x03 0x22 X+1 0xC4 0x03 0xF1974356432043564331 0x62 Y+1 0xC4 0x03 0xF1974356432043564331 0x62 Y+1 SDTPR APAR 0 633132 KeyrequestHKDF(ikm, salt, info, 64) -> null TAG || CHACHA20-POLY1305authenticate(Keyrequest, N, A, null)-> CHACHA20-POLY1305verify(Keyrequest, N, A, null, TAG)-> ok Keyresponse SecuredDataTransmissionKey (ikm) from 0x29 service Client s state variables PREQTAG=TAG_X Server s state variables A || TAG A CHACHA20-POLY1305authenticate(Keyresponse, N, A, null)-> || null TAG 8 A CHACHA20-POLY1305verify(Keyrequest, N, A, null, TAG)-> ok || TAG A 8 ||X+1 N ||X+1 N ||Y+1 N ||Y+1 N Figure 8 – Example of client and server's behavior using SDT_POLY1305 The example in Figure 8 shows an AEAD_CHACHA20_POLY1305 authenticated SDT transaction.Statement0x84 0x03 0x22 X+1 SDT APAR 0x84 0x03 0x22 X+1 0xC4 0x03 0xF1974356432043564331 0x62 Y+1 0xC4 0x03 0xF1974356432043564331 0x62 Y+1 SDTPR APAR 0 633132 KeyrequestHKDF(ikm, salt, info, 64) -> null TAG || CHACHA20-POLY1305authenticate(Keyrequest, N, A, null)-> CHACHA20-POLY1305verify(Keyrequest, N, A, null, TAG)-> ok Keyresponse SecuredDataTransmissionKey (ikm) from 0x29 service Client s state variables PREQTAG=TAG_X Server s state variables A || TAG A CHACHA20-POLY1305authenticate(Keyresponse, N, A, null)-> || null TAG 8 A CHACHA20-POLY1305verify(Keyrequest, N, A, null, TAG)-> ok || TAG A 8 ||X+1 N ||X+1 N ||Y+1 N ||Y+1 N Figure 8 – Example of client and server's behavior using SDT_POLY1305 The example in Figure 8 shows an AEAD_CHACHA20_POLY1305 authenticated SDT transaction. | None | None | None | None | RFQX-CVS32-0112 / 56h | Not imported | Still Requires Customer Decision | No P1 link | certificate/key handling; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0113 | The encircled “||” denotes concatenation and the concatenation order is top to bottom relative the symbol.StatementThe encircled “||” denotes concatenation and the concatenation order is top to bottom relative the symbol. | None | None | None | None | RFQX-CVS32-0113 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0114 | This specification is mainly concerned with errors generated or detected by the client and server’s security sub-layer [1].StatementThis specification is mainly concerned with errors generated or detected by the client and server’s security sub-layer [1]. General UDS error handling is out of scope of this document. Figure 9 shows how the different “layers”1 interact conceptually. | None | None | None | None | RFQX-CVS32-0114 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boundary ownership; diagnostics exposure; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0115 | A UDS request/response, in the figure, means any request/response other than SDT (service 0x84).StatementA UDS request/response, in the figure, means any request/response other than SDT (service 0x84). | None | None | None | None | RFQX-CVS32-0115 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0116 | The SDT positive response may of course contain an encapsulated negative UDS response.StatementThe SDT positive response may of course contain an encapsulated negative UDS response. | None | None | None | None | RFQX-CVS32-0116 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0117 | Figure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer.StatementFigure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer. | None | None | None | None | RFQX-CVS32-0117 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0118 | Note that the markings in the figure, (“S1” through “S3”), and the values for the state variables are correlated with Figure 3.StatementNote that the markings in the figure, (“S1” through “S3”), and the values for the state variables are correlated with Figure 3. | None | None | None | None | RFQX-CVS32-0118 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0119 | Other than the NRCs 0x3A, 0x13 and 0x21, specified by ISO14229-1:2020 [1], the server shall support the NRC 0x34 “authenticationRequired”.StatementOther than the NRCs 0x3A, 0x13 and 0x21, specified by ISO14229-1:2020 [1], the server shall support the NRC 0x34 “authenticationRequired”. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0119 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0120 | At reception of an SDT request, if the security sub-layer is busy, the server shall respond withStatementAt reception of an SDT request, if the security sub-layer is busy, the server shall respond with | SSR-COM-013 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-007 | component | RFQX-CVS32-0120 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0121 | At reception of an SDT request, if the requesting client is unauthenticated, the server shall respond with an SDT negative response using the NRC 0x34.StatementAt reception of an SDT request, if the requesting client is unauthenticated, the server shall respond with an SDT negative response using the NRC 0x34. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0121 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0122 | At reception of an SDT request, if the request is too short or otherwise malformed, the server shall respond with an SDT negative response using the NRC 0x13.StatementAt reception of an SDT request, if the request is too short or otherwise malformed, the server shall respond with an SDT negative response using the NRC 0x13. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0122 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0123 | At reception of an SDT request, if ANTIREPLAYCNT ≤ PREQARC, the server shall respond with an SDT negative response using the NRC 0x3A.StatementAt reception of an SDT request, if ANTIREPLAYCNT ≤ PREQARC, the server shall respond with an SDT negative response using the NRC 0x3A. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0123 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0124 | At reception of an SDT request, if PRESARC is exhausted, the server shall respond with an SDT negative response using the NRC 0x3A.StatementAt reception of an SDT request, if PRESARC is exhausted, the server shall respond with an SDT negative response using the NRC 0x3A. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0124 / 29h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0125 | At reception of an SDT request, if SIGENCRYPT is not supported, the server shall respond with an SDT negative response using the NRC 0x3A.StatementAt reception of an SDT request, if SIGENCRYPT is not supported, the server shall respond with an SDT negative response using the NRC 0x3A. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0125 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0126 | At reception of an SDT request, if APAR is in conflict with SIGENCRYPT, the server shall respond with an SDT negative response using the NRC 0x3A.StatementAt reception of an SDT request, if APAR is in conflict with SIGENCRYPT, the server shall respond with an SDT negative response using the NRC 0x3A. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0126 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0127 | For example, APAR dictates encryption, but SIGENCRYPT does not offer encryption.StatementFor example, APAR dictates encryption, but SIGENCRYPT does not offer encryption. | None | None | None | None | RFQX-CVS32-0127 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0128 | At reception of an SDT request, if SIGLEN is in conflict with SIGENCRYPT, the server shall respond with an SDT negative response using the NRC 0x3A.StatementAt reception of an SDT request, if SIGLEN is in conflict with SIGENCRYPT, the server shall respond with an SDT negative response using the NRC 0x3A. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0128 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0129 | For example, the CipherScheme indicated by SIGENCRYPT produces a TAG of a length different from that indicated by SIGLEN.StatementFor example, the CipherScheme indicated by SIGENCRYPT produces a TAG of a length different from that indicated by SIGLEN. | None | None | None | None | RFQX-CVS32-0129 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0130 | At reception of an SDT request, if the server fails to verify/decrypt the request, the server shall respond with an SDT negative response using the NRC 0x3A.StatementAt reception of an SDT request, if the server fails to verify/decrypt the request, the server shall respond with an SDT negative response using the NRC 0x3A. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0130 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0131 | The server shall update its state, (set PREQARC to the value received in the ANTIREPLAYCNT protocol element in the SDT request), if and only if it successfully verifies/decrypts the SDT request.StatementThe server shall update its state, (set PREQARC to the value received in the ANTIREPLAYCNT protocol element in the SDT request), if and only if it successfully verifies/decrypts the SDT request. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0131 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0132 | This means that if the server generates an SDT negative response, the server’s state remains unchanged, i.e.StatementThis means that if the server generates an SDT negative response, the server’s state remains unchanged, i.e. | None | None | None | None | RFQX-CVS32-0132 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0133 | The server shall update its state, (increment PRESARC by one (1)), if and only if it can successfully authenticate/encrypt the SDT response (“S3”).StatementThe server shall update its state, (increment PRESARC by one (1)), if and only if it can successfully authenticate/encrypt the SDT response (“S3”). | SSR-DAI-009 | Secure communication and freshness protection — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS32-0133 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0134 | This means that if the server fails to generate an SDT response, the server’s state remains unchanged, i.e.StatementThis means that if the server fails to generate an SDT response, the server’s state remains unchanged, i.e. | None | None | None | None | RFQX-CVS32-0134 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0135 | As mentioned above in this specification, the UDS standard allows for a request to result in multiple responses, e.g.StatementAs mentioned above in this specification, the UDS standard allows for a request to result in multiple responses, e.g. | None | None | None | None | RFQX-CVS32-0135 / 24h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0136 | Figure 11 shows an example where the client sends a RDBI and the server responds with two instances of RCRRP before delivering the final response.StatementFigure 11 shows an example where the client sends a RDBI and the server responds with two instances of RCRRP before delivering the final response. | None | None | None | None | RFQX-CVS32-0136 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0137 | Although this behavior does not alter the requirements put on the server, it is worth to point out that since the server will reuse the TAG received in the request for several responses, the server has to “remember” the TAG from the request.StatementAlthough this behavior does not alter the requirements put on the server, it is worth to point out that since the server will reuse the TAG received in the request for several responses, the server has to “remember” the TAG from the request. | None | None | None | None | RFQX-CVS32-0137 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0138 | Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer.StatementFigure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer. | None | None | None | None | RFQX-CVS32-0138 / 24h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0139 | The client shall update its state, (increment PREQARC by one (1), if and only if it can successfully authenticate/encrypt the SDT request (“C2”).StatementThe client shall update its state, (increment PREQARC by one (1), if and only if it can successfully authenticate/encrypt the SDT request (“C2”). | SSR-DAI-009 | Secure communication and freshness protection — Data Authenticity and Integrity Verification | AD-007 | component | RFQX-CVS32-0139 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0140 | At reception of an SDT response, if the client is unauthenticated, the client shall discard theStatementAt reception of an SDT response, if the client is unauthenticated, the client shall discard the | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0140 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0141 | At reception of an SDT response, if the request is too short or otherwise malformed, the client shall discard the response.StatementAt reception of an SDT response, if the request is too short or otherwise malformed, the client shall discard the response. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0141 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0142 | At reception of an SDT response, if ANTIREPLAYCNT ≤ PRESARC, the client shall discard theStatementAt reception of an SDT response, if ANTIREPLAYCNT ≤ PRESARC, the client shall discard the | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0142 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0143 | At reception of an SDT response, if SIGENCRYPT is not supported, the client shall discard theStatementAt reception of an SDT response, if SIGENCRYPT is not supported, the client shall discard the | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0143 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0144 | At reception of an SDT response, if APAR is in conflict with SIGENCRYPT, the client shall discard the response.StatementAt reception of an SDT response, if APAR is in conflict with SIGENCRYPT, the client shall discard the response. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0144 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0145 | At reception of an SDT response, if SIGLEN is in conflict with SIGENCRYPT, the client shall discard the response.StatementAt reception of an SDT response, if SIGLEN is in conflict with SIGENCRYPT, the client shall discard the response. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0145 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0146 | At reception of an SDT response, if the client fails to verify/decrypt the response, the client shall discard the response.StatementAt reception of an SDT response, if the client fails to verify/decrypt the response, the client shall discard the response. | SSR-COM-010 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-008 | component | RFQX-CVS32-0146 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | TOO BROAD SYSTEM REQUIREMENT |
| RFQX-CVS32-0147 | The client shall update its state, (set PRESARC to the value received in the ANTIREPLAYCNT protocol element in the SDT response), if and only if it successfully verifies/decrypts the SDT response (“C3”).StatementThe client shall update its state, (set PRESARC to the value received in the ANTIREPLAYCNT protocol element in the SDT response), if and only if it successfully verifies/decrypts the SDT response (“C3”). | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0147 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust; backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0148 | This means that if the client fails to verify/decrypt the SDT response, the client’s state remains unchanged, i.e.StatementThis means that if the client fails to verify/decrypt the SDT response, the client’s state remains unchanged, i.e. | None | None | None | None | RFQX-CVS32-0148 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0149 | Messages can get lost going from client to server, or vice versa.StatementMessages can get lost going from client to server, or vice versa. | None | None | None | None | RFQX-CVS32-0149 / 56h | Not imported | Still Requires Customer Decision | No P1 link | backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0150 | Note that busyRepeatRequest, NRC 0x21 (BRR), can be sent in an SDT negative response, or, encapsulated in an SDT positive response.StatementNote that busyRepeatRequest, NRC 0x21 (BRR), can be sent in an SDT negative response, or, encapsulated in an SDT positive response. | None | None | None | None | RFQX-CVS32-0150 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0151 | If the client determines an SDT request to be lost in transit, or, if it receives an SDT negative response with NRC BRR (0x21), the client shall • repeat the request byte for byte and leave state variables unchanged.StatementIf the client determines an SDT request to be lost in transit, or, if it receives an SDT negative response with NRC BRR (0x21), the client shall • repeat the request byte for byte and leave state variables unchanged. | SSR-COM-009 | Secure communication and freshness protection — Secure Communication and Boundary Control | AD-002 | component | RFQX-CVS32-0151 / 24h | Not imported | No linked clarification | No P1 link | backend connectivity | No closure evidence required | SECURITY REVIEW OPEN |
| RFQX-CVS32-0152 | .Statement. | None | None | None | None | RFQX-CVS32-0152 / 16h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0153 | A negative UDS response BRR encapsulated in a positive SDT response can of course never result in the resending of an old SDT request.StatementA negative UDS response BRR encapsulated in a positive SDT response can of course never result in the resending of an old SDT request. | None | None | None | None | RFQX-CVS32-0153 / 8h | Not imported | Still Requires Customer Decision | No P1 link | diagnostics exposure | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0154 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0154 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0155 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0155 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0156 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0156 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0157 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0157 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0158 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0158 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0159 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0159 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0160 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0160 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0161 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0161 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0162 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0162 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0163 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0163 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0164 | UpdatedStatementUpdated | None | None | None | None | RFQX-CVS32-0164 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0165 | SDT_AES_SIV_CMAC_256 and SDT_CMAC_128 was deprecated and replaced with SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305.StatementSDT_AES_SIV_CMAC_256 and SDT_CMAC_128 was deprecated and replaced with SDT_AEAD_CHACHA20_POLY1305 and SDT_POLY1305. | None | None | None | None | RFQX-CVS32-0165 / 8h | Not imported | Still Requires Customer Decision | No P1 link | None | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0166 | (new cipher-schemes) Updated Table 2 (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated Table 2 (new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0166 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0167 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0167 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0168 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0168 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0169 | (new cipher-schemes) Updated Figure 4 (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated Figure 4 (new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0169 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0170 | (new cipher-schemes) Updated 3.2.2 heading (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated 3.2.2 heading (new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0170 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0171 | (new cipher-schemes) Updated Figure 5 annotation (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated Figure 5 annotation (new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0171 / 56h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0172 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0172 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0173 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0173 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0174 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0174 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0175 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0175 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0176 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0176 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0177 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0177 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0178 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0178 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0179 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0179 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0180 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0180 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0181 | (new cipher-schemes) Updated Figure 6 (new cipher-schemes)Statement(new cipher-schemes) Updated Figure 6 (new cipher-schemes) | None | None | None | None | RFQX-CVS32-0181 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0182 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0182 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0183 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0183 / 8h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0184 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0184 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0185 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0185 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0186 | (new cipher-schemes) AddedStatement(new cipher-schemes) Added | None | None | None | None | RFQX-CVS32-0186 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0187 | (new cipher-schemes) Added Figure 7 (new cipher-schemes) UpdatedStatement(new cipher-schemes) Added Figure 7 (new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0187 / 8h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0188 | (new cipher-schemes) AddedStatement(new cipher-schemes) Added | None | None | None | None | RFQX-CVS32-0188 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0189 | (new cipher-schemes) AddedStatement(new cipher-schemes) Added | None | None | None | None | RFQX-CVS32-0189 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0190 | (new cipher-schemes) AddedStatement(new cipher-schemes) Added | None | None | None | None | RFQX-CVS32-0190 / 19h | Not imported | No linked clarification | No P1 link | None | No closure evidence required | COMPLETE |
| RFQX-CVS32-0191 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0191 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0192 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0192 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0193 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0193 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0194 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0194 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0195 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0195 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0196 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0196 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0197 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0197 / 29h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0198 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0198 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0199 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0199 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0200 | (new cipher-schemes) Updated Figure 8 (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated Figure 8 (new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0200 / 24h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0201 | (new cipher-schemes) UpdatedStatement(new cipher-schemes) Updated | None | None | None | None | RFQX-CVS32-0201 / 24h | Not imported | No linked clarification | No P1 link | boot/update trust | No closure evidence required | COMPLETE |
| RFQX-CVS32-0202 | (new cipher-schemes) Updated 4 References (new cipher-schemes) Updated Annex A (new cipher-schemes) Updated test vectors to be correct after change from SHA-256 to SHA-512 Exhausted PRESARC server behavior.Statement(new cipher-schemes) Updated 4 References (new cipher-schemes) Updated Annex A (new cipher-schemes) Updated test vectors to be correct after change from SHA-256 to SHA-512 Exhausted PRESARC server behavior. | None | None | None | None | RFQX-CVS32-0202 / 29h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust; backend connectivity | MISSING CLARIFICATION EVIDENCE | COMPLETE |
| RFQX-CVS32-0203 | and updated Figure 9.) 2025-08 1 This standard has been revised and is valid for continued use.Statementand updated Figure 9.) 2025-08 1 This standard has been revised and is valid for continued use. | None | None | None | None | RFQX-CVS32-0203 / 29h | Not imported | Still Requires Customer Decision | No P1 link | boot/update trust | MISSING CLARIFICATION EVIDENCE | COMPLETE |